Legal entity register template: the fields to track before your spreadsheet gets too complex
A spreadsheet can be a reasonable starting point for a small portfolio. The important part is choosing fields that support real governance and reporting rather than creating another list that nobody knows how to maintain.
Start with a better legal-entity register and know when it has outgrown the spreadsheet.
Includes a recommended field list and governance rules you can adapt.
Key takeaways
- Keep one row per legal entity for master identity fields.
- Do not flatten multi-valued relationships such as directors and shareholders into endless columns.
- Add source, owner and last-reviewed information early.
- When relationships, history and workflows become important, move beyond a single spreadsheet.
Minimum legal entity register fields
This practical template is the spreadsheet counterpart to the Legal Entity Master Data guide; use the separate guide for field stewardship, authority and governance.
| Field | Why it matters |
|---|---|
| Registered legal name | Primary legal identity |
| Registration / company number | Stable identifier for registry and duplicate matching |
| Legal Entity Identifier (LEI), where applicable | Useful standardized identifier for entities that have or require an LEI |
| Country and jurisdiction | Legal and compliance context |
| Legal form / entity type | Reporting and obligation logic |
| Status | Active, dormant, dissolved or other lifecycle state |
| Incorporation date | Reference and reporting |
| Entity owner | Accountability |
| Last reviewed date | Data currency |
This page is deliberately tactical: it gives you a usable register artifact. For field stewardship, source authority, ownership and governance rules, use the separate Legal Entity Master Data guide.
Useful extended fields
Add fields based on real use cases rather than collecting everything possible.
- Tax IDs and fiscal year-end.
- Registered office and effective date.
- Direct parent entity.
- Responsible Legal / Secretariat contact.
- Local accounting-framework / GAAP classification where relevant.
- Registered agent / local service provider.
- Next material obligation and due date.
- Data source / source document reference.
- One named owner for the master file.
- Controlled editing rights.
- Defined field values for status, country and entity type.
- Change log or review process for important updates.
- No emailed copies treated as current masters.
- Regular review date and clear exception list.
Signs the spreadsheet is becoming the problem
Watch for multiple versions, directors encoded as Director 1 / Director 2 columns, manual ownership calculations, separate deadline trackers, links to documents nobody can access, recurring reconciliation before every report, or inability to answer point-in-time questions.
Conditional formatting before migration
Even a spreadsheet can surface stale review dates before you move to a dedicated platform. In Excel, apply conditional formatting to the Last Reviewed Date column using a simple review cadence. The downloadable EntityOS template now includes an example:
- Red: last reviewed more than 365 days ago.
- Amber: approximately 9–12 months since review.
- Green: reviewed within approximately the last 9 months.
Use thresholds that match your organization’s policy. The purpose is to make stale records visible — not to imply that a green spreadsheet proves legal compliance.
Prepare the register for future migration
Use stable column names, avoid merged cells, keep one value per cell where possible, maintain jurisdiction and status dictionaries, and preserve unique identifiers. Most importantly, record where important values came from.
registered_name, registration_number, country, jurisdiction, entity_type, status, incorporation_date, tax_id, fiscal_year_end, registered_office, direct_parent, entity_owner, last_reviewed_date, source_reference
If you share or adapt this field list, please link to the canonical page so users can see the governance notes and updated version.
Questions
Can Excel be used as a legal entity register?
Yes for a small and relatively stable portfolio, provided access, ownership and review are controlled. Complexity increases quickly when relationships, history and workflows are added.
Should directors be columns in the entity register?
Avoid Director 1, Director 2 and similar patterns. People-to-entity appointments are relationships and are better kept in a separate structured table or system.
What is the most important field in an entity register?
There is no single field, but a stable registration identifier plus jurisdiction is critical for distinguishing entities reliably.
Should tax IDs be stored in the entity register?
They are often useful cross-functional data, but access and ownership should reflect the sensitivity and responsibility model in your organization.
How often should an entity register be reviewed?
Use a defined review cycle and event-driven updates. Highly active entities may need more frequent review than dormant or stable entities.
Prepared by the EntityOS Editorial Team for operational education. Regulatory references are checked against primary sources where cited. Jurisdiction-specific legal, tax and regulatory decisions should be reviewed by qualified advisers.
This resource is general operational information, not legal, tax, accounting or regulatory advice. Requirements vary by jurisdiction and facts. Use qualified advisers for jurisdiction-specific decisions.