Sound familiar?
What Clover merchants who keep books in QuickBooks tell us before a project starts.
- After closing I copy the Clover totals into QuickBooks.
- The processor deposit is short and I can't see which fees took the difference.
- Tips show up as sales and the payroll side never sees them.
- Cash, card and gift card sales all land in one account.
- A refund last week made this week's report look wrong.
What we build
Each one is a working piece you can open and check when it's done.
Tenders and categories mapped
Cash, card, gift card and other tenders, plus item categories and tax, each map to the QuickBooks account you choose, so the entry reads like your own books.
QuickBooks, Xero and HubSpot integrations API integrations and data syncTips, discounts and refunds
Tips go to a liability account, discounts are shown as discounts, and refunds post against the day they were given with the tax reversed.
QuickBooks, Xero and HubSpot integrationsCard fees and batch deposits
Processor fees go to an expense account and each batch is recorded as one deposit net of fees, so it equals the bank line.
QuickBooks, Xero and HubSpot integrations Python scripts and utilitiesAlerts when a batch fails
A missing account, a locked period or a lapsed Clover authorisation sends the date and cause to email or Slack, and the batch can be re-run once repaired.
n8n, Make and Zapier automationBackfill of past months
Earlier sales from your chosen date are loaded into a test company, compared with your current books, and then added to the live one.
ETL and data pipelinesReconciliation and handover
A weekly report matches deposits to sales and fees, and short notes explain the mapping so your bookkeeper can change it without us.
Dashboards and reportingThe two tools: Clover, QuickBooks.
Also connected on request: Clover, 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
Closing the day in one entry
Example: a convenience store wants each Clover day close to post one summary entry to QuickBooks, split by tender and tax rate.
Clover REST API, QuickBooks Online API, scheduled jobExample project
Tips owed to staff
Example: a pizzeria wants card tips from Clover held in a liability account each day, with a total ready for payroll.
Clover payments, QuickBooks Online, Google SheetsExample project
Two stores, one bookkeeper
Example: a frozen yogurt owner with two Clover merchants wants each store posted to its own QuickBooks class and a combined view each Monday.
Clover merchants, QuickBooks classes, Slack alertsQuestions people ask first
Isn't there already a native connector or app for this?
Apps in the Clover app market and other tools connect Clover to QuickBooks, and for some shops they are enough. We check yours first. If it fits, we set it up properly. If how it summarises sales, tips or fees is the problem, we build around it.
Will it change our existing books?
Only in the ways agreed. We test in a copy first and compare totals with yours before anything reaches the live company.
Who owns what you build?
You do. It runs in your own Clover and QuickBooks accounts, with notes on how to change it.
How do we start?
Tell us how many Clover locations you run and how your bookkeeper books a 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