Accounts Payable | Payment Scheduling

Payments queued by due date. MSME-aware. With cash visibility.

Approved bills queue by due date. MSME 43B(h) bills auto-prioritised. ITC-at-risk and TDS holds gate the run. Bank rails (NEFT, RTGS, IMPS, UPI) fire on release. Cash position projected against the next two weeks.

Start free trial Book a demo

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
MSME 45-day prioritisation	MSME flag + invoice date	Bills approaching 45 days surfaced first
Hold engine	2B status, TDS status, KYC, MSME	Per-bill hold with reason
Cash projection	Bank balance + scheduled receivables + outflows	2-week rolling cash position
Rail decisioning	Amount + urgency + bank rail status	NEFT / RTGS / IMPS / UPI per bill
Maker-checker release	Run plan + dual-control approver	OTP / DSC release with audit trail

Run scheduling

Input

Approved bill set + due dates + vendor priority

Output

Run plan with line-level priority
MSME 45-day prioritisation

Input

MSME flag + invoice date

Output

Bills approaching 45 days surfaced first
Hold engine

Input

2B status, TDS status, KYC, MSME

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 + bank rail status

Output

NEFT / RTGS / IMPS / UPI per bill
Maker-checker release

Input

Run plan + dual-control approver

Output

OTP / DSC release with audit trail

Compliance + integrations

Maker-checker as RBI expects, MSME as the IT Act requires.

The release flow respects both RBI maker-checker norms and Section 43B(h) MSME timing. Bank rail selection follows the RBI value bands. The audit trail is hash-chained for Rule 11(g).

Regulations we work within

Section 43B(h), Income Tax Act

MSME bills past 45 days held; disallowance amount surfaced before override.
RBI dual-control norms

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

Append-only audit trail across the release decision.

Connects to

ICICI Bank Connected Banking API
HDFC Bank Connected Banking API
Axis Bank Connected Banking API
Yes Bank Connected Banking API
Kotak Mahindra Connected Banking API
SBI Corporate Banking integration

Payment Scheduling FAQ

What buyers ask.

Can a payment be held when the GSTR-2B match is not yet clean?

Yes. Bills with unresolved 2B mismatches surface as held, with the ITC-at-risk amount visible. The CFO can release with an override (audit trail captured) or hold until the vendor or the recon engine resolves it.

What if NEFT is down on the bank side?

Rail decisioning has auto-fallback. If NEFT is unavailable, the system falls through to IMPS where the amount is within the IMPS limit, or queues for the next NEFT window where required. 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.

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, MSME priorities, ITC at risk and the cash position, all on one screen.