Module
Supplier Payments
What to pay this week, to whom, and the remittance that says what it settles.
What it produces
- A payment run proposed from what is due, what is disputed and what discount is still earnable
- Approval by a named person against a limit, never a batch released by a schedule
- A remittance advice naming the invoices settled, so the supplier's ledger can agree with yours
- The payment recorded against those invoices, so the ageing moves when the money does
A worked example
Illustrative only — nothing is paid or proposed today
supplier invoices and their due dates are already recorded, which is what a run selects from
what is missing is the run, the approval and the remittance
and a boundary that will not move: no money leaves through this software
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Supplier invoices and their ageing are already recorded, so what is due is known. What is missing is the run that proposes a week's payments, the approval against a limit, and the remittance advice that lets a supplier's ledger agree with yours. One boundary is fixed whatever gets built: SIAARU will not move money. Any banking step is the tenant's own, through their own channel, and this would end at an approved instruction and the record of what it settles — never at a transfer this software made.
Opened by the finance director and the procurement lead — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no figure your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
Not built. Supplier invoices and their ageing are recorded, but nothing proposes a payment run and nothing produces a remittance. SIAARU will not move money: any banking step is the tenant's own, through their own channel, and this module would end at an approved instruction and the record of what it settles — never at a transfer this software made.
Where this sits
One of 32 modules, on one engine.
Supplier Payments reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 31 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.