Outside Counsel Accruals for Month-End Close

Outside counsel accruals estimate the cost of legal work performed before period end but not yet invoiced. In a month-end close, the corporate legal or finance team asks each firm for a matter-level accrual statement showing the service period, matter, currency, unbilled fees, unbilled expenses, and any comments needed to judge the estimate. Legal ops or finance reviews the estimate, posts the accrual, and trues it up when the actual invoice arrives.

That is the core of outside counsel accruals month-end close: the business records legal expense in the period the work happened, not only when a bill reaches AP. The firm sees the same activity as work in progress. The buyer sees it as an expense that belongs in the closing month, even though the invoice may land weeks later.

The accrual statement is not an invoice. AP should not pay it, route it for payment approval, or treat it as an open vendor liability in the same way as a bill. It is also not a litigation reserve. A reserve deals with exposure from a claim or contingency; an outside counsel accrual deals with fees and expenses for legal services already performed but not yet billed.

The practical problem is less theoretical than that distinction sounds. A legal department may have one firm sending an Excel WIP export, another sending a PDF by email, another entering an estimate in an ELM portal, and another replying with a single sentence in an email body. Finance still needs one register: matter, period, amount, currency, cost center, review status, and posting decision.

A workable close process therefore has five moving parts. The company requests accruals before close. Firms submit WIP estimates around the first days of the following month. Legal ops or finance extracts the fields into a register. Matter owners or finance partners review the estimates for reasonableness. The controller posts the accrual and later clears the difference when the invoice arrives.

The accrual statement is its own financial document

A law firm accrual statement should be specific enough that finance can post by matter and legal ops can challenge the estimate if it looks wrong. At minimum, each row should identify the client matter ID, matter name, service period, unbilled fees, unbilled expenses, currency, firm contact, and any comment that explains the estimate. Many teams also ask for the firm's matter ID, responsible partner, cost center, and a confidence note where the amount is based on an early WIP pull rather than a final month-end report.

That field set matters because outside counsel spend is material enough to deserve controls. CLOC's 2025 State of the Industry Report, based on responses from 186 organizations, reports median external legal expenditure of $20.6 million among surveyed legal departments and notes that external spend includes outside counsel spend. A month-end accrual process that captures only a single firm-level total leaves too much judgment buried outside the company's ledger review.

Matter-level accrual breakdown extraction is the difference between "Firm A says $85,000" and "Matter 10492 accounts for $62,000 of the estimate because the trial team worked through the final week of the month." The second version supports budget checks, matter owner review, cost center allocation, and later invoice matching. It also gives finance a defensible explanation when the actual bill differs from the estimate.

The statement should include only unbilled work performed in the closing period. If the legal department has already received an invoice that AP has not processed, that is not the same as WIP. It may still affect month-end expense, but it belongs in the pending-invoice workflow, not in the firm's unbilled accrual total. Mixing the two is how teams double count legal spend.

Formats will vary. One firm sends an Excel export from its time and billing system. Another sends a PDF from a partner's assistant. A third submits through a portal. A fourth writes the estimate in an email body because the amount is small. The receiving team should not let those formats define the accounting process. The register schema defines the process; each submission is just evidence feeding it.

Run the monthly request-to-register cycle on a close calendar

The legal spend accrual workflow starts before the month closes. Legal ops or finance should send the request while firms still have time to pull WIP by matter, confirm the service period, and identify any bill already issued for part of the month. The request should specify the submission deadline, required fields, currency convention, and where to send the statement.

A practical calendar looks like this:

• Before period end: send the request and remind firms of the matter-level field set.
• Day 1 or 2 of the following month: firms pull WIP and submit accrual statements.
• Day 2 or 3: legal ops extracts the submissions into the register and marks missing firms.
• Day 3 or 4: matter owners or finance reviewers accept, query, or estimate each material item.
• Day 4 or 5: finance posts the legal-spend accrual to the close package.

The register is the control point. Each row should represent one matter-period estimate, not one email and not one firm invoice queue. Useful columns include firm, client matter ID, matter name, service period, amount, currency, cost center, reviewer, status, query reason, source file, and final posting amount. Once the register exists, late submissions, partial bills, and currency issues become visible exceptions rather than scattered inbox threads.

If the legal department already has a mature ELM portal and panel firms actually use it, the portal path is usually cleaner. It can enforce due dates, capture firm submissions, and export a review file. The harder case is the department with a partial ELM rollout, a spreadsheet close process, or a panel that sends mixed formats anyway.

That is where extraction belongs. Native spreadsheet submissions can be mapped into the register directly, and email-body estimates can be copied into the same register, but PDF statements and scanned attachments still need normalization. A team can use Invoice Data Extraction to extract monthly legal accrual statements into structured data, asking for the matter ID, service period, unbilled fees, expenses, currency, and comments, then download the result as Excel, CSV, or JSON. The product supports large batches of up to 6,000 files, so a panel's first-of-month submission rush does not require a separate template for every firm.

Firms are under timing pressure too. Their finance teams may be closing their own books, and WIP for the final day of the month may not be perfect when the client request arrives. The buyer's process should allow a confidence note or comment field instead of pretending every estimate has the same level of precision.

Review accruals before finance posts them

Collected accruals are not ready for posting until someone has judged whether the amounts make sense. The review does not need to become a second invoice audit, but it should catch estimates that are plainly inconsistent with the matter, the budget, or the work pattern.

Start with the matter budget and burn rate. If a litigation matter has been running at $30,000 per month and the firm submits $140,000 without a trial date, discovery deadline, or staffing change, the reviewer should query it. If a deal matter closed during the month, the accrual should reflect that status rather than assume the same run rate will continue. Prior invoices give another useful check: the accrual should be explainable against recent monthly bills, new work activity, and any staffing shift the matter owner knows about.

Multi-currency legal accrual close needs a written convention. The cleanest approach is for firms to submit in the matter currency and for the buyer to convert at the company's period-end FX rate from a stable internal source. If the firm pre-converts, the register should show both the original matter currency and the converted amount, plus the rate source if finance requires it. Without that discipline, FX differences get mistaken for law firm estimate errors.

Partial invoices create the most common double-counting problem. If a firm issued a mid-month bill for work through May 15, the accrual should cover unbilled work after that date, not the full month's activity. The register should carry a field for "invoice already covers part of period" or a similar note so the reviewer can see why the accrual is smaller than the normal monthly run rate.

The review disposition should be explicit:

• Accept when the amount is plausible and the field set is complete.
• Query firm when matter detail, period, currency, or explanation is missing.
• Estimate when the firm is late but close cannot wait, using prior invoices, matter owner input, and company materiality thresholds.
• Flag for true-up when the amount is usable for close but likely to move next month.

For missing firms, legal-spend accruals follow the same accounting logic as other expense accruals: use the best available evidence rather than ignore a material cost because an invoice has not arrived. The broader mechanics are similar to AP accrual estimation methods for missing invoices, but legal spend needs the matter-level lens because each matter can carry its own budget, owner, currency, and billing pattern.

Post the legal-spend accrual and clear the true-up

After review, finance posts the approved accrual to put the legal expense in the month the work was performed. In plain language, the entry debits legal-spend expense for the relevant matter, cost center, or GL account, and credits a legal-spend accrual liability. The debit records the expense. The credit records that the company expects a later bill or settlement of that estimate.

The posting file should tie back to the register, not to a loose email folder. Each posting line should be traceable to a matter, firm, service period, currency, review status, and source statement. That traceability is what lets AP and finance explain the balance when invoices arrive after close.

When the invoice arrives next month, AP does not simply ignore the accrual and book a fresh expense. The invoice should be matched against the accrual by matter and service period. If the accrual was $40,000 and the invoice for the same period is $42,500, the $2,500 difference is the true-up to expense under the company's policy. If the invoice is lower, the true-up reduces expense. The exact posting mechanics vary by ERP and accounting policy, but the control objective is stable: clear the accrual liability and record the difference transparently.

For teams documenting the accounting pattern, the mechanics are close to invoice accrual and reversal journal entries. The legal-spend wrinkle is that the invoice may include multiple matters, partial periods, expenses, VAT or sales tax treatment, and adjustments from earlier rejected bills. For UK bills where counsel's fees flow through a solicitor invoice, counsel-fee VAT treatment on solicitor bills needs its own evidence trail before AP reclaims tax. Those details determine whether the invoice clears the original accrual cleanly or creates a visible variance.

The invoice-side extraction step matters because the later bill is the evidence that proves or corrects the estimate. Teams that extract legal invoice line items after the accrual clears can compare matter ID, date range, fees, expenses, currency, and narrative patterns against the accrual register instead of relying on invoice totals alone.

Handle late, vague, and repeatedly wrong firm submissions

Late submissions need a defined path before the close calendar starts. A reminder on the due date is not enough if finance must post by day four. Legal ops should set a request date, a due date, and an escalation route through the relationship partner or matter owner. If a material firm misses the deadline, the team should estimate from prior invoices, current matter activity, and matter owner input, then mark the row as estimated rather than hold close open for one response.

Blanket firm-level estimates are a different problem. A single total may be acceptable for a very small panel or one immaterial matter, but it does not support budget review, cost center allocation, or later invoice matching. The response should be firm but operational: ask for a matter-level split, explain that finance posts by matter or cost center, and reserve firm-level totals for immaterial exceptions agreed in advance.

Repeated over-accruals or under-accruals are visible only if the register keeps true-up history. A rolling three-month view of estimate versus invoice can show whether a firm consistently pads WIP, estimates too early, excludes expenses, or misses time entered late in the cycle. The first response is usually a process conversation, not an accusation: ask when the firm pulls WIP, whether partner review happens before submission, and whether timekeepers are entering time promptly near month end.

Rejected e-bills create stale accruals if no one owns the clearing step. A firm may submit an invoice, have it rejected for billing-guideline reasons, revise it, and resubmit after the original accrual would normally have cleared. A buyer-side legal e-bill resubmission workflow keeps the rejected bill tied to the original invoice while AP waits for the corrected version. The register should carry unresolved accruals forward until AP can match a corrected bill or finance can book the true-up.

Rate cards and staffing mix are useful checks when variances repeat. If the matter was staffed by associates in prior months but the accrual assumes partner-heavy work, the estimate may be valid because the matter changed, or it may be based on stale assumptions. The reviewer does not need to audit every time entry at accrual stage. They do need enough information to know whether the variance has a business explanation.

Decide what workflow fits your legal department

The right workflow depends on panel size, submission discipline, and the financial risk of a weak close process.

A mature ELM portal fits legal departments with a larger panel, strong outside counsel guidelines, and enough leverage to require firms to submit accruals inside the system. The advantage is control: due dates, matter lists, reminders, review grids, and export files live in one place. The weakness is adoption. If firms still send side emails or the portal data is incomplete, finance still needs a reconciliation process outside the module.

Spreadsheet plus extraction fits the middle case: enough firms and formats to make manual entry painful, but not enough process maturity or budget to justify a full accruals module. The spreadsheet is not the control by itself. The control is a consistent register schema, source-file reference, review status, and posting decision for each matter-period estimate.

Manual email collection fits only a small, low-risk panel where the amounts are immaterial or the same matters recur with little variance. Even then, the team should avoid inbox-only evidence. Save the submission, keep a register, and record who accepted the estimate.

The implementation sequence should follow the controls finance will rely on at close. Standardize the requested fields. Set a submission calendar. Agree with finance on materiality, FX rates, and true-up treatment. Define the allowed review dispositions before close begins. Keep source-file references so internal audit or the controller can trace each posting line back to the firm submission that supported it.