Sound familiar?
What restaurants that run Toast and keep books in QuickBooks tell us before a project starts.
- My bookkeeper rebuilds each day from the Toast sales summary.
- Tips, tip-outs and service charges are all tangled together.
- Comps and voids vanish from the books and I can't see what we gave away.
- Deposits from the processor never match the daily total.
- Food and beverage sales are not split the way my accountant wants.
What we build
Each one is a working piece you can open and check when it's done.
Sales groups to accounts
Food, beverage, retail, gift cards, discounts and tax each map to the QuickBooks account or class you choose, so the daily entry follows your chart of accounts.
QuickBooks, Xero and HubSpot integrations API integrations and data syncTips, service charges and tip-outs
Card tips and service charges go to liability accounts, so what is owed to staff is separate from what the restaurant earned.
QuickBooks, Xero and HubSpot integrationsVoids, comps and multiple locations
Voids and comps are shown on their own lines, and each restaurant location posts to its own class, so the group and each site can both be read.
ETL and data pipelines API integrations and data syncAlerts when a day does not post
A missing mapping, a closed period or a lapse in access sends the date and cause to email or Slack, and the day can be re-run after repair.
n8n, Make and Zapier automationBackfill of past months
Earlier days from your chosen start are loaded into a test company, compared with your current books, and only then added to the live one.
Python scripts and utilitiesDeposit reconciliation and notes
A report ties processor deposits to the days and fees behind them, and notes explain the mapping so your bookkeeper can adjust it.
Dashboards and reportingThe two tools: Toast, QuickBooks.
Also connected on request: Toast, QuickBooks Online, Google Sheets, Slack, Gmail.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Nightly close to QuickBooks
Example: a neighbourhood bistro wants the Toast close-out numbers posted to QuickBooks each morning, with food, drinks and tax on separate lines.
Toast data export, QuickBooks Online API, scheduled jobExample project
Tips held until payroll
Example: a taqueria wants card tips from each day held in a liability account, with a running total for the week's payout.
Toast reports, QuickBooks Online, Google SheetsExample project
Two restaurants, one owner
Example: an owner with two Toast locations wants each site posted to its own QuickBooks class and a combined comparison every Monday.
Toast, QuickBooks classes, Slack alertsQuestions people ask first
Isn't there already a native connector or app for this?
Toast offers accounting integrations through partners, and other tools connect Toast to QuickBooks. For many restaurants one of those is enough. We check yours first. If it fits, we set it up properly. If its limits are the problem, such as how it groups tips or handles several locations, we build around them.
Does it depend on access in our Toast account?
Yes, what we can read depends on the access your Toast account allows. We confirm that at the start and write it into the scope.
Who owns what you build?
You do. It runs in your own Toast and QuickBooks accounts, with notes on how to change it.
How do we start?
Tell us how many locations you run and how your bookkeeper handles a Toast day today. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com