Module
Receivables & Payables
Who owes you what and how late, what you pay this week, and the days outstanding counted the way a CFO counts them.
Watch demo
Monday: who do we ring first for money, and what do we pay this 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
- Receivables and payables aged by bucket — current, 1–30, 31–60, 61–90, 90+ — from the invoices your ERP states
- DSO and DPO by countback over the months' invoicing, with the arithmetic printed
- The collections list: who to ring today, in order of amount and age, with credit exposure and disputes held out
- The payment run: what falls due in the window, what is approved, and which early-pay discount lapses when
- Disputes and payment approvals as a named person's act, audited
A worked example
AR 4.2 Cr open, 31% past due · DSO 47 days by countback · pay 1.1 Cr this fortnight
Gumi Enterprises: 38.4 L overdue, oldest 52 days, 112% of credit limit — ring first
INV-5521 disputed (short delivery) — held out of the overdue number until settled
countback: Aug 3.1 Cr consumed +31 d; Jul 1.1 of 2.9 Cr = 11.7 d → DSO 42.7 days
SUP-2088: 2% if paid by Friday — 18,400 on offer, lapses in 3 days
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Every finance manager can pull an ageing report; few can say on a Monday who to ring first, which early-pay discount lapses on Friday, and what the DSO actually is by a method an auditor accepts. This reads the invoices and payments the ERP already states and answers those three questions with the arithmetic beside each number. It posts nothing.
Opened by the finance director, the supply chain manager and the sales manager — 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.
Visibility by design, not a ledger. Invoices and payments come from your ERP or accounting package, and nothing here posts a journal or issues an invoice — your book of record should stay the book of record. A due date is never assumed: an invoice without one takes the party’s stated terms, and says so where there are none.
Where this sits
One of 36 modules, on one engine.
Receivables & Payables 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.