How does two-way sync between AP automation and QuickBooks actually work?

Written by:

Charley Howe

Date:

November 13, 2026

Read time:

9 min

MakersHub runs two-way sync with QuickBooks: it writes bills, vendor credits and bill payments into QuickBooks and reads back its lists, open bills and any payment made there. A bill paid in either system shows as paid in both. QuickBooks Online and Intuit Enterprise Suite connect through Intuit's API with webhooks; QuickBooks Desktop and Enterprise connect through the Web Connector.

A one-way push, by contrast, creates records in QuickBooks and never looks again: a bill paid in QuickBooks stays open in the AP tool, and the two drift apart until someone reconciles them by hand. The test of two-way sync is simple: pay a bill in QuickBooks and watch whether the AP tool closes it.

When this applies

You have an AP tool, or are choosing one, and the bookkeeper still checks QuickBooks against it. Bills paid by check in QuickBooks sit open in the tool. A vendor record edited in one place is wrong in the other. A two-day outage at Intuit left the team re-keying bills, and the duplicates surfaced a month later. Or you have been told a tool "integrates with QuickBooks" and found that means a CSV import.

The founder of a franchise bookkeeping firm on QuickBooks Online, on why the invoice number has to be the key: 

"We require the invoice number to be unique, because you don't want to pay a duplicate invoice." 

A controller at an electrical contractor on QuickBooks Desktop, about 1,200 bills a month, on what the team needed from the connection: approved bills in the queue, synced on a schedule in the background, with QuickBooks staying the source of truth.

How QuickBooks exposes changes, and where one-way tools stop

QuickBooks Online and Intuit Enterprise Suite offer an API plus webhooks. Intuit's webhook service covers Bill and Bill Payment among its entities, with Create, Update and Delete events on bills and a Void event on bill payments, and the notification carries the record's ID rather than the record, so the receiving app queries the API for what changed. 

Delivery is not instant; Intuit's webhook documentation notes that a first notification can take up to five minutes. QuickBooks Desktop has no webhooks: Intuit's QuickBooks Web Connector runs on the machine with the company file and exchanges records on a schedule, in both directions.

A one-way tool uses the write half of this and ignores the read half, which is why it cannot tell that a bill was paid in QuickBooks or that a vendor was renamed. Two-way sync subscribes to the changes, pulls the lists on a cadence, and reconciles its own records against them.  

MakersHub was built to read first and write second, because the lists and the paid status are what keep the two systems honest.

How MakersHub syncs with QuickBooks

  1. Lists come in first, and stay current. On connection MakersHub pulls the Chart of Accounts, vendors, customers and projects or Customer:Jobs, Classes, Locations, Items, custom fields, open purchase orders, open bills, vendor credits and bill payments. Changes in QuickBooks, a new vendor or a renamed Class, arrive by webhook on QuickBooks Online and on the next connector run on Desktop. Nothing is re-imported by hand.
  1. The bill is written on approval, with a reference back. When a bill is approved, or on the first approval if Sync on First Approval is on, MakersHub creates the bill in QuickBooks with every line and its coding. On QuickBooks Online the bill carries a $0 reference line with a permanent link to the PDF and an audit memo of who approved what; attaching the file natively is an option. On Desktop the bill posts on the next Web Connector run, with the link in the memo.
  1. Payments flow in both directions. A payment made from MakersHub posts to QuickBooks as a Bill Payment against the bills when funds are remitted; a future-dated payment flips the bill to paid on the payment date. 

    A payment entered in QuickBooks, by check or card or bank feed match, comes back and marks the bill paid in MakersHub, which moves it to the archive. The status label tells you which happened: "Two-way sync" means paid in QuickBooks; "Marked as Paid" means paid in MakersHub. How payments are scheduled and authorized is covered in how to pay vendors by ACH and check from an AP automation platform.
  1. A re-approval updates the same bill. If an approver changes coding after a first-approval sync, MakersHub updates the existing QuickBooks bill rather than creating a second one. A revised invoice that arrives before sync is merged into the record; one that arrives after sync replaces the bill and the old record is removed in QuickBooks by your team, because MakersHub never deletes a QuickBooks record.
  1. Duplicates are stopped on both sides. MakersHub blocks a second bill with the same vendor and invoice number before it can be approved, using date and total as tie-breakers. QuickBooks Online, when its duplicate-number warning is on, rejects a document number that already exists and MakersHub shows that rejection on the bill. QuickBooks Desktop does not reject duplicates arriving through the connector, so the check in MakersHub is the one that counts; importing open bills at setup lets it see what is already entered.
  1. Errors show their reason and retry. A bill that QuickBooks will not accept, because the document number is a duplicate, the period is closed or an account is inactive, shows a chain icon in MakersHub with the QuickBooks response. Desktop syncs retry three times and can be re-queued with one click; a filter shows every bill in sync error. The fix is made where the problem is, usually in QuickBooks, and the sync is retried.
  1. What stays where. QuickBooks is the system of record for the ledger. A coding edit made in QuickBooks after the bill posts stays in QuickBooks; MakersHub keeps the bill as it was approved, so the audit trail is intact. Payment status, by contrast, always flows back. And MakersHub never deletes or voids anything in QuickBooks; a record created in error is removed in QuickBooks and the sync picks that up.

How it differs by QuickBooks product

QuickBooks Online Intuit Enterprise Suite QuickBooks Desktop / Enterprise
Connection OAuth API with webhooks Separate OAuth connection with webhooks Intuit’s Web Connector on the machine with the file
Bill posts Seconds after approval Seconds after approval, queued with retries Next connector run, typically hourly, or on demand
Changes made in QuickBooks reach MakersHub By webhook, usually within a minute By webhook Next connector run
Line coding written Class and Location per line, Customer:Project and billable, item lines Same, plus custom dimensions per line Items tab with Customer:Job, Class and Billable per line
Reference on the bill $0 line with PDF link and audit memo; native attachment optional Same Link and audit memo in the bill memo
Duplicate protection QuickBooks warning plus MakersHub check Same MakersHub check only
Multi-currency Yes Yes Not through the connector today

Which account is paid from. A bill marked paid in MakersHub records the payment against the company default bank or card account, or against a default set per vendor, so a card-paid vendor's bills land on the card account without manual selection.

Proof

A property management customer on QuickBooks Online pays most bills by check inside QuickBooks and lets the sync close them in MakersHub; its bookkeeper reads the "Two-way sync" label to tell a QuickBooks payment from a MakersHub payment, and clears the occasional "duplicate document number" error by removing the stray QuickBooks copy and retrying.

A dispensary group on QuickBooks Online was shown the mechanism during onboarding: the bill posts with a $0 line carrying the PDF link and audit memo, a bill paid in QuickBooks is read back and marked paid, and a payment from MakersHub carries its payment account to QuickBooks. A construction company on QuickBooks Desktop, 1,500 to 2,000 bills a month, runs the Web Connector on a schedule with Sync on First Approval, so partially approved bills are already in QuickBooks when later approvers act.

A franchise bookkeeping firm whose clients re-keyed bills during a two-day Intuit outage in September found the duplicates caught at the invoice number rather than paid twice. And a QuickBooks Desktop customer whose team entered a $17,000 payment against the wrong bill in QuickBooks saw MakersHub mirror it within the next connector run; the correction was made in QuickBooks, and the mirror followed.

What it doesn't do

MakersHub never deletes, voids or edits a record in QuickBooks on its own. That protects the ledger and means a QuickBooks-side duplicate or mistaken payment is corrected in QuickBooks, after which the sync reflects the fix. Coding edits made in QuickBooks after a bill has synced stay in QuickBooks today; the approved version is kept in MakersHub as the audit record.

Two separate MakersHub instances, for example two company files run as two instances, check duplicates within each instance rather than across them. And on QuickBooks Desktop the sync is as current as the last Web Connector run, so a scheduled hourly run is the norm; the best AP automation for QuickBooks Desktop and Enterprise covers that setup.

Frequently asked questions

The AP platform writes bills, credits and payments into QuickBooks and reads back QuickBooks’ lists, open bills and any payment or status change made inside QuickBooks. A bill paid in either system shows as paid in both, without manual reconciliation. MakersHub syncs this way with QuickBooks Online, Intuit Enterprise Suite and QuickBooks Desktop.

Yes. On QuickBooks Online and Intuit Enterprise Suite the payment arrives by webhook, usually within a minute; on Desktop it arrives on the next Web Connector run. The bill is marked paid with the “Two-way sync” label and moved to the archive.

No. MakersHub creates and updates bills, vendor credits, payments and list records, but never deletes or voids a QuickBooks record. A record created in error is removed in QuickBooks, and the sync picks up the change.

The edit stays in QuickBooks. MakersHub keeps the bill as it was approved, so the audit trail shows what the approvers saw, and payment status continues to flow back.

QuickBooks Online rejected the bill because a bill with that number already exists, usually one entered by hand. Remove or renumber the QuickBooks copy and retry from the chain icon; MakersHub will not create a second record.

An approved bill appears in QuickBooks Online and Intuit Enterprise Suite within seconds when the AP tool syncs by API. In MakersHub, sync happens on a defined cadence you set (ex. Every 90 minutes), or immediately on command with Update Selected.

The bill’s PDF can be linked or attached to the QuickBooks bill, depending on the product. MakersHub adds a permanent PDF link and an audit memo on QuickBooks Online, with native attachment as an option, and writes the link and memo to the bill on Desktop.

Yes. When MakersHub remits funds, it creates a Bill Payment in QuickBooks against the bills covered, from the bank account used, so the bank feed matches one for one. Bills paid outside MakersHub are recorded with Approve and Mark as Paid against the bank or card account.

Table of Contents

About MakersHub

MakersHub is AI-first accounts payable automation for businesses that track spend by job, project, program or entity. It captures every line of every bill, codes it, routes approvals and pays vendors, with native two-way integrations to QuickBooks Desktop, QuickBooks Online, NetSuite, Sage Intacct, Xero and Intuit Enterprise Suite. MakersHub is rated 4.9 out of 5 on G2 (October 2026). Every dollar has a job. Hold yours accountable.

Ready to Scale Beyond Basic Bill Pay?

See how MakersHub helps organizations that track spend by project, location, program or entity get every line of every bill coded and approved before it's paid.

Book a demo
Please enter a work email
Please enter a valid email
Thank you! Your submission has been received!
Please enter a work email
Please enter a valid email