Read the rejection code before the invoice
Open the rejection notice and read the code, the message, and the affected line before returning to the invoice. A rejection often names a specific field or rule, and that detail determines whether the fix is clerical or substantive. Starting with the whole invoice encourages a broad rewrite that introduces new defects. Write the rejection code at the top of the triage note so the next reviewer sees the same starting point.
Separate the portal's technical response from the client's billing objection. A missing invoice number, an invalid timekeeper identifier, or an unsupported file format is a technical defect. A challenge to a charge, a rate, or a narrative is a billing decision that belongs to an authorized owner. The assistant can prepare evidence for both, but only one category can be corrected without approval.
Classify the rejection by owner
Assign each rejection to one of four owners: the assistant, the billing manager, the timekeeper, or the client contact. The assistant owns formatting and data-completeness fixes that follow a written rule. The billing manager owns guideline interpretation, rate questions, and client communication. The timekeeper owns narrative corrections that require knowledge of the work performed. The label should reflect the decision the item needs, not the person who noticed it first.
Put the owner's name or role in the triage note before any correction begins. An unassigned rejection tends to bounce between people while the resubmission deadline approaches. If the owner is unavailable, name the backup and the date the item was handed over. Ownership should be visible even when the answer is still unknown. The note should survive a shift change and a planned vacation.
Fix line-level defects first
Correct the smallest set of fields that caused the rejection before touching anything else. A wrong matter number should not trigger a rewrite of the narrative, and a missing task code should not reopen the rate. Line-level fixes are easier to verify and less likely to disturb approved content. After each fix, re-read the rejection message to confirm the correction actually addresses it.
Keep a before-and-after note for every changed field, including the old value and the new value. The note lets a reviewer confirm that the change is limited to the defect. It also helps the next rejection investigation if the same field fails again. A clean change record is more useful than a polished invoice with no trace of what was corrected.
Preserve the original submission record
Save the original submission file, the rejection notice, and the timestamp before editing anything. The original record is the only proof of what the client received and when. If the portal overwrites the submission, export a copy to the approved matter folder immediately. Never rely on a screenshot alone when the underlying file is available.
Record the portal's rejection identifier and the resubmission deadline in the same note. That information connects the technical event to the billing cycle and prevents a late response. If the client requests a different format for the resubmission, save that instruction with the original record. The history should show why the second submission differs from the first.
Write a resubmission note a reviewer can follow
The resubmission note should state the rejection reason, the change made, the evidence attached, and the remaining risk. Keep it to a few lines so a reviewer can read it in under a minute. Avoid saying that the issue was fixed without naming the field and the new value. A precise note lets the reviewer approve the resubmission without reconstructing the whole event.
If the correction required a judgment from an attorney or billing manager, quote the approval in the note. Include the approver's role and the date, but do not paste privileged content into the portal. For a charge that remains disputed, state that the resubmission preserves the firm's position and identifies the owner handling the discussion. The note should never imply a settlement or concession that no one approved.
Set the appeal window and evidence packet
Some rejections can be corrected and resubmitted, while others require an appeal with supporting evidence. Identify the client's appeal window and the evidence the portal accepts before drafting anything. Typical evidence includes time-entry detail, matter authorization, or a prior written approval. Missing the window can convert a correctable defect into a write-off. Check the portal help page or the client guideline for the current rule before assuming the window is generous.
Build the evidence packet as a small set of labeled files rather than one large attachment. Name each file for the field or line it supports so the reviewer can match evidence to the objection. Keep a copy of the packet in the matter record after submission. If the appeal is denied, the same packet explains what was argued and what remains unresolved.
Avoid resubmitting the same defect twice
Before resubmitting, compare the new file against the original rejection message and the portal's validation rules. A second rejection for the same field usually means the correction addressed a symptom rather than the rule. Check the field format, the allowed values, and the client-specific configuration. If the rule is unclear, ask the portal support contact before sending another version.
Track repeat rejection codes by client, matter, and timekeeper so patterns become visible. A code that appears across many matters may point to a template or integration problem rather than individual mistakes. Share the pattern with the billing manager and the system owner, not only with the assistant who fixed the latest instance. Prevention is cheaper than another round of resubmission.
Close the rejection with a prevention note
After the invoice is accepted, write a short prevention note in the matter record or the team log. State the root cause, the fix, and the check that should catch it next time. If the fix changed a template, a matter field, or a client instruction, link to that change. A rejection that is closed without a prevention note is likely to return in the next cycle.
Review the week's rejections together and look for one process change worth making. The change might be a new pre-submission check, a clearer matter opening step, or a refreshed guideline summary. Assign an owner and a review date so the improvement does not depend on memory. Over time the rejection log becomes a record of system learning rather than a list of individual errors.
Common questions answered
Should the assistant ever correct a charge without approval? No, a charge correction that changes the amount or the client's obligation requires the authorized owner. The assistant may prepare the correction and attach the evidence for review. The approval should be recorded before resubmission. Formatting and completeness fixes can follow the written rule without a separate charge decision.
What belongs in the triage note? Include the rejection code, the affected line, the owner, the correction made, and the evidence attached. Add the portal deadline and the resubmission identifier. Keep the note short enough to read during a live review. The goal is a traceable decision, not a narrative of everything that happened.
How do we stop repeat rejections? Group rejections by code and by client, then look for a shared cause in the template, the matter setup, or the guideline summary. Fix the cause rather than coaching each instance. Track whether the same code returns in the next cycle. A weekly review of the pattern is more useful than a monthly count.
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


