Map Ingredients to Accounting Categories: Cleaner Restaurant Reporting

Clean Category Reporting Starts With How You Tag Each Ingredient

An accounting category is a reporting bucket you define once, give a code, and attach to every ingredient you buy. Tag each item to one category, and every purchase, waste event and cost figure rolls up to that line on its own. Your food cost then reads by category, by site, in one report instead of a month-end export job.

You decide the categories and which ingredient belongs where. Supy does not guess that a case of tomatoes is produce. You set that link once, or bulk-set it, and after that the roll-up runs by itself. The structure you design is the structure your finance team reads, so mapping ingredients is really the work of deciding how you want to see cost.

Most groups already have the categories in their head. They just live in a spreadsheet tab or a chart of accounts that the inventory system knows nothing about, so every report means re-keying. Mapping the two together once removes that copy step for good.

Design the Accounting Category List Before You Tag Anything

Start with the list, not the items. A category list that mirrors how finance reads the profit and loss statement saves you from re-tagging later. Keep it short enough to stay useful and detailed enough to answer the questions you actually ask about cost.

• Match your profit and loss statement. Name categories the way your accounts already group spend, so the COGS report and the books use the same language.
• Give each category a code. A short code keeps the category stable if you rename it, and it is what the accounting integration posts against.
• Split a category only where you will act on it. Separate seafood from meat if you manage them differently. Do not split produce into twelve lines you will never read apart.
• Agree the list with finance first. Ten minutes before setup beats re-tagging 250 items after the first month-end.

A workable starting list for a mid-size group looks like this.

Eight to ten categories cover most operations. You can add one later without disturbing the items already tagged.

Tag Each Ingredient Once, Then Bulk-Tag the Rest

Tagging is a one-time setup, not a daily task. Open an ingredient, assign its category, and every future purchase of that item inherits the category automatically. Manage the category list and the item tags in the web settings, where you build and edit the structure.

For a list of 250 items, do not tag one at a time. Bulk-tag by supplier, storage area or item type, then fix the handful that do not fit. A new category never means editing every item by hand.

Untagged items are where invoices stall. A supplier invoice arrives, one line has no category or cost centre, and invoice matching cannot post it. The line waits in an exception queue until someone adds the detail by hand. Tag the item once and it clears on its own next time. The same tag that feeds your reports lets automated invoice receiving post straight through.

From Tagged Items to Food Cost by Category

Once items carry categories, the COGS report reads by category across every site, and the per-location view adds a category summary on top. You stop exporting raw lines into a spreadsheet to group them by hand, because the grouping already lives in the data.

Say an eight-site group spends about $420,000 a month on food. Split by category, meat and poultry is $138,000 of that, produce $82,000, and dairy $54,000. Seeing those lines side by side, by site, turns a single food cost percentage into something you can act on. It is the breakdown a restaurant group COGS report should hand you without manual extraction.

The categories also flow into your dashboards and spreadsheet reports, so a finance director filtering restaurant analytics by category sees the same numbers the kitchen does. One structure feeds the daily view and the month-end pack.

Running More Than One Company: Post Each Category to the Right Ledger Account

If your group runs several legal entities, the category link carries further than reporting. Map each site to the right cost centre, and assign every category to a general ledger purchase account in your connected accounting system. Supy posts against the account you choose, aligned to how Xero, QuickBooks or NetSuite expects the data, so the books and the inventory system agree.

This is also what stops stock crossing cost centres from producing variance nobody can explain. When a transfer moves between branches, the category and cost centre travel with it, so the cost lands where the activity happened. For the reporting side of the same setup, see how cost centre reporting splits the profit and loss statement by site and category.

Your First Week

List eight to ten categories that match your profit and loss statement, give each a code, and bulk-tag your top suppliers' items into them this week. Then open one report, the COGS breakdown by category, and check that every line lands where finance expects it. If a category holds items you would never analyse apart, merge it. If one line hides two costs you manage differently, split it. Get that structure right once and every report, invoice and cost centre downstream inherits it.