Accounts Payable | Payment Scheduling
Payments queued by due date. Discounts caught. With cash visibility.
Approved bills queue by due date, with early-payment discount deadlines surfaced before they lapse. Holds gate the run where a vendor is struck off, a match is unresolved, or a payment to a non-resident attracts withholding. Multi-currency runs settle in each vendor's own currency. Cash position projected against the next two weeks.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Run scheduling | Approved bill set + due dates + vendor priority | Run plan with line-level priority |
| Discount deadline prioritisation | Agreed terms + invoice date | Bills where the discount window is about to close surfaced first |
| Hold engine | Register status, match status, withholding position | Per-bill hold with reason |
| Cash projection | Bank balance + scheduled receivables + outflows | 2-week rolling cash position |
| Rail decisioning | Amount + urgency + currency + bank rail status | The right rail per bill, with auto-fallback |
| Maker-checker release | Run plan + dual-control approver | Released run with audit trail |
-
Run scheduling
- Input
- Approved bill set + due dates + vendor priority
- Output
- Run plan with line-level priority
-
Discount deadline prioritisation
- Input
- Agreed terms + invoice date
- Output
- Bills where the discount window is about to close surfaced first
-
Hold engine
- Input
- Register status, match status, withholding position
- Output
- Per-bill hold with reason
-
Cash projection
- Input
- Bank balance + scheduled receivables + outflows
- Output
- 2-week rolling cash position
-
Rail decisioning
- Input
- Amount + urgency + currency + bank rail status
- Output
- The right rail per bill, with auto-fallback
-
Maker-checker release
- Input
- Run plan + dual-control approver
- Output
- Released run with audit trail
Compliance + integrations
Dual control on release, withholding caught before it.
No single user can release a payment run. Where a bill is a payment to a non-resident, the withholding position is surfaced at scheduling rather than discovered after the money has gone, which is the point at which it becomes expensive to fix.
Regulations we work within
-
Withholding tax, Section 45
Payments to non-residents flagged at scheduling, with the position shown before release.
Connects to
- Bank feeds Direct feed where available
- Payment file upload Batch file to your bank
- Xero Payment posted back to the books
- QuickBooks Payment posted back to the books
Payment Scheduling FAQ
What buyers ask.
Can a payment be held when the three-way match is not yet clean?
Yes. Bills with an unresolved quantity or price variance surface as held, with the variance visible on the line. The CFO can release with an override, which the audit trail captures, or hold until procurement resolves it.
What if a rail is down on the bank side?
Rail decisioning has auto-fallback. If the chosen rail is unavailable the system falls through to another one where the amount allows, or queues for the next window where it does not. The status post-back captures every retry.
Can we run partial payments?
Yes. Partial payments are supported per bill, with the unpaid balance staying on the bill for the next run. Vendor statement reconciliation handles the partial position.
How does the cash projection work?
It pulls bank balance from connected banks, projected receivables from AR ageing, and scheduled outflows from the run plan. The 2-week view is a rolling projection. CFO can adjust assumptions inline.
More in Accounts Payable
Related features
See your next payment run, with the holds, before you release.
Connect one bank and one entity, free. The next run shows held bills, the discounts about to lapse, the withholding flags and the cash position, all on one screen.