Module
Supplier Payments
What to pay this week, to whom, and the remittance that says what it settles.
Watch demo
Thursday is payment day. The list is a spreadsheet somebody rebuilds every week.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- A run proposed from what is due, and every invoice it left out with the reason it was left
- Approval by a named person, re-checked at approval so a bill disputed since preparation stops it
- A remittance advice naming the invoices settled, and saying plainly that SIAARU made no transfer
- The payment recorded through finance's own verb, so the ageing moves when the money does
A worked example
₹1,00,000 overdue · ₹50,000 due in the window · ₹30,000 disputed and left out
due = amount − paid ; saving = due × 2% where the value date is inside the early-pay window
pay now = due − saving, so ₹50,000 at 2% leaves ₹49,000 and the ₹1,000 is shown as earned
the disputed bill is excluded and says why, because a clerk who cannot see it pays it separately
and the boundary that does not move: SIAARU records the payment, it does not make it
Illustrative numbers. 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 number 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.
Released, and one boundary that does not move: SIAARU does not move money. A run ends at an approved instruction and the record of what it settles; the transfer is the tenant's own, through their own bank, and the remittance says so on its face. There is no bank file export and no banking integration, and a run is one currency — two currencies means two runs.
Where this sits
One of 36 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 35 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.