Distinguish preparation from approval
Preparation includes gathering the time entries, the billing history, the client agreement, and the reason for the adjustment. Approval is the decision that the firm will reduce or waive a charge. The assistant can complete the first part and must route the second to an authorized owner. Keeping the two steps separate protects the client relationship and the firm's revenue.
Describe the assistant's output as a decision packet rather than a decision. The packet should state the proposed adjustment, the basis, the affected invoices, and the approver who is needed. It should also note any alternative the approver might prefer, such as a credit or a payment plan. A well-built packet makes the approval faster without pretending the decision is clerical.
Set thresholds by role and matter risk
A single dollar threshold for every matter is easy to write but often wrong. A small adjustment on a sensitive client may need partner review, while a larger routine correction may sit with a billing manager. Set thresholds by role, matter type, and client risk so the approval level matches the consequence. Write the matrix in plain language and test it against recent examples.
Include a cumulative threshold as well as a per-invoice limit. Several small adjustments across a billing cycle can add up to a material reduction that no single approval captured. The assistant should be able to see the cumulative amount for the matter and route the request when it crosses the limit. A cumulative rule prevents the appearance of splitting a decision into smaller pieces.
Require a reason code and evidence
Every write-down request should carry a reason code, a short narrative, and the evidence that supports it. Common reason codes include a billing guideline conflict, a timekeeping error, a client accommodation, and a collection compromise. The code makes patterns visible, while the narrative explains the specific facts. The evidence should be the smallest set that lets the approver verify the reason.
Do not accept a reason code without the corresponding record. A guideline conflict needs the guideline section, and a timekeeping error needs the entry and the correction. A client accommodation needs the communication or approval that established it. The assistant should return an incomplete request rather than filling the gap with an assumption. The return note should ask for the specific missing item, not for better documentation in general.
Route exceptions before the prebill closes
Write-down requests should reach the approver before the prebill is released, not after the invoice has been sent. A late request can force a credit, a revised invoice, or an awkward client conversation. Build the routing step into the prebill checklist so the assistant cannot close the packet while an approval is pending. The approver needs enough time to read the evidence and decide.
If a client deadline makes the normal route impossible, define an expedited path with a named backup approver. Record why the expedited path was used and who authorized it. Do not let urgency become a reason to skip the evidence or the approval. The exception should be visible in the record so the firm can review whether the process needs to change.
Log every approval with the approver
Record the approver's name or role, the date, the amount approved, and any conditions attached to the decision. If the approver changed the requested amount, record the final amount separately from the proposal. The log should let a later reviewer reconstruct who decided what and on which evidence. A decision without an approver is not an approval.
Keep the log in a system that the billing team and the finance owner can access. A personal inbox is not an approval log because it disappears when the person leaves. Link each entry to the matter and the invoice so the record can be found from either direction. The log becomes the evidence trail for the next audit or client question.
Sample approvals for consistency
Review a small sample of approvals each month and compare the reason, the evidence, and the amount across similar cases. Look for the same reason receiving different treatment or a threshold being applied inconsistently. A sample of five to ten decisions is often enough to reveal a pattern. Share the findings with the approvers without turning the review into a blame exercise.
When the sample shows disagreement, clarify the rule or the evidence standard rather than retraining everyone on general principles. If two approvers read the same guideline differently, the guideline summary needs a worked example. If one approver consistently asks for more evidence, the packet template may be missing a field. Fix the system that produced the variation.
Revisit limits after a pattern appears
Review the thresholds when the volume, the client mix, or the firm's policy changes. A limit that fit a small practice may be too high when the billing team grows or when a client adds a new guideline. Use the approval log to see where requests cluster and where approvals take too long. Adjust the matrix with the responsible partner rather than by convenience.
Document the reason for each change and the date it takes effect. Tell the assistants which requests move to a new approver and which evidence requirements changed. A threshold update that is not communicated will be applied unevenly. The policy stays usable when the change history is as visible as the current matrix. Keep the old matrix available so a reviewer can see what applied to an earlier invoice.
Common questions answered
Can an assistant approve a small write-down? Only if the firm's written policy explicitly delegates that authority to the role. Preparation and approval are different acts, and a small amount does not automatically make a decision clerical. The approval should be recorded with the approver and the evidence. When the policy is silent, the assistant should route the request.
What evidence should accompany a request? Include the affected time entries or invoice lines, the client guideline or agreement, and the reason for the adjustment. Add any prior approval or communication that supports the request. Keep the packet small enough for the approver to review. Missing evidence should return the request to the preparer.
How do we prevent split approvals? Track a cumulative amount by matter and billing cycle, not only a per-invoice amount. Route the request when the cumulative total crosses the threshold. Review the log for clusters of small adjustments that share a reason. A cumulative rule makes the pattern visible before it becomes material.
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


