Restaurant month-end reconciliation: connect POS sales, delivery reports and the bank

What a useful month-end close should explain

A restaurant month-end close should explain the relationship between activity, costs, amounts still owed and cash. It should let another authorised person trace the result to its evidence. It does not require every report to show the same total. A point-of-sale report, a delivery-platform statement, a supplier invoice and a bank statement describe different parts of the business. The job is to connect them without counting a sale or expense twice.

This walkthrough uses an original fictional restaurant called Copper Table. Its amounts are in INR, but no actual platform fee, tax rate or merchant result is represented. Revenue and operating costs use a consistent tax-exclusive management basis. Tax settlements, financing, depreciation, capital purchases and owner transactions are outside the simplified operating model. Keep those categories separately when they apply to an actual business. The example produces a selected operating remainder, not an audited profit or a tax return.

We will build four connected views: sales and operating costs, platform clearing, invoice evidence and bank reconciliation. Keep the views separate long enough to understand their purpose, then connect them through explicit references. If a source is missing, show what remains uncertain. A close with a clear exception is more useful than a seemingly perfect spreadsheet built by replacing unknown amounts with zero.

Define the close before collecting more files

Write the period, outlets, currency, sales basis and accounting method at the top of the close pack. Identify which location is included and whether the point-of-sale system already records integrated delivery orders. State the event used to place sales in the period. That might differ from the date a customer payment is processed or a payout is initiated. Follow the business's actual policy rather than adopting the first date field that appears in an export.

Give the pack a version and preparation date. A report generated after a later refund can differ from an earlier snapshot. Preserving the generation date helps explain that difference. Keep original downloads read-only in a private source folder, with working copies elsewhere. Use an organised naming convention that makes source, outlet and period understandable without exposing unnecessary bank or customer identifiers. A name can describe scope without containing every piece of sensitive information.

Choose a reviewer and a practical completion sequence. The owner might prepare the operating schedule while a bookkeeper checks evidence and classifications. Give unresolved issues named owners and review dates. If the business has a formal close or accounting policy, follow it. This teaching checklist is a way to organise the work, not authority to override an accountant's treatment, an employment obligation or a statutory filing requirement.

For Copper Table, the month contains one operating outlet. Its POS net sales include counter, pickup and the integrated platform orders. The management view excludes tax and tips throughout. We do not assert that these are the correct exclusions for every report. They are explicit assumptions that make the example's totals comparable. A real close should explain its own inclusions just as plainly.

Make an evidence register with one purpose per source

List the files needed for the questions you are answering. Include the POS sales report, authorised platform order and settlement information, fee invoices, refund or adjustment records, bank statements, supplier purchases, stock counts, payroll totals and relevant operating bills. Record source, selected outlet, date basis, currency, report version and retrieval status. Mark a missing file as missing. A spreadsheet row headed “received” should mean the evidence actually exists and its scope has been checked.

Add a purpose column. The POS establishes the selected sales population; the platform detail explains its portion and settlement components; an invoice documents a service or purchase; the bank establishes posted cash movement. A source can have several uses, but record each relationship. For example, the same commission amount can appear in a platform statement and a separate fee invoice. Those are two pieces of evidence for one charge, not automatically two charges.

Check completeness before calculating. Does the export contain all selected days? Were any modules unavailable? Does the file contain diagnostic rows instead of usable transactions? A successful archive download does not prove every upstream record was recovered. Inspect warnings and counts. If an item-level dataset is incomplete, do not use its recovered dish quantities as if they describe the whole month. State the affected part of the analysis and obtain the missing evidence.

Keep the register small enough to review. A folder containing hundreds of downloads is not a close pack unless somebody can identify which files support the result. Retain superseded versions separately and point the working schedules to the approved version. When a later correction arrives, update the register and exception log together so the next person knows why the close changed.

Check dates, states and row grain before adding money

Inspect a known order through its source records. Find the order identifier, outlet, status, order time, payment time and settlement reference where available. Establish what one row represents. Two dish lines can belong to one order; a payout can have a summary and several breakdown rows. Adding those rows as if each were another independent sale or payout can produce a balanced-looking but inflated workbook.

Compare the period boundaries between sources. A provider report may group by order date, payout initiation date or another defined basis. The bank groups posted movements by its own statement dates. Do not move an order simply because its transfer arrived later. Instead, retain the sale in the appropriate operating period and explain the amount still due in the clearing schedule. Ask for advice when the business's accounting basis changes that treatment.

Keep completed, cancelled, refunded and pending activity distinguishable. A cancelled order may or may not create a payment or compensation under the actual arrangement. A refund can be partial and can occur after the original sale. Do not decide its effect from the status word alone. Read the amount fields and the provider's current explanation. Preserve unresolved status questions rather than treating every non-completed row as a zero-value transaction.

Use a scope check before the full calculation: source total, selected record count, distinct order count and excluded categories. These controls should refer to the actual grain. If one source contains item rows and another contains orders, explain the grouping method. The report dictionary can help the reviewer distinguish those terms without relabelling the provider's original fields.

Connect POS and platform sales without duplicating them

Copper Table's fictional POS net sales are INR 115,000. Of that total, INR 40,000 already represents the integrated platform sales. Counter and pickup contribute the remaining INR 75,000. The platform report's INR 40,000 is useful supporting evidence, but it is not another revenue stream to add to the POS total. Adding the two full reports would show INR 155,000 and overstate this model's sales by INR 40,000.

Prove overlap using the actual integration and order references where possible. Similar daily totals do not prove that every platform order appears correctly in the POS. Prepare a coverage table identifying orders present in both sources, platform-only records, POS-only records and records requiring a mapping. The purpose is to identify the same sale once. Do not erase a source merely because it overlaps; retain it as evidence for the platform and cash questions.

If a platform order is absent from the POS, investigate before adding it manually. It may fall outside the selected date boundary, use another identifier or reflect a genuine integration gap. Document any confirmed adjustment with its source and classification. A manual adjustment should explain why the selected sales population changes. It should not be an unexplained number inserted to make the totals resemble a dashboard screenshot.

For multiple platforms, repeat the coverage exercise for each one. Do not assume that one correctly configured integration proves all integrations behave identically. Keep channel definitions consistent across the month. A pickup order from a marketplace can still be a platform order, while a direct website pickup might belong to another channel. The channel name should describe the chosen business question, not merely the delivery method.

Give refunds and later corrections their own trail

Start with the chosen revenue definition. Copper Table's INR 115,000 and the platform portion of INR 40,000 are already net of the sales reductions included in this example. There is no additional current-month refund deduction in the payout bridge below. If an analyst subtracts the same included refund again because it appears in another report, the close understates the result. Keep the raw source fields and write which reductions are already included.

Create a refund and correction log linking the original order, event date, amount, source, status and eventual settlement treatment. A complaint, submitted dispute, approved adjustment and received payment are separate stages. Keep each stage's evidence. A pending support request is not a receivable merely because the owner expects approval. Conversely, an approved amount still needs to be linked to the appropriate statement or accounting treatment before it is considered resolved.

Do not count a credit-note document automatically as an extra payout credit. Providers can use that term for particular document or tax adjustments. Deliveroo's public guidance, for example, explains a specifically named Credit Note column that does not itself change payout. Read the actual field definition. Match documents to statement entries and avoid turning a generic accounting label into a universal rule for every platform.

When a later correction relates to an earlier month, retain both dates. Ask the person responsible for the books how the correction should be recognised. The operational learning can still be tracked separately: a refund processed today might reveal a packing failure last month. Keep the service investigation and financial classification connected without forcing both into the same reporting date.

Use fee invoices as evidence without paying twice

In the fictional month, platform fees total INR 8,000 and advertising totals INR 2,000. They are included once in the operating-cost schedule. Both are withheld in calculating the current platform entitlement. A fee invoice can support the INR 8,000 charge, but its arrival does not create another INR 8,000 cash payment. The invoice and settlement evidence need to be linked to the same cost rather than treated as independent expenses.

Prepare an invoice register with supplier, document identifier, service period, invoice amount, relevant tax information, payment method and settlement reference. Distinguish paid through withholding from paid through a separate bank movement. Keep credit notes and adjustments linked to the original invoice. If an invoice covers several outlets or periods, obtain the appropriate allocation and retain the method. Do not divide an amount arbitrarily simply because the close is easier with equal pieces.

Compare the fee basis and signs with the agreement and statement. An invoice total can include components outside a single order's commission. Advertising, recurring service fees or tax can need separate categories. If a figure is unexplained, use an exception rather than estimating a universal percentage. A fee's amount alone does not establish whether it is correctly billed, tax recoverable or attributable to the current operating month.

Keep bank matching separate from expense recognition. An unpaid supplier invoice can still belong to the selected operating period under the relevant accounting method. A bank payment can settle a prior invoice. The close needs both the cost schedule and the amounts payable schedule when those timing differences matter. Explain the distinction to a new reviewer using the actual records rather than relying on the word paid in a filename.

Reconcile purchased food with food used

Copper Table begins the month with INR 12,000 of valued food stock. Purchases are INR 33,000 and closing stock is INR 9,000. With no transfers, returns or other stock adjustments in this simplified case, food used is INR 12,000 plus INR 33,000 minus INR 9,000, giving INR 36,000. Using only the purchase total would understate this month's food use by INR 3,000 because the restaurant also consumed some opening stock.

Check quantities and valuation before trusting the stock totals. A case, kilogram and portion are not interchangeable units. A supplier return should not be recorded as an extra purchase, and a transfer from another outlet should follow the group's documented treatment. Preserve count dates and any supported corrections. If the closing count was taken before the last service, establish how intervening movements are handled rather than quietly calling the count a month-end quantity.

Food used is not automatically theoretical food cost. A recipe-based expectation for sold dishes can differ because of waste, staff meals, transfers, portion changes or measurement errors. Keep those explanations distinct. A variance is a prompt to investigate, not proof that somebody stole stock. The actual-versus-theoretical guide explains a separate operational comparison that can sit beside the close.

Keep purchasing evidence separate from supplier payment evidence. An invoice contributes to the relevant purchase schedule even if its payment is later, subject to the business's actual accounting basis. Conversely, this month's supplier bank payment may include an older balance. Ask the reviewer to reconcile stock use, purchases and payables rather than choosing whichever number produces the smallest food-cost percentage.

Complete the cost set before interpreting the remainder

The fictional operating schedule includes INR 36,000 food used, INR 2,500 packaging, INR 8,000 platform fees, INR 2,000 advertising, INR 30,000 staffing, INR 12,000 occupancy and INR 5,000 other selected operating costs. Those amounts sum to INR 95,500. Subtracting them from INR 115,000 defined revenue leaves INR 19,500. Every category is an invented teaching assumption rather than a normal or recommended restaurant cost.

Write what staffing includes. A payroll payment alone may not show the full cost of work attributable to the month. Salaries, employer costs and benefits can need appropriate treatment. Do not invent lawful wage rates or payroll obligations from a percentage target. Use actual payroll evidence and qualified current advice. A manager reviewing an aggregate staffing cost does not automatically need copies of every employee's personal banking or identity details.

Check packaging and operating bills for timing and overlap. A bulk purchase can leave stock for later periods. A software invoice might cover several months or locations. A card-processing charge can appear in a payment report and a separate invoice. Classify each item using the chosen method and count its effect once. Retain exclusions beside the result so nobody interprets INR 19,500 as money immediately available for owner withdrawal.

A completeness review should ask about omitted categories before arguing over small percentage movements. Financing, depreciation, taxes, capital spending and owner transactions may sit outside this teaching operating result, but an actual set of accounts needs the appropriate treatment. A public planning worksheet cannot decide those classifications. Record who will resolve the issue and where the final treatment is documented.

Roll platform clearing forward from opening to closing

Start with the amount already due at the beginning of the month. Copper Table has INR 4,000 opening platform receivable. Current platform sales on the defined net basis are INR 40,000. The current platform fees of INR 8,000 and ads of INR 2,000 reduce current entitlement to INR 30,000. Matched bank receipts during the month are INR 29,000. The closing amount due is therefore INR 4,000 plus INR 30,000 minus INR 29,000, or INR 5,000.

The same relationship can be checked in the other direction: opening INR 4,000 plus current INR 30,000 minus closing INR 5,000 gives the INR 29,000 bank receipts. This proves the arithmetic of the defined roll-forward. It does not prove every receivable is collectible or every fee correct. Support the opening balance, current entitlement, cash receipts and closing detail with actual source records. An unexplained opening balance will otherwise carry confusion into every later month.

Keep a list of the closing items rather than one unsupported total. Record their periods, references, status and expected next evidence. Some might clear shortly after the statement cutoff; others might need investigation. A balance labelled pending is not resolved just because it is carried forward. Assign a review date and compare later statements. If an item changes or is reversed, keep the original history and the reason for the change.

Run the schedule separately for each relevant platform, currency and outlet scope. The current settlement analyser supports its specified Zomato and Swiggy structures; it is not a universal bank or overseas-platform reconciliation system. For multiple outlets, use an explicitly outlet-keyed workbook and verify the scope rather than assuming a batch import safely performs consolidation. The separate outlet comparison guide explains that boundary.

Match bank receipts using evidence, not just equal amounts

Compare the provider reference, account scope, currency, amount and bank posting date. Equal amounts alone are weak evidence because two transfers can happen to share a value. Preserve complete references privately, and use redacted descriptions in public questions. If one bank receipt combines several settlement amounts, record the supported composition. If a provider splits a payout, match each part without counting the total and its components again.

Consider receipts from before the sales period. The INR 29,000 in Copper Table's clearing schedule is a bank-period total, not a statement that every rupee arose from current-month orders. That is why the opening INR 4,000 and closing INR 5,000 are essential. Comparing only current platform sales with current bank receipts hides the timing bridge and can misclassify legitimate older receipts as unexpected revenue.

Keep failed or rejected transfers separate from posted receipts. A provider status can describe initiation, pending processing or rejection; the bank evidence answers a different question. Do not promise a universal arrival time based on an article for another country or a different account arrangement. Where a transfer remains unresolved, inspect the actual statement and use authenticated provider support with the relevant references and calculation.

Reconcile other collection routes as well. Cash, direct card payments, invoices and deposits can have their own timing and deductions. A platform schedule is only part of the restaurant's cash picture. For cash on hand, use the business's actual till and deposit controls. Do not assume that every POS cash sale should already appear as a separate bank receipt, or that an owner transfer is another customer sale.

Reconcile the bank statement and the cash book separately

Here is a separate fictional bank-reconciliation exercise, expressed in INR. The bank statement balance is INR 24,900. An evidenced deposit in transit of INR 1,800 has been recorded in the books but has not appeared on that statement. An outstanding payment of INR 1,100 has been recorded in the books but has not yet cleared the bank. Adjusting the statement side gives INR 24,900 plus INR 1,800 minus INR 1,100, or INR 25,600.

The cash book shows INR 25,900 before correction. The bank has deducted an INR 300 service charge that is missing from the cash book. Recording that charge reduces the book balance to INR 25,600. The two adjusted balances now agree. The transit deposit and outstanding payment do not need to be entered as new sales or costs merely because they have not cleared. They are timing items already represented in the books.

This is a deliberately small exercise, not Copper Table's complete bank statement. Its purpose is to show which side needs which adjustment. In real work, each item needs evidence, and book or bank errors can require different corrections. Ask an appropriate adviser when the accounting entry is uncertain. Do not use a journal entry called reconciliation difference to hide a gap you have not investigated.

Check outstanding items against later evidence. A payment that remains outstanding for an unusual period needs attention rather than permanent rollover. A deposit in transit should eventually match the appropriate statement or be reclassified when its original assumption proves wrong. Keep a dated reviewer note. A reconciliation is a continuing record of resolution, not a monthly ritual of copying old adjustments indefinitely.

Explain why the operating result is not the bank balance

The INR 19,500 operating remainder and INR 29,000 platform cash receipts answer different questions. The remainder includes the whole restaurant's defined revenue and selected costs. The receipts cover only matched platform transfers posted in the bank period. Neither number is the closing bank balance. Presenting them next to each other without labels invites a false comparison, even when both calculations are correct.

Stock movements, amounts receivable, unpaid invoices and other timing differences can separate a period's operating result from its cash movement. Owner contributions, borrowing, equipment purchases and repayments can move bank cash without representing the month's operating revenue or cost in the same way. Keep a cash bridge that identifies the relevant movements rather than trying to make operating profit equal a deposit total.

Use the three worked restaurant months for complete original examples in which stock, receivables and payables explain the difference exactly. One case has a positive operating remainder while cash falls because more money is tied up in stock and unsettled platform balances. That demonstrates a possible relationship under stated assumptions, not a prediction that every growing kitchen will have the same cash pattern.

A practical close meeting should finish with both operating and cash questions. Are the selected costs complete? Which balances remain due? What payments fall before the next expected receipts? A favourable margin does not eliminate a funding shortage. Equally, a large deposit may include prior-period receipts and does not establish a strong current-month result. Clear labels make those decisions easier.

Manage unresolved items without inventing an answer

Create an exception list with source, amount or affected population, possible explanations, evidence needed, owner and next review date. Separate a confirmed correction from a question. If a platform report is missing one day, the exception concerns completeness; it is not automatically a monetary shortfall of a guessed size. If a bank receipt is unmatched, preserve it for investigation rather than assigning it to whichever payout makes the worksheet balance.

Classify the investigation route. A missing integrated order may belong with the integration provider. A disputed fee may need the platform's statement and agreement. An unknown accounting classification belongs with the person responsible for the books. A legitimate question can require more than one source. Record what each response actually establishes instead of treating a generic support acknowledgement as proof that the financial issue is resolved.

Use safe evidence in support requests. Identify the report, outlet scope, dates, references and exact arithmetic through the authorised private channel. Do not send passwords, OTPs, session cookies or unrelated customer data. Public community discussions can use a redacted teaching example. Keep the original source privately available for an authorised reviewer when needed, but share only what the particular investigation requires.

Decide how an unresolved item affects the close. A reviewer may approve a clearly provisional management schedule while reserving a particular classification. That decision and its limits should be recorded. Do not call the entire month fully verified when a material source remains missing. The aim is a reliable statement of what is established, what is uncertain and how the uncertainty will be resolved.

Test the spreadsheet relationships, not just its final total

Trace how detailed records reach the summary. If orders have several item lines and several adjustments, joining both tables using only an order identifier can multiply records. For example, two item rows matched to two adjustment rows create four combinations. A total calculated after that expansion can repeat the original amounts. Check the intended relationship before merging: one row per order, one row per item or one row per adjustment. Aggregate each side to a compatible key where the question requires it.

Inspect control counts before and after each transformation. Keep the count of distinct orders, accepted event records and unmatched keys. Preserve amounts on each side of a merge so you can detect accidental duplication. Do not judge a merge only by whether the software reports success. A technically valid join can answer the wrong financial question. The export-cleaning walkthrough shows how to retain a transformation log and distinguish real repeated events from repeated copies.

Check spreadsheet ranges when a new month adds rows. A fixed total range can silently omit later entries; a summary can also include a prior month's carryforward as current activity. Keep opening balances in their designated cells and current movements in their designated tables. Protect formula cells where the workbook supports that feature, but continue reviewing the meaning of the inputs. Formula protection cannot establish that an amount belongs to the selected period or category.

Use a small known example to check the output. Change one input and predict what should change before recalculating. If changing a bank receipt unexpectedly changes sales, the sheet may link unlike concepts. If a closing balance updates but the next month's opening does not, the handover needs correction. These are useful model checks because they test relationships that matter to the close.

Review open invoices and shared costs without changing their meaning

Ask whether each unpaid item represents goods received, a service supplied, a deposit or a disputed document. The answer affects its place in the management and accounting schedules. A receipt for an equipment deposit should not automatically be treated like ingredients used in the month. An invoice sent in advance should not automatically become a full current operating cost. Keep a short description of the actual transaction and refer the classification to the person responsible for the accounts when needed.

Where a bill supports several outlets, preserve the total before allocation. Name the allocation rule and show that the assigned parts sum to the original amount. The group close should not include a central invoice once centrally and again inside every branch result. If a branch manager reviews a directly controllable result, label that view separately from the fully allocated group view. Both can be useful, but they answer different management questions.

Follow disputed invoices through the correct evidence route. An owner may disagree with a charge while the supplier still shows it payable. Keep the invoice, dispute reference, current status and any confirmed credit separate. Do not delete the original document or record an expected credit as if it has already been granted. Ask for the appropriate accounting treatment while the dispute remains open, and record the later evidence that changes the position.

Use this close to make the next one easier

Retain a small calendar of recurring evidence rather than waiting for a large month-end download. Record when stock is counted, which payroll periods overlap the close and where invoice statements arrive. Assign a backup person for an important export. Keep the process tied to authorised access: the backup should use their permitted role, not somebody else's password. A predictable evidence routine reduces last-minute guessing without requiring the restaurant to publish or centralise unnecessary personal records.

Write a short lesson from the current close. If the main delay came from inconsistent outlet labels, update the outlet mapping. If several fee invoices were confused with separate payments, add a clear settlement-method field to the register. If an incomplete report was mistaken for a zero-sales day, add a completeness check before totals are approved. The improvement should address an observed error and have a simple way to confirm that it worked.

Keep the close pack understandable when you return to it later. Use plain descriptions for unusual entries and link to the exact source version. Avoid unexplained shorthand known only to the preparer. A new reviewer should be able to tell what happened, which amounts changed and which questions remain. That continuity is particularly important when the person running restaurant service is different from the person preparing financial records.

Record corrections so the next month starts correctly

Keep a correction log separate from the raw sources. Each correction should name the original record, explanation, effect, evidence and approval where the business requires it. Preserve the original value and the corrected interpretation. If a transformation error caused the problem, correct the transformation rather than manually changing only the final total. Otherwise the same error can reappear when the next export is processed.

Version the affected schedules and explain which totals changed. A revised closing platform receivable changes the next month's opening balance. A corrected stock valuation can affect food used. A reclassified invoice may move between periods or categories under the appropriate policy. Trace those consequences before issuing a revised close pack. Do not quietly replace the prior version without telling the authorised people relying on it.

Carry unresolved items forward with their original history. Do not create a fresh unexplained opening item that loses the previous investigation. When an item clears, record the statement or response that resolved it and the date. A later reader should be able to distinguish a received credit, an accounting reclassification and an amount written off under an approved treatment. These actions have different meanings.

Use lessons from corrections to improve the next preparation cycle. A recurring date mismatch may need a clearer export checklist. Repeated double-counted invoices may need a withholding flag. A stock-unit error may require a better purchasing or count reference. Change one specific control and review whether it works; avoid adding a large form that nobody can maintain during ordinary restaurant work.

Run a review another person can reproduce

Ask the reviewer to trace one sale, one deduction, one supplier item and one bank receipt from source to schedule. Then reverse the direction: select a material schedule amount and locate its source. The two directions test different weaknesses. A workbook can contain all source files yet still add them incorrectly, or calculate correctly from a source population that is incomplete. Both checks matter.

Review totals and narrative together. The note should say that Copper Table has INR 115,000 defined revenue, INR 95,500 selected operating costs, INR 19,500 operating remainder and INR 5,000 closing platform receivable. It should also explain the INR 29,000 matched platform bank receipts. Those statements are more informative than a single green label saying reconciled, because they identify exactly which relationships were checked.

Prepare a handover containing source register, mapping definitions, approved schedules, calculation notes, corrections, exceptions and the next review dates. Keep access appropriate for each role. A manager planning food production may need aggregate demand and cost information rather than raw bank references. A bookkeeper may need financial records without unrestricted platform administration. Use the actual account controls available to the business.

Finish by deciding one operational action and one evidence action where needed. An operational action might address a repeated packing error. An evidence action might obtain a missing fee explanation. Keep the questions separate: fixing service can prevent future refunds, while reconciling this month's entries establishes what already happened. Neither task is completed merely by discussing the other.

Practise the close without private files

First, explain why adding Copper Table's INR 40,000 platform sales to its INR 115,000 POS sales is wrong under the stated overlap. The platform amount is already inside the POS total. The correct combined defined sales remain INR 115,000, with INR 75,000 belonging to the other selected routes. This answer depends on the confirmed overlap; it is not a rule that every restaurant's POS automatically includes every marketplace order.

Next, change only the matched platform receipts from INR 29,000 to INR 27,000. Keep opening receivable INR 4,000 and current entitlement INR 30,000 unchanged. Closing amount due becomes INR 7,000. That is a cash-and-clearing change, not automatically a change in current revenue or cost. The next task is to establish whether the extra INR 2,000 is a timing item, an unmatched receipt or another supported adjustment.

Finally, suppose the fee invoice of INR 8,000 was mistakenly entered twice as an operating cost. The faulty selected-cost total would be INR 103,500 and the faulty operating remainder INR 11,500. Removing the confirmed duplicate restores INR 95,500 costs and INR 19,500 remainder. Keep the invoice evidence; remove only the duplicated effect. A well-designed register prevents that mistake by linking invoice and withholding to the same charge.

Sources, research date and implementation limits

Reviewed 17 October 2026. OpenStax's reconciliation chapter supports the bank-and-book distinction. Toast's current reporting FAQ and Uber's report descriptions support separating sales, payment and deposit questions. The examples and figures here are original teaching material, not rewritten provider statements.

Deliveroo's invoice explanation supports its particular document categories. HMRC's scoped record guidance and the IRAS GST record guide show why supporting documents and cash records both matter. They do not establish a single accounting or retention rule for every country. No authenticated merchant account or bank connection was tested for this article.

Use the restaurant workbooks for clearly labelled manual schedules and the payout investigation guide for an unresolved difference. Keep native file headers intact, preserve originals and confirm supported formats before using the settlement analyser. A manual close can organise evidence; it cannot certify accounts, determine a tax position or guarantee a provider payment.