Which accounting tools does TuringDock integrate with?

QuickBooks Online today, one connection per workspace, over standard OAuth. Xero is next (the integration is built around a shared provider interface, so adding it is straightforward). If your accountant uses Sage, FreshBooks, or Wave, tell us at hello@turingdock.com so we can prioritize.

What gets pushed, and when?

Shipments push as invoices, supplier bills push as bills, and payments push applied to the matching invoice or bill, the moment you record them. It is one-way (TuringDock to your books); stock movements stay inside TuringDock. Re-recording the same shipment or payment never double-posts.

How does tax mapping work?

After OAuth, you pick which of your real QuickBooks tax codes your default rate maps to, and that choice applies to every invoice we push from then on.

What happens if a push fails?

The provider’s exact error is recorded in the Settings activity log, so a failure is visible rather than silently dropped. Nothing is lost: the TuringDock record is the source of truth and the push is only a copy.

Is the connection secure?

OAuth tokens are encrypted at rest with AES-256-GCM, access tokens are short-lived, and refresh tokens rotate on every use. Disconnect drops the tokens immediately, the same pattern as our Slack integration.

Does this post inventory journal entries (the perpetual-ledger MRP bar)?

Not yet. Today the integration covers the AR/AP layer, the records most QBO integrations stop at: customers, vendors, invoices, bills, and payments. The perpetual inventory-ledger journal entries (PO receipt, COGS at shipment, production, cycle counts, landed cost, revaluation) are the next phase. The table above marks what is live versus planned.

Can a customer or accountant review what we sync before signing?

Send them this page. The table above is the authoritative list of what posts today and what is planned, with no hidden behaviour. The in-product activity log is the live record, scoped to your workspace.

Money

Your books stay in lockstep. Without the re-keying.

Connect QuickBooks Online once, and every shipment, bill, and payment posts straight to your books, no re-typing.

Get started for free Talk to the founder

The new way

How this works in the future of MRP.

You shipped four orders Tuesday and now have to re-type each one into QuickBooks before the books match. TuringDock pushes every shipment, bill, and payment the moment it happens, so there is nothing to re-key.

How it works

Connect in 10 seconds

Authorize on QuickBooks’ OAuth screen once, then pick which QuickBooks tax code your default rate maps to.

Shipments become invoices automatically

Record a shipment and TuringDock pushes the invoice with the mapped tax code and the same order number.

Supplier bills and payments post too

Record a supplier bill or a payment and it posts as a bill or an applied payment. One-way: TuringDock is the source of truth, your books are the copy.

What we never touch

Bank feeds, payroll, remittance, and year-end stay your accountant’s; we only push shop-floor transactions.

What we push to your books

A per-event list of what TuringDock posts to QuickBooks Online. The AR/AP layer below is live today; the perpetual inventory-ledger journal entries, the depth a NetSuite, SAP Business One, or Acumatica clears, are the next phase and are marked as planned.

AR & AP layer · live today

The records most QBO/Xero integrations stop at. Customers, vendors, invoices, bills, payments, sales tax.

TuringDock event	Posts to QuickBooks	Accounts touched
Customer created/edited	Customer record	—
Supplier created/edited	Vendor record	—
Inventory item created/edited	Inventory item with unit cost	Inventory Asset
Customer-order shipment recorded	Invoice with line items + sales tax	DR Accounts Receivable / CR Revenue + Sales Tax Payable
Customer payment recorded	Receive Payment applied to invoice	DR Undeposited Funds (or Bank) / CR Accounts Receivable
Supplier invoice recorded	Bill with line items + tax	DR Expense or Inventory / CR Accounts Payable
Supplier payment recorded	Pay Bill applied to bill	DR Accounts Payable / CR Bank

Perpetual inventory ledgerRolling out

Every inventory-affecting event posts a journal entry, so your inventory value in QuickBooks matches what TuringDock says you have. This is the industry-standard MRP bar, the depth a NetSuite, SAP Business One, or Acumatica clears. The receipt, bill-match, shipment, production, and cycle-count entries are live; landed cost and revaluation are rolling out.

TuringDock event	Posts to QuickBooks	Accounts touched
PO physically received at the dockLive	Journal entry, immediate	DR Inventory / CR Goods Received Not Invoiced (GRNI)
Customer shipment leavesLive	Journal entry paired with the invoice push	DR COGS / CR Inventory
Supplier bill arrives + matches the receiptLive	Bill posted to the GRNI clearing account	DR GRNI / CR Accounts Payable
Production task marked completeLive	Journal entry, build cost roll-up	DR Finished Goods / CR Inventory (labor accrual later)
Cycle count variance appliedLive	Adjustment journal entry	DR/CR Inventory ↔ Inventory Adjustment
Landed cost (freight/duty/customs) booked to a receiptPlanned	Allocation journal entry, pro-rata by line value	DR Inventory / CR Landed Cost Clearing
Standard unit cost changed on an item with on-handPlanned	Revaluation journal entry	DR/CR Inventory ↔ Inventory Revaluation Gain/Loss

Tax mapping: one-time setup, transparent forever

After OAuth, you pick which of your real QuickBooks tax codes your default rate maps to, from a dropdown of your actual codes. The mapping persists, so every invoice we push from then on uses it. As the inventory-ledger phase lands, the same screen will map the ledger accounts (Inventory Asset, GRNI, COGS, and the rest).

Every push is idempotent: re-recording the same shipment or payment never double-posts. A failed push surfaces in the in-product activity log with the provider's error verbatim, so it is visible rather than silently dropped.

Sync log + last-sync visibility, in-product

Settings → Integrations shows the last successful sync timestamp, a failed-event count if any need attention, and the last 50 sync events as an activity feed: timestamp, status icon, what was posted, the external reference in QuickBooks, and the provider's error message if it failed. Auditable.

Common questions

Which accounting tools does TuringDock integrate with?: QuickBooks Online today, one connection per workspace, over standard OAuth. Xero is next (the integration is built around a shared provider interface, so adding it is straightforward). If your accountant uses Sage, FreshBooks, or Wave, tell us at hello@turingdock.com so we can prioritize.
What gets pushed, and when?: Shipments push as invoices, supplier bills push as bills, and payments push applied to the matching invoice or bill, the moment you record them. It is one-way (TuringDock to your books); stock movements stay inside TuringDock. Re-recording the same shipment or payment never double-posts.
How does tax mapping work?: After OAuth, you pick which of your real QuickBooks tax codes your default rate maps to, and that choice applies to every invoice we push from then on.
What happens if a push fails?: The provider’s exact error is recorded in the Settings activity log, so a failure is visible rather than silently dropped. Nothing is lost: the TuringDock record is the source of truth and the push is only a copy.
Is the connection secure?: OAuth tokens are encrypted at rest with AES-256-GCM, access tokens are short-lived, and refresh tokens rotate on every use. Disconnect drops the tokens immediately, the same pattern as our Slack integration.
Does this post inventory journal entries (the perpetual-ledger MRP bar)?: Not yet. Today the integration covers the AR/AP layer, the records most QBO integrations stop at: customers, vendors, invoices, bills, and payments. The perpetual inventory-ledger journal entries (PO receipt, COGS at shipment, production, cycle counts, landed cost, revaluation) are the next phase. The table above marks what is live versus planned.
Can a customer or accountant review what we sync before signing?: Send them this page. The table above is the authoritative list of what posts today and what is planned, with no hidden behaviour. The in-product activity log is the live record, scoped to your workspace.

Build what’s next.

Leave the MRPing to our AI. Free to start, set up in an afternoon.

Get started for free

Last updated 2026-06-13 (QuickBooks AR/AP live; Xero + the inventory-ledger journal entries are on the roadmap)