slipstream Book a call
ProductFor law firms

Bill Guard

Every invoice checked against your client's billing guidelines before it goes out. Every cut that still comes back, explained.

88%of firms expect write-offs to rise.BigHand, 2026
115→134day law firm collection cycle, 2019–2024.Citi Hildebrandt, 2026
38 seconds

One invoice line, before it goes out.

A block-billed discovery entry gets cut by $390.00. Then the same line goes through Bill Guard: the flag cites the guideline it breaks, the fix asks the timekeeper to split the entry, and when payments come back the cut is matched to its rule.

The invoice and the carrier are fictional, an illustrative example. The $220.91 cost per e-bill is from Thomson Reuters. Every word is on screen, so it plays without sound.

Read the transcript
  1. The work was done. The invoice still came back. Reduced: $390.00.
  2. $220.91 to process a single e-bill. Every rejection means paying part of it again. (Source: Thomson Reuters)
  3. Bill Guard checks every LEDES invoice against each client's billing guidelines, before it goes out.
  4. Check: every flag cites the rule it breaks. Block billing on line 14, likely rejected. (Illustrative example)
  5. Fix: bill accurately, never disguise the work. Ask the timekeeper to split the entry. Never re-code, pad or invent detail.
  6. Learn: when payments come back, every cut is matched to its rule, or flagged as a practice nobody wrote down.
  7. Get paid for the work you already did.

What it does: check, fix, learn.

Check.

Every line of every LEDES 1998B invoice, against the guidelines of the client it is going to.

  • — File structure, arithmetic and totals, the checks a portal runs before anyone reads the invoice.
  • — UTBMS task, activity and expense codes, including the lowest-level-code rule that rejects phase codes.
  • — Each client's own rules, from the guidelines you upload. Bill Guard proposes each rule with the exact sentence it came from; nothing checks an invoice until someone at the firm accepts it.
  • — Each client's approved rate for each timekeeper, by date.
  • — No guidelines from a client, or years-old ones? Bill Guard's own default standards cover the common problems, and every flag they raise is labeled as ours, not the client's.

Fix.

A cited, honest fix for each flag, routed to the person who can make it.

  • — Each flag quotes the guideline and shows the dollars at risk.
  • — Questions only a timekeeper can answer go to them through a secure link. Bill Guard never rewrites a narrative with facts the timekeeper didn't give.
  • — Work through the flags one at a time from the keyboard, or apply a fix to many lines at once.
  • — Export the corrected LEDES file, with a line-by-line list of the changes to make in your billing system.

Learn.

What each client actually paid, and why.

  • — Import remittance and reduction notices. Every cut is matched to the rule that predicted it, or marked as one no published rule explains.
  • — From the cuts no rule explains, Bill Guard proposes the client's unwritten practices, each with its evidence (for example, how many comparable entries the client cut, and over which months). A person accepts or rejects each one.
  • — For invoices already cut, it ranks the entries worth appealing, with the client's own history as the evidence.
  • — These run on your firm's own payment history; the more of it you load, the more they find.
How it fits

Your billing system stays the hub.

Bill Guard sits in the loop twice: once on the way out, once on the way back.

Works with any billing system that exports LEDES 1998B. No billing system? Upload a time and expense spreadsheet and Bill Guard builds the LEDES file.

  1. 1Your billing system exports the LEDES file (or a pre-bill, as PDF, Excel or CSV).
  2. 2Bill Guard checks every line and fixes it with citations.
  3. 3Your billing system sends the corrected invoice to the client's portal and applies the changes list to its own records.
  4. 4The client pays and sends remittance and notices.
  5. 5Bill Guard reconciles every cut and feeds what it learns into the next check.
  6. Step five feeds step two. Each cycle tightens the next check.

Where the human stays

The check flags; it never decides. A rule checks invoices only after someone at your firm accepts it. Narrative suggestions may clarify, never add facts. A flag that needs the timekeeper goes to the timekeeper. Nothing is re-coded, split or re-dated to get past a rule.

What it does not do

Bill Guard doesn't submit invoices to client portals, and it doesn't write into your billing system: it gives you the corrected file and the list of changes. It reads LEDES 1998B; other formats when a customer needs them. It doesn't promise that an invoice will be paid. It shows what each client's guidelines say is likely to be cut, and what the client did afterwards.

Your data

  • — Each firm's data is isolated in the database and encrypted under the firm's own key.
  • — Every view and change is logged.
  • — No client data trains any model, ever.
  • — Delete your firm and its data goes with it.
  • — SOC 2 is planned, not done; ask us where it stands.

Plans

ValidatorFreeUpload an invoice or a pre-bill, pick the client, get a cited report with the dollars at risk.
Self-serve plansThe full review workflowPriced by the number of timekeepers.
The Rejection LoopFor firms that want the money backWe start with a diagnostic on last quarter's invoices and reduction notices, then run the loop with you.

Every plan runs the same checks. Plans differ in workflow, history and seats, never in accuracy.

Bill Guard started as our billing guideline compliance use case for insurance defense firms: the same rules, the same “the check flags, it never rewrites time”, built into a product you run yourself.

Read the use case →

Send one invoice.

Bring an invoice and the client's guidelines. We'll show you what Bill Guard flags, and why.

Get early access