Building for multi-entity finance from day one
Here’s a pattern we see constantly: a business starts with one location and picks financial tools designed for single-entity operations. QuickBooks, a basic bank feed, maybe a simple POS integration. It works fine.
Then they grow. A second location. A new brand. A franchise model. Suddenly they need consolidated reporting across entities, intercompany reconciliation, and per-location P&Ls — and every tool in their stack assumes they’re one business with one bank account.
The bolt-on problem
The usual fix is bolt-on multi-entity support: duplicate the single-entity setup for each new entity and aggregate at reporting time. This creates a maintenance nightmare. Every integration needs to be configured N times. Every report needs to be built N times and then manually combined. Every month-end close requires reconciling across N separate books.
Some tools handle this better than others. NetSuite was built for multi-entity. But NetSuite is also a six-figure annual commitment that takes months to implement — overkill for a 15-location restaurant group that just needs to see all their data in one place.
Data model decisions
At Genledger, multi-entity support isn’t a feature we added. It’s a property of the data model. Every event in the system is tagged with an entity identifier from the moment of ingestion. The enrichment graph naturally crosses entity boundaries when transactions do — an intercompany transfer is just an edge between nodes in different entity subgraphs.
This means:
- Consolidated views are just queries without entity filters
- Per-entity views are the same queries with one filter applied
- Intercompany reconciliation is a graph traversal across entity boundaries
- New entities require zero schema changes — plug in the data sources and the entity exists
Why this matters early
If your data model assumes a single entity and you bolt on multi-entity support later, you inherit years of data that wasn’t tagged correctly, reports that need to be rebuilt, and integrations that need to be reconfigured. Starting with the right model means growth doesn’t break your financial infrastructure.
We made this decision on day one because the businesses we’re building for — multi-location operators, franchise groups, holding companies — are multi-entity by nature. The tool should match the business, not the other way around.