R365 Authority
TRIS | The Restaurant Intelligence Solution • R365 Implementation • 9 min read
How to Build a Chart of Accounts in R365 That Actually Works for a 20-Location Casual Dining Group
The R365 chart of accounts is not a configuration task; it is a strategic decision that determines the accuracy of every report your group will ever produce.
Quick answer
A well-structured R365 chart of accounts for a 20-location casual dining group separates revenue by channel, COGS by category, labor by role, controllable expenses using standardized codes across every unit, and occupancy costs from operating expenses. It should contain between 80 and 120 accounts, be built at the entity level within R365's location hierarchy, and include dedicated clearing accounts for intercompany transactions. Building it correctly before go-live takes two to three weeks. Rebuilding it under live conditions takes significantly longer and disrupts every close in the interim.
80–120
Accounts in a well-structured casual dining R365 COA
2–3 weeks
To build and validate a COA correctly before go-live
6 months
Typical lag before a wrong COA structure surfaces clearly
The R365 chart of accounts is the most consequential financial decision a casual dining group makes before go-live, because every report the business produces flows directly through it; your P&L, your prime cost calculation, your location-level comparisons, your consolidated financials for lenders or investors — all of it is only as accurate and useful as the framework underneath it.
In Restaurant365, the chart of accounts is that framework, and most multi-unit groups build it wrong; not wrong in a way that surfaces immediately, but wrong in a way that appears six months later when you try to compare food cost across 20 locations and the numbers do not reconcile. Wrong in a way that produces a monthly close that looks clean but cannot tell you which location is underperforming or why the variance exists.
Related resources from TRIS
What a chart of accounts for a 20-location casual dining group actually needs to do
A chart of accounts built for a 20-location casual dining group needs to accomplish several things at once; it needs to reflect how that specific concept generates and spends money, enable meaningful comparison across every unit, support the financial reporting your leadership team actually uses, and integrate cleanly with your POS, payroll, and vendor data.
That is not a default template task. It is a design exercise, and the distinction matters because the consequences of getting it wrong are not theoretical — they are operational, financial, and compounding in ways that become harder to unwind the longer they run.
For a casual dining group in 2026, revenue separation is a baseline requirement, not an advanced configuration. At minimum, revenue accounts need to distinguish dine-in food sales, dine-in beverage sales, delivery channel sales broken out by platform, catering where applicable, and gift card redemptions.
Blending these into a single food sales line hides channel-level profitability entirely; it makes it impossible to understand margin by order mode, and it obscures the true cost impact of third-party delivery commissions on your COGS percentage. The groups that understand their
delivery margin are the ones that separated it at the account level before they ever ran a period close.
COGS accounts need to separate food cost from beverage cost at minimum, and for casual dining groups with meaningful bar programs, the separation needs to go further. Liquor, beer, wine, and non-alcoholic beverage costs each carry different margin profiles and different theft and waste exposure.
Paper goods and packaging belong in a separate COGS line, particularly for groups with delivery volume; blending them into food cost inflates your theoretical food cost percentage and makes variance analysis unreliable. This is a structural decision that determines whether your operations team can manage by line item or whether they are always managing an aggregate that conceals more than it reveals.
Labor is the largest and most variable cost in a casual dining operation, and a single labor line on the P&L is not useful for a group running 20 locations. The accounts that actually support management decisions separate front-of-house hourly wages, back-of-house hourly wages, management salaries, employer payroll taxes, and benefits; each as a distinct account that can be compared across locations and traced to a specific variance driver.
Without this structure, when a location runs 3 points high on labor cost, you cannot identify whether the problem sits in BOH scheduling, FOH overstaffing, or management salary allocation. You see the number but not the cause, which means you cannot fix it with any precision.
Every casual dining group has a set of operating expenses that location managers can influence; supplies, cleaning, smallwares, repairs and maintenance, marketing, and miscellaneous. These accounts need to be standardized across every location using the same structure and the same codes.
If Location 4 codes a repair to supplies and Location 11 codes the same repair to maintenance, your portfolio-level comparison of controllable costs is worthless. You are not comparing locations; you are comparing coding habits. The standardization of these accounts is what makes manager accountability possible and portfolio benchmarking meaningful.
Rent, property taxes, insurance, and common area maintenance charges are fixed costs; they belong in their own category, completely separate from the expenses managers can influence. Blending occupancy into operating expenses distorts your four-wall EBITDA calculation and makes location-level comparisons misleading in ways that are difficult to spot until someone audits the structure directly.
The multi-location structure R365 needs to make this work
Beyond the account structure itself, a chart of accounts for a 20-location group needs to be built with R365's location hierarchy in mind; accounts configured at the entity level, location codes set up consistently so consolidation runs cleanly, and dedicated clearing accounts for any intercompany transactions such as inventory transfers between locations or management fee allocations.
What the goal actually looks like in practice
The goal is a reporting structure where you can view your full portfolio consolidated, drill into any single location, and see the same line structure on both reports; same categories, same order, same codes. That consistency is what makes comparison possible and makes variance visible the moment it emerges, rather than weeks later in a manual reconciliation exercise.
At TRIS, the chart of accounts is the foundation we build before anything else goes live in R365; not because it is the most technically complex part of implementation, but because everything that comes after depends on it being right.
What breaks when the R365 chart of accounts is wrong
A misconfigured chart of accounts does not produce obvious errors; it produces subtle ones that compound over time. Prime cost calculations run slightly off because labor is missing a component. Food cost percentages inflate because COGS catches expenses that belong in operating costs. Consolidated P&Ls surface line items that cannot be traced reliably back to a source location.
Why catching this problem late is costly
By the time these issues surface clearly, usually during a lender review, an audit, or an acquisition conversation, the data remediation required is significant. Rebuilding a chart of accounts under live operating conditions, across 20 locations, while the business keeps running, is one of the most operationally disruptive interventions a finance team can undertake; it affects every close, every report, and every comparison until the rebuild completes and the historical data reconciles.
The decision that cannot wait
The right time to build the R365 chart of accounts correctly is before go-live. The right partner to build it with is one who has done it at your scale, in your concept type, inside R365, and understands the operational consequences of every structural decision made at the account level.
Sources and further reading
Frequently asked questionsR365 chart of accounts for casual dining groups: what operators need to know
How many accounts should a casual dining restaurant group have in R365?
A well-structured chart of accounts for a 20-location casual dining group typically contains between 80 and 120 accounts. Fewer than that and you lose the granularity needed to manage by line item. More than that and the chart becomes unwieldy for location-level managers. The right number is determined by the reporting questions your leadership team needs answered, not by a default template.
Should every location in a multi-unit group use the same chart of accounts?
Yes, with limited exceptions for concept-specific revenue categories. A standardized chart of accounts across every location is the foundation of meaningful multi-unit comparison. When locations use different structures, even slightly, consolidated reporting becomes unreliable and variance analysis becomes impossible to perform accurately.
Can I import my existing chart of accounts into R365?
R365 allows you to import an existing chart of accounts, and this is often the right starting point. However, the import needs to be preceded by a thorough audit of your existing structure; cleaning duplicate accounts, standardizing categories, and adding restaurant-specific lines that your current system may lack. Importing a flawed chart of accounts into R365 imports the flaws directly.
What is the difference between a chart of accounts and a cost center structure in R365?
Your chart of accounts defines what categories you track; food cost, labor, rent, and so on. Your cost center or location structure in R365 defines where those costs are tracked; which unit, which concept, which entity. Both need intentional design for a multi-unit group. A strong chart of accounts paired with a weak location structure still produces consolidated reporting that is difficult to parse by unit.
How long does it take to build a proper R365 chart of accounts for a 20-location group?
Building and validating a chart of accounts for a 20-location group typically takes two to three weeks when done correctly; including POS mapping, payroll integration alignment, and location hierarchy configuration. Groups that compress this into three to four days almost always rebuild it within six months, which is significantly more disruptive and expensive than doing it right the first time.
TRIS | The Restaurant Intelligence Solution
Building your R365 chart of accounts before go-live?
TRIS has built and validated R365 chart of accounts structures across more than 400 locations in QSR and casual dining groups. If you are pre-implementation, mid-implementation, or rebuilding after go-live, that is the conversation we are built for.
Talk to TRIS →
