Operational Integrity for Multi-Location Cash Ledgers

Challenge

Cash moves constantly between branches through couriers and transfers. Every entry needed independent verification, branch systems had to feed a central ledger over connections that weren't always reliable, and the approval process had to prevent collusion between staff at the same location.

Approach

• Encode separation of duties, not just roles. Approvers must belong to the entry's location, a second approval from the same location is blocked unless explicitly permitted, and entries are approved only once a configurable threshold is met.
• Sync from the edge, safely. A connector at each site batches new entries, retries after failures and marks entries as sent only once the central ledger has them.
• Resume, don't replay. The central ledger consumes an event stream and resumes from the last ingested transaction after any interruption.
• Make the state visible. Dashboards update live as entries move through verification.

Implementation

• Modules for transfers, couriers, locations, check-offs with reconciliation, petty cash, encashments, overages and balances.
• A verification queue for unverified entries with send-for-approval and approve actions, plus approver notifications.
• An activity audit log covering every operation.
• Reporting with CSV export and search.
• A branch connector service and scheduled maintenance tasks.

Outcome

Cash movements across locations are recorded in one place, approvals are segregated by location and every action is auditable. Branch data keeps flowing through connectivity problems instead of being lost or double-sent.

Technical perspective

The interesting constraints weren't technical scale; they were organizational. Approval rules had to model who is allowed to check whom, and multi-site sync had to tolerate days offline without losing or duplicating a single entry.