Accounts Payable | Vendor Payment Batches
Approve the batch here. Pay it from your own bank.
Approvals, dual control and the audit trail run here, where the bill and the vendor already live. The money moves through your bank, as a NACHA ACH file or a push to your ERP. We take no cut of the payment, hold no float, and you onboard no new banking relationship to go live.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Rail selection | Bill amount + urgency + bank cut-off | An ACH file your bank accepts |
| 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 feed 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
- An ACH file your bank accepts
-
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 feed 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 an append-only trail on each decision. The approved batch leaves as a NACHA file for your bank or as a push to your ERP, and a positive pay file goes to the bank alongside it where you use one.
Regulations we work within
-
Dual control
Maker-checker enforced on every batch; no single user can release a payment instruction.
-
Audit trail
Append-only record on every release decision, including the override and who made it.
-
Positive pay
A file of the payments you authorised, so the bank can reject anything you did not.
Connects to
- NACHA file ACH batch export for your bank
- Positive pay Authorised-payment file to the bank
- ERP push Approved bills into QuickBooks or Xero
- Bank feed Mark-as-paid on confirmation
Vendor Payment Batches FAQ
What buyers ask.
Which banks are integrated for direct payment?
Any bank that accepts a NACHA file, which is effectively all of them, so no bank is a blocker and none needs to onboard you. Where you would rather not handle a file at all, approved bills push to your ERP and pay from there.
Can we use the same software for ERP plus payments?
Yes. The bill is captured and approved in OneFinOps and pushes to QuickBooks Online or Xero, or leaves as a payment file. Either way the bank feed closes the bill out as paid, so nothing is marked off by hand.
Is dual authorisation required for release?
Yes. Maker-checker dual control is enforced on every batch, with the checker authenticating on release and the trail capturing both. Single-user release is not supported, which matters more here than usual because the artefact leaving the system is an instruction to move money.
What does this cost per payment?
Nothing from us. We do not charge per ACH or per check, take no cut of the payment and hold no float, so you keep whatever rate your bank already gives you. Platforms that execute payments price per transaction, and at a few hundred payments a month that becomes a meaningful annual number worth comparing against your bank's.
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.