PRACTICAL RESTAURANT REFERENCE

Restaurant Excel workbooks: turn your records into repeatable checks

Use formula-ready restaurant Excel workbooks for payouts, invoices, contribution, food usage, campaigns, capacity, recipes and outlet comparisons.

By Anurag · Reviewed 17 October 2026

A useful restaurant workbook should answer a question you can act on and show where its answer came from. A payout worksheet should tell you whether a particular bank credit agrees with a particular settlement cycle. A recipe worksheet should show how a purchased pack becomes an ingredient cost per serving. A branch comparison should use matching periods and a consistent revenue definition. Placing several unrelated figures in the same file does not establish those relationships. The work begins with selecting the right records, defining what each amount includes, and keeping the calculation visible.

The downloadable restaurant operations workbook contains eight worksheets: Settlement, Invoices, Contribution, Food variance, Campaign, Capacity, Recipe costing and Outlets. The first six are compact worksheets for one record or scenario at a time. Recipe costing has twelve prepared ingredient rows, and Outlets has twelve prepared branch rows. The workbook contains actual formulas, editable inputs and input validation. It does not import a merchant portal, retrieve bank transactions, calculate statutory tax liabilities, or connect to a restaurant account. Enter normalized amounts from records you are authorized to use.

Every included business name, identifier, order count and monetary amount is fictional. The sample currency is INR. These examples explain the arithmetic and the decisions around it; they do not describe a real restaurant or establish a suitable commission, tax rate, food cost, capacity or profit target. Start with the supplied examples so you understand how the outputs behave, then save a separate working copy before replacing sample inputs. Keep the original download as a reference when a formula or label is accidentally changed.

Choose the worksheet that matches your question

Use Settlement when a bank credit seems different from the amount expected for an identified payout cycle. Use Invoices when the issue concerns how an invoice, its tax and a related credit note connect to a deduction. These are connected tasks, but they answer different questions. A bank credit can agree with the statement while an underlying service charge still needs investigation. An invoice can be correctly calculated while its deduction occurs in a later payout. Preserve both explanations instead of treating every difference as one undifferentiated shortage.

Use Contribution to examine the amount a particular order or menu scenario leaves after the variable costs listed on that sheet. Use Food variance when physical inventory and recorded purchases imply a different cost of usage from the recipe expectation for the same period. Use Campaign when deciding whether an estimated number of additional orders would cover campaign spending. Use Capacity when comparing a simplified monthly break-even requirement with your own measured daily capacity. Keep the question written in ordinary language alongside the records you collect.

Use Recipe costing when purchase pack size, usable yield and the quantity included in a batch need to be translated into a portion cost. Use Outlets when several branches must be compared on the same month, currency and sales definition. A recipe calculation can inform a contribution calculation, and contribution can inform a capacity assumption, but the supplied worksheets do not automatically transfer figures between those tasks. This is deliberate: the person entering the number must check that the recipe, menu mix, period and cost scope actually match.

Suppose a manager says that sales rose but cash fell. Begin by deciding which part of that statement needs explaining. The timing of unpaid settlements belongs in the cash investigation. A larger ingredient bill may need inventory and purchasing records. A discount campaign may need a contribution comparison. Running all eight sheets without identifying the question can create more totals without a clearer answer. Select the smallest useful workflow, finish it, and then use the next worksheet only when the remaining question calls for it.

Prepare records before entering amounts

Create a working folder for the period being examined. Preserve the original settlement export, issued invoices, relevant credit notes, bank evidence and any inventory count or sales summary. Give each file a descriptive name containing the store, reporting period and document type. Do not replace a downloaded statement with a manually edited version carrying the same name. If you need to clean column formats or allocate a combined amount, put that work in a clearly named separate file so the original remains available for comparison.

Write down the store, currency, start date, end date and timezone represented by each source. Check whether an end date means the end of that local day, the start of the next day, or a report-specific boundary. A month of restaurant sales and a month of bank deposits usually cannot be compared simply because both files carry the same month label. The bank record measures cash received during its own dates; an order report measures transactions under its own eligibility rules. Link the records through the relevant cycle and references.

Before copying monetary values, inspect the number formats. A value that looks like a number may actually be text containing a currency symbol, a space or a locale-specific separator. Enter numeric amounts in amount cells and keep identifying references as text. The workbook displays amounts to two decimal places, but display formatting does not decide the correct accounting treatment. Use the source precision and document any allocation or rounding method. Do not turn a missing statement field into an assumed zero merely to make a result appear.

Remove unnecessary personal information from your working copy. These worksheets do not require customer names, addresses, payment card details or login credentials. A cycle identifier, invoice reference or internal outlet code is usually enough to trace the example calculations. If several people review the file, agree who owns input changes and how the reviewed version is identified. The workbook itself does not manage permissions, approvals or a multi-user change log. Your storage and review process must provide those controls.

Settlement: explain the difference from the bank

On Settlement, enter the cycle identifier in B6 and the eligible start and end dates in B7 and B8. These dates label the record; they do not filter an imported transaction table. The sheet calculates from the amounts you enter, so the person preparing it must establish that all amounts belong to the identified cycle and store. Use the official payout detail to determine the relevant revenue base. DoorDash's report field documentation illustrates why payout identifiers, local dates, fee fields and adjustments matter when interpreting a report.

The fictional example starts with merchant revenue of INR 100,000 in B10. It then deducts merchant-funded discounts of INR 4,000, service fees of INR 20,000, tax on those fees of INR 3,600, refunds and other deductions of INR 1,400, and withholding of zero. Credits of INR 500 are added. The resulting expected payout in B18 is INR 71,500. Entered deductions are positive amounts because the formula performs the subtraction. A negative source adjustment must first be interpreted and assigned to the appropriate deduction or credit category.

The matched bank credit in B19 is INR 70,900. B20 calculates bank credit less expected payout and therefore displays a negative INR 600 difference. This direction is important: a negative difference means that the entered bank credit is lower than the calculated payout. It does not establish why. Check whether there is another bank credit, a transfer fee outside the statement, an amount allocated to another cycle, or an adjustment omitted from the worksheet. Keep the unmatched amount visible until the evidence explains it.

The tax entry is an amount copied from the relevant statement or issued document. The example does not calculate a tax rate or imply that this figure applies to another contract, platform or jurisdiction. Likewise, zero withholding in the example is a fictional confirmed amount. Deleting that input leaves an incomplete calculation. If the statement already reports revenue after a restaurant-funded discount, do not enter that net revenue and deduct the same discount again. Normalize the starting amount or use a separately documented bridge that preserves the original meaning.

When the amount difference becomes zero, B21 still asks you to verify the evidence. Matching arithmetic cannot confirm that you selected the correct store, currency, payout reference or reporting window. Save the matched statement page and bank reference with the workbook. If two bank credits settle one cycle, build a separate allocation showing their sum and references before using the combined matched amount. If one bank credit combines several cycles, preserve a reconciliation by cycle. This compact worksheet does not perform automatic many-to-many matching.

Invoices: match an allocated document to its deduction

The Invoices worksheet separates the document calculation from the settlement comparison. B6 records the invoice identifier, B7 identifies the service month and B8 records the mapped cycle. Enter the service value allocated to that cycle in B10 and its associated tax in B11. B12 adds those two amounts. Enter a matched credit note in B14 and the settlement deduction after that credit is applied in B15. The sheet then calculates the expected deduction after credit and the unexplained difference.

In the fictional example, the service value is INR 20,000 and the tax amount is INR 3,600. The allocated invoice total is therefore INR 23,600. A related credit note is INR 1,000, leaving an expected deduction of INR 22,600. The entered settlement deduction is also INR 22,600, so B18 shows zero difference. If you change the credit note to zero while leaving the deduction unchanged, the difference becomes negative INR 1,000. This shows that the assumed credit application materially changes the reconciliation.

One issued invoice may cover services appearing in several payout cycles. Do not copy its full value into a separate workbook for every cycle. First create an allocation that divides the invoice service value and tax across the relevant cycles, with a total that agrees to the issued invoice. Then use one allocated mapping on this sheet. Retain the invoice number even when an allocation is necessary, and explain the allocation basis so a reviewer can reconstruct it without guessing why the split was chosen.

A credit note is documentary evidence of an adjustment, but its existence alone does not prove that the platform has applied a settlement credit or sent cash. If the deduction is still the full invoice amount, keep the actual deduction in the sheet and document the pending credit outside the amount bridge. Do not reduce the bank shortage merely because you expect a future recovery. Follow the credit through the relevant document, statement entry and settlement cycle until the amount has actually been applied under the platform's records.

Contribution: keep revenue and variable costs on one basis

Contribution answers how much the stated order revenue leaves after the variable costs you have included. It is not the amount deposited by a delivery platform and it is not net profit after every business expense. The distinction matters because a payout deducts some charges but does not necessarily include ingredient costs, packaging purchased elsewhere or fixed restaurant overheads. The OpenStax contribution margin explanation supports the underlying distinction between sales, variable costs and the amount available toward fixed costs.

The sample Contribution sheet uses INR 600 of pre-discount restaurant revenue in B8. Its costs and discount are ingredients of INR 180, packaging of INR 25, a merchant-funded discount of INR 45, variable platform services of INR 120, marketing assigned per order of INR 30, a refund allowance of INR 12 and other variable cost of zero. Together these inputs total INR 412 in B17. The remaining contribution is INR 188 in B18. B19 divides that amount by the stated revenue base, producing approximately 31.3 percent.

Keep the revenue definition written down when sharing the percentage. Another restaurant might report a margin against revenue after discounts. That percentage cannot be compared directly with a rate using pre-discount revenue without aligning the bases. The supplied sheet deducts the discount separately, so enter the corresponding pre-discount revenue. Do not copy the net amount from an unrelated report field because its label sounds similar. The report dictionary can help identify which parts of a source amount require a bridge before being used here.

Classify the costs according to the decision being examined. A per-order packaging item is different from a fixed monthly rent commitment. A marketing allocation can be useful for one analysis, but the same campaign spending must not also be subtracted as a separate fixed campaign cost in a connected calculation. When using the Campaign sheet, enter contribution before the particular campaign spending being evaluated. Keep any recurring advertising allocation or merchant-funded discount distinct enough that a reviewer can see which expenses have been counted.

Try a focused change after reproducing the example. Increasing ingredient cost by INR 18 lowers contribution from INR 188 to INR 170 when the other inputs stay fixed. That is an arithmetic comparison, not a prediction that sales volume will remain unchanged after a price or menu change. Record the assumption being tested, keep an unchanged copy of the base case, and compare the amount difference alongside the percentage. If revenue is zero, the contribution amount can still be negative, but the margin ratio is unavailable rather than a reassuring zero percent.

Food variance: reconcile usage before assigning a cause

Food variance starts with inventory values and movements for one defined period or ingredient category. Enter opening inventory in B9, net purchases in B10, transfers in B11, transfers out B12 and closing inventory B13. The calculated usage in B15 adds opening inventory, purchases and inward transfers, then subtracts outward transfers and closing inventory. The basic inventory relationship is explained in BCcampus's monthly food cost chapter and is consistent with the periodic inventory approach described by OpenStax.

The fictional opening inventory is INR 50,000. Net purchases are INR 30,000, transfers in are INR 2,000, transfers out are INR 1,000 and closing inventory is INR 42,000. Calculated usage is INR 39,000. The theoretical usage entered in B16 is INR 35,000, so actual less theoretical usage is INR 4,000. Expressed against theoretical usage, this difference is approximately 11.4 percent. These numbers describe the supplied example only. They do not establish an acceptable variance for your kitchen.

The theoretical figure must be built from a comparable set of meals and recipe costs. If your actual inventory includes staff meals, samples or recorded waste, decide how those categories appear in the theoretical comparison. Otherwise the worksheet may be measuring a scope difference rather than a kitchen process issue. The same applies to transfers between branches: the value leaving one outlet should be recorded consistently with the value entering the other. A mismatch can create apparent losses at one branch and apparent gains at another.

Investigate the underlying records before assigning responsibility. Check count sheets, purchase returns, pack-size changes, recipe revisions, portion measurements and inventory units. A closing count entered in packs while the valuation assumes individual units can produce a large difference without any change in physical usage. A supplier price increase may alter valuation even when portions are unchanged. A negative calculated usage should lead you back to the count and cutoff evidence; it should not be quietly replaced with zero to make the monthly presentation look plausible.

Keep a short investigation log outside this compact calculator. For each material difference, record the suspected explanation, evidence checked, confirmed correction and remaining unresolved amount. Correct the input only when the evidence supports the change. Preserve the original observation if the worksheet is used in a management review. The purpose is to improve purchasing, portioning and recording decisions; a single variance result cannot prove theft, waste, poor employee performance or an error by a particular supplier.

Campaign: distinguish observed orders from additional orders

The Campaign worksheet accepts campaign spend, contribution before that campaign spending, observed delivered orders and an estimated incremental order count. The observed order count is displayed for context and does not automatically feed the incremental result. This prevents a common analytical mistake: treating every order seen during a promotion as an order caused by that promotion. Google describes this distinction through treatment and control comparisons in its Conversion Lift documentation. The workbook itself does not run such an experiment or estimate statistical significance.

The fictional campaign costs INR 9,000. Each additional order is assumed to contribute INR 90 before the campaign spending. Dividing spend by positive contribution gives a requirement of one hundred incremental orders to cover that spend. The sample observed delivered orders are one hundred eighty, but the entered incremental estimate is one hundred ten. Multiplying that estimate by INR 90 and subtracting INR 9,000 produces INR 900 of estimated incremental contribution after spending. That is ten percent of the entered campaign spend.

Write the evidence supporting the incremental estimate in your working records. If it comes from a comparison with a previous period, record the differences in weekdays, weather, holidays, opening hours, stock availability and menu changes. An increase during a festival does not become causal proof merely because a promotion was also active. If you cannot support a credible estimate, use the break-even requirement as a planning question and leave the incremental input unavailable. Do not substitute the observed order count simply because it is easier to find.

The sheet allows a negative incremental estimate because a business comparison can show a decline. An estimate of negative ten additional orders at INR 90 contribution, with INR 9,000 spending, produces negative INR 9,900 after spend. The workbook preserves that direction rather than forcing a zero minimum. Similarly, a zero campaign spend makes the spend-based return ratio unavailable. Zero spend does not justify dividing by a tiny invented number or calling the result an infinite return.

Check the cost boundary before linking this result to other work. The contribution input must exclude the campaign spending deducted separately here. If discounts apply to each extra order, include their variable effect in contribution. If a fixed creative or campaign setup cost belongs to the decision, include it in campaign spending using a documented basis. Do not call this result accounting profit, total advertising return or a platform-certified lift measurement. It is a conditional contribution calculation based on the evidence and assumptions you enter.

Capacity: compare a simplified requirement with measured operations

Capacity combines a monthly financial requirement with a separately entered operational limit. The simplified break-even relationship uses fixed costs divided by positive contribution per order. The Small Business Administration's break-even guidance describes this relationship. A restaurant with several menu items must still choose a realistic contribution assumption for its expected mix. Changing the mix, staffing arrangement or equipment can change both contribution and fixed costs, so the result should be read as a stated scenario.

In the sample, monthly fixed costs are INR 150,000 and contribution per order is INR 150. The sheet rounds the monthly break-even order requirement up to a whole order, giving one thousand orders. With thirty open days, the daily average requirement is approximately 33.33 orders. The entered sustainable daily capacity is fifty-five, leaving average headroom of approximately 21.67 orders per open day. These are example assumptions, not recommended operating targets or evidence of what a particular kitchen can safely produce.

The peak orders per hour input records an additional measurement but does not automatically convert daily capacity into a peak-hour guarantee. A restaurant can have enough total time across a day while still failing during a concentrated dinner rush. Measure the stages that constrain your own operation: preparation, cooking, packaging, checking, dispatch or pickup handover. Keep the measurement period, staffing level and menu mix alongside the number. A capacity figure measured with a reduced menu should not silently be used for a more complex menu.

When per-order contribution is zero or negative, the sheet does not produce a finite break-even order count. Selling more identical orders under those assumptions does not cover the fixed-cost requirement. Investigate price, discounts, variable costs and the product mix before treating higher volume as the answer. If the financial requirement exceeds measured capacity, test operational and cost changes separately. Do not simply raise the capacity assumption until the comparison looks favorable. A useful decision requires an implementable change supported by evidence.

Recipe costing: connect the purchased pack to the serving

Recipe costing has a short assumption area and a twelve-row ingredient table. Enter the recipe name in B6, portions per batch in B7, packaging per portion in B8 and a pack-price change assumption in B9. Ingredient inputs occupy A14:F25. The columns record ingredient name, unit, purchased pack quantity, pack cost, usable yield and ingredient quantity used in the batch. Columns G and H calculate current and revised batch costs. The table is designed for ingredients expressed at the same costed stage, with trimming or draining yield between zero and one hundred percent.

The yield calculation uses the cost of the usable quantity rather than pretending discarded material was free. For example, a fictional carrot pack contains one thousand grams, costs INR 80 and yields eight hundred usable grams after preparation. Using five hundred usable grams in a batch consumes INR 50 of ingredient cost. This follows the relationship between purchased and edible quantities described in BCcampus's yield chapter. The USDA Food Buying Guide's Appendix B independently illustrates the quantity relationship. Its program-specific serving rules are not adopted here.

The other fictional ingredients are potatoes and oil. The potato pack contains one thousand grams, costs INR 60 and has a ninety percent usable yield. A batch quantity of nine hundred usable grams therefore costs INR 60. The oil pack contains one thousand millilitres, costs INR 180 and is entered at a one hundred percent usable yield; fifty millilitres cost INR 9. The three ingredients total INR 119 for the batch. At ten portions, ingredient cost is INR 11.90 per portion. Packaging of INR 5 raises the displayed cost including packaging to INR 16.90.

The pack-price change input is a simple what-if assumption applied to all ingredient pack costs. At a ten percent increase, the batch ingredient total becomes INR 130.90. Dividing by ten portions gives INR 13.09 per portion. Packaging remains INR 5 because the assumption applies to ingredient packs, so the combined cost becomes INR 18.09. This calculation keeps quantities, yields and packaging fixed. It does not estimate how a supplier price change affects demand, wastage, recipe substitutions or a customer's willingness to pay.

Use the same unit for the purchased pack quantity and the recipe quantity within a row. Grams must be compared with grams, millilitres with millilitres, and individual pieces with individual pieces. The unit selector does not convert kilograms into grams or mass into volume. If your invoice uses kilograms, convert the purchased quantity into grams before entering it and preserve the conversion in your workings. Do not assume that one millilitre weighs one gram for an ingredient without a justified ingredient-specific basis.

Cooking can add water or remove moisture, so the preparation-yield input is not a universal cooking expansion factor. If a rice recipe is costed from dry purchased rice, express the batch ingredient quantity on that same dry costed basis. If you instead cost a prepared subrecipe, first establish its own batch cost and measured yield in separate workings. Then enter the relevant purchased-equivalent or prepared-unit cost consistently. Mixing cooked weights with raw purchase costs and an unrelated trimming percentage can create a convincing-looking but incorrect portion cost.

Count the actual number of saleable portions produced at the intended portion size. Do not increase portions per batch simply to reduce the cost shown. If a batch makes ten full portions and a partial leftover that cannot be sold under the same specification, document how that leftover is handled. Packaging is added per portion, so confirm that the packaging entry represents the complete item being costed rather than a carton of containers. Labour, rent and other costs are outside this sheet's ingredient-plus-packaging result and belong in the appropriate contribution or operating analysis.

Outlets: compare branches with weighted rates

The Outlets sheet provides twelve prepared rows, from row twelve through row twenty-three. Enter the comparison month in B6 and the common currency in B7. Each row needs a distinct outlet identifier, net restaurant revenue, variable costs, total orders and refund-affected orders. Revenue on this sheet is after merchant-funded discounts and excludes pass-through taxes. Variable costs should therefore exclude discounts already deducted from revenue. This revenue definition differs from the pre-discount entry on Contribution, so align the basis before transferring any figures.

The fictional first outlet has INR 100,000 of revenue, INR 70,000 of variable costs, two hundred orders and six refund-affected orders. Its contribution is INR 30,000, its contribution margin is thirty percent and its refund order rate is three percent. The second outlet has INR 300,000 of revenue, INR 180,000 of variable costs, five hundred orders and ten refund-affected orders. Its contribution is INR 120,000, its margin is forty percent and its refund order rate is two percent. Neither branch includes fixed-cost allocations in contribution.

The portfolio revenue is INR 400,000 and contribution is INR 150,000. Dividing those matching totals produces a portfolio margin of 37.5 percent. Averaging thirty percent and forty percent would give thirty-five percent, which ignores the different revenue sizes of the branches. The same principle applies to revenue per order and refund rates. Portfolio revenue per order is approximately INR 571.43 across seven hundred orders. Sixteen refund-affected orders divided by those seven hundred orders gives approximately 2.3 percent, rather than the simple average of the two branch percentages.

Use refund-affected order counts consistently. If several refunded items belong to one order, that order should not be counted several times when the denominator is total orders. If one report counts refunds issued in the month and another counts orders placed in the month, establish a consistent comparison before combining them. The sheet can reject an entered refund count greater than total orders, but it cannot inspect the underlying order-level evidence. A plausible-looking rate still depends on the preparer's definitions and deduplication work.

Duplicate outlet identifiers and incomplete used rows prevent a portfolio total from silently omitting a branch. Entirely blank prepared rows are available for later outlets. The sheet does not verify different currencies or periods on individual rows because those fields are shared comparison settings. You must confirm that each source extract agrees with the stated month and currency. International branches need a separate, documented currency-conversion process and consistent reporting basis before a combined comparison is meaningful. This download does not apply exchange rates automatically.

Understand blank, zero and unavailable results

A blank input means that a required amount has not been supplied. An entered zero means that you checked the relevant item and its amount is actually zero. These states lead to different results. Deleting the withholding value on Settlement blocks the expected payout because a deduction remains unknown. Entering a confirmed zero allows the calculation to proceed. Leaving an unused ingredient row completely blank is different: it means the row is unused, so it should not prevent a completed recipe from being calculated.

Partly completed table rows are treated as used but incomplete. Typing an ingredient name without its quantity, price and yield should not make the batch total quietly ignore that ingredient. The Recipe costing sheet displays an instruction to complete the ingredient rows. Similarly, an outlet name without its sales and order counts must not disappear from a portfolio result. Complete the row or clear all of its input cells if it was added accidentally. Clearing only the name while leaving amounts can still leave an incomplete record.

A zero denominator is not the same as a zero result. No revenue means a revenue-based margin ratio is unavailable. No orders means revenue per order and refund order rate are unavailable. Zero or negative contribution means that the simplified break-even formula cannot provide a finite positive order requirement. The workbook uses an unavailable label or an empty dependent result where appropriate. Read the related inputs and messages before interpreting a blank output as a technical failure or replacing it with a number.

Input validation helps with common entry mistakes, but spreadsheet applications can handle pasted values and validation prompts differently. Do not treat validation as a security control or a substitute for review. If a pasted range bypasses a prompt, inspect the data and the dependent results. Preserve visible errors until the cause is understood. Replacing every error with zero can make an incomplete restaurant appear reconciled, a campaign appear harmless or a missing branch disappear from a comparison.

Respect row limits and preserve formulas

The workbook is deliberately bounded. Settlement, Invoices, Contribution, Food variance, Campaign and Capacity each describe one record or scenario. Save a separate working copy when you need another cycle, invoice allocation or scenario. Typing a second record below the notes does not add that record to the calculation. A restaurant that needs a continuous register across hundreds of cycles should build or use a properly structured transaction register rather than treating the empty area below a compact calculator as an automatically expanding database.

Recipe costing includes twelve ingredient rows at A14:H25. The editable part is A:F, and the formula columns are G:H. The current outputs are B29:B31, with the revised-price outputs at D29:D31. Outlets includes twelve outlet rows at A12:I23; A:E are inputs and F:I contain formulas. Its portfolio outputs and row review occupy B26:B31. These prepared ranges are part of the calculation design. Rows outside them are not automatically included simply because you insert or type more data nearby.

If you need more than twelve ingredients or outlets, extend the design carefully in a separate copy. The detail formulas, total references, required-input handling, duplicate checks, validation ranges and exception formatting all need to cover the enlarged input area. The instruction labels and frozen headers also need review. Copying the appearance of the last row is insufficient. Test a complete new final row and an incomplete new final row, then confirm that the former changes the total and the latter prevents an understated total.

No cells are protected. This makes the arithmetic inspectable and allows an experienced user to adapt the file, but it also permits a formula to be overwritten accidentally. Amber fill identifies the intended input areas; it is not a password or permission boundary. Use the original download to compare a suspicious formula, or restore a clean copy and re-enter the documented inputs. Do not use worksheet protection as a reason to trust a formula without checking its references and the meaning of its inputs.

Make the review repeatable

Choose a clear file-naming convention before the first real reporting cycle. Include the restaurant or outlet code, the task, the reporting period and a review version. A name such as a store code followed by settlement period and a short version is more useful than several files called final. Keep the data period separate from the day you prepared the workbook. A file prepared in October may legitimately analyze September activity, and both dates should remain understandable without opening several source documents.

Before marking a working copy reviewed, repeat one independent calculation using the source amounts. For Settlement, recompute the expected payout and check the bank reference. For Recipe costing, calculate one ingredient's usable unit cost and confirm its contribution to the batch. For Outlets, divide total contribution by total revenue and compare it with the displayed portfolio rate. This independent step checks the logic, while a source-to-input check confirms that the values entered actually match the intended records.

Test one relevant change in a disposable copy rather than in the record you intend to retain. Increase a cost and confirm that contribution falls by the expected amount. Delete one required input and confirm that the dependent result becomes unavailable. Add a partly completed outlet row inside the prepared range and confirm that the portfolio does not present an understated total. Restore the sample or discard the disposable copy after testing. A static result that never reacts to an input change is not evidence of a working calculation.

Record the decision made from the completed work. A useful note might identify a settlement reference to investigate, a recipe yield to measure again, a supplier price to confirm or a peak-hour process to observe. Avoid turning the worksheet into a list of unsupported conclusions. When the evidence is incomplete, write what remains unknown and who will obtain the missing record. The practical value of the workbook is the traceable next action, not the presence of many formatted percentages.

What was checked and how to use the sources

The released workbook was checked by recalculating its formulas in the authoring calculation engine, comparing the fictional example outputs with independent arithmetic, changing representative inputs, testing missing and zero values, exporting the file and importing it again for result comparisons. Every worksheet was rendered and visually reviewed for readable labels, visible amounts and working-area layout. Microsoft Excel desktop execution was not tested during this release. If your organisation relies on a particular Excel version or another spreadsheet application, open a copy there and verify the examples before using it for a reporting process.

The workbook's source references describe the methods and report-field boundaries. They do not supply its fictional financial inputs. Source links are stored in ordinary Excel Notes on the relevant input cells, with each sheet identifying where to find its note. Depending on the spreadsheet application, the command for showing a note may differ. The guide links above provide another route to the same method references. Check official report documentation when a platform changes its export version, field name, timing rule or available report type.

Uber's official reporting documentation is another useful reference for the distinction between merchant report details and payout reconciliation. Current issued statements, contracts and local professional advice remain necessary when determining the treatment of a particular charge or tax amount. The workbook performs the stated calculations with your inputs; it does not certify the accuracy of a platform statement, interpret a contract, approve a tax filing or guarantee recovery of a disputed deduction.

Continue with the restaurant report dictionary when a source label is unclear, the export data-cleaning guide when dates or identifiers need preparation, and the month-end reconciliation walkthrough when several worksheets must connect to one closing process. The recipe and portion-costing guide and outlet-comparison guide provide deeper operational examples. Keep the original records, complete the relevant inputs, check the calculation and preserve the action that follows.