.jpg)
Multi-Entity Accounting for Restaurant Groups: Clean Books Per Site
Why a Restaurant Group's Books Split by Legal Entity
Multi-entity accounting is how a restaurant group keeps separate legal entities on one reporting structure while each entity still files its own books. Each trading company has its own profit and loss and balance sheet. Stock, invoices and sales have to land in the right one. When they do not, group reporting stops reconciling.
A group of three entities and 12 outlets shows the shape of the problem. Two trading companies hold the restaurants. A third company owns the central kitchen. The food an outlet sells started as a purchase in the central kitchen's books, moved across a legal boundary, and has to show up as a cost in the outlet's books and a sale in the kitchen's. Nothing about that is automatic once the entities are separate.
Supy maps each location to its matching entity in the connected accounting system, so a document knows which books it belongs to before anyone touches it. The group still sees one consolidated view across all three.
How Two Entities Code the Same Cost Differently
The chart of accounts is the first thing to break. As a group adds branches and entities, the same cost category stops carrying the same code everywhere. One entity books packaging to one account, another books it somewhere else, and a consolidated profit and loss can no longer trust its own subtotals.
The drift is quiet. It does not throw an error. It shows up at month-end when two sites that run the same menu report different cost structures, and finance cannot tell whether that is real or a mapping mistake. A partner who onboards multi-branch groups named this as the scalability wall operators hit on standard accounting platforms.
A shared mapping fixes it at the source. Supy posts each entity's invoices and costs against one consistent account structure, so "food cost" means the same thing in every entity's ledger. The group reports on like-for-like categories instead of reconciling three different charts into one.
When a Stock Transfer Becomes a Recharge Invoice
Move stock from the central kitchen to an outlet in a separate company and you have created an intercompany transaction. It needs a recharge invoice: a cost in the receiving entity, a sale in the sending one, each on its own nominal code. A group doing dozens of these a month, re-keyed by hand, loses days of finance time and still posts errors.
In Supy, a transfer between two sites runs through three stages, raised, submitted and received, and the destination accepts it before any stock or cost moves. Because each location already maps to an entity, the transfer carries the recharge with it instead of waiting for someone to write the invoice afterwards. The sending and receiving sides stay in balance by construction.
Operators can also select many documents and post them to the connected accounting system in one action, so a month of transfers and supplier invoices clears in a batch rather than one entry at a time.
Choosing Your Structure: One Entity or Many
Not every group needs separate entities. The right structure depends on whether the legal and tax split is real or just organisational. Run the two options against your own situation before you commit, because unwinding the choice later is expensive.
| Criterion | Single entity, location tags | Separate entities, intercompany |
|---|---|---|
| Legal and tax | One company files once | Each entity files its own return |
| Transfers between sites | An internal move, no invoice | A recharge invoice, cost and sale |
| Consolidation effort | Low, one ledger | Higher, needs eliminations |
| When it fits | Shared ownership, one tax registration | Separate owners, franchises, distinct tax status |
Choose a single entity with per-location tags when one company owns every site and files one return: you get per-site reporting without the intercompany overhead. Choose separate entities when the companies are genuinely distinct, by ownership, franchise, or tax registration, and accept that transfers between them are recharge invoices that have to balance and eliminate at consolidation.
Whichever branch you are in, the fix is the same first move. Map every location to its entity in the accounting system now, so invoices, transfers and sales post themselves to the right books from day one. If you already run separate entities and reconcile recharges by hand at month-end, put that mapping in place before the next close. The restaurant chart of accounts guide covers keeping the codes consistent across them. Supy connects to QuickBooks, Xero, Zoho Books, MYOB, Oracle NetSuite, Wafeq and 75+ other platforms. It shows live sync status per entity, so invoices and credit notes land where they belong without a manual pass.
.png)
.png)
