Skip to content

Solution

Approval Workflow System

Maker-checker on everything that moves money

Loans, journals, expenses, transfer batches, field batches, account openings and large deposits all wait for approval by an officer other than the one who raised them, on the web and in the mobile app.

Nothing that moves money in Zenus Banking Pro posts on one person's say-so. Every approval queue enforces that the approver is not the maker, and every approve or reject action is enforced again in the API, so the rule cannot be bypassed from the mobile app.

Supervisors see pending items on the dashboard the moment they log in and can approve from the road on Android.

What it does

  • Maker-checker enforced on loans, journals, expenses, batches and account openings
  • Deposit approval requests for amounts above a teller's limit
  • Pending-approval widgets on the dashboard per queue
  • Approve or reject from the Android app with the same rule
  • Rejections carry a reason back to the maker
  • Every decision recorded in the audit log with the officer's name

How it works

  1. 1

    An officer raises the item and submits it.

  2. 2

    A different officer sees it in the queue and approves or rejects.

  3. 3

    On approval, Zenus posts the balanced entry.

  4. 4

    The audit log records both officers and the timestamps.

Related

Works together with

See Approval Workflow System on a live demo

A live demonstration on a sandbox with sample data, then a free two-day data assessment for a fixed go-live date.

Prefer WhatsApp? Chat with us