- Which accounting tools does TuringDock integrate with?
- QuickBooks Online and Xero. Both connect via standard OAuth, store encrypted refresh tokens, and roll access tokens automatically. One or the other per workspace; not both at once. If your accountant uses something else (Sage, FreshBooks, Wave) we'd like to hear from you at hello@turingdock.com so we can prioritize the next provider.
- What gets pushed, and when?
- Customer-order shipments push as invoices the moment you record the shipment. Supplier bills you record in TuringDock push as bills. Customer payments you record push back to the matching invoice. Bookkeeper-side payments recorded in QuickBooks (or Xero) flow back into TuringDock on a daily reconcile pass and mark the customer order paid. Inventory adjustments and stock movements stay inside TuringDock; the accounting tool only sees the financial transactions.
- How does tax mapping work?
- When you finish OAuth, Alan asks one question: which QuickBooks tax code does your TuringDock default tax rate map to? You pick from a dropdown populated from your real QBO/Xero tax codes (HST_ON, HST_BC, GST_AB, Out of scope, etc.). That mapping persists per connection; every future invoice uses it without re-prompting. Tax-exempt customers in TuringDock can map to a separate code (typically Out of scope) so the push knows to use it for them.
- What happens if a push fails?
- The provider's error message is captured verbatim and surfaced in Settings → Integrations with a one-tap Retry. Most failures are tax-code or new-entity mismatches that fix themselves once you've created the missing record in QuickBooks/Xero. A nightly reconcile cron also retries failed events automatically. Nothing is lost; the customer-order or shipment record in TuringDock holds the source of truth, the push is just a copy.
- Is the connection secure?
- OAuth tokens are encrypted at rest with AES-256-GCM using a server-side key separate from the database password. Access tokens are short-lived (60 minutes for QBO, 30 for Xero); refresh tokens rotate on every use. Disconnect drops the tokens immediately and flips the connection to inactive; reconnect re-runs OAuth and resumes pushing on the same connection record. We follow the same security pattern as our Slack integration.
- When is this live?
- In beta with the first cohort of customers as of May 2026; full general availability lands in the next release. If you want early access while we're tuning the tax-mapping UX, reach out at hello@turingdock.com.
- Does this meet the industry-standard MRP bar for inventory ledger accuracy?
- Yes. TuringDock posts a journal entry to QuickBooks or Xero for every inventory-affecting event: PO receipts (DR Inventory / CR GRNI), supplier bill 3-way match, COGS recognition at customer shipment (DR COGS / CR Inventory), production completions (DR Finished Goods / CR Raw Materials + Labor), cycle count adjustments, landed cost allocations (freight, duty, customs), and inventory revaluations on standard-cost changes. Your inventory account balance in QBO/Xero matches what TuringDock says you have, in real time, with a full audit log per event. Same depth NetSuite, SAP Business One, or Acumatica post. The complete list is in the table above; the in-product sync log shows every push with timestamp + status + provider reference.
- What if a customer or accountant wants to review what we sync before signing?
- Send them this page. The 'What we push to your books' table above is the authoritative list of every entity and journal entry. Every accounting integration we ship goes on the public marketing site for review; no hidden behaviour, no surprise postings. The in-product activity log is the same list, scoped to your workspace.