Choose the fields billing cannot close without
Start with the fields that block a prebill or an e-billing submission when they are missing. Typical examples include the client entity, the matter number, the billing contact, the rate schedule, and the timekeeper assignment. Add any client-specific field that the portal validates, such as a purchase order or a matter identifier. The audit should focus on fields with a known downstream consequence.
Separate mandatory fields from useful fields so the audit does not become an endless cleanup. A missing marketing code may matter to the firm, but it should not hold a billing close. A missing billing contact or rate can stop an invoice. Rank the fields by their effect on the current cycle and review the rest on a slower cadence.
Run the check before the prebill cycle
Schedule the field audit before the prebill cycle begins, not during the final review. Early detection gives the matter team time to correct a record without delaying the invoice. A short audit window also makes it easier to compare the same fields across matters. Waiting until the draft invoice exists turns a data fix into a billing emergency.
Publish the audit date and the fields being checked so matter teams know what to expect. Send a reminder to the owners of matters with open exceptions. If a correction requires a partner decision, name the deadline before the prebill locks. A predictable schedule reduces the number of last-minute requests. A short reminder with the field list and the deadline is usually enough.
Compare the matter record to the engagement letter
Check the client entity, the matter description, the fee arrangement, and the billing contact against the engagement letter. A record that has drifted from the agreement can produce an invoice the client did not authorize. Pay particular attention to entities with multiple subsidiaries or matters with a shared billing contact. The engagement letter is the source of truth for the commercial terms.
When the record and the letter differ, do not correct the record from memory or from a prior invoice. Route the discrepancy to the owner who can confirm the current terms. Record the question and the answer with the date. A field audit is only useful if it resolves ambiguity rather than replacing one assumption with another.
Flag missing client billing contacts
A missing or outdated billing contact is one of the most common reasons an invoice stalls after it leaves the firm. Confirm the contact name, email, phone, and any portal requirement before the close. If the client uses a shared accounts payable address, record it alongside the relationship contact. The invoice should have a clear destination and a person who can answer a question.
Check whether the contact has changed since the last invoice and whether the client requires a copy to another address. A new contact may need to be introduced before a large invoice arrives. For clients with strict submission rules, confirm that the contact is authorized to receive the invoice. A correct contact field prevents a collections problem that looks like a billing problem.
Check rate and timekeeper assignments
Confirm that each timekeeper assigned to the matter has a rate that matches the current agreement or rate notice. Look for timekeepers who transferred from another matter, because their prior rate may follow them by mistake. Check the effective date of any rate change and whether the client approved it. A rate error can invalidate an otherwise clean invoice.
Review the matter's timekeeper list for people who should no longer bill to it. A departed timekeeper or a reassigned associate can create entries that are difficult to support later. Confirm that new timekeepers have the required client approval before they record time. The audit should catch the assignment before the prebill, not after the client questions it.
Catch duplicate or retired matter numbers
Search for duplicate matter numbers, reopened matters, and records that were retired but still receive time. A duplicate can split the billing history and make a balance look wrong even when the underlying work is correct. A retired matter that still accepts time can produce an invoice the client did not expect. Resolve the record before the entries are rolled into the prebill.
When two records appear to describe the same matter, compare the engagement letter, the client entity, and the billing history before merging anything. A merge can destroy the audit trail if the records represent different engagements. Route the decision to the matter owner and document the resolution. The goal is a clean billing record, not a tidy list at any cost.
Give the owner a short correction list
Send each matter owner a short list of the fields that need attention and the reason each one matters. Avoid a full export of every field, because the owner will not know where to start. Group corrections by owner and deadline so the work can be completed in one pass. A focused list is more likely to be acted on than a general data-quality reminder.
Include the source the owner should use to confirm the correction, such as the engagement letter or the client portal. Ask for the corrected value rather than a note that it will be handled later. If the owner cannot resolve the item before the deadline, record the escalation path. The audit closes when the blocking fields are resolved or formally deferred.
Record what changed and why
Keep a change log for the fields corrected during the audit, including the old value, the new value, and the person who confirmed it. The log supports the next audit and helps explain a billing difference if a client asks. It also shows whether the same fields fail every month. A repeated failure points to a matter-opening or integration problem rather than individual carelessness.
At the end of the close, review the log for one systemic fix worth making. The fix might be a required field at matter opening, a validation rule in the billing system, or a clearer handoff from the engagement team. Assign an owner and a review date. The field audit becomes valuable when it reduces next month's correction list.
Common questions answered
How many matters should the audit cover? Cover every matter that will be billed in the cycle, using a field-level check rather than a full manual review. If the population is large, prioritize matters with new clients, rate changes, or prior rejections. The audit should be repeatable and scoped to fields that affect billing. A sample can supplement the check but should not replace it for blocking fields.
Who fixes a missing field? The matter owner or the team that maintains the client record should fix it, depending on the field. The billing assistant can flag the gap and prepare the correction, but should not invent a client entity or rate. Record the owner and the deadline. The audit is a detection and routing process, not an authorization to change terms.
What if the correction cannot be made before close? Document the deferral, the reason, and the person who accepted the risk. Hold the affected invoice if the missing field would prevent a valid submission. Do not release a prebill with a known blocking defect merely to meet the calendar. The deferral record should be reviewed at the next close.
Put the guidance to work
Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.
Discuss your workflow


