Approvals and controls
Approval rules you draw yourself.
Your approval policy lives in the system, not in a circular. Draw a flow for each event, say who may decide and how many must, and Fused refuses the person who raised an item and records every write on a hash-chained trail.
The person who raised the loan is never one of the two.
What it does
Flows drawn on a canvas
A flow per event, with conditions on the record's own values, such as an amount or a branch, ending at an outcome or at an approval gate.
Who, how many, by when
A gate names a permission and an office rule, a quorum such as two of three managers at this branch, and a deadline in the branch's working days, with reminders.
Four eyes, enforced
The person who raised an item cannot approve it. Any rejection settles the gate; approvals settle it when the quorum is met.
One inbox per person
Everything waiting on someone, read from its sources rather than copied into a second list.
Office-scoped roles
A role reads the whole institution, its holder's own branch, or that branch and those below it, so one role covers every branch.
A trail that proves itself
Every write records a SHA-256 hash-chained event in the same transaction. Each chain's tip is copied every minute to a separate database under a separate credential.
What it refuses
A control is only a control if the system enforces it.
- Fused refuses an approval from the person who raised the item.
- Fused refuses a decision from someone the gate's permission and office rule do not match.
- Fused refuses a sign-in without an authenticator code.
- Fused refuses a publish that removes a gate records are waiting at, until someone confirms it.
The rules underneath
The detail your finance and IT teams will ask about.
- Gated events
- Loan approval and disbursement, manual journals and reversals, receipts and vouchers, till closes, collection batches, client activation, savings withdrawals and reactivation, collateral release, period close and holidays applied to signed schedules.
- Quorum
- A number of distinct people, or everyone the gate's rule matches. Any rejection settles the gate.
- Office rule
- Own office, own office and below, a named office, or any, anchored on the record's office.
- Deadline
- Advisory, counted in the branch's working days. Reminders are sent; nothing is decided by the clock.
- Audit chain
- Each event stores the hash of the event before it and its own SHA-256. Anchors live in a separate database the application can only read and append to.
- Sign-in
- A password, then an authenticator app (TOTP), which is mandatory. Codes are never sent by SMS.
Works with
- AccountingA general ledger in which every entry balances or is refused, and no posted entry can be edited.
- Clients and KYCNIC-aware client records, groups and centres, KYC documents with verification, custom fields and CSV import.
- ReportingFour built-in reports, a designer for your own queries over sandboxed views, and scheduled CSV, XLSX or PDF.
Approvals and controls: questions
Could someone approve their own loan?
No. The person who raised an item cannot decide it, and a gate can require several distinct approvers, such as two of three managers at the branch.
What if no flow is drawn for an event?
The write goes ahead as the person's permissions allow. A flow adds a gate on top of the permission check; it never replaces it.
Can the audit trail be rewritten?
Not without being caught. Each event's hash covers the one before it, and each chain's tip is copied every minute to a separate database under a separate credential.
Can a branch manager see other branches?
Only if their role's office scope says so: the whole institution, their own branch, or their branch and those below it.
See it on your own products and numbers.
A walkthrough with the team that builds Fused: your loan products, your branches, your month-end.