Billed vs collected, by month
Billed Collected Tap a month to filter
How long invoices have been unpaid as of 30 Sep
| Month | Billed | Collected |
|---|---|---|
| Feb 2026 | $191,615 | $26,923 |
| Mar 2026 | $218,995 | $90,928 |
| Apr 2026 | $238,375 | $181,420 |
| May 2026 | $357,035 | $299,225 |
| Jun 2026 | $353,641 | $274,017 |
| Jul 2026 | $446,695 | $276,104 |
| Aug 2026 | $485,096 | $468,571 |
| Sep 2026 | $532,208 | $435,973 |
| Age | Balance | Invoices |
|---|---|---|
| 0–30 days | $444,688.40 | 42 |
| 31–60 days | $114,105.40 | 14 |
| 61–90 days | $42,899.28 | 7 |
| 90+ days | $168,804.98 | 25 |
Two reports, two different numbers. Partners stop using both.
Your team rebuilds the same spreadsheets by hand, every month.
The data is there. Getting it out takes a SQL expert.
Firm Data Health Check
A ranked list of what to fix first, from three read-only checks you run yourself.
Book a free 30-minute consultationDiagnostic tools available upon request.
We provide the script and you run it and review the findings yourself.
Prefer our help? Get in touch
Senior back-office systems help for professional-services firms: we make your billing, close, reporting and integrations reconcile - with deep mid-sized firm experience
Accountants know the numbers. IT knows the systems. BI consultants know dashboards. We know all three.
| What matters | MethodML | Accountant or CPA firm | IT or software vendor | BI consultant |
|---|---|---|---|---|
| Speaks accounting | Yes | Yes | Rarely | Rarely |
| Knows your systems | Yes | No | Yes | Varies |
| Dashboards partners read | Yes | Spreadsheets | Reports | Yes |
| Ties back to your books | Yes | Yes | Not their job | Often not |
| Free way to start | Yes Health Check | Usually hourly | Usually hourly | Usually hourly |
Two small examples, built the way we build them for firms. All figures are made up.
Time entries post, hours and fees accumulate, disbursements and trust apply, and the balance due is the arithmetic, not a typed number. The stamp appears only when the prebill agrees with the ledger.
The layout is a prebill review sheet of the kind a law firm circulates before invoices go out. The same data drives the report in the next sheet.
Fictional firm, fictional matter| Date | TK | Description | Hours | Rate | Amount |
|---|---|---|---|---|---|
| 08-03 | JHM | Review lease amendment and correspondence from landlord's counsel | 1.8 | 450 | 810.00 |
| 08-04 | ATR | Assemble exhibit binder; confirm service list | 0.6 | 285 | 171.00 |
| 08-07 | JHM | Draft response to notice of default; call with client | 2.4 | 450 | 1,080.00 |
| 08-12 | ATR | Research cure-period provisions; memo to JHM | 3.1 | 285 | 883.50 |
| 08-19 | JHM | Settlement conference preparation | 0.9 | 450 | 405.00 |
| 08-26 | JHM | Attend settlement conference; report to client | 1.5 | 450 | 675.00 |
Ask it in plain language -- which matters slipped, where realization moved, what changed since last month. The question becomes a query against the firm's own data, and every cell below re-runs on one governed set of facts, so the tiles, the chart and the table cannot disagree with each other.
The model writes the query; the database returns the number, and the query travels with it. A figure can still be wrong -- a query can ask the wrong question -- but it cannot be made up, and it can be checked, because the query sits beside the answer.
Once a query is accepted it is saved with the report and the model leaves the loop. That is what makes a schedule dependable: it lands at seven on Monday and runs the way it ran last Monday.
Published as a report for the people who read it, kept as a notebook for the people who maintain it -- and the same facts drive a live WIP screen for the billing desk, where any difference from the month-end figure is a timing difference, not a data one.
Fictional firm, fictional timekeepers# "fees by timekeeper for August, and flag WIP over 60 days" month = mo.ui.dropdown(months, value="2026-08", label="Month") facts = ledger.fees(month.value) # generated query, shown with the result
| Timekeeper | Fees | Share |
|---|---|---|
| JHM | $38,700 | 26.3% |
| ATR | $39,400 | 26.7% |
| LKO | $30,150 | 20.5% |
| PDS | $23,850 | 16.2% |
| MRC | $15,300 | 10.4% |
You tell us what is not working and which systems you run. We tell you whether the Health Check fits and what we would look at first. If we are not the right fit, we say so.
One report, most urgent first, from three read-only checks of your SQL Server, your data and what is actually used. It is free, and you decide whether to go further.
Run three scripts with a read-only login. It takes a few minutes, and the results stay on your computer. Prefer we run them? Ask on the call.
Yes. The scripts only read; they change nothing, and they are plain text, so your IT team can read every line first.
Only the people on our team doing the work, and we sign your NDA first. We work inside your environment wherever we can, and any copy we hold is returned or deleted within 30 days.
Nothing unless you ask for more. Reviews, fixes and projects are quoted in writing under a signed agreement before work starts; ongoing support is a monthly plan.
No. Everything we build runs on tools you already own, with notes your next admin can follow. You can stop working with us and keep it all.
No. We know ProLaw well, and we help any professional-services firm with its back-office systems and data.
A report nobody trusts. A month-end that takes too long. Write a few lines, or book a call. A person replies.
Send a message