CEDX Field AR · Customer Service
Field AR is accounts receivable for field service: job-to-cash scored and tiered, deposits on a risk board instead of in a drawer, and invoices with their age in days — so the gap between a finished job and collected cash has an owner.
The overview's sharpest card is not the $3.48M. It is the $744K: forty-nine completed jobs, never billed, with the note “cash clock not started.” That is not a collections problem; it is an office habit, priced.
Runs on demo data. Ridgeline Mechanical is the software's demo tenant, not a customer.
What it is
Three hundred twenty jobs scored for lag risk and tiered P0 to P3 with dollars attached: one P0 at $16K sitting unbilled for 73 days, eleven P1s worth $167K between them. Stages run unbilled → partial → disputed → billed-unpaid, so lag has a location.
One hundred eighteen deposit rows scored critical through safe, with amount, days held and status per row. A cancelled job's $2.5K deposit has been held 76 days with the refund pending — the board puts it second, at 78.
The invoice list shows status, amount, balance, due date and age per row. The top disputed row — $64K at 18 days with a PO dispute — is the same job the overview alert names at 63 days of cash lag with its deposit still held.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/field-ar.
01 — Overview
Collected-versus-billed across the fiscal year with policy changes as markers — a same-day invoice pilot, a deposit-apply policy tightening. The DSO proxy reads 51 days against a 28-day field target, and the aging buckets show where it sits: $695K in the 61–90 band, nothing past 90.
02 — Job-to-cash
Three hundred twenty scored jobs in a ranked queue. The tiers carry dollars — P0 $16K, P1 $167K — and the stage column tells you whether the lag is in the office (unbilled), the customer (billed unpaid) or an argument (disputed).
03 — Deposit risk
One hundred eighteen deposits with risk scores, tiers and days held. Three are critical — including a $426 deposit held 47 days — and the policy simulator sits one tab over for changing the rules that created them.
04 — Invoices
Three hundred sixty invoices with $3.48M open and $2.28M overdue. Disputed is a filter state with 68 rows — an argument in progress is a different problem from a late payer, and the list keeps them apart.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Turns completed jobs into invoices inside the 7-day bill lag — or explains why the clock slipped. The receipts-and-laptop desk in the photograph is this job at a small firm.
unbilled · 49
Works the ranked queue each morning: the single P0 first, then the eleven P1s worth $167K.
P0 + P1 · $183KOwns the deposit board — releases the $271K that is earned, refunds the cancelled jobs before they become disputes.
held · $271KThe 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
The tech finishes; the cash clock has not started. Forty-nine completed jobs sit unbilled, worth $744K.
Bill lag runs 7 days on average against a 25-day cash lag — the cards put both numbers on the same screen so the office gap is visible.
The ranked queue orders the work: one P0, eleven P1s, $183K at risk between them, stages named per job.
Deposits come off hold by policy — $271K idle while AR ages is the board's whole argument, and 3 critical rows lead it.
One record
Field AR is the financial tail of the service day. The job, the invoice and the conversation about the invoice live in one estate.
Field AR begins where Field's board ends: a completed job with parts closed. The 49 unbilled jobs are completions that never crossed over.
CEDX InvoicingThe 360 job invoices here are the trade's own shape of AR; Invoicing is the estate's general engine for the rest of it.
CEDX DeskA disputed invoice with a PO question is a support conversation. Desk's queue is where those get worked and counted.
CEDX CopilotAsk AI — ⌘J — sits on every Field AR screen, versioned and traced by the Copilot console behind it.
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 jobs, your ledger
Field AR with the rest of it
Questions
Yes. Every screenshot is a capture of the running build, open at /app/field-ar. It runs on demo data — the tenant on the chrome is the demo company.
No. Field AR is field-service accounts receivable: job-to-cash scoring, deposit risk and invoices. The captures on this page are the product as it actually runs, and we would rather correct the expectation here than on a call.
Because the overview prices them: $744K of completed work with the note “cash clock not started.” Bill lag of 7 days against cash lag of 25 means the office, not the customer, holds the first days of every dollar.
Held deposits by risk — 118 rows, critical through safe — using days held, job state and refund path. A cancelled job's $2.5K held 76 days sits at 78, second on the board, which is exactly where a refund-pending deposit belongs.
No certification has been issued. What we can evidence about hosting, encryption and access is on the security page.
Live build, demo data, no card. Then ask how many completed jobs your office invoiced this week.