Article
How MSPs Review Invoices Before Sending
A practical guide to review invoices before sending: what diligent MSPs check, where manual review breaks down, and how automated review closes the gap.
To review invoices before sending is to inspect each invoice against a known set of checks — margin, time, notes, tax, and stray internal text — while there’s still time to fix it. It’s the last gate before a billing document becomes a client conversation. Done well, it’s invisible. Skipped, it shows up as a disputed invoice, a credit memo, and a customer who now reads every line twice.
The invoice is the most-read document an MSP sends. The client may never open your SLA report, but they always open the bill. A wrong number there doesn’t just cost the dollars — it costs the assumption that your numbers are right, which is the entire basis of a managed-services relationship.
Why a pre-send review step matters
Every mistake that reaches a client invoice has the same shape: it was cheap to catch and expensive to explain. A below-cost product line is a margin you can’t get back once it’s invoiced. Time logged three months ago invites “what is this?” A note that reads “TODO: confirm rate with Dave” tells the client you bill first and check later.
None of these are exotic. They’re the ordinary residue of a busy month — a rushed catalog entry, a late time sheet, an internal reminder that escaped. The review step exists because the people doing the work and the people reading the invoice are not the same people, and the gap between them is where trust leaks out.
What diligent MSPs check before sending
The MSPs who rarely get billing disputes aren’t lucky. They run the same handful of checks on every invoice, every cycle. Each one maps to a real failure mode.
- Margin on product lines. A product billed below cost is money given away. Even a thin margin on a re-billed license is worth a second look before it’s locked in.
- Stale time. Billable time logged long before the invoice date is the single most common trigger for client pushback. Old work needs a note explaining why it’s only landing now.
- Thin or missing ticket notes. A ticket billed for three hours with one vague line of notes looks like padding to the client — even when the work was real. Documentation should scale with the dollars.
- Non-billable time slipping through. Work marked No Charge or Do Not Bill that ends up on the bill anyway is a refund waiting to happen. Catching it lets you decide: write it off, or rebill it on purpose.
- Wrong or missing tax setup. An unset tax code means tax wasn’t calculated. You find out when the client’s accountant does.
- Internal text leaking out. “TODO,” “FIXME,” and placeholder notes are written for your team, not the client. They should never survive to a PDF.
That’s the checklist. The problem isn’t knowing it — it’s running it on every invoice, every month, without skipping the boring parts.
Where ConnectWise Invoice Routing stops
ConnectWise Manage already has a pre-send review mechanism: Invoice Routing. You build a routing list, and the invoice moves through it — the Routing tab in Invoice Search, and Route Forward and Route Backward in My Invoices, where reviewers act on their queue.
Routing answers who needs to look. It does not answer what they should be looking for. The invoice lands in a reviewer’s queue with no indication that line 4 is below cost or that a ticket was billed with empty notes. The reviewer either knows the data cold and eyeballs it, or rubber-stamps it and routes it forward.
For the native flow, see the Routing tab and My Invoices. The mechanism is sound. What’s missing is the part that does the checking.
Where manual review breaks down at volume
At ten invoices a month, an experienced biller can hold the whole checklist in their head and spot-check the data by eye. At a hundred, that doesn’t hold.
The first thing that goes is the boring checks — the ones with no obvious payoff on any single invoice. Nobody skips the total. Everybody skips “did the notes density keep up with the hours on ticket 88421.” Spreadsheets help, but a spreadsheet is a snapshot: it’s stale the moment the invoice is re-synced, and it has no idea which rows a human already cleared.
The deeper problem is that manual review has no memory. Last month you decided that ticket’s stale time was fine because the client agreed to a delay. This month, the same pattern shows up and someone re-litigates it from scratch. The checks aren’t hard. Running them consistently, across volume, while remembering what you already decided — that’s the part humans lose.
How automated review closes the gap
Automated invoice review runs the checklist for you and surfaces only what fails. Better Invoice evaluates each invoice against a set of rules and attaches a flag wherever something needs a human’s attention — so the reviewer reads a short list of problems instead of re-deriving the whole checklist.
The default rules map directly to the checks above:
- Low profit margin flags product lines whose margin falls below a threshold; below-cost lines escalate to errors. Default threshold: 20%.
- Stale time entries flags billable time logged more than a set number of days before the invoice date. Default: 60 days.
- Insufficient ticket notes flags tickets whose substantive note lines fall short relative to hours billed. Default: 6 lines per billable hour.
- Non-billable time on invoice flags No Charge or Do Not Bill time above an hours threshold. Default: 2 hours.
- Keyword on the invoice flags internal text in descriptions or notes. Default watch list: TODO and FIXME.
Other rules — No tax code on invoice, Product not marked taxable, Large expense, Flagged work type billed — ship turned off so you can opt in to the ones that match your billing rules. Each flag carries a severity (error, warning, or info) and, where it makes sense, a deeplink straight to the offending product or invoice in ConnectWise. For the full list and exact defaults, see the review rules reference.
Crucially, the automation has the memory that manual review lacks. Flags are keyed to the specific issue, so when an invoice is re-synced, a flag you already marked OK stays dismissed — and a flag whose underlying problem was fixed upstream simply disappears. You don’t re-litigate last month’s decisions. To see how flags behave across rescans, see understanding flags.
Reviewers, without rebuilding your routing
Automated checks don’t replace the human sign-off — they sharpen it. Better Invoice keeps the reviewer model and seeds it from ConnectWise so you don’t rebuild what you already have.
- Connect Better Invoice to ConnectWise Manage and open the review inbox.
- Select an invoice to open its detail view, where flags appear in the Flags panel.
- Confirm the reviewers under Reviewers — they’re seeded automatically from the invoice’s existing Invoice Routing list in ConnectWise.
- For each open flag, either fix the underlying data in ConnectWise or select the flag’s checkbox to Mark as OK.
- When the checks are clear, select Approve to record your sign-off.
Reviewers who aren’t Better Invoice users can still take part. Mention someone in a comment and Better Invoice sends a guest share link — they can view the invoice, comment, and, if assigned, approve or reject, all without an account. See share links and guest reviewers.
Every action — a comment, a dismissal, an approval, plus the relevant ConnectWise audit events — lands on a single timeline, so there’s a clear record of who checked what before the invoice went out. See activity and audit trail.
The one-line version
A pre-send review is the cheapest insurance an MSP has against billing disputes — and the first thing that gets skipped at volume. Better Invoice runs the checks automatically, remembers what you’ve already cleared, and keeps the reviewers you already route to in ConnectWise. Start with what invoice review is, or see the whole picture at invoice review.
Frequently asked questions
Why should MSPs review invoices before sending them?
An invoice is the most-read document you send a client. A wrong tax code, a below-cost line, stale time, or an internal "TODO" note that reaches the client erodes trust and triggers disputes and write-offs. A pre-send review step catches those before they leave the building.
What is ConnectWise Invoice Routing?
Invoice Routing is the native ConnectWise Manage feature that moves an invoice through a list of reviewers — the **Routing** tab in **Invoice Search**, and **Route Forward** and **Route Backward** in **My Invoices**. It tracks who needs to look, but not what they should check. Better Invoice seeds its reviewers from that same routing list and adds automated checks on top.
What should an MSP check before sending an invoice?
Margin on product lines, time logged long before the invoice date, thin or missing ticket notes, non-billable time that slipped onto the bill, a missing or wrong tax code, and any internal text (TODO, FIXME, temp notes) that should never reach a client.
Can invoice review run automatically in ConnectWise?
ConnectWise routing moves an invoice between reviewers but does not inspect the data. Better Invoice runs rules against each invoice automatically — flagging low margin, stale time, missing tax codes, and keyword leaks — so reviewers see problems instead of hunting for them.