Digital approval chain for a multi-entity group

A payment moved through the business as a physical object. It was printed, walked to a desk, signed, scanned, and filed — and if a signer was travelling, it waited. The audit record was a folder of scans whose filenames were the only index.

Across entities in two jurisdictions the same process ran with different forms and different signing thresholds, so nobody could answer a simple question — where is this payment, and who is it waiting on — without asking three people.

A five-step approval chain with an explicit signing interface. Each step records who approved, when, and against which supporting evidence — the payment application, the invoice, the receipt — so the audit trail is produced as a by-product of doing the work rather than assembled afterwards.

Thresholds and routing are configured per entity, which lets the two jurisdictions keep their own rules while running on one system. Approved payments generate the bank instruction directly, so the figures on the instruction come from the record that was approved rather than being re-keyed from it.

Approvals stopped depending on physical presence, and the question of what is waiting on whom became a screen instead of a phone call. Every completed payment carries its own chain of custody — who signed, when, against what.

Re-keying between the approved application and the bank instruction was removed entirely, which closed the most common route for a transcription error to reach a bank.