Automated Matter Numbering: Designing the Protocol

Your invoices, reports, and finance exports only line up if every matter has one reliable identifier. How automated matter numbering works, and the governance rules that keep the IDs trustworthy.

Automated matter numbering is the practice of letting your legal platform assign a unique identifier to every matter at the moment it is created, and then using that identifier as the single key that links invoices, tasks, documents, and reports to the matter. Nobody types it, nobody chooses it, and no two matters ever share one. That one decision removes a whole class of errors from eBilling, finance reporting, and data migration.

The identifier is simple. The protocol around it is where the design work sits: how the system ID relates to the names people use, how law firms quote it on invoices, how it travels to finance, and how legacy numbers map across.

What is automated matter numbering?

Automated matter numbering is the system-controlled assignment of a unique matter ID at creation, used as the stable technical reference for everything connected to that matter. People find matters by name, type, or business unit, and the system relates records through the ID.

Manual numbering usually starts as a spreadsheet of sequential numbers or a format such as year, practice code, and sequence. It works while one person maintains it. Once several people open matters, duplicates, skipped numbers, and typos appear, and every one of them breaks a link between a matter and its invoices.

Why should matter IDs be system-generated?

Matter IDs should be system-generated because uniqueness, consistency, and speed are guaranteed by the platform. Each benefit removes a recurring cleanup task from legal operations.

  • Guaranteed uniqueness. The platform never issues the same ID twice, so duplicate matters with the same number cannot occur.
  • No formatting drift. Every ID follows the same format, so reports, filters, and integrations behave predictably.
  • Immediate availability. The ID exists the moment the matter is saved, so firms can be engaged and invoices routed without waiting for someone to issue a number.

How does automated matter numbering work in Onit SimpleLegal?

Automated matter numbering in Onit SimpleLegal assigns a unique Client Matter ID to each matter when it is created, and that ID connects the matter to its invoices. Matter IDs in SimpleLegal are system-generated and numeric only.

The Matter ID is also available as a numeric field in SimpleLegal reporting, which makes it a reliable key for joining matter data with vendors, invoices, and spend. One timing detail matters for users: SimpleLegal’s out-of-the-box Matter Analytics report refreshes once every 24 hours, so a matter created this morning may only appear in that report tomorrow. Tell users this during training to save a round of support tickets. SimpleLegal is Onit’s ELM platform for mid-market legal departments, combining matter management with eBilling and reporting.

Should a legal matter number carry meaning?

A legal matter number works best as a plain technical key, with meaning carried in separate fields that users can read and filter. Packing practice area, year, or region into the ID creates numbers that become wrong when the matter changes.

  • System ID as the key. Use the generated ID for every link between records and every integration, and never edit it.
  • Descriptive matter name. Put the business unit, counterparty, or subject in the matter name, following a short naming convention such as “Business unit, counterparty, subject.”
  • External references in their own fields. Store purchase order numbers, court case numbers, and ERP project codes in dedicated fields where they can be searched and reported on.

A matter that moves from one practice area to another keeps its ID and simply gets a new practice area value. With a meaningful number, the same move leaves a misleading code on every invoice.

How do matter IDs connect invoices to the right matter?

Matter IDs connect invoices to the right matter when law firms quote the exact ID on every invoice and the eBilling platform validates it before the invoice moves to review. The ID is the field that tells the system which matter, budget, and reviewer an invoice belongs to.

  • Give firms the ID at engagement. Send the matter ID in the engagement confirmation and make it visible in the firm portal.
  • Validate on submission. Reject or hold any invoice with a missing or unknown matter ID, with a clear reason the firm can act on.
  • Report orphan invoices. Track invoices without a valid matter link and aim for zero at month end.

LEDES invoice files carry a client matter ID on every line, so a firm’s billing system needs the correct ID set up once per matter. The format is strict, since LEDES 1998B is a pipe-delimited format containing 24 fields, and a wrong ID in one field sends the whole invoice to the wrong place. Outside counsel billing guidelines should state exactly how firms reference matters on invoices, which turns the rule into a contractual expectation.

How should matter IDs flow to finance and other systems?

Matter IDs should flow to finance, accounts payable, document management, and reporting systems as the shared reference for each matter, with no system inventing its own number. When every system uses the same ID, spend reconciles cleanly and nobody maintains a translation spreadsheet.

Pass the ID in every integration payload and store it in a dedicated field on the receiving side. Where finance needs its own cost center or project code, hold that code as an attribute on the matter and send both values together. Agree which system creates matters, usually the ELM platform, so finance never creates a matter record the legal team cannot see. Integrating ELM with finance and ERP systems depends on agreeing one shared matter reference, and the matter ID is that reference.

How do you handle legacy matter numbers during migration?

Legacy matter numbers are handled during migration by storing them as a reference field on each migrated matter while the new platform assigns its own system ID. Users and firms can still search by the old number, and the new ID becomes the key from go-live.

  • Keep the legacy number searchable. Load it into a dedicated “Legacy matter number” field on every migrated matter.
  • Build a mapping table. Produce a complete old-to-new ID list for finance, document management, and outside counsel.
  • Clean duplicates first. Resolve legacy numbers used for two matters before loading, since the new platform will treat them as separate records.
  • Notify firms early. Send each firm its old-to-new mapping two to four weeks before the first invoice cycle on the new platform.

Most departments migrate open matters plus two to three years of closed matters. Rushed legacy data migrations create problems that surface for months after go-live, and mismatched matter numbers are among the first to appear on invoices.

Which governance rules protect matter IDs after go-live?

Governance rules protect matter IDs by keeping the system ID untouched, preventing parallel numbering schemes, and controlling who can see matter data. These rules belong in your platform administration guide.

  • Never overwrite the system ID. Treat it as permanent, including when a matter is renamed, transferred, or reopened.
  • Retire manual numbers. Stop issuing numbers from spreadsheets after go-live, so two competing numbers never circulate.
  • Restrict confidential matters. Apply role-based access where a matter’s name or existence is itself sensitive, since IDs appear in reports and exports.
  • Review orphan records monthly. Check invoices, tasks, and documents that lack a valid matter link, and fix the cause at the source.

How do you test matter IDs before go-live?

Matter IDs are tested before go-live by creating matters through every route your design allows and confirming each one receives a valid, unique ID that flows correctly to invoices and reports. Fifteen to twenty-five test cases usually cover it.

  • Every creation route. Test direct creation, request-to-matter conversion, and bulk loading, and confirm each matter gets a valid ID.
  • Invoice validation. Submit test invoices with a correct ID, a wrong ID, and no ID, and confirm each behaves as designed.
  • Reports and integrations. Confirm the ID appears correctly in reports and in data sent to finance, allowing for any scheduled report refresh.

Ask five to ten of your highest-volume firms to submit a test invoice during user acceptance testing. Legal analytics dashboards are only as reliable as the matter data underneath them, and reporting is still largely manual: a 2025 survey of in-house legal teams found 77 percent still handle all or part of their reporting manually.

Conclusion

Matter numbering looks like a small configuration detail, and it shapes the reliability of every invoice, report, and integration your legal department runs. Let the platform generate the ID, keep meaning in names and dedicated fields, give firms the ID at engagement and validate it on every invoice, and carry legacy numbers as searchable references. Then protect the protocol with simple governance and a monthly orphan check, and your matter data will reconcile across legal and finance from the first billing cycle.

How Basla can help

Basla provides delivery teams for enterprise legal management and eBilling software implementation, covering legal technology consulting, business analysis, matter data design, legacy matter migration support, invoice validation and eBilling configuration, finance integration support, testing, documentation, and hypercare after go-live. The team designs the matter identification protocol with your legal and finance leads, builds the legacy mapping, and tests every creation route and invoice path before go-live.

Basla has delivered matter management and eBilling across more than ten global jurisdictions, where consistent matter identification kept invoices, budgets, and reporting aligned across regions.

Frequently asked questions

What is automated matter numbering?

Automated matter numbering is the system-controlled assignment of a unique ID to every legal matter at creation. The ID links the matter to its invoices, tasks, documents, and reports, and it is never typed or edited by users.

Does Onit SimpleLegal generate matter numbers automatically?

Onit SimpleLegal generates a unique Client Matter ID automatically for each matter, and that ID connects the matter to its invoices. SimpleLegal Matter IDs are system-generated and numeric only.

Should matter numbers include the practice area or year?

Matter numbers work best without practice area or year codes, because those details can change during the life of a matter. Keep them in separate fields and in the matter name.

What happens to old matter numbers after migration?

Old matter numbers should be stored in a searchable legacy reference field on each migrated matter, while the new platform assigns its own ID. A mapping table helps finance and law firms move to the new IDs.

How do law firms know which matter ID to use on invoices?

Law firms know which matter ID to use when the legal department sends it at engagement and makes it visible in the firm portal. Billing guidelines should require the exact ID on every invoice.

Why does a new matter not appear in a SimpleLegal report yet?

A new matter may not appear in SimpleLegal’s out-of-the-box Matter Analytics report yet because that report refreshes once every 24 hours. The matter will show after the next refresh.


*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.*