Legal entity mapping is the configuration in an ELM that ties every matter and invoice to the legal entity responsible for paying it, then applies that entity’s ledger, coding, approval, and tax rules before the invoice goes to accounts payable. A group with a US parent, a UK subsidiary, and a Singapore holding company has three sets of books, three tax registrations, and often three approval chains, and the mapping decides which one each invoice belongs to. When the mapping is right, finance posts legal spend without touching it. When it is loose, invoices land in the wrong ledger and someone spends close week moving them back.
What is legal entity mapping in an ELM?
Legal entity mapping in an ELM is a maintained reference that links each legal entity your department bills to its ERP instance, company code, currency, tax registration, and approval owner. Matters and invoices point to an entity. The map supplies everything that entity requires at posting time.
The map is small and changes rarely, which makes it easy to neglect. A department billing to 12 entities might have 12 rows and touch them twice a year. Those 12 rows still decide where every dollar of outside counsel spend lands, so they deserve an owner and a change process.
Why does the legal entity matter so much for legal invoices?
The legal entity matters for legal invoices because it decides whose books, taxes, and statutory reports carry the cost.
- Separate ledgers. Each entity keeps its own accounts. An invoice posted to the wrong entity misstates two sets of books at once and needs an intercompany correction to fix.
- Tax obligations. VAT, GST, and withholding rules follow the entity being billed. A law firm invoice addressed to the UK subsidiary carries different tax treatment from the same work billed to the US parent.
- Audit and reporting. Auditors test that costs sit with the entity that incurred them. Legal spend booked to a convenient entity is a recurring audit finding.
The matter owner usually knows which entity the work serves, and that knowledge has to reach the invoice.
What belongs in a legal entity map for an ELM?
A legal entity map for an ELM needs five fields per entity, and finance should confirm every value before go-live.
- Entity code and registered name. The code finance uses and the exact legal name law firms must put on their invoices.
- ERP instance and company code. Which ERP the entity posts to and its company code or operating unit there, which vendor ID mapping uses to pick the firm’s vendor record.
- Functional currency. The currency the entity’s books are kept in, which drives conversion on foreign-currency invoices.
- Tax registration. The VAT, GST, or other registration number, plus whether invoices to this entity normally carry tax.
- Approval owner. The finance or business contact who approves spend above threshold for that entity.
Keep the map in one place and sync it into the ELM, since every field in an ELM finance integration needs exactly one owning system.
Should the legal entity be set on the matter or on the invoice?
The legal entity should be set on the matter as the default, with an invoice-level override only for the occasional bill addressed to a different entity.
Make the entity a required field at matter creation, chosen from the synced list, so every invoice on the matter inherits it with no reviewer action. A firm sometimes bills a specific piece of work to a sister entity, for example a local filing handled for the regional subsidiary, and then the reviewer changes the entity on that invoice and records why.
Lock the matter entity once invoices have posted, and require a documented change process after that. Overrides should stay rare, typically under 5 percent of invoices. A higher rate points to matters opened under the wrong entity. Across accounts payable generally, a 2026 benchmark survey found the average invoice exception rate is 19.9 percent, against 11.8 percent for the best-performing teams.
How does cost code filtering by legal entity work?
Cost code filtering by legal entity limits the GL accounts and cost centers a reviewer can choose to those valid for the invoice’s entity.
- GL accounts. Each entity’s chart of accounts may differ, especially across ERPs. The ELM shows only accounts that exist and are open for that entity.
- Cost centers. Cost centers belong to entities. Filtering prevents a UK cost center from being charged on a US entity invoice, which the ERP would reject.
- Dependent picklists. Selecting the entity narrows the cost center list, and selecting the cost center can narrow the GL accounts further, so reviewers choose from a short valid list.
In a department with 8 entities and 300 cost centers, a reviewer typically sees 20 to 40 relevant choices, which is faster and far more accurate.
How should approval rules differ by legal entity?
Approval rules should differ by legal entity wherever thresholds, signatories, or segregation requirements differ between entities.
- Currency thresholds. A $50,000 approval threshold in the US parent may be set at £40,000 in the UK entity. Store thresholds per entity in its own currency.
- Local signatories. Some subsidiaries require a local director or finance lead to approve spend above a set level. The approval chain adds that person only for that entity.
- Segregation of duties. The person who opened the matter or changed its entity should not be the final approver on its invoices. Apply this check per entity.
Test approval chains entity by entity with real user accounts. Permission gaps often show up only for the smaller entities.
How do tax rules change the invoice by legal entity?
Tax rules change the invoice by legal entity because VAT, GST, and withholding depend on where the billed entity is registered and where the firm provides the service. A firm billing a UK entity from a UK office normally charges VAT. Platforms model both sides of that relationship: in Unity, the vendor’s tax authority shows where an invoice comes from, and the legal entity’s tax authority identifies who the vendor is billing. The same firm billing a US entity usually does not. Cross-border billing between registered businesses often falls under reverse charge rules, where the recipient accounts for the tax. Your eBilling VAT tables should hold each treatment your tax team approves.
For legal operations, the practical point is that the firm must address the invoice to the right registered entity name, with the right tax treatment, before review starts. Put the exact entity name and tax registration in each firm’s billing instructions. Reject invoices addressed to the wrong entity early in the ELM, because AP cannot fix a tax invoice issued to the wrong legal person.
What should legal entity mapping validation check before dispatch?
Entity validation should run four checks on every approved invoice before it leaves the ELM, so entity errors stay with legal operations to fix.
- Entity active. The invoice’s entity is active in the map and in the ERP on the posting date.
- Addressee matches. The entity named on the firm’s invoice matches the entity on the matter or override.
- Coding belongs. Every GL account and cost center on the invoice is valid for that entity.
- Currency allowed. The invoice currency is accepted for that entity, with a conversion rule if it differs from the functional currency.
Failures go to a named exception queue with a readable reason. In a stable setup, entity-related exceptions settle at 1 to 2 percent of invoice volume within the first two or three billing cycles. Configure these checks alongside the invoice workflow itself, including which entity and coding fields reviewers can edit.
How do restructurings and new entities affect legal entity mapping?
Restructurings and new entities affect the entity map by changing which entity owns open matters and which entities firms can bill. A new subsidiary needs a map row, ERP setup, cost centers, approval owners, and firm billing instructions before its first invoice arrives. Allow four to six weeks between the decision and the first invoice.
A merger or divestment can move 50 to 200 matters between entities at once. Effective-date the change so invoices approved before the date keep the old entity and later invoices follow the new one, and run the bulk update with finance sign-off. Accruals must move too, because eBilling accrual configuration controls how unbilled legal work reaches the general ledger, and an accrual left in a retired entity reverses into the wrong books.
Conclusion
Legal entity mapping works when the entity is set on every matter, the map is owned by finance and synced into the ELM, and coding, approval, and tax rules follow the entity automatically. Validate every invoice against the map before dispatch, plan entity changes with effective dates, and your multi-entity legal spend will post as cleanly as a single-entity department’s.
How Basla can help
Basla provides delivery teams for enterprise legal management and eBilling software implementation, covering legal technology consulting, business analysis, legal entity and cost code mapping, approval matrix design, integration specifications for AP, validation and exception configuration, testing with finance, documentation, and hypercare after go-live. Basla teams have delivered matter management and eBilling programs across more than 10 global jurisdictions, and Basla has supported legal technology deployed across more than 100 jurisdictions for a global retail organization.
Frequently asked questions
What is legal entity mapping for legal invoices?
Legal entity mapping for legal invoices links each matter and invoice in the ELM to the legal entity that pays for it, along with that entity’s ERP, coding, approval, and tax rules. It makes sure each approved invoice posts to the correct ledger.
Who should own the legal entity map?
Finance should own the legal entity map, because entities, company codes, and tax registrations are finance master data. Legal operations owns the entity assignment on each matter and requests new map rows when the business adds entities.
Can one legal matter be billed to more than one entity?
One legal matter can be billed to more than one entity through a cost split or an invoice-level override. Each entity’s share becomes a separate posting in its own ledger, with coding valid for that entity.
What happens if a law firm addresses an invoice to the wrong entity?
If a law firm addresses an invoice to the wrong entity, the ELM should reject it before review and ask the firm to reissue it. A tax invoice issued to the wrong legal entity generally cannot be corrected by AP.
How do you change the legal entity on an existing matter?
You change the legal entity on an existing matter by effective-dating the change, so earlier invoices keep the old entity and later ones follow the new one. Finance approves the change and moves any open accruals with it.
How many legal entities can an ELM support?
An ELM can typically support dozens of legal entities, and large groups run 20 or more in a single instance. Each one needs a map row, valid cost codes, and an approval owner before its first invoice.
*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.*