Payment scheduling
Pay on time, pay once, and pay only what matched.
Clean matches flow into payment runs by due date. Variances stay out until someone decides. The run is approved by a person who did not place the order.
Payment run
A run you can approve in minutes, because the checking is already done.
Every invoice in the run has a matched PO and receipt behind it, and one click opens the full chain.
- Grouped by vendor and due date
- MSME invoices highlighted
- Held invoices listed separately with the reason
Capabilities
The last step, with the same controls as the first.
Due-date aware runs
Matched invoices are proposed for the payment run before their due date, based on the credit terms on the PO or vendor.
MSME timelines
Invoices from registered micro and small enterprises are flagged as their statutory payment window approaches.
Early-payment discounts
Where a vendor offers a discount for early payment, Ipcosys shows the saving and the date it expires.
Separate payer role
The person who approves a payment run cannot be the one who raised or approved the purchase.
Only matched invoices
Held invoices never appear in a payment run. They join the next run once the variance is resolved.
Bank and ledger export
Approved runs export in the format your bank and accounting system expect, with invoice references on every line.
Questions
Payment scheduling
Does Ipcosys move money?
How are partial payments handled?
Can we run payments on fixed days?
Only pay what matched.
Set up a workspace with your own approval rules and tolerances, or walk through your current process with us first.