Connect QuickBooks Online to Foundry
Stop re-keying vendor invoices. Approve a bill once in Foundry and it appears in QuickBooks Online, with payment status flowing back so you can see what's still outstanding without leaving your purchasing screen.
What you'll get
- • Vendor invoices in Foundry become bills in QuickBooks automatically
- • Bill totals always match the Foundry invoice, to the cent
- • Payment status reads back, so Foundry knows what's been paid
- • Invoices open at connect time backfill on their own — no migration step
- • Failures are visible and retryable instead of silently dropped
What it does — and what it doesn't
This app covers accounts payable: what you owe your suppliers. It's built around the purchase-order flow, so the direction of travel is Foundry → QuickBooks for bills, and QuickBooks → Foundry for payment status.
In scope today
- • Vendor invoices → QuickBooks bills
- • Vendor records matched or created as needed
- • Payment status read back onto the Foundry invoice
Not in scope
- • Sales invoices and customer receivables
- • Inventory valuation or COGS journal entries
- • Item-level expense mapping — every line posts to one expense account for now
If you need any of these, say so — it shapes what we build next.
Setup
Connecting is an OAuth handshake with Intuit — there are no API keys to copy anywhere.
Open the app and click Connect
In Foundry, go to Settings → Apps and choose QuickBooks. Clicking Connect sends you to Intuit to sign in and pick which company file to link. You need permission to manage apps in Foundry, and admin rights on the QuickBooks company.
Authorize, and you're returned to Foundry
Intuit redirects back once you approve. Foundry stores the connection encrypted and refreshes it on its own — you won't be asked to re-authorize during normal use.
Pick the expense account
Foundry reads your chart of accounts and asks which expense account bill lines should post to. Pick the one your bookkeeper already uses for inventory purchases or cost of goods. This is required before anything syncs — it's the one decision the integration can't make for you.
Let the first sweep run
Syncing starts automatically. Invoices that were already open when you connected are picked up too, so there's no separate import step. Sync now forces a pass if you don't want to wait.
What syncs
| Data | Direction | Trigger |
|---|---|---|
| Vendor invoices → bills | Foundry → QuickBooks | Recurring sweep, once per invoice |
| Vendors | Foundry → QuickBooks | Matched or created with the bill |
| Payment status | QuickBooks → Foundry | Polled periodically |
Totals always reconcile
The rule that matters for AP: the QuickBooks bill total always equals the Foundry invoice total. Where line-level detail can't be represented cleanly — freight and handling that don't distribute evenly, or a discount that would make a line negative — Foundry posts a single total line rather than lines that don't add up. You'll never reconcile a bill that's off by a few cents from its source.
Push-once, by design
A Foundry invoice becomes a QuickBooks bill exactly once. Invoices are immutable after they leave draft, so there's no edit to propagate and no risk of a second push creating a duplicate bill. Corrections are made in QuickBooks, the way your accountant expects.
Failures retry, then surface
A bill that fails to post is retried on a widening schedule over about two days. If it still hasn't succeeded, it's marked as an error you can see and retry by hand — nothing fails silently, and a QuickBooks outage doesn't cost you invoices.
Limits worth knowing
One expense account for all lines
Every bill line posts to the single account you chose at setup. Per-product or per-category account mapping is a later phase. If your chart of accounts splits purchases finely, you'll still be re-categorizing in QuickBooks.
Sync is scheduled, not instant
Bills post on a recurring sweep rather than the instant you approve an invoice. Use Sync now when you need one immediately. The sweep design is deliberate: it self-heals and backfills, which event-driven pushes don't.
One QuickBooks company per organization
A Foundry organization connects to a single QuickBooks company file. Separate books per brand means separate Foundry organizations.
QuickBooks Online only
Desktop editions aren't supported — the integration is built on Intuit's online API. Xero is the next accounting platform planned.
Troubleshooting
"Reconnect required"
The Intuit authorization was revoked or expired — usually because someone disconnected Foundry from the QuickBooks side, or the company file changed hands. Click Connect again. Queued bills resume where they left off; nothing is lost.
Bills aren't appearing
Check the expense account is set — syncing won't start without it. Then confirm the invoice has actually left draft status; drafts are deliberately excluded. If both look right, open the sync errors list to see what QuickBooks rejected.
Duplicate vendors in QuickBooks
Vendors are matched by name. If a supplier is spelled differently in Foundry than in QuickBooks — "Acme Inc" versus "Acme, Inc." — you'll get a second vendor record. Align the names before your first big sync; merge any duplicates in QuickBooks afterwards.
Sync slowed down or paused
Intuit rate-limits their API. Foundry backs off and resumes automatically, so a large backfill may take several passes to drain. This resolves itself — no action needed.
Payment status looks stale
Payments are polled on a slower cycle than bill pushes, so a payment recorded minutes ago may not show in Foundry yet. If it's still missing after an hour, check the bill wasn't paid against a different QuickBooks record than the one Foundry created.
Questions about your chart of accounts or a migration? Email support — this is one worth setting up carefully the first time.