Accounts Payable | Vendor Payment Batches

Pay 200 vendors in one click. The right rail, the right release, the right reconciliation.

NEFT, RTGS, IMPS or UPI selected per amount and urgency. Auto-fallback if a rail is down. Connected Banking with ICICI, HDFC, Axis, Yes, Kotak and SBI. Maker-checker release with OTP or DSC. Status posts back UTR by UTR.

Start free trial Book a demo

How it works

From run plan to UTR-by-UTR confirmation.

Step 01

Rail decisioning

RTGS for amounts at or above ₹2L where speed matters. UPI under ₹5L for retail vendors. NEFT as the default. IMPS as fallback.

Step 02

Maker-checker release

The maker prepares the batch. The checker reviews and releases with OTP or DSC. RBI-aligned dual control on every batch.

Step 03

Status post-back per UTR

Each UTR returns success, pending or failure. Failed payments auto-retry on the fallback rail or queue for review.

Step 04

Books update on confirmation

On UTR confirmation, the bill marks paid in the books. The payment posts to the vendor ledger and bank account. Rule 11(g) audit trail captures the release decision.

What the system does

Capability, input, output.

Capability	Input	Output
Rail selection	Bill amount + urgency + bank cut-off	NEFT / RTGS / IMPS / UPI per bill
Auto-fallback	Rail status from bank API	Failover with retry trail
Maker-checker	Maker submission + checker action	Released batch with OTP / DSC
Status post-back	Bank UTR confirmation	Per-bill paid / pending / failed status
Failure retry	Failed UTR + retry policy	Auto-retry on fallback rail

Rail selection

Input

Bill amount + urgency + bank cut-off

Output

NEFT / RTGS / IMPS / UPI 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 with OTP / DSC
Status post-back

Input

Bank UTR confirmation

Output

Per-bill paid / pending / failed status
Failure retry

Input

Failed UTR + retry policy

Output

Auto-retry on fallback rail

Compliance + integrations

Released the way RBI expects, recorded the way Companies Act requires.

Maker-checker dual control on every batch. OTP or DSC on release. Audit trail on every decision. Connected Banking with the major Indian banks; cheque and DD as fallback for vendors who still need them.

Regulations we work within

RBI Master Directions on dual control

Maker-checker enforced; no single user can release a payment.
Rule 11(g), Companies Act

Append-only audit trail on every release decision.
IT Act 2000, Section 5

DSC-signed release recognised as a legal record.

Connects to

ICICI Bank Bulk NEFT, RTGS, IMPS, UPI
HDFC Bank Bulk NEFT, RTGS, IMPS, UPI
Axis Bank Bulk NEFT, RTGS, IMPS, UPI
Yes Bank Bulk NEFT, RTGS, IMPS, UPI
Kotak Mahindra Bulk NEFT, RTGS, IMPS, UPI
SBI Corporate bulk NEFT / RTGS

Vendor Payment Batches FAQ

What buyers ask.

Which banks are integrated for direct payment?

Connected Banking is live with ICICI, HDFC, Axis, Yes, Kotak Mahindra and SBI. Each supports bulk NEFT, RTGS, IMPS and UPI. Other banks supported via NEFT / RTGS file upload.

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 Tally or Zoho, the payment posts back as a receipt to your ERP.

Is OTP or DSC required for release?

Yes. Maker-checker dual control is enforced on every batch. The checker authenticates with OTP (sent to a registered mobile) or DSC (where the bank requires it). The audit trail captures both. Single-user release is not supported.

Can we do bulk UPI?

Yes. UPI as a rail is supported in bulk where the bank API allows. The system enforces the per-transaction UPI limit (₹5L on most banks; ₹15L for verified merchants on supported banks).

Related features

Run your next batch through Connected Banking, free.

Connect one bank, run a batch of up to 100 vendors. The release follows maker-checker; the books update on UTR confirmation.