2026, August 21st – Contractor Foreman and QuickBooks

August 21st, 2026
Hosted by: César Macedo, Trainer at Contractor Foreman
Co-presenter: Amber Wells, Construction Accountant & Integration Specialist
Topic: Contractor Foreman + QuickBooks — The Recommended Workflow

Webinar Description

In this advanced training session, César Macedo and Amber Wells walk through the recommended workflow for running Contractor Foreman alongside QuickBooks — what to create where, what syncs when, and why the order of operations matters far more once two systems are talking to each other. Amber brings six years at Contractor Foreman and more than three thousand completed integrations to the technical side of the discussion, while César covers the Contractor Foreman workflow itself.

The session opens with the distinction everything else rests on. Contractor Foreman is construction management software, organized around projects. QuickBooks is an accounting system, organized around the company. Both are necessary, and neither replaces the other. From there César makes the point that frames the whole hour: Contractor Foreman on its own is highly flexible about where a project begins — a lead, an opportunity, an estimate, the projects module, the directory. Once you integrate with QuickBooks, that flexibility becomes rigid. The recommended path narrows to one: create the estimate in Contractor Foreman and let it sync to QuickBooks, not the other way around.

Before demonstrating anything, César covers three concepts that recur throughout. Cost items are the line items in your estimate, carrying quantity, unit cost, unit, and markup. Cost codes are labels with no dollar value of their own — the connection between estimated cost, actual cost, and your accounting system. Item types are Contractor Foreman’s five categories: material, labor, equipment, subcontractor, and other.

Amber then supplies the piece that makes cost codes matter more under an integration than without one: a cost code in Contractor Foreman becomes a product or service in QuickBooks, and every product and service must be assigned an income account and an expense account. If a line item goes out without a cost code, QuickBooks assigns a generic default rather than the right one. Her guidance is to confirm every item has a cost code before sending an estimate to a customer — the fix is easy, but only if you catch it.

The live build starts with approving the estimate, which triggers the first sync and creates a sub-customer in QuickBooks alongside the project in Contractor Foreman. Amber flags the step most people miss here, and it is probably the single most actionable item in the session: that sub-customer must be converted to a project inside QuickBooks. If it stays a sub-customer, every bill and expense arriving from Contractor Foreman gets marked billable regardless of how it was entered — a QuickBooks rule dating from when they opened the projects module to third-party syncing, with no workaround. She recommends checking weekly rather than daily, and notes two related requirements: QuickBooks Online Plus or Advanced is necessary because lower tiers lack the projects module, and QuickBooks Desktop isn’t supported at all. She also walks through how to restructure a three-tier customer setup — a developer with multiple subdivisions, say — down to the two tiers the integration expects.

The money-out workflow follows. César recommends creating a subcontract for each subcontractor, framing it as a tracking tool: it’s what tells you how much has been billed to date and how much remains. Subcontracts themselves don’t sync, because QuickBooks has no equivalent module. The sync fires when you generate a bill against the subcontract. His demonstration from the Procurement tab takes three clicks, with item type, cost item, and cost code all carried through from the estimate untouched — which he offers as a concrete argument for why the estimate is worth doing carefully.

Amber adds the technical reason this workflow isn’t merely a preference. QuickBooks permits multiple projects on a single bill: line one to project A, line two to project B. Contractor Foreman does not split bills — one bill belongs to one project. So a multi-project bill entered directly into QuickBooks will still sync, but it will assign the entire amount to whichever project appears first on the bill, leaving the others with nothing. Purchase orders follow the same pattern as subcontracts, with one difference César points out: subcontract bills are generated by percentage or progress, while PO bills are generated by quantity.

The session then returns to cost codes with a constraint that has real design implications. Because a cost code maps to a QuickBooks product or service, and each product or service carries exactly one income account and one expense account, a cost code created for subcontractor work cannot also be used for crew clock-ins or material purchases on the same trade. César is candid that in Contractor Foreman alone, a single “cabinets and vanities” cost code covering everything would be entirely reasonable from a construction standpoint. With QuickBooks in the picture, it isn’t.

Expenses are covered as the simplest record in the system, with one rule attached: project-related expenses belong in Contractor Foreman, overhead and office expenses belong in QuickBooks. Time cards sync hours only — not wage rate, burden rate, or billing rate.

The money-in workflow centers on the Schedule of Values, which César describes as the tracking tool for the up-to-date contract amount, what’s been invoiced, and what remains. Change orders, work orders, and service tickets all feed into it. Invoices behave differently from bills: they sync when moved to submitted status, not on creation. His argument against invoicing from QuickBooks is that it forfeits SOV tracking entirely, and that QuickBooks has no change order function to fall back on. He also distinguishes billing from the SOV versus pulling from the approved estimate — the SOV remembers what’s already been billed; the estimate does not.

Amber closes with a practical fix for a question that came up twice: field staff seeing the full QuickBooks chart of accounts when entering expenses. Her approach is to prefix the commonly used accounts with numbers, since numbers sort ahead of letters in an alphabetized list — pushing five to seven relevant options to the top. The alternative is to default everything to uncategorized expense, have the field attach a receipt photo, and let whoever works in QuickBooks categorize it, with the two-way sync updating Contractor Foreman afterward.

Attendee questions covered modifying a subcontract amount after the first payment (César’s recommendation: use a change order rather than editing the contract, so there’s a paper trail), where subcontractor invoice numbers go, multiple addresses per customer, and collapsing change orders to a single summary line on an invoice.

Attendees were offered a complimentary one-on-one training session and a follow-up email with the recording.

This session is ideal for:

• Contractors who have completed their QuickBooks integration and want to confirm they are working in the right order
• Teams experiencing sync issues, duplicate entries, or transactions landing on the wrong project
• Anyone whose accountant currently enters bills and invoices directly in QuickBooks, and who wants to understand what that costs them in Contractor Foreman
• Office and field staff who need a shared, documented workflow rather than individual habits