An invoice audit trail in legal eBilling is the complete record of what happened to an outside counsel invoice, from the file the firm submitted through every review decision, adjustment, rejection, approval, and payment status. An audit-ready history is one where that record can be pulled together quickly for any invoice, by someone who was never involved in reviewing it. Internal audit, finance, and law firms disputing a reduction all ask the same question: who decided what, when, and why.
What is an audit-ready eBilling history?
An audit-ready eBilling history is an invoice record complete enough that a person outside the review can reconstruct every decision on it without interviewing the reviewers. It covers the legal review, the communication with the firm, and the downstream payment, joined into one traceable chain.
Three groups usually rely on it:
- Internal audit. Auditors sample invoices, often 25 to 60 per review, and test that approvals followed delegated authority and that adjustments had a reason.
- Finance and AP. Accounts payable needs to match the approved amount to what was posted and paid, and explain any difference.
- Law firms. A firm appealing a reduction is asking which rule or reviewer cut the line and on what basis.
Audit readiness is mostly a configuration and process outcome. The platform records events, and your setup decides whether the reason fields, comments, and links are filled in consistently enough to be useful.
What should an invoice audit trail record?
An invoice audit trail should record the original submission, every check and decision applied to it, and its final financial outcome. Missing any one of those links means someone ends up reconstructing the story from email.
- Original submission. The LEDES file or PDF exactly as received, with invoice number, vendor, matter, currency, and submission timestamp.
- Validation results. Which billing rules fired, on which lines, and what each rule did, from rate checks to billing guideline rules.
- Reviewer decisions. Each approval, rejection, adjustment, or payment hold, with the user, date, and comment.
- Payment outcome. AP transmission, posting, and payment status, plus the amount actually paid.
Keep the original file even after corrections. A reviewer comparing the firm’s first and second versions needs both, and an auditor needs proof the first one existed.
How does Onit Unity record invoice review activity?
Onit Unity records invoice review activity in a system-level Activity Log that captures most actions by users and by the system itself. Each entry shows the date and time, the person who acted, the record changed, and a description that includes names, email addresses, and value changes, so an admin can see who adjusted an invoice or a validation rule.
Logging communications matters more than it first appears. A firm that says it never received a rejection notice is disputing a fact, and an emailed notice recorded against the invoice settles it. Such disputes are becoming more common, because billing data from about 400 law firms shows invoice rejection rates climbed from 11 to 18 percent in 2025. Treat comment fields as part of the record too. “Adjusted per guideline 4.2, block-billed entry” is evidence; a blank comment on a 30 percent cut is a question waiting to be asked. These records sit at the center of what legal eBilling software has to provide.
How should adjustments and rejections be documented?
Adjustments and rejections should be documented with the original value, the new value, a reason drawn from a fixed list, and a free-text comment the firm can understand. The fixed list makes reporting possible, and the comment makes the decision defensible.
- Reason codes. Keep a list of 10 to 20 reasons mapped to guideline sections, such as rate above approved rate, unapproved timekeeper, or a vague or block-billed narrative.
- Comments. Require one for any adjustment over a set threshold, for example 500 or 1,000 in your system currency.
- Rejection notices. Record the reason, the reviewer, the date, and the notice sent to the firm.
A rejections report by reason and vendor shows which firms repeatedly break billing requirements, and line-level task codes show where in the work they do it. That only works when reason codes are used consistently, so lock the list and train reviewers on it during go-live.
How are rejected and resubmitted invoices linked?
Rejected and resubmitted invoices are linked when the firm submits the corrected invoice against the original rejected one. Onit’s Counsel Exchange portal links a resubmitted invoice to the original it replaces, so the correction cycle reads as one chain.
That link keeps the correction cycle readable. Without it, an auditor sees two invoices with similar amounts and has to decide whether the department paid twice. With it, the trail shows the rejection reason, the correction, and the second review in order. Check after go-live that firms actually use the resubmission route, since a firm that uploads a corrected invoice as a brand-new submission breaks the chain. A monthly report of near-duplicate invoices from the same vendor and matter, within a 10 percent amount range, catches most of these.
How do you track an invoice through accounts payable?
You track an invoice through accounts payable by reporting on its lifecycle status from receipt to payment. In Onit Unity, invoice statuses run from Received and On Hold through Approved, Rejected, Sent to AP, and Paid.
- Approved but never sent. Invoices stuck between approval and AP transmission for more than five business days usually point to an integration or mapping problem.
- Sent but not posted. These need a check against the ERP, often a missing vendor record, a missing cost center, or a failed PO match on the finance side.
- Partially paid or overpaid. Each one needs an explanation recorded against the invoice, since auditors will ask about every one.
The status values depend on what your finance integration sends back, so confirm during design which statuses return from the ERP and how often. That decision belongs in the design for integrating ELM with finance and ERP systems.
Who should be able to change eBilling records?
Only authorized users with a defined role should be able to change eBilling records, and every administrative change should be attributable to a named person. An audit trail is only as strong as the controls on who can alter what it records.
- Reviewers. Act on invoices assigned to them, within their approval limit.
- eBilling administrators. Change rules, rates, and vendor setup, usually two or three people with a documented change process.
- Overrides. Any reopened invoice, reversed decision, or manual status change should record the user, reason, and timestamp.
Review user roles at least twice a year, and remove access the week someone leaves the team. A former reviewer’s active account is one of the first things an auditor looks for.
How long should eBilling records be kept?
eBilling records should be kept for as long as your legal, tax, finance, and litigation-hold requirements demand, which for many departments means seven to ten years. No eBilling platform sets a universal retention period, so the period is a policy decision for your organization. Check how long system logs last as well, since the Unity Activity Log keeps activities for the past 90 days, and anything needed for longer has to be exported or held elsewhere.
- Retention policy. Agree the period with finance and records management, and document it in the solution design.
- Legal holds. Decide how invoices on held matters are protected from deletion or archiving.
- Exports. Test an export of a full invoice history once a year, so the record stays readable if you change platforms.
How do you test that eBilling history is audit-ready?
You test that eBilling history is audit-ready by picking sample invoices and reconstructing each one’s full story from the system alone. Run it before go-live in the test environment, using at least ten scenarios: a clean approval, an adjustment, a rejection and resubmission, a held invoice, a partial payment, and an administrative override among them. For each, confirm the original file, decisions, comments, emails, link, and AP status are all retrievable. Repeat the exercise after promotion through sandbox-to-production deployment testing, then quarterly on 20 random live invoices. Remember that Onit’s Enhanced Reporting data refreshes once every 24 hours, so a same-day audit query should use the invoice record itself.
Conclusion
An invoice audit trail is ready when anyone can open an invoice and see what was submitted, what each rule and reviewer did, what the firm was told, and what was paid. The platform records most of these events. Your configuration decides whether reason codes, comments, resubmission links, AP statuses, and access controls make the record complete. Settle retention with finance, test reconstruction before go-live and every quarter after, and audit requests become a quick lookup.
How Basla can help
Basla provides delivery teams for enterprise legal management and eBilling software implementation, covering legal technology consulting, business analysis, review workflow and reason code configuration, finance and AP integration requirements, testing, documentation, and post-go-live support. Basla analysts define the audit evidence each invoice must carry, and the QA team runs reconstruction tests that prove it before go-live.
Basla teams have delivered matter management and eBilling programs across more than 10 global jurisdictions, and the delivery bench supports hypercare while the first live invoices move through review and payment.
Frequently asked questions
What is an invoice audit trail in legal eBilling?
An invoice audit trail is the complete record of an outside counsel invoice from submission through review, adjustment, rejection, approval, and payment. It shows who made each decision, when, and why.
Does Onit Unity keep an activity log for invoices?
Onit Unity records most user and system activity in an Activity Log, with the date, the person who acted, the record changed, and a description of the change. Admins use it to see who adjusted an invoice or a validation rule.
How are resubmitted invoices tracked?
A firm resubmits a corrected invoice against the original rejected one, so the platform links the two. The trail then shows the rejection reason, the correction, and the second review in order.
Which payment statuses can legal invoices be tracked through?
Onit Unity tracks invoices through statuses including Received, On Hold, Approved, Rejected, Sent to AP, and Paid. Which payment statuses come back from finance depends on what the integration returns.
How long should legal eBilling records be retained?
Legal eBilling records should be retained for as long as legal, tax, finance, and litigation-hold requirements demand. Many departments set seven to ten years, documented in a retention policy.
How often is Onit’s Enhanced Reporting data refreshed?
Onit’s Enhanced Reporting data refreshes once every 24 hours, overnight Pacific time, while other reports update in real time. For same-day questions, check the invoice record itself.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*