Bills queued by due date
Approved bills queue automatically by due date and vendor priority. MSME bills are auto-prioritised against the 45-day window.
Accounts Payable | Payment Scheduling
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.
How it works
Approved bills queue automatically by due date and vendor priority. MSME bills are auto-prioritised against the 45-day window.
Bills with unresolved 2B mismatches, missing TDS section, KYC gaps or MSME breach surface as held. The CFO sees the held amount and the reason before any release.
Bank balance plus projected receipts and scheduled outflows shown for the next 2 weeks. The release decision is informed, not blind.
NEFT, RTGS, IMPS or UPI selected per amount and urgency. Auto-fallback if a rail is down (NEFT outage triggers IMPS where amount allows). Status posts back per UTR.
What the system does
| 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
MSME 45-day prioritisation
Hold engine
Cash projection
Rail decisioning
Maker-checker release
Compliance + integrations
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
Payment Scheduling FAQ
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.
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.
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.
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.
More in Accounts Payable
Udyam status verified. 45-day rule at scheduling. Disallowance impact surfaced before override.
See MSME 43B(h) ComplianceNEFT/RTGS/IMPS/UPI rail selection with auto-fallback. Connected Banking integration. Status posted back.
See Vendor Payment BatchesBills matched against GSTR-2B every night. Vendor non-filers caught the day they should have filed, not at year-end.
See GSTR-2B Bill ReconciliationConnect 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.