Prebilling, Explained: How a Faster Prebill Cycle Shortens Invoice-to-Payment Time

Prebilling is quality control for revenue: until the prebill clears review, recorded time cannot be invoiced, and until it is invoiced, it cannot be paid.

Why prebill cycles slow down

Most slow prebill cycles fail in the same four ways, and three of them are really the same failure: the conversation about the bill happens somewhere other than on the bill.

The bill travels as a PDF, and the discussion travels as email. The prebill is exported and marked up by hand or in reply threads. Copies multiply, two reviewers annotate different versions, a question about one entry sits in an inbox while the answer sits in another, and billing staff re-key handwritten edits, introducing fresh errors into the step meant to catch them.

Nobody is sure who approves what. If approval order and responsibility are unclear, drafts wait. A reviewer assumes someone else is first, a partner is travelling, or a question sits unanswered because nobody knows whose decision it is.

The discussion leaves no record on the bill. Comments made in email threads and margins are detached from the entries they concern. Months later, during a client query or internal check, reconstructing who changed what, when, and why is slow and sometimes impossible.

Everything lands at month-end. If review only happens when the billing cycle closes, a whole month of drafts arrives at once. Reviewers rush, billing queues behind them, and invoices that could have gone out in stages go out late, together.

The workflow: one place for the bill and its review

The fix is to keep the bill, the reviewers, and the conversation in one place. In Aprotime, it runs like this:

• Keep time current all month. Reviewers can only approve entries that exist. Live timers, manual entry, and templates help timekeepers record work as it happens, and AI-assisted narratives turn rough notes into client-ready descriptions earlier, so review does not begin with a backlog.
• Review happens where the bill lives. The prebill is reviewed where it lives, previewed as the client will see it, worked through the firm’s approval stages without leaving the system, with reviewers’ comments and the billing team’s responses kept with the bill rather than scattered across email. Nobody guesses who goes first or chases the draft by email; its status is visible to everyone in the chain. When the final approval lands, the bill moves on the same day (to invoicing, by whichever route the firm uses (next section)) and the record of who changed what, and why, stays attached to it.
• Track what is still outstanding. Aging and collection views show which invoices are unpaid and for how long; the workflow view shows which prebills are still in review and with whom. Both queues need an owner every week.

Why reviewing the bill in one place beats PDF markups by email

Email markup fails on versioning, visibility, and memory. Versioning: the second a PDF is attached, there are two truths: the system and the attachment. Visibility: only the thread’s recipients can see it, so a covering colleague starts from zero. Memory: six months later, the reasoning behind a write-down exists, if anywhere, in someone’s sent items. An in-system prebill has none of these problems: one current draft, a visible status, and the reasoning behind every edit and approval kept with the bill itself, so a client query is answered from the record, and the review becomes part of the firm’s institutional memory of the matter.

From prebill speed to payment date

Payment terms usually run from the invoice date, not from the date the work was done. That makes the chain simple: the prebill clears, the invoice goes out, the payment clock starts. Every day a draft sits in review is a day added to the payment date at the other end.

Illustrative example (not a measured result): suppose a firm’s invoices are typically paid 30 days after issue. If a prebill batch clears review on the 5th and invoices go out that day, payment on those terms lands around the 4th of the following month. If the same batch waits in review until the 15th, the same 30-day terms put payment around the 14th, ten days later, purely from review delay. Your firm’s dates will differ; the arithmetic of the delay will not.

Where the prebill goes next

Approval is not the end of the story, and Aprotime is deliberately built for both of the ways firms finish it.

Route one: invoice and collect in Aprotime. An approved prebill becomes an invoice in Aprotime, the invoice is sent to the client from Aprotime, and collections are tracked there until it’s paid, with aging views showing what is outstanding. This suits smaller firms that want capture, prebill, invoicing, and collections in a single system, with no re-keying and no second ledger to reconcile.

Route two: keep your accounting system. Larger firms typically generate invoices and accept payments in their own accounting system, and reasonably expect to keep doing so. For them, Aprotime manages the pre-bill (the capture behind it, the review, the approvals) and connects with that system through its integration options, so the approved bill reaches it without re-keying. It issues the invoice and takes payment exactly as it does today: Aprotime strengthens the stage it owns without forcing a rip-and-replace of the firm’s financial core.

Neither route is a compromise version of the other. The prebill, where narratives are defended and adjustments agreed, is where the revenue is actually protected, and it works identically in both.

Monthly prebill checklist

• All time for the period entered, with narratives drafted
• Prebills generated in batches, not one month-end pile
• Each prebill reviewed in final form before approval
• Each batch worked through the firm’s approval stages in order
• All reviewer comments resolved, none outstanding in email
• A named owner chasing every draft stuck at any stage
• Approved prebills moved on the same day, invoiced in Aprotime, or into the firm’s accounting system
• Aging and collection views reviewed for last month’s invoices
• Budgets, estimates, and retainers checked against alerts before the next cycle

Frequently asked questions

What is the difference between a prebill and an invoice?

A prebill is an internal draft of proposed charges that reviewers check, edit, and approve. An invoice is the final, approved bill sent to the client for payment. Work cannot move from draft to invoice until prebill review is complete.

Who should approve prebills, and how do they comment?

Whoever your firm’s policy names, typically the attorneys responsible for the client relationship and the work performed, with billers coordinating. Reviewers’ comments and the billing team’s responses stay with the bill itself, in the system where it is reviewed, instead of circulating as PDF markups by email.

Our firm invoices from its own accounting system. Do we have to change that?

No. Aprotime manages time capture and the pre-bill, and its integration options connect with your accounting system, so invoicing and payment stay where they are today. Smaller firms can instead generate, send, and collect on invoices inside Aprotime.

How long should a prebill cycle take?

There is no single right number, because review depends on draft volume and approval stages. The practical test is whether drafts clear in a steady flow during the month or pile up at the end. An in-system workflow (the bill reviewed where it lives, through the firm’s approval stages) is what makes a shorter, predictable cycle possible.

If your prebill cycle is where invoices go to wait, and where the conversation about them goes to get lost, see what an in-system workflow looks like on your own matters: review, approval, and then on to invoicing, wherever your firm does it. Schedule a demo of Aprotime and walk through it with your firm’s process in mind.