CEDX Receivables · Finance
$12.2M open across 391 invoices, $7.27M of it overdue across 228 — and $1.94M of received cash sitting unapplied because the remittance evidence is not good enough. Receivables scores both problems instead of burying them.
The match-risk board's honest number is zero: of 85 suspect remittance pairs, not one cleared the confidence bar for automatic application. A person decides, with the evidence in front of them.
Runs on demo data — the match board labels its own threshold: “safe auto · conf ≥ 85”.
What it is
391 open invoices scored and tiered. Seven P1s carry $344K; each row adds an expected-pay date and how far it has slipped — INV-20883 at $45K is 41 days old and 39 days past its own pattern. Collectors Rina, Amara and Sasha are named per row.
85 remittance-to-invoice candidates, every one below the 85-confidence bar, every one an exception for a person. REM-4495 against INV-20616 for Quartz Retail pairs $65K with $65K at confidence 53 — plausible, not provable, so it waits.
420 invoices carry an expected-pay column derived from each customer's own payment history: “07-24 · +18d” means the invoice was already 18 days past when this customer usually pays. $7.39M is past expected across 228 rows.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/receivables.
01 — Overview
Open AR $12.2M, overdue $7.27M across 228 invoices, collected MTD $401K, DSO proxy 54 days against the 35-day target. The two leaks are priced on cards: $1.94M of cash unapplied, $1.85M of match risk sitting in the queue.
02 — Priority
The ranked queue puts seven P1 invoices at the top worth $344K — Union Logistics at $127K and 39 days, two more Union rows behind it. Zero P0s this week, and the board says so rather than inventing urgency.
03 — Match risk
85 pairs in the risk board, all high risk, all exceptions. The unapplied queue behind them holds $1.94M — including a $41K wire with an incomplete memo that the overview root-causes against $186K of open AR.
04 — Invoices
420 rows where overdue is only one of the states: Open, Partial, Overdue, Disputed, Paid and Past expected are all chips. INV-20721 to Granite Foods sits disputed at $119K with an expected-pay of 11-05 — on track against its own pattern despite the dispute.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Works the scored queue top-down with the expected-pay slip on the row — the conversation starts from when this customer usually pays, not a generic dunning script.
P1 7 · $344K at risk
Clears the 85-pair exception queue — the wires and remittances that did not clear the confidence bar, with the candidate matches ranked in front of them.
95 remittances · $1.94M
Watches DSO proxy against the 35-day target and the disputed balance, and prices the week before the board asks.
DSO 54d · disputed $1.88MThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Every open invoice gets an expected-pay date from the customer's own history — the slip in days is visible before the invoice is technically late.
The scored queue sets the calling order: score, tier, age, slip and a named collector on every row, with disputes tracked as their own state.
Cash arrives with whatever evidence the payer sent — a $41K wire with an incomplete memo is money received and revenue uncounted until it is matched.
Pairs below the confidence bar wait for a person; nothing is auto-applied on a guess. The $1.94M queue is the price of that honesty, and it is on a card.
One record
These captures come from one demo workspace — Northline Systems — so the customers and balances here are the same ones the rest of the finance apps carry.
Where the invoices being chased were issued — drafts, plans and the priority score on the billing side of the same book.
CEDX PaymentsThe rails the collected cash arrives on, with auth rates and fees on the same demo workspace.
CEDX BooksThe ledger the applied cash posts to — and the finished reference page for this estate's evidence standard.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your customers, your remittances
Receivables with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/receivables. It runs on demo data.
Each open invoice carries the date this customer usually pays, derived from their own history, plus the slip in days. “07-24 · +18d” on a row means 18 days past their pattern — visible before the invoice is contractually late.
Because in the demo book no candidate pair clears the printed confidence bar of 85. All 85 pairs go to a person as exceptions with the evidence ranked — that is the design, not a gap.
The queue names an owner per invoice — Rina, Amara and Sasha split the demo book. The scoring model tab shows what drives the rank; assignment rules are a pilot conversation.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then find your own unapplied cash and compare the number.