Your QuickBooks data, finally analysed properly.
Most "QuickBooks integrations" push your invoices into QB and stop there. OmniPATH does both directions: invoices and journals out and a persistent local mirror of your P&L history, bank transactions and customer balances back in. So LEDGE can run trend analysis QuickBooks itself can't.
What goes which way. And why.
Most "integrations" are one-way pushes that treat your accounting tool as a write-only destination. OmniPATH treats QuickBooks as both source-of-truth (for what's posted) and as a data lake to be enriched and analysed.
Invoices, journals, vendors. Posted clean.
Every approved purchase invoice in OmniPATH posts to QuickBooks as a Bill, with the line items mapped to your GL codes, the vendor matched to the QB Vendor record and the AP sync status tracked back in OmniPATH for audit.
- Purchase invoices as Bills, with line-items split by GL code
- Vendor records created or matched on first invoice from a new supplier
- Expense reimbursements posted as Bills to the employee's vendor record
- Sync status tracked per invoice - `ap_sync_at`, `external_id`, retries on failure
P&L, banking, customers. Stored locally.
Five data types pulled from QuickBooks and stored persistently in OmniPATH - so we can run trend analysis, reconciliation and customer analytics without rate-limiting QB or losing historical context when you change reports.
- P&L + Balance Sheet snapshots · daily, persistent, 6-year history
- Bank transactions from connected feeds, refreshed every 30 min
- Customer master + AR aging · names, balances, overdue amounts
- Chart of accounts mapped to OmniPATH GL codes via `xero_id` field
- Tax rates per account - used for VAT auto-calc and review checks
The bit other integrations don't do.
Most QuickBooks integrations cache reports for 4 hours and refetch when the cache expires. OmniPATH stores them permanently, so your historical view doesn't depend on what QuickBooks is willing to recompute today.
P&L history that doesn't expire.
OmniPATH takes a daily snapshot of your P&L, Balance Sheet and cash position from QuickBooks and stores it permanently. Long-term history, queryable in milliseconds, never subject to the QuickBooks API recomputing differently because someone reclassified a transaction in March.
So when LEDGE answers "How has our gross margin changed over six months?" - it's reading from snapshots, not asking QuickBooks to re-render six months of P&L on demand.
- Daily P&L · Balance Sheet · Cash Position captured
- JSONB storage - preserves the exact report shape at point of capture
- Long-term retention - snapshots accumulate for as long as you're connected
- Powers LEDGE trend analysis without hitting QB rate limits
What actually cleared the bank.
OmniPATH syncs bank-feed transactions from QuickBooks every 30 minutes - payments out, deposits in, fees, transfers. Stored locally with reconciliation status, so OmniPATH can verify "this invoice we approved actually paid" without round-tripping to QB for every check.
This is what powers LEDGE's cash-position answers - giving you visibility into what's actually cleared the bank alongside what's been approved in procurement.
- 30-minute refresh from connected QB bank feeds
- Account-level granularity - current, savings, credit cards, FX
- Reconciliation status preserved (matched / unmatched in QB)
- Supplier-name parsing for unmatched payments
Your customers, scored.
Every QuickBooks customer record is mirrored locally with current outstanding balance, overdue amount and AR aging bucket. So LEDGE can answer "Which customers represent 70% of our revenue?" or flag "Olive Group is now 45 days overdue" without you running a manual aged-debtors report.
This is the data layer behind revenue concentration analysis, customer health scoring and customer health visibility.
- Customer name, email, type, contact info synced
- Live outstanding balance + overdue amount per customer
- AR aging buckets: current / 30 / 60 / 90+ days
- Powers concentration analysis and dunning workflow triggers
What we've just shipped.
Features that went live in the latest release - expanding the QuickBooks integration into full expense sync with intelligent vendor handling.
Approved expenses pushed as QBO Purchase entities. Company card expenses use CreditCard PaymentType, personal reimbursements use Cash.
Finds vendor by DisplayName before creating a new one. Prevents duplicate vendor records building up in QuickBooks over time.
qb_purchase_id stored on every synced expense. Duplicate push prevented - safe to retry without creating duplicate records in QBO.
Supplier bank details encrypted at rest with Fernet. Masked in API responses (****5678). Full reveal requires Admin role and creates an audit event.
Single POST endpoint auto-detects connected provider. Same response shape across Xero, QuickBooks and Sage. Per-org toggle to enable or disable.
Every sync returns { ok, already_synced, provider, external_id } - consistent across all three accounting providers. One integration pattern for your team.
Ask things that QuickBooks alone can't.
Because LEDGE has both your live procurement data AND a persistent history of QB snapshots, it can answer questions that need both sides of the picture - questions that would normally mean exporting two CSVs and pivoting in Excel.
OAuth in. Sync starts.
The QuickBooks connection uses Intuit's standard OAuth 2.0 flow. No file uploads, no data exports, no IT involvement.
Click connect
From OmniPATH Settings → Integrations, click "Connect QuickBooks". You're redirected to QuickBooks Online to authorise OmniPATH against the realm of your choice.
Map your accounts
OmniPATH pulls your full chart of accounts and lets you map OmniPATH GL codes to QB accounts. Defaults are pre-populated based on common naming. Five-minute task.
First sync runs
Initial sync brings down 24 months of P&L history, your customer list, vendor list and bank-feed transactions. Push side activates on next approved invoice. Done.
The technical details.
Which QuickBooks editions are supported?
Will OmniPATH duplicate Bills if my team also keys invoices into QB manually?
What happens to the snapshots if we disconnect QuickBooks?
How does the bank-transaction mirror handle un-categorised transactions?
What about payment terms, credit notes and partial payments?
How is the data secured?
QuickBooks. With memory.
Two-click OAuth, daily snapshots, bank mirror and customer balances. Bring your QB realm to the demo and we'll connect it live.