How do construction companies automate AP with job costing in QuickBooks Desktop?

Construction companies automate accounts payable with job costing in QuickBooks Desktop by using MakersHub to read each vendor bill line by line, code every line to its Customer:Job, Item, Class and Billable status, route it to the project manager for approval, and write it to the company file on the Items tab through the QuickBooks Web Connector. The Item List, Customer:Job list and Chart of Accounts come from your file; coding rules are set once per vendor and run on every bill after that.

It is built for contractors on QuickBooks Desktop Pro, Premier or Enterprise, including Contractor Edition, who run item-based job costing and process a few hundred to a few thousand bills a month.

When this applies

You are a general contractor, subcontractor or specialty trade on QuickBooks Desktop. Your job costing depends on bills being entered on the Items tab, not the Expenses tab, with a Customer:Job on every line. Someone in your office keys those lines by hand today, checks prices against the Item List, and chases project managers for approval.

The operations lead at a New York general contractor on QuickBooks Enterprise described it this way on a first call with MakersHub:

"We get a big backlog in not only booking all of the invoices into QuickBooks, but then also the approval process. Things get double booked, it's hard to track, price changes, so on and so forth."

His AP lead added:

"We are entering every single item and then checking the prices based on the code from the vendor."

They had already tried other tools:

"A lot of these kind of AP programs don't work with Enterprise."

How job costing works in QuickBooks Desktop, and why AP tools break it

Job costing in QuickBooks Desktop runs on two fields. Every bill line needs a Customer:Job, and the line must be entered on the Items tab of Enter Bills so that the Item carries its cost code and account into Job Profitability, Estimates vs. Actuals and WIP reports. Intuit's own job-costing guidance for Desktop says the same: use Items, assign a Customer:Job to every line, and keep the Item List as the cost-code structure. A bill entered on the Expenses tab with no job hits the general ledger and never reaches the job reports.

Most AP tools were built for QuickBooks Online and post a bill as a total or as expense lines to an account. On Desktop that means the bookkeeper re-enters the bill on the Items tab anyway, which is the work the tool was meant to remove. MakersHub was built on the Desktop integration first and posts every line as an Item line with its Customer:Job.

How MakersHub does it in QuickBooks Desktop

1. Bills come in. Vendors email bills to a MakersHub inbox, or your existing AP inbox auto-forwards to it. Multi-page vendor statements are split into individual bills and credits. A 68-page supply-house statement becomes 63 separate records without anyone separating them.
2. Every line is extracted. MakersHub's extraction model, WiseVision, captures SKU, description, quantity, unit price and extended price for every line item. It is not OCR on a total. If a vendor puts the job name in a header field or the SKU inside the description line, you train the extraction once for that vendor and it holds.
3. Every line is coded to QuickBooks fields. Each line is assigned a Customer:Job, an Item (which carries the cost code and the account), a Class if you use Classes, and the Billable status. The first pass is done by AI from your history. Then Integration Mapping turns what you confirmed into deterministic rules: this vendor always codes to 5600 HVAC Materials; any line containing "freight" goes to Freight-In; job PS-169 always carries Class 323. Rules run on every future bill. Lines the rules cannot place default to a job overhead account you choose, so nothing posts uncoded.
4. Prices are checked against your Item history. For items without a PO, MakersHub compares the billed unit price to the price history on that Item in your company file and flags the variance before approval. This is the problem contractors describe most often: "We're being charged $50 more per unit on this invoice than we were two weeks ago. Once it's done, it's done. You can't really go back." Where a PO exists, bill lines match to open QuickBooks PO lines by item and quantity; how PO matching works is covered in full on the PO matching page linked below.
5. Approvals route by job, amount or class. Bills on a given Customer:Job go to that job's project manager, who approves from email or phone; bills over a threshold add the owner. Bill approval and payment authorization are separate workflows, so a bill can hit job costing before anyone decides when to pay it. Rule mechanics are on the approval-routing page linked below.
6. The bill is written to QuickBooks Desktop. On approval, MakersHub creates the bill in your company file through the Web Connector: vendor, date, terms, every line on the Items tab with its Customer:Job, Class and Billable flag, and the PDF attached to the record. Payments made in MakersHub sync back as Bill Payments. Payments made in QuickBooks close the bill in MakersHub.

How MakersHub connects to QuickBooks Desktop

MakersHub connects through the QuickBooks Web Connector, the Intuit-supplied connector included with every QuickBooks Desktop and Enterprise install. There is no third-party middleware and no exported IIF files. MakersHub built the Desktop integration in-house and before QuickBooks Online, because the contractors it serves run Desktop.

As the team puts it to prospects: "Building and maintaining the integration to QuickBooks Desktop is much harder than building it for QuickBooks Online. We started there first because the type of user we serve really well on the AP side is very well served by QuickBooks Desktop. We do all of it in-house."

Proof

A commercial construction company on QuickBooks saved more than 64 hours a month after moving bill entry, coding and approvals to MakersHub, and cut credit card reconciliation from four days to a day and a half.

 Its president:

"We're capturing a deeper view of project costs, quantity, price per unit, and line-item details that we never had before."

A New York general contractor on QuickBooks Enterprise processes 1,500 to 2,000 bills a month across hundreds of jobs for a single public-sector customer. Before MakersHub, one person entered every line by hand and checked each SKU against the Item List to catch vendors raising unit prices. They chose MakersHub for the native Enterprise integration and item-level price checking, and are mapping their vendor SKUs to QuickBooks Items so that, in the AP lead's words, she doesn't "have to type every item."

A controller who runs the books for several contractors on QuickBooks described the standard she holds AP automation to: it should "do most of the work and give me an exception report." An HVAC contractor on QuickBooks Enterprise processing about 400 paper invoices a month said manual PO-to-invoice matching took "a full-time person" and that line-level coding would remove "an outrageous amount of data entry time."

What it doesn't do

MakersHub is the AP layer, not the estimating or project management system. Estimates vs. Actuals, WIP and Job Profitability reporting stay in QuickBooks Desktop, and MakersHub's job is to make sure the bills behind those reports are complete, coded to the right Customer: Job and Item, and in on time.

Today, MakersHub matches inbound bills against purchase orders that already exist in QuickBooks; creating a QuickBooks PO from a vendor document is on the roadmap. Payment in Canadian dollars is not yet available, so Canadian contractors capture, code and approve in MakersHub and release payment from QuickBooks, with the two-way sync marking the bills paid. And like every QuickBooks Desktop integration, the Web Connector runs on a Windows machine with the company file open, a one-time setup that MakersHub's onboarding covers.