Accounts Payable | Payment Scheduling
Queued by due date, with the cash position before you commit.
Approved bills queue by due date with holds gating the run, discount deadlines surfaced before they lapse, and the projected cash position for the next two weeks shown before anything is released. The approved run leaves as an ACH file for your bank or a push to your ERP.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Run scheduling | Approved bills, due dates, vendor priority | A run plan with line-level priority |
| Discount deadlines | Terms offering early payment | Offers about to lapse, with the annualised yield beside each |
| Hold engine | Match variance, missing W-9, unverified bank details | Per-bill hold with the reason on the line |
| Cash projection | Bank position, scheduled receipts and outflows | A two-week rolling position, before the run is committed |
| Batch output | The released run | A NACHA ACH file for your bank, or approved bills pushed to your ERP |
| Maker-checker release | Run plan and a dual-control approver | Released under dual control with the audit trail retained |
-
Run scheduling
- Input
- Approved bills, due dates, vendor priority
- Output
- A run plan with line-level priority
-
Discount deadlines
- Input
- Terms offering early payment
- Output
- Offers about to lapse, with the annualised yield beside each
-
Hold engine
- Input
- Match variance, missing W-9, unverified bank details
- Output
- Per-bill hold with the reason on the line
-
Cash projection
- Input
- Bank position, scheduled receipts and outflows
- Output
- A two-week rolling position, before the run is committed
-
Batch output
- Input
- The released run
- Output
- A NACHA ACH file for your bank, or approved bills pushed to your ERP
-
Maker-checker release
- Input
- Run plan and a dual-control approver
- Output
- Released under dual control with the audit trail retained
Compliance + integrations
Released under dual control, recorded for the auditor.
Maker-checker on every run with an append-only trail on each decision. Bills missing a W-9 or carrying an unverified bank-detail change are held before the run rather than found after it, which is when both become expensive.
Regulations we work within
-
Dual control
Maker-checker enforced on every run; no single user can release a payment instruction.
-
Audit trail
Append-only record of every release decision, including the override and who made it.
-
Backup withholding
Payees with a missing or mismatched taxpayer number are flagged before the run, since the liability for not withholding sits with the payer.
Connects to
- 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. It can be released with an override, which the audit trail captures, or held until procurement resolves it.
How does the money actually leave?
Through your bank. The approved run exports as a NACHA ACH file, or the approved bills push to your ERP and pay from there. We take no cut of the payment and hold no float, so you keep whatever rate your bank already gives you rather than paying a platform per transaction.
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.
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 and the cash position, all on one screen.