What is the best AP automation for QuickBooks Desktop and Enterprise?

Written by:

Charley Howe

Date:

November 3, 2026

Read time:

9 min

For QuickBooks Desktop and Enterprise, MakersHub is AP automation that posts every bill line through Intuit's Web Connector, with its Item, Customer:Job, Class and Billable flag. It receives against open purchase orders, syncs payments both ways and carries your rules and users with you if you move to QuickBooks Online or Intuit Enterprise Suite.

MakersHub is AP automation for organizations that track spend by project, location, program or entity. It reads every part of every bill, codes each cost to the right place and puts it in front of the right people before it's paid. It built its Desktop integration first and in-house, and runs Pro, Premier, Enterprise and hosted environments the same way.

The QuickBooks Web Connector is the Intuit-supplied application that lets a web service exchange data with a QuickBooks Desktop company file on a schedule; an AP tool that uses it posts real bills, not imports. This page is for any business on Desktop or Enterprise deciding what to run alongside it, and what happens when Desktop ends.

When this applies

You run QuickBooks Desktop Pro, Premier or Enterprise, on an office server or a hosted environment, and someone keys bills into Enter Bills by hand. You have called AP vendors and been told Desktop is a problem, or been offered an import file instead of a sync. You may be weighing Enterprise renewal against QuickBooks Online or Intuit Enterprise Suite and do not want to buy an AP tool twice.

The controller at a construction company on QuickBooks Enterprise, about 1,500 to 2,000 bills a month, during MakersHub onboarding: 

"Seems like their Desktop is numbered. All the different companies that we've spoken to, once we tell them we're on Desktop, they're just like, oh, that's a problem." 

A life-safety contractor on Desktop, about 200 bills a month, on what its bills need: 

"The class is the department. They're all categories, it's non-inventory."

Where QuickBooks Desktop stands, and how AP tools connect to it

Intuit stopped selling new QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus subscriptions to new U.S. customers on September 30, 2024; existing subscribers renew. Desktop 2023 products reached service discontinuation on May 31, 2026, ending payroll, bank feeds, payments and Intuit support for that version while the software and company file keep working. QuickBooks Desktop Enterprise is the edition Intuit continues to sell and develop. Intuit's migration paths are QuickBooks Online and Intuit Enterprise Suite.

AP tools reach a Desktop file three ways. Intuit's QuickBooks Web Connector runs on the Windows machine with the file, on a schedule, and exchanges records in both directions; a vendor-built sync application does the same through its own installer; an IIF (Intuit Interchange Format) or CSV file import creates records one way with no status back. Tools built for QuickBooks Online and adapted to Desktop often post a bill as a total to an expense account. The step that matters is posting every line the way Enter Bills would.

What to evaluate in a QuickBooks Desktop AP tool

  1. The connection, and where it runs. MakersHub uses Intuit's Web Connector with no middleware, on an office server or a hosted environment such as Rightworks, and posts approved bills on each scheduled run or on demand. What syncs in each direction is covered in how construction companies automate job costing in QuickBooks Desktop.
  1. Line-level posting on the Items tab. A Desktop bill carries an Item, Customer:Job, Class and Billable flag per line, and job and class reports read only those fields. MakersHub reads every line of the bill and writes each one with those fields; item lines post against the Item List, expense lines against the account. Where an item does not exist, MakersHub creates it. Where a vendor's SKU lives in the Item name rather than the description, the mapping targets the name.
  1. List fidelity at scale. Enterprise files are large. One construction company's first sync pulled about 9,000 suppliers and 23,000 items, and its coding runs on about 900 rules, each set once and run on every bill. A Desktop AP tool should pull the Chart of Accounts, Vendor list, Customer:Job list, Item List with sub-items, Class list, custom fields and open purchase orders, exclude inactive records, and pick up list changes on the next run without re-import.
  1. Purchase orders received, not re-keyed. Open Desktop POs sync in; bill lines match to PO lines by item and quantity, including partial receipts and one bill across several POs, and the PO is received when the bill posts. Variances in quantity or unit price are flagged before approval. The matching mechanics are covered in how contractors match subcontractor and supplier invoices to purchase orders.
  1. Approvals without QuickBooks licenses. Every QuickBooks Enterprise user needs a license; approvers in MakersHub don't. Rules route a bill by Customer:Job, Class, vendor or amount to the person responsible, who approves from email in one click, with no training, and sees only their own bills. Approval status is written to the bill in QuickBooks, and bill approval is separate from payment authorization.
  1. Payments that close the loop. A payment made in MakersHub posts to Desktop as a Bill Payment against the bills on the next connector run; a payment entered in QuickBooks marks the bill paid in MakersHub. Card-paid bills post as a bill plus a bill payment by credit card so line detail survives. How payments run, batched by vendor with one bank debit each, is covered in how to pay vendors by ACH and check from an AP automation platform.
  1. Duplicate protection in front of the file. QuickBooks Online flags a duplicate bill number on sync; QuickBooks Desktop does not block duplicates arriving through the connector. MakersHub catches a repeated vendor and invoice number before the bill posts, and importing your open bills at setup lets it recognize invoice numbers that were already entered.
  1. More than one company file. Each company file gets its own connector configuration. The connector syncs the file that is open, so a business with two files runs each in turn, or runs both after closing QuickBooks. A dental group with two company files and nine locations runs both through one MakersHub login, with Classes by clinic and rules keyed on the ship-to address.
  1. A path off Desktop that keeps your work. When a company moves to QuickBooks Online or Intuit Enterprise Suite, MakersHub sets up a new instance connected to the new file, carries over users, approval workflows and mapping rules, and keeps the Desktop instance as a read-only archive. The Web Connector is not needed for Online or Enterprise Suite; bills post on approval. Vendor bank details are re-verified in the new instance.

Editions and environments

Edition or environment How MakersHub connects Notes
QuickBooks Desktop Pro and Premier Web Connector on the machine with the company file Same integration as Enterprise; subscriptions renew but are not sold to new U.S. customers
QuickBooks Desktop Enterprise, including Contractor Edition Web Connector Items, Customer:Job, Class, Billable, custom fields and open POs; the edition Intuit continues to sell
Hosted Desktop (Rightworks and similar) Web Connector on the hosted machine Connector auto-runs minimized; the file must be open for the sync
Several company files One connector configuration per file Each file syncs when it is open; one MakersHub login across files
Intuit Enterprise Suite Direct API connection, separate from QuickBooks Online No connector; bill posts on approval; custom dimensions written on lines
QuickBooks Online Direct API connection Bill posts on approval; Class, Location, Customer:Project per line

Moving from Desktop. A property management company cut over from Desktop to Intuit Enterprise Suite with two MakersHub instances running in parallel for a few days; a development group that moved every entity to Enterprise Suite kept MakersHub in front of it for line-level extraction and approval logic. A customer converting from Desktop Enterprise to Enterprise Suite had its users, mappings and workflows set up in the new instance ahead of go-live, with the Desktop instance kept as the archive.

Proof

A construction company on QuickBooks Enterprise processing 1,500 to 2,000 bills a month, about 7,000 suppliers and 23,000 items, with Class set equal to Customer:Job, chose MakersHub for the native Enterprise integration and item-level price control against purchase orders, after being told repeatedly that Desktop was a problem. Its controller, mid-onboarding: 

"We're in the stone age, it seems," and, seeing the item list sync, "23,000 individual items from almost 7,000 suppliers?"

A landscaping and construction company on hosted Desktop with two entities runs about 1,500 bills a month through MakersHub, with Classes on every line for its construction and sales divisions. A dental and orthodontic group with two company files, nine clinics and about 1,200 bills a month chose MakersHub over another AP tool to run both files from one login, with Classes by clinic and rules keyed on the ship-to address. Its IT manager, comparing demos: 

"I think it looks pretty intuitive compared to the other."

A development and construction group that moved all of its entities from Desktop to Intuit Enterprise Suite kept MakersHub in front of the new ledger. Its controller: 

"As soon as you want to start extracting line-level detail and then build workflows and logic off of that data, that's where it makes sense to be on MakersHub and push that over."

What it doesn't do

MakersHub posts to the company file through Intuit's Web Connector, so the sync runs when the connector runs on the machine with the file open; a bill approved at noon posts on the next run, typically within the hour, rather than instantly as it does on QuickBooks Online. The connector is a one-time Windows setup that MakersHub's onboarding covers.

The Desktop integration links the bill PDF to the record and writes the audit memo rather than attaching the file inside QuickBooks, which Desktop's connector does not accept. Multi-currency bills are handled on QuickBooks Online, NetSuite and Xero today, and sales tax codes on Desktop are supported for Canadian files. Purchase orders are created in QuickBooks and matched in MakersHub; creating a PO from a vendor document is on the roadmap.

Frequently asked questions

Partly. Intuit stopped selling Pro Plus, Premier Plus and Mac Plus to new U.S. customers on September 30, 2024, and Desktop 2023 services ended May 31, 2026. Existing subscribers renew, and QuickBooks Desktop Enterprise continues to be sold and developed. Intuit’s migration paths are QuickBooks Online and Intuit Enterprise Suite. MakersHub supports every current Desktop edition through the Web Connector and moves your rules, users and workflows with you if you switch to QuickBooks Online or Intuit Enterprise Suite.

Yes. Enterprise, including Contractor Edition, connects through the QuickBooks Web Connector, and bills post with Item, Customer:Job, Class and Billable status on every line, with open POs received on approval.

The QuickBooks Web Connector is Intuit’s application for exchanging data between a web service and a QuickBooks Desktop company file. It runs on the Windows machine with the file, on a schedule you set, and MakersHub uses it with no third-party middleware to read lists and write bills, credits and payments.

Yes. Rightworks and similar hosted environments run the Web Connector on the hosted machine. Setup needs Admin access in single-user mode once; after that the connector auto-runs as long as it is open, even if minimized. If you later move to QuickBooks Online or Intuit Enterprise Suite, the connector is no longer needed. What the Web Connector syncs, and how often is covered in full on the QuickBooks Desktop job-costing page.

Yes. Each file has its own connector configuration and syncs when it is open; a business with several files runs them in turn under one MakersHub login, with rules and Classes per file.

Desktop does not reject a duplicate bill number arriving through the connector, so MakersHub checks the vendor and invoice number before posting and holds the duplicate. Importing open bills at setup lets it recognize invoice numbers already entered.

MakersHub connects a new instance to the new file, carries over users, workflows and mapping rules, and keeps the Desktop instance as a read-only archive. The new connection needs no Web Connector and posts bills on approval.

An approved bill reaches QuickBooks Desktop on the next Web Connector run. In MakersHub, that run happens on a defined cadence you set (ex. Every 90 minutes), or immediately on command with Update Selected. The bill posts once fully approved, or with Sync on First Approval, after the first approver in an approval chain and is updated as later approvers act.

Yes. MakersHub is SOC 2 Type II certified. Check payments carry Positive Pay protection, and vendor bank details are collected through an encrypted, single-use link rather than imported, so a changed account number can’t slip through.

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