Every invoice in one book, ranked by who needs a nudge.
Open AR of $7.74M across 245 invoices, $3.40M of it overdue across 97 — the overview card says so before you read anything else. Invoicing is where bills are drafted, sent, chased and matched to the payments that settle them.
The collections queue is scored, not alphabetical. One P0 at $130K sits above everything else this week, and the screen says why.
invoicing.cedxsystems.com — live build
Runs on demo data — the matching view says “340 rows · 35 drafts · 73 plans” on the screen itself.
$7.74M open AR245 invoices with balance · $3.40M overdue across 97
340 invoices in the workspacedraft to paid · 73 on payment plans
180 payments recorded$732K applied MTD · $40K still unapplied across 14
What it is
Billing, chasing and cash application in one book.
340 invoices, every state from draft to paid
The register carries number, customer, status, plan, amount, balance, due date and age on every row. INV-10737 to Zenith Industries sits at $102K, 42 days old, with a plan badge showing 3× — the installment state is on the row, not in a side panel.
Status chips: Draft · Open · Sent · Overdue · Paid · Partial · Has plan
Matching view $8.82M across 340 rows
CSV export of the view you were looking at
invoicing — invoices
A scored queue, not an alphabetical list
245 open invoices carry a score and a tier: 1 invoice at P0, 3 at P1, $130K of P0+P1 balance at risk. The queue ranks the chasing order and names an owner per row — Amara, Rina and Sasha split this book between them.
Score, tier, balance, age and owner per row
P0–P3 chips filter the queue
Ranked queue · scoring model · tier board tabs
invoicing — screen-4
Cash applied down to the invoice
180 payments recorded with method, date and the invoice each was applied to. PMT-9116, $40K by card from Glassline Packaging, is applied to INV-10454; the $40K still unapplied across 14 payments is a number on a card, not a mystery in a bank rec.
Method chips: Card · ACH · Wire · Check · Credit
$4.43M all-time applied, labelled demo book
Unapplied amount printed on the row
invoicing — payments
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/invoicing.
invoicing.cedxsystems.com
01 — Overview
The AR position before anything else
Open AR $7.74M, overdue $3.40M across 97 invoices, collected MTD $732K, DSO proxy 50 days against a 35-day target. Alerts arrive root-caused: 35 drafts still unsent holding $1.07M of unbilled revenue, and Glassline INV-10460 sitting in 90+ aging at $9.9K.
Drafts 35 · recurring MRR $420K on active templates
Alerts arrive symptom → cause → fix, priced
AR aging bars: $1.85M current to $30K at 90+
02 — All invoices
The register the chase works from
340 rows with balance, due date and age. The largest open rows are named on screen: Willow Apparel $106K current, Zenith Systems $102K at 45 days, Oak Partners $97K at 71 days — so the aging conversation starts from the same table everyone sees.
1–25 of 340 invoices per page, sortable
Age in days on every row, red when overdue
Filter chips mirror the invoice lifecycle
03 — Priority
Who gets chased first, and why
The top of the queue: INV-10686 to Granite Markets, score 83 at P0, $30K and 86 days old, owned by Amara. Below it three P1s at $72K, $13K and $14K. The scoring model is a tab on the same screen, not a hidden service.
P0 1 · P1 3 · $130K at risk across them
Owner column on every row
245 scored rows, $7.74M in view
04 — Payments
Where the money lands
180 payments newest-first: Maple Logistics $51K by wire, Vertex Systems $49K by ACH, Zenith Logistics $25K by card. The unapplied column flags what still needs matching — $7.3K on PMT-9104 is the largest single gap in view.
180 recorded · $732K collected MTD
$40K unapplied across 14 payments
Applied-to invoice on every settled row
Who runs it
Three roles keep the book moving.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
AR and collections
Works the priority queue top-down: P0 first, then the P1s, with the score and the invoice age in front of them before they pick up the phone.
P0 1 · P1 3 · $130K at risk
Billing operations
Clears the 35 drafts holding $1.07M of unbilled revenue, keeps the recurring templates honest, and owns the 73 payment plans.
35 drafts · $1.07M unsent
Controller
Reads the overview the way the board will: open AR, overdue, DSO proxy against target, and whether collected MTD is keeping pace with new billing.
DSO 50d · target 35d
The shape of it
What the demo workspace actually looks like.
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.
$7.74Mopen AR245 invoices with balance
$3.40Moverdue97 invoices · DSO proxy 50d vs 35d target
AR aging, open $7.74Mby bucket · $K · from the overview capture
Current$1.85M
1–30 days$2.69M
31–60 days$2.21M
61–90 days$0.96M
90+ days$30K
Invoices with balance, overdue share97 overdue of 245 with balance
Overdue · 97 invoices · $3.40M
Not yet due · 148 invoices
Collections healthMTD pace · printed on the overview
38
Collected MTD · $732K applied
Pace 38 with one P0 · $130K at risk
How it runs
An invoice's life, in the order it actually happens.
01
Draft
Bills start as drafts — 35 of them are sitting unsent right now, $1.07M of revenue not yet billed. The overview prices the pile instead of hiding it.
02
Send
Drafts become open invoices with due dates and terms; recurring templates carry $420K of MRR without anyone re-typing a line.
03
Chase
What slips lands in the scored queue. Age, balance and history set the score; the owner column decides who calls, and dunning runs from the same book.
04
Apply
Payments arrive by card, ACH, wire, check and credit, and are applied to the invoice they settle. What cannot be matched stays visible as the $40K unapplied figure.
One record
The invoice is one record across the estate.
These captures come from one demo workspace — Northline Systems — so the customer names and balances you see here are the same ones the rest of the finance apps carry.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Invoicing is not generally available. What opens today is the live build running on demo data — the payments screen labels its own $4.43M all-time figure “demo book”.
We have no named customers to show you, so this page shows none. Northline Systems, Willow Apparel and the other names in the captures are the software's demo workspace, not references.
The Dunning tab is visible in the build, but we are not claiming deliverability: no capture shows a reminder leaving the system, and we do not assert inbox placement.
The priority score's inputs are shown as a scoring-model tab; we are not claiming it predicts payment, only that it ranks the demo book the way you see.
No audit or compliance certification has been issued for Invoicing. What we can evidence about hosting, encryption and access is on the security page.
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/invoicing. It runs on demo data — the payments screen labels its own all-time figure “demo book”.
Where do the figures on this page come from?
From the captures. The $7.74M open AR, the 97 overdue invoices, the $732K collected MTD and the aging buckets are all printed on the overview screen you can open yourself.
How does the chasing order get set?
The Priority screen scores all 245 open invoices and tiers them P0–P3. Right now one invoice — INV-10686, $30K, 86 days old — holds the only P0, and the scoring model is a tab on the same screen rather than a hidden service.
Does it send payment reminders for me?
A Dunning tab exists in the build and waves are marked on the collections chart, but we are not claiming deliverability yet — no capture shows a reminder leaving the system. That stays in limits until we can show it.
What happens to cash that cannot be matched?
It stays visible. The payments screen carries an unapplied column and a card totalling $40K across 14 payments, so unmatched cash is a queue to work, not a write-off discovered at month-end.
Is Invoicing audited or certified?
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
The book is open. Go and look at it.
Live build, demo data, no card. Then find your own 97 overdue invoices and compare the view.