Accounts Payable | Vendor Payment Batches
Pay 200 vendors in one click. The right rail, the right release, the right reconciliation.
The right rail selected per amount and urgency, with auto-fallback if one is down. Direct bank feeds where available. Maker-checker release. Multi-currency where you settle across the region, and status posts back payment by payment.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Rail selection | Bill amount + urgency + bank cut-off | The right rail per bill |
| Auto-fallback | Rail status from bank API | Failover with retry trail |
| Maker-checker | Maker submission + checker action | Released batch under maker-checker |
| Status post-back | Bank payment confirmation | Per-bill paid / pending / failed status |
| Failure retry | Failed payment + retry policy | Auto-retry on fallback rail |
-
Rail selection
- Input
- Bill amount + urgency + bank cut-off
- Output
- The right rail per bill
-
Auto-fallback
- Input
- Rail status from bank API
- Output
- Failover with retry trail
-
Maker-checker
- Input
- Maker submission + checker action
- Output
- Released batch under maker-checker
-
Status post-back
- Input
- Bank payment confirmation
- Output
- Per-bill paid / pending / failed status
-
Failure retry
- Input
- Failed payment + retry policy
- Output
- Auto-retry on fallback rail
Compliance + integrations
Released under dual control, recorded for the auditor.
Maker-checker dual control on every batch, with the audit trail on every decision. Direct bank feeds where your bank offers one, and file upload where it does not, for vendors who still need it.
Regulations we work within
-
Dual control
Maker-checker enforced on every batch; no single user can release a payment.
-
Audit trail
Append-only record on every release decision, including the override and who made it.
-
Electronic Transactions Act
An electronically authorised release carries the same legal weight as a signed instruction.
Connects to
- Bank feeds Direct feed where available
- File upload Payment file to your bank
Vendor Payment Batches FAQ
What buyers ask.
Which banks are integrated for direct payment?
Direct feeds where your bank offers one, and payment-file upload otherwise, so no bank is a blocker. Coverage adds as bank APIs become available.
Can we use the same software for ERP plus payments?
Yes. The bill posts in OneFinOps, the payment fires from OneFinOps, the books update on confirmation. If you keep books in Xero or QuickBooks, the payment posts back as a receipt to your ERP.
Is dual authorisation required for release?
Yes. Maker-checker dual control is enforced on every batch, with the checker authenticating on release. The audit trail captures maker and checker. Single-user release is not supported.
Do you handle multi-currency payment runs?
Yes. A batch can pay vendors in several currencies, each settled in its own currency with the rate captured at payment rather than reconstructed later.
Run your next batch, free.
Connect one bank, run a batch of up to 100 vendors. The release follows maker-checker; the books update on payment confirmation.