AI can do most of the typing: reading receipts and supplier invoices, suggesting categories for bank lines and matching card deposits to sales. A person still checks the judgement calls: tips, sales tax, odd purchases, stock and month-end cut-offs. An accountant reviews the month before anything is filed.
Restaurants make this harder than most small businesses, because one night's takings arrive in pieces: food, drink, tax, tips, card fees and delivery-platform commission, and only some of that is income. An AI that books the card deposit as "sales" will produce a profit figure that looks wonderful for about a day.
A useful rule: hand over what can be checked against a document and costs little when wrong, and keep what turns on a rule or a judgement. Receipts, deposits and sums sit on the first side. Tips, tax treatment, stock and the month-end cut-off sit on the second.
Three questions that sort every bookkeeping task
Ask of each task: can the answer be checked against a document, such as an invoice, the POS report or a bank statement? What does a mistake cost, a few dollars or tax, wages and a bad decision? Is the answer a rule or a judgement? AI does well where the answers are yes, a little, and a rule. It needs a person where no document settles the question, where mistakes compound, or where the answer takes judgement.
| Task | The AI's part | A person's part | Why the split |
|---|---|---|---|
| Reading invoices and receipts into bills | Extract supplier, date, total, tax and lines | Spot-check totals; always check credit notes and duplicates | The document is the proof, but credit notes and mixed receipts fool readers |
| Coding bills to food, drink, packaging, cleaning | Apply supplier rules; suggest for new suppliers | New suppliers and mixed invoices | Rules cover repeat suppliers; the edges need judgement |
| Categorising bank lines | Suggest an account with a confidence level | Every flagged line, plus a sample of the rest | Cheap to check, costly if a wrong rule repeats all month |
| Posting daily POS sales | Map categories, tax, tips and payment types to accounts | One day a week against the POS end-of-day report, and the monthly total | A mapping error repeats every day |
| Matching card deposits to POS days | Show the arithmetic, day by day | Variances, chargebacks and timing | A sum with a document on each side |
| Tips collected and paid out | List collected and paid for each period | The liability balance against payroll, every month | Staff are owed the money, so it must be right |
| Totalling sales tax by rate | Add up what the POS charged | Whether the rates and exemptions are right, and the filing | Rules differ by item and by place, and errors carry penalties |
| Filing the tax return | Nothing | Owner or accountant | Legal responsibility stays with you |
| Payroll and holiday pay | Nothing (payroll software calculates) | Payroll provider and accountant | Rules, deadlines and employee rights |
| Stock value and cost of goods sold | Do the sum once the counts exist | Do the count; decide write-offs | The shelf is physical |
| Accruals, prepayments, depreciation, loan interest | Draft suggestions from the documents | Accountant | Judgement about timing and treatment |
| Personal spending and owner drawings | Flag lines that look personal | Owner decides | Only you know what it was |
| Supplier price changes | Compare invoice lines over time and flag rises | You decide whether to switch | Spotting is mechanical; choosing is commercial |
| Month-end summary and query list | Draft it | Read before it goes anywhere | A confident wrong summary is worse than none |
Filing returns, running payroll and deciding how an odd transaction is treated never sit on the AI's side of that table, and that is deliberate. "AI" here means whichever of three things you use: the features inside your accounting software, a connector from your POS, or a chat assistant working on an export. The split is the same for all three.
One month at a 45-seat restaurant: who did what
These figures are made up for illustration; replace them with your own. The restaurant charges a flat 8 per cent sales tax on everything and takes cash and cards.
| Item | Figure |
|---|---|
| Net sales (food $41,500, drinks $15,800), after discounts and comps of $1,150 | $57,300 |
| Sales tax collected at 8% | $4,584 |
| Cash takings (sales and tax) | $7,900 |
| Card payments for sales and tax ($57,300 + $4,584 - $7,900) | $53,984 |
| Card tips collected | $6,420 |
| Card processing fees | $1,542 |
| Card refunds | $186 |
| Expected card deposits ($53,984 + $6,420 - $1,542 - $186) | $58,676 |
Now the month's work, step by step, with the split between the machine and the owner:
| Step | What happened | AI's part | Person's part |
|---|---|---|---|
| Daily sales | 30 daily summaries posted | Mapped categories, tax, tips and payment types; flagged days that did not foot | Owner compared one day a week with the POS end-of-day report |
| Supplier documents | 64 invoices and receipts | Read and coded 55 correctly | Fixed nine: two duplicates, three delivery notes, two credit notes, two mixed receipts |
| Bank feed | 212 lines | Suggested accounts; 171 high confidence, 41 flagged | Reviewed all 41 and sampled 20 of the 171; changed six |
| Card deposits | Four weekly reconciliations | Matched deposits to POS days and showed the arithmetic | Chased a $23 difference in week three |
| Tips | $6,420 collected | Listed collected against paid | Confirmed the $440 still owed with payroll |
| Sales tax | $4,584 collected | Totalled by rate; worked out the ratio to sales | Confirmed the rates; caught an untaxed dish |
| Stock and cost of goods | Month-end count | Did the sum | Counted the shelves; chose write-offs |
| Month-end pack | Profit and loss draft | Drafted a summary and a query list | Read it, then sent it to the accountant |
About four in five bank lines needed only a sample check, and nearly all of the owner's time went on the 41 flagged lines, the nine odd documents and the deposit that did not match. That is the pattern worth planning for: the AI clears the routine bulk, and a person spends the saved time on exceptions.
Receipts and supplier invoices: what capture reads and misreads
Capture tools read a photo or PDF and create a draft bill. Xero lists Smart Document Capture on all three of its plans. Dext's Business plan is $302.50 a year for 250 documents a month and five users. Intuit says QuickBooks' Accounting AI is on the Essentials, Plus and Advanced plans, not Simple Start. Match the limits to your volume: Xero's pricing page lists its Early plan ($27 a month list price, with a first-six-months discount shown) as "Enter 5 bills", so a restaurant with 64 supplier documents a month should price the plan above it, Growing at $59. Confirm all of these on the vendor pages, because plans change.
Of the 64 documents, 55 came through right. The nine that did not show where these tools slip:
- Two duplicates. A supplier emailed an invoice and the driver also handed over a paper copy, so both were captured. Defence: duplicate detection on supplier, number and amount, and a monthly comparison of each main supplier's statement with your bills.
- Three delivery notes read as invoices. The note lists quantities and sometimes prices, so the reader treated it as a bill. Defence: keep delivery notes out of the invoice inbox and match them to the invoice later.
- Two credit notes booked as costs. A $96 credit for spoiled produce arrived as a $96 expense. Defence: a rule that any document with "credit" in its title, or a negative total, goes to a person.
- Two mixed receipts. A cash-and-carry receipt with food, cleaning supplies and bin liners. Defence: split by line before coding, or ask whoever shops to keep cleaning items on a separate receipt.
One rule keeps everything else safe: the AI drafts bills, and a person approves and pays them. Once invoices flow in cleanly, the same lines show price movements, which is the subject of catching supplier price creep on hospitality invoices. For a deeper look at the capture tool itself, whether Xero Smart Document Capture is enough without Dext compares the two.
Daily sales: split the POS summary before it reaches the books
The POS knows what was sold. The books need to know what each part means. A day's summary holds food sales, drink sales, discounts, tax, tips, gift cards and the ways customers paid: cash, card, a delivery platform. Only some of that is income. The usual route is a connector or a CSV that posts one journal a day, with each line mapped once to an account.
Toast's partner directory lists two examples of such connectors. Sync, powered by xtraCHEF, is listed as posting daily sales journal entries to QuickBooks Online; it runs through xtraCHEF, so check which xtraCHEF subscription it needs before you plan around it. Bookkeep lists QuickBooks Online, Xero, Sage Intacct, Zoho Books and NetSuite, and captures sales, tax, tips, discounts, gift cards, payments and processing fees. If you use another POS, look for its list of accounting integrations, or export the daily summary as a CSV and map it yourself once.
Here is a realistic mistake and how it showed up. In the first month, the bank feed brought each card settlement into the books as income, while the daily journals also booked the sales. The books showed $115,976 of income against a POS monthly report of $57,300: the sales figure plus the $58,676 of card deposits, so most of the month's takings were counted twice. Profit looked superb until the owner compared the monthly total with the POS report.
The fix has two parts. Card settlements and delivery-platform payouts land in a clearing account that the daily journals clear, and never in income. And a monthly reasonableness check becomes routine: net sales in the books must match the POS monthly report to the dollar. Delivery-platform payouts deserve the same treatment, because they arrive net of commission and fees and will never equal that platform's sales.
Tips are a liability until they are paid out
Card tips pass through your bank account but belong to staff. In the books they sit in a liability account called something like tips payable, not in sales. This month $6,420 was collected on cards and $5,980 was paid out through payroll, so $440 was still owed at month-end. That closing balance should match what staff are actually owed for the last days of the month.
Errors to look for: tips booked as sales, which overstates revenue, or the payout booked as a cost, which counts the same money twice. A third is tips lumped into the card deposit line so that nobody can see them. The check takes two minutes: the opening balance, plus tips collected, less tips paid, must equal the closing balance, and the closing balance should fall close to zero after each payout run. A balance that grows quietly means someone's tips are late or wrong.
Two cautions belong with the accountant, not the AI. Cash tips that staff keep directly sit outside your books, but a tip pool has rules of its own. And a service charge that the restaurant adds to the bill is treated differently from a voluntary tip in many places, for tax and for payroll. Ask your accountant which you have and how to record it. If you are drafting a pooling policy at the same time, can AI draft a fair tip pooling policy under the rules covers it.
Sales tax: let AI add it up, let a person decide the rules
The POS charges tax item by item. The AI can total what was collected by rate from the daily summaries and park it in a payable account. A person confirms that the rates and exemptions are right and that the return is filed. Menu prices that include tax, rates that differ between eating in and taking away, gift cards, refunds and service charges can all change the answer in some places. That is a question for your accountant, not a prompt.
One check catches a surprising number of POS setup errors: tax collected divided by net sales should sit at your blended rate. This restaurant's month comes out at exactly 8.0 per cent ($4,584 on $57,300). If you charge more than one rate, work out your normal blend first.
Here is how it caught a typical set-up error. A seasonal dish was added to the POS with no tax rate set, and it sold $600 in a week when net sales were about $14,325. The week's ratio fell from 8.0 per cent to 7.7 per cent ($1,098 on $14,325). The AI's weekly ratio line flagged it on Monday. The owner corrected the rate in the POS and told the accountant, who advised on the $48 of tax that had not been charged. Without the ratio check, the first sign would have been a return that did not tie to the books.
Card deposits: the week-three reconciliation
Deposits never equal sales. The sum is: card sales plus card tips, less processing fees, refunds and chargebacks, equals the deposit. Here is week three of the month, with the figures from the POS card report and the bank:
| Line | Week 3 |
|---|---|
| Card sales including tax | $12,640 |
| Card tips | $1,480 |
| Gross card total | $14,120 |
| Less processing fees | -$361 |
| Less refunds | -$42 |
| Expected deposits | $13,717 |
| Deposits received | $13,694 |
| Difference | -$23 |
The $23 turned out to be a $15 dispute fee and an $8 statement fee that the processor deducted. The AI can build this table from the POS card report and the bank lines. Insist on seeing the arithmetic, ideally in a spreadsheet with formulas rather than a chat answer, because language models can slip on sums and a formula lets you see the working. Plan for timing too: a weekend's card batches may not land until Monday or Tuesday, so each reconciliation needs a "deposits in transit" line, and a person decides whether a gap is timing or a genuine miss. The method for checking AI matches generally is in automating bank reconciliation with AI and checking the matches.
A categorisation prompt, a sample answer and the fixes
For the 41 flagged lines, and for a second opinion on the rest, a chat assistant is useful on a redacted export. Strip account numbers and names, then paste:
Below is a redacted bank export for a 45-seat restaurant (CSV: date, description, amount).
Our chart of accounts: Card clearing, Delivery platform clearing, Cost of sales - food, Cost of sales - drink,
Packaging, Cleaning, Utilities, Rent, Bank and card fees, Repairs, Loan, Owner's drawings, Staff welfare.
For each line give: suggested account, confidence (high, medium, low) and a one-line reason.
Rules:
- Card settlements and delivery-platform payouts go to their clearing accounts, never to sales.
- Transfers to the owner are drawings, never expenses.
- If a line could be split between accounts (cash-and-carry, supermarket), write SPLIT and say what you need.
- If you are unsure, ask a question instead of guessing. Do not invent suppliers or invoice numbers.
A realistic answer, with what a person would change:
| Bank line (illustrative) | Amount | AI suggestion | Person's fix |
|---|---|---|---|
| CARD SETTLEMENT | +$2,184.10 | Card clearing (high) | None |
| PRODUCE SUPPLIER | -$1,236.40 | Cost of sales, food (high) | None; matches an approved bill |
| CASH AND CARRY | -$214.30 | Cost of sales, food (medium) | Split: $168.20 food, $46.10 cleaning, after reading the receipt |
| GAS AND POWER DIRECT DEBIT | -$486.20 | Utilities (high) | None |
| STAFF PARTY VENUE | -$380.00 | Staff welfare (low) | Asked the owner; it was a private booking, so owner's drawings |
| TRANSFER TO OWNER | -$1,500.00 | Owner's drawings (high) | None |
| LOAN REPAYMENT | -$950.00 | Loan (medium) | Split interest and principal from the lender's statement |
| DELIVERY PLATFORM PAYOUT | +$1,372.55 | Delivery platform clearing (high) | Reconcile to the platform's own statement, not to POS sales |
Three of those eight needed their category changed or split, and all three were flagged medium or low by the AI, which is the point of asking for confidence. The payout line needed a check rather than a change. The staff party line is the instructive one: an AI cannot know whether a payment was for the business or personal, and it should say so rather than pick. Use your accounting software's bank rules for repeat lines, such as the gas and power direct debit, because rules behave the same way every time, and keep the chat assistant for the oddments. The broader question of what still needs an accountant is covered in can AI do my bookkeeping.
Stock, accruals and the entries only a person can make
Cost of goods sold is opening stock plus purchases, less closing stock. This month: $6,200 plus $23,250 less $6,650 is $22,800, which is 39.8 per cent of net sales. The AI can do that sum in a second. It cannot count the shelves. A person counts, decides what to write off (spoiled stock, staff meals, comps) and decides whether a case of wine bought for a private event belongs in stock or in an expense. Compare the result with your recipe costs, as in building a recipe costing spreadsheet with ChatGPT, because a gap between theoretical and actual cost is often where waste hides.
Then there are the entries that depend on timing and treatment. Three bills for deliveries made in the month arrived after it ended, $1,260 in all, so someone decides they belong in this month. Insurance paid for a year is not a one-month cost. A deposit taken for a private event is not income until the event happens, and a gift card sold is a liability until it is redeemed. Equipment loses value over time. A loan repayment is part interest and part principal. The AI can draft each of these from the documents, but the treatment comes from your accountant's rules, and an unreviewed guess here changes profit and tax.
What goes to the accountant, and what to ask them
A tidy month-end pack makes the review shorter and cheaper. Send the profit and loss draft, the bank reconciliation, the tips payable and sales tax payable balances with their workings, the clearing accounts (which should sit near zero), the stock sheet, the list of the month's AI queries with what you decided, and any owner's drawings you identified. Ask the accountant these questions once, early, and write down the answers:
- Which of my sales are taxable, at what rates, and how should unusual items such as gift cards and service charges be treated?
- How do you want tips and service charges recorded, and how should payouts appear in payroll?
- Which entries may be posted without your review, and which must wait for it?
- How often will you review: monthly, quarterly, at year-end?
- What would make you reject an AI-prepared file, and what do you want attached?
The answers become the rules you give the AI, which closes the loop. Keep posting approval switched on until a few months of checks have come back clean, because letting an assistant post unreviewed entries is the riskiest setting.
Keep payroll and bank logins out of the chat
Bank exports, payroll reports and supplier contracts hold personal and commercial data. Use a business plan where the vendor says business content is not used for training by default, which is the position for ChatGPT Business, Claude Team, Microsoft 365 Copilot and Gemini in Workspace. On a consumer plan, find the model-training switch in privacy settings and turn it off. Redact account numbers and staff names before pasting. Do not give a browser agent your banking login: Anthropic's safety page for its browser agent says to avoid financial accounts.
Finally, keep your own monthly export of the books outside any single tool. Online services close: Bench, an online bookkeeping service, shut down on 27 December 2024. A monthly backup of the ledger, the bank reconciliation and the month-end pack means a supplier's decision never leaves you without your records.
Questions restaurant owners ask about AI bookkeeping
Can AI keep track of cash takings?
It can record the counts you give it and compare them with the POS cash total, but it cannot count the drawer. Have the closing manager count and record the float and takings each night, bank them on a fixed routine, and let the AI flag any day where counted cash and POS cash differ by more than a set amount, such as $5.
Do I still need an accountant if AI does the books?
Yes. AI drafts entries; an accountant decides how unusual items are treated, files or checks returns and spots problems that only show up across months. Treat the AI as a faster bookkeeper whose work always gets reviewed, not as a replacement for professional advice.
How often should a person check the numbers?
Weekly for card deposits, tips and one daily sales summary against the POS. Monthly for the full bank reconciliation, stock and accruals. Agree a review rhythm with your accountant too, such as quarterly and at year-end. Check more often in the first two months, while you learn where the tool slips.
Can capture tools read handwritten invoices and faded till receipts?
Less reliably than printed PDFs. Handwritten delivery dockets, faded thermal receipts and creased phone photos are where misread totals and dates cluster, so route them to a person for a check. Ask regular suppliers to email PDF invoices, photograph paper receipts flat on the day you get them, and keep the originals until the month is closed.
Further reads
- AI Receipt Capture and Bank Categorisation: A Bookkeeper's Setup — A bookkeeper's setup for receipt capture and bank rules.
- How to Speed Up Month-End Close in a Small Business With AI — A month-end routine you can reuse for any small business.
- AI Software for Restaurants: POS-Built AI or an Add-On Tool? — Which restaurant software already includes AI and which needs add-ons.
- Restaurant Labour Cost Percentage: Test Rota Changes With AI First — Test rota changes before they reach payroll and the books.
- Restaurant Pre-Shift Meeting Notes: Draft Them From POS Data With AI — How to draft a daily pre-shift briefing from a POS export or Toast IQ: yesterday's numbers, sold-out items, today's covers forecast and specials.
- Restaurant Supply Ordering: Compare Prices and Draft Orders — A weekly workflow: two supplier price lists in one sheet, AI-flagged cheapest lines and substitutes, price-creep alerts and draft orders from par levels.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Xero's USD pricing page and Toast's partner listings for Sync powered by xtraCHEF and Bookkeep (checked 28 October 2026), Dext's pricing page, Intuit's QuickBooks help pages, Anthropic's safety guidance for its browser agent, and restaurant bookkeeping guides from accounting firms on tips, sales tax and deposit reconciliation.