Record off-app payments with receipts. Choose how they get verified. Let the system suggest the fewest payments needed to clear every debt.
Minimum settlements
3 of 12 clearedFive built-in verification modes. Switch any time from the workspace settings — no code changes, no migrations.
Admin or Receiver
First of admin or receiver to approve wins. Balanced flexibility — the default.
Receipt thresholds
Require proof of payment above a configurable amount. Above the threshold without an attachment, the submission is blocked.
Auto-approve threshold
Set a small-amount threshold below which settlements auto-approve, skipping the workflow entirely. Saves time for the small stuff.
Min cash-flow engine
Computes the minimum number of payments needed to clear all debts. Replace 20 settlements with 4.
Reversal workflow
Admins can reverse any approved settlement with a required reason. The ledger creates an exact opposite entry — no manual cleanup.
Comments & attachments
Every settlement supports threaded comments and multiple file attachments. The full story stays attached to the record.
Duplicate detection
Submitting an identical settlement within minutes triggers a warning — and a hard block if it's clearly a duplicate.
Immutable ledger
Every approval and reversal writes mirrored DEBIT/CREDIT entries. Balances are derived, never mutated directly.
Full audit trail
submitted → approved → reversed: every state change logs to the audit log with actor, timestamp, and reason.
PK payment methods
EasyPaisa, JazzCash, bank transfer, cash — all first-class options. Localised for how Pakistani teams actually pay.
From draft to reversal, every state change writes an audit log entry with actor, timestamp, and reason.
DRAFT
Saved but not submitted
PENDING
Awaiting verification
PENDING_RECEIVER_APPROVAL
Receiver needs to approve
PENDING_ADMIN_APPROVAL
Admin needs to approve
APPROVED
Ledger updated · balance moved
REJECTED
Declined with reason
CANCELLED
Submitter pulled it back
REVERSED
Approved then undone · audited