CEDX Books · Finance
General ledger, AR and AP subledgers, revenue schedules and statements — multi-entity, accrual or cash, on the customer record CRM and Desk already write to.
Every finance team has a surface like this one — the board, the spreadsheet, the one analyst's laptop. It exists because the ledger, the bank and the customer record disagree, and somebody has to hold the real number in between.
Runs on demo data. No card, and no call before you can look at it.
What it is
Northline Systems on FY2026 running February to January is a switch in the header, not a second installation. Each entity keeps its own fiscal calendar, its own close and its own statements.
An aging report tells you the problem exists. This is the list you actually chase from: filtered to overdue, sorted by balance, with the age of every line next to the customer who owes it.
The simulator carries a panel headed “Why this is defensible”. It prints the weekly step it used — cash += collect×0.9 − netBurn/4.3 — and names the live arrays each lever reads from. You can check it instead of trusting it.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/books.
01 — Overview
Cash, AR open, AP open, revenue and opex pulse, runway — and underneath them root-caused alerts that name the invoice, the bill and the payroll run behind the movement.
02 — Invoices
320 invoices in books. $7.75M open AR, $1.90M of it overdue across 52 invoices. Number, customer, status, amount, balance, due date and age — sorted by whatever you are chasing today.
03 — Runway
Thirteen weeks projected against the do-nothing baseline, with seven levers each carrying its own cash impact — collect 10 days faster, chase all overdue this week, freeze non-committed marketing for 30 days.
04 — Cash
Four accounts with auto-match on or off per account, 157 lines waiting in the match queue and 64 already reconciled — unmatched counts sitting on the account that owns them.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the close. Wants the checklist, the cutoffs and the entity calendar in one place instead of three.
Close checklist · per entity
Chases the money in and schedules the money out. Lives in the aging list, not the aging report.
$1.90M overdue · 52 invoices
Assembles the quarter. Wants the export to come from the numbers the dashboard has been showing all month.
One export storyThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your business — it is the state of the demo data.
$5.34M$4.00M$2.67M$1.33M$0
W1W5W9W13
The close
Invoices, bills, expenses and transactions land against the customer record CRM already created. Nothing is retyped at the boundary between two teams.
Revenue schedules run off the contract — not off a spreadsheet that one person maintains and nobody else can open.
A checklist with owners and cutoffs, per entity, on that entity's own fiscal calendar rather than a shared one.
Statements and the board pack export from the same numbers the dashboard was showing all month.
One record
Books is not a finance silo with a connector bolted onto it. It reads the customer record the rest of the estate writes.
The customer Books bills is the customer sales closed. Same record, same identity, no reconciliation step in between.
CEDX DeskSupport opens a ticket already knowing what the account pays and what is currently overdue.
CEDX InvoicingBilling runs and subscriptions feed this AR ledger rather than a second one that has to be matched to it.
CEDX PaymentsMoney in lands against the invoice it settles, not into an unallocated bucket someone clears on Friday.
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 numbers, one entity
Books 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/books. It runs on demo data, which the Cash screen states on screen rather than in a disclaimer.
Yes, and not as an add-on. Each entity carries its own fiscal calendar — the capture shows FY2026 running February to January — its own close checklist and its own statements.
No, and most pilots do not. Starting on AR, or on revenue schedules alongside an existing ledger, is a normal way to arrive. The estate map is where that sequence gets decided.
It prints the arithmetic on the screen. The “Why this is defensible” panel states the weekly step and names the live arrays each lever reads from, so the number can be checked rather than believed.
Nothing. Books exports the view you are looking at, and the close is designed to produce one export story instead of six that have to be reconciled to each other first.
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 tell us which entity you would put on it first.