Billing problems usually begin before the invoice
Professional services firms rarely struggle to produce an invoice document. The harder work happens earlier. Time must be recorded against the correct engagement. Expenses need supporting detail. Scope changes require approval. Partners or engagement managers must review the draft. Purchase order references, matter codes, billing contacts, and portal requirements must be current.
When those inputs arrive through separate e-mails and spreadsheets, billing becomes an exercise in reconstruction. The finance team spends days finding out whether work is complete, whether a fee cap still applies, or why an engagement manager has not approved the draft. The invoice is delayed, but the underlying cause remains hidden.
This is not primarily an accounts receivable problem. It is a handoff problem.
Make unbilled work visible by status
A single total for unbilled work is not enough. It combines items that require very different actions. Recent time awaiting the normal billing cycle is healthy. Time held because of a fee dispute is not. An expense missing a receipt is different again.
A useful work-in-progress schedule assigns each item to an operational status, such as:
- Open work within the billing cycle
- Ready for draft preparation
- Awaiting engagement approval
- Blocked by missing information
- Held by an agreed billing decision
Each blocked item also needs an owner and a next action. “Awaiting approval” is not actionable unless it identifies whose approval is required and when the request was sent. Finance Operations should maintain this queue as part of routine billing work, not recreate it just before month-end reporting.
One useful control is to age work from the date it became billable, not only from the date the time was entered. Those dates answer different questions. Entry date reveals late time recording. Billable date reveals how long completed work has been waiting for commercial or administrative action.
Define a real billing cutoff
A calendar deadline does not create discipline by itself. “Submit time by Friday” leaves several details unresolved. Can people amend submitted time on Monday? Who approves adjustments? What happens to an expense received after the draft invoice has been reviewed? Does finance reopen the draft, carry the expense forward, or escalate it?
The cutoff needs a defined sequence. Time is submitted, reviewed, and locked. Exceptions enter a queue. Drafts are prepared from the locked records. Changes after that point require a documented reason and an identified approver.
This matters because silent edits break reconciliation. If the billing system extracts one version of the time ledger and someone changes the underlying entry later, the draft invoice no longer ties to the current record. The difference often appears as unexplained residual work in progress. A simple post-lock change report prevents hours of investigation.
Separate draft approval from invoice acceptance
Internal approval does not mean the customer has accepted the invoice. Many firms mark billing as complete when the invoice is e-mailed or uploaded. That leaves finance blind to rejected submissions.
The workflow should distinguish several events: draft approved, invoice issued, invoice submitted through the required channel, and invoice accepted for processing. A portal rejection caused by an expired purchase order or incorrect matter code belongs in a billing exception queue. It should not sit in the accounts receivable aging as though the customer were simply late.
This distinction produces a better collection process. The accounting aging clock starts from the invoice date. The operational collection clock starts when the customer has a valid invoice that entered its payment process. Both dates matter, and neither should replace the other.
Give reviewers the right information
Reviewers delay drafts when they must search elsewhere for context. A useful billing package contains the proposed invoice, prior billed amounts, unbilled work, relevant fee limits, and any open billing instructions. It also highlights changes since the previous review rather than asking a partner to reread the entire engagement history.
Approval should be explicit. Silence is not approval. At the same time, escalation rules should prevent drafts from waiting indefinitely because the normal reviewer is unavailable. Defined alternates matter in firms where a small number of senior people approve most invoices.
Finance should also record why a draft changes. Common reason codes include scope clarification, time transfer, fee adjustment, missing support, and customer instruction. Over time, those codes show where the process repeatedly breaks. A high volume of time transfers points to engagement setup or time-entry problems. Repeated missing purchase orders point to weak onboarding controls.
Connect billing and collections without merging them
Billing and collections need shared information, but they are not the same activity. Billing establishes a valid receivable. Collections manages the customer’s path to payment.
The accounts receivable team should receive the invoice, submission evidence, billing contact, acceptance status, and any known dispute. Without that handoff, collectors waste time asking whether an invoice was sent correctly. Worse, they may press a customer for payment on an invoice that never passed the customer’s validation rules.
A managed finance team embedded in the firm’s environment can own these handoffs end to end while preserving the firm’s existing approval authority. The work remains visible. Responsibilities remain defined. Exceptions reach the people equipped to resolve them.
Build the process around exceptions
Most invoices should move through a standard route. Management attention belongs on the exceptions: work held beyond policy, drafts returned repeatedly, rejected portal submissions, and invoices without a confirmed processing status.
Transformation & Advisory work starts by tracing those exceptions to their source. The answer may be a poorly designed engagement setup form, unclear approval rights, or a cutoff that allows records to change after drafting. The resulting roadmap should specify controls, ownership, and reporting before proposing new tools.
If unbilled work is growing or invoice delays are difficult to explain, an Elim Financials consultation can map the handoffs and identify the first operational changes worth making.