How ExpenseFlow syncs with QuickBooks Online
ExpenseFlow connects to QuickBooks Online via Intuit’s official OAuth 2.0 flow. A bookkeeper authorises a connection per QuickBooks company, and from that point the sync runs continuously in the background. Receipts captured by staff on mobile, forwarded by email, or bulk-uploaded from a back-office workflow get categorised by the AI against the client’s live QuickBooks chart of accounts, vendor list and tax codes, and post as bills, expenses or supplier credits once approved.
The integration is two-way. ExpenseFlow pulls the chart of accounts, the vendor list, every active tax code, the class and location lists (where enabled), and the bank-account structure. The AI uses those live structures so categorisation always lines up with what actually exists in the client’s books. New vendors are created in QuickBooks with the captured details when the AI sees a supplier for the first time. New classes or locations are flagged for review rather than auto-created, because that is a structural decision a bookkeeper usually wants to make consciously.
Receipts post to QuickBooks with the original image attached as a file. Reviewers working inside QuickBooks see the source document inline, which keeps quarter-end review tight and means external audit requests do not have to bounce between systems. The image is also stored hashed and timestamped on ExpenseFlow’s side, so the evidence chain stays intact regardless of what happens to the QuickBooks attachment later.
Tax codes and tracking dimensions preserved
QuickBooks Online has slightly different tax-code mechanics per country variant, and ExpenseFlow’s sync handles the full set:
- UK QuickBooks: standard, reduced, zero-rated, exempt and out-of-scope VAT, plus the reverse-charge codes for construction and imported services
- Australia: GST, GST-free, input-taxed and the not-reportable variants used for FBT treatments
- New Zealand: 15% GST, zero-rated, exempt and no-GST
- Canada: the federal GST, HST per harmonised province, plus PST / RST / QST as separate line components where the receipt requires it
- Singapore: 9% GST (current rate), zero-rated, exempt and out-of-scope
Mixed-rate receipts post line by line, so a single QuickBooks transaction can carry several tax codes. Classes and locations default from per-client rules: the supplier, the staff member who captured the receipt, the GL account, or a project tag. That keeps the reviewer focused on exceptions rather than the routine 80% of receipts that should code themselves.
Multi-jurisdiction support
ExpenseFlow’s QuickBooks Online integration works identically across every country variant Intuit serves. A practice managing a mixed portfolio (UK head office plus an Australian or Canadian subsidiary, for example) uses the same integration with the same plumbing. The per-jurisdiction differences live in the tax-code mapping and the local receipt-format conventions the AI knows about, not in the integration itself.
For country-specific tax-rule depth, the jurisdiction pages walk through the local edge cases the AI catches at capture: United Kingdom VAT and MTD readiness, Australian BAS, New Zealand IRD coverage, the Canadian GST/HST/PST split, and Singapore IRAS compliance.
Common QuickBooks Online integration questions
Practical questions about the QuickBooks integration are covered in the FAQ below: direction, cadence, multi-currency, attachments and edit reconciliation. The short version is that the integration is designed to stay out of the way. It posts cleanly, holds documents in review until approved, and only escalates the exceptions a human needs to handle.
Connecting a client takes under a minute through Intuit’s standard OAuth consent. Disconnecting is just as quick, and ExpenseFlow keeps the captured documents on its side regardless of the connection state, so the audit trail does not break if you ever switch accounting platform.