Connects from Settings → Integrations · reads and writes back · disconnect any time
What you get
What Fynex does with QuickBooks Online
Fynex reads from QuickBooks Online and writes back when the money moves.
Reads invoices as they change
Every invoice, its status and its payments arrive by webhook the moment QuickBooks records them — no export, no nightly job.
Reads bills and customers too
Who you owe and who owes you, from the same connection, so a supplier payment and a customer receipt sit on one ledger.
Writes the job reference back
When Fynex ties an invoice to a job, the reference lands on the invoice in QuickBooks, where your accountant will look for it.
Sends the reminder for you
An invoice that is overdue gets a reminder sent through QuickBooks from Fynex — one click, or on a rule you set.
How to connect
Connect it in three steps
Done once, from the dashboard, by whoever owns the account.
1
Approve Fynex
OAuth — you sign in to Intuit and approve Fynex. Fynex never sees your QuickBooks password.
2
Confirm the connection
Fynex confirms the connection and starts the first sync straight away.
3
Let it run
QuickBooks notifies Fynex by webhook when a record changes; a scheduled resync catches anything missed.
Reads and writes
What Fynex reads, and what it writes
Read from QuickBooks Online: invoices and their status, payments received, customers and bills, with their vendors.
Written to QuickBooks Online: a job reference on the invoice's note and send an invoice, or a payment reminder, from Fynex. Each write is logged with what changed and why.
QuickBooks · syncedLive
INV-1042 · Harbor Ltdpaid · matched to bank
$4,200
INV-1043 · Elm Studiooverdue 12 days · reminder sent
$1,850
Bill · Northgate Supplydue Friday · early-pay 2%
$2,310
Job ref writtenINV-1042 → JOB-88
✓
Security
How the connection is held
The same three rules on every connection Fynex makes.
OAuth, never a password
You approve Fynex inside the provider's own sign-in. Fynex holds an access token, not your credentials, and you can revoke it from either side.
Tokens encrypted at rest
Every connection token is stored encrypted (AES-256-GCM) with a key that never leaves the Fynex environment. One connection per business per provider.
Every write is logged
Where Fynex writes back, the write is recorded with what changed and why — only after the underlying event actually happened, never speculatively.
FAQ
Questions, answered
Through Intuit's OAuth. From Settings → Integrations you choose QuickBooks, sign in to Intuit and approve Fynex. The access token is stored encrypted and can be revoked from either side at any time. Fynex never sees your password.
Invoices and their status, payments received, customers, and bills with their vendors. Changes arrive by webhook as QuickBooks records them, and a scheduled resync catches anything a webhook missed.
Two things: a job reference on the invoice's note when Fynex ties the invoice to a job, and invoices or payment reminders sent from Fynex through QuickBooks. Every write is logged, and nothing is written silently.
No. QuickBooks stays your book of record. Fynex reads it, does the calculations between your bank, your invoices and your bills, and writes the result back where your accountant expects to find it.
Yes, from Settings → Integrations, or by revoking Fynex in your Intuit account. Disconnecting stops the sync; nothing already written to QuickBooks is removed.
We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.
Reminders sent, references written — without opening QuickBooks
Essential cookies keep the site working. With your OK we also use analytics cookies (PostHog and Google) to see how the site is used and improve it. See our Cookie Policy.