QuickBooks Enterprise + Payment Hub, invoice and deposit payments recorded in QuickBooks through the Desktop SDK

Why QuickBooks Enterprise businesses add Payment Hub, and what changes when they do

QuickBooks Enterprise is the point where a growing business has outgrown Pro and Premier but is not ready for a full ERP. It handles more users, more list entries and more inventory. Taking and recording payments is still mostly a manual job, and the volume that pushed you to Enterprise is the same volume that makes it painful.

The businesses we see on Enterprise share a pattern. Invoices go out by email from QuickBooks. Some customers mail checks. Some call with a card, which someone types into QuickBooks Payments or a separate terminal. A few set up their own ACH. At the end of the week the bookkeeper opens the merchant portal and the bank feed and works out which payment belongs to which invoice, then records ReceivePayment transactions one at a time. Deposits get matched in the bank feed if the amounts line up and chased if they do not.

Payment Hub takes that apart. The customer pays from a link on the invoice QuickBooks already sends, or in a portal that shows their open invoices, and the payment is written into QuickBooks as a ReceivePayment applied to that invoice, into Undeposited Funds or straight to the bank account, the way your books are set up. The bookkeeper reviews a list of applied payments instead of building it.

The reason this matters at Enterprise scale is that the bookkeeper is often the whole accounting department. A business doing 400 invoices a month with one person in the back office cannot afford a payment process that takes a day a week. Removing the re-keying is where that day comes back.

What stays in QuickBooks Enterprise

QuickBooks remains the system of record. Customers, items, invoices, sales orders, payments and the bank register all stay in your company file. Payment Hub reads customers and open invoices through the SDK and writes payments back in the same transaction types your bookkeeper would enter. Reports look the same, with fewer gaps.

Your existing Enterprise setup does not change. Invoice templates, payment terms, item lists, class tracking, Advanced Inventory and Advanced Pricing all stay as configured. Payment Hub adds a payment link to your invoice template and a portal beside QuickBooks, not inside it.

QuickBooks Enterprise industry editions, all served by Payment Hub

Intuit ships Enterprise in industry editions that add features for specific kinds of business. Payment Hub works across all of them, and the payment pattern that matters most changes with the edition.

Contractors on Enterprise live on deposits and progress billing, so the integration between sales orders, progress invoices and payments is the feature they notice. Manufacturing and wholesale businesses carry the most open invoices and get the most from the portal and consolidated payment. Professional services firms want retainers and scheduled draws. Retail businesses on Enterprise usually already have a point-of-sale system and use Payment Hub for invoiced and phone sales that the POS does not cover. Nonprofits use it for pledges and program fees that need to hit the right class.

Because the same Enterprise install often serves a business that fits two editions, the full feature set is installed and you enable what your office uses.

Payment Hub vs QuickBooks Payments, honest side-by-side

QuickBooks Payments is Intuit's own processing, built into Enterprise, and for a small business it is a sensible default. Payment Hub is the option for businesses that have outgrown it, and the differences are concrete.

QuickBooks Payments is the right answer for a business with modest card volume that values having everything from Intuit. The case for Payment Hub starts when your processing fees become a line item you notice, when customers ask to pay several invoices at once, when you run more than one company file, or when deposits and progress billing turn into monthly cleanup. Any one of those is usually enough.

How Clarity Connect integrates Payment Hub with QuickBooks Enterprise

The integration uses the QuickBooks Desktop SDK with the QuickBooks Web Connector, Intuit's supported path for third-party applications on Enterprise. Eight capabilities make up the integration, and none of them modify your company file structure or require add-on code inside QuickBooks.

The integration workflow, sales order deposit to reconciled bank deposit

A concrete walk-through. A commercial HVAC contractor on QuickBooks Enterprise Contractor Edition, hosted on Right Networks, wins a $37,900 rooftop unit replacement that requires a 50 percent deposit before equipment is ordered. Payment Hub handles the deposit, the final invoice and the bank deposit, through the Desktop SDK.

The detail worth noticing is the deposit. On most contractor setups the deposit sits as an unapplied credit until someone remembers to apply it, or it gets booked to income and corrected at year-end. Here it is a prepayment applied to the final invoice, which is how QuickBooks expects it.

Payment Hub use cases on QuickBooks Enterprise

All 11 Payment Hub use cases run on Enterprise. The ones QuickBooks businesses deploy first are highlighted here, and each links to the full use-case page.

Technical details, for QuickBooks admins and ProAdvisors

The engineering reality of the integration, for the office manager who administers QuickBooks, the IT provider who hosts it, and the ProAdvisor or accountant who keeps the books clean.

• Integration layer. QuickBooks Desktop SDK (qbXML) through the QuickBooks Web Connector, Intuit's supported path for third-party applications on Enterprise. There is no REST API for QuickBooks Desktop. Anything that claims a direct API to Enterprise is using this same SDK underneath. Supported on Enterprise 20 and later.
• Web Connector. Runs on the machine or hosted desktop where QuickBooks Enterprise is installed, connects outbound to Payment Hub over TLS on the schedule you set (every few minutes is typical), and exchanges qbXML. No inbound firewall rules are needed.
• Authentication. A QuickBooks user created for the integration with rights limited to customers, sales transactions and payments, plus a Web Connector application password. Credentials are stored encrypted on Payment Hub's side.
• Data direction. Reads: Customers, Invoices, Sales Orders, Credit Memos, open balances, and the account and item lists needed to record payments correctly. Writes: ReceivePayment and Sales Receipt transactions, and Deposit transactions where configured. Payment Hub never writes items, prices, invoice lines or journal entries.
• Card data. No cardholder data reaches QuickBooks, your company file, your host or Payment Hub's application tier. Entry happens on a PCI DSS Level 1 hosted surface at the gateway, and QuickBooks receives a reference. Your PCI scope shrinks.
• Multi-company files. Each company file gets its own Web Connector application entry and is mapped to its merchant account and bank account. Adding a company file is a configuration change.
• Hosting. Works with Enterprise on-premise and on hosting providers such as Right Networks and other Intuit-authorized hosts. The Web Connector is installed on the hosted desktop like any other Web Connector application.
• Timeline. Standard go-live is 48 hours from Web Connector access: install and authorize the connector, map accounts, add the payment link to your invoice template, test in a copy of your company file, cut over. Portal branding and gateway migration add time only if you want them.
• Support. Clarity supports the integration and the payment side. Your ProAdvisor, accountant or IT provider keeps supporting QuickBooks exactly as they do today.

Related resources