OHM · Workflows · Payment processing
Payment processing
The run is built from approved entries only — and checked again before it leaves.
The last checkpoint before money is irreversible. Everything in the run passed entry, and the things that can change between approval and payment are tested one more time.
The same step, two ways
How it runs today
- The run is assembled from a list, under time pressure, on payment day.
- A beneficiary account changed since approval and nobody re-checked it.
- A discount that was available expired while the file was being prepared.
- An MSME vendor crosses day 45 and the interest is discovered later.
With the team on it
- Only entries that passed every check are eligible for the run.
- Bank details are re-verified against what was approved, not what is current in the master.
- Discounts still open are captured; ones being let go are recorded as a decision.
- Statutory clocks are respected as scheduling constraints, not reported as breaches.
Who runs, and what they enforce
All of them, on the same payment run, at the same time. Not a queue.
| Agent | What it enforces |
|---|---|
| Payments Agent | Run built from approved entries only |
| Bank Agent | Beneficiary account unchanged |
| Duplicate Agent | No second payment against the same invoice |
| DOA Agent | Released by two signatories |
| Discount Agent | Early-payment discount captured |
| MSME Agent | Paid inside the statutory window |
Agents without a link yet are part of the team but do not have a page written up.
What lands in your ERP
A payment file containing only entries that cleared every check, released under the delegation, with each payment traceable to the invoice and the checks behind it.
Released
The stamp on a payment run that cleared this step. It means every check ran and passed — not that a sample did, and not that it will be reviewed later.
See this step run on your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→