If you run AP for a Canadian multi-entity construction company on QuickBooks Desktop, with GST, HST, and PST obligations that vary by vendor, by purchase category, and by province, this is written for you.
One of the hardest things about building in a crowded market is that most of the words people use to describe what you do stop meaning anything. AP automation. AI-powered. Intelligent workflows. The space is full of them. The best antidote I've found is specificity. Actual people, actual problems, what we built to solve them. This is that series.
Here is what I shared on LinkedIn:
Early on in MakersHub, we had a lot of interest from Canadian prospects. I grew up in Connecticut, Phong in Arizona by way of Vietnam. I knew about as much about Canadian tax codes as I do Sanskrit. But the ask was consistent enough that we figured something more thematic must be underpinning the inquiry. What we learned is that most AP platforms "understand" bills and integrate with QuickBooks at the headline level, where MakersHub integrates at the custom field and line level, which is the only place Canadian tax actually lives.
We set out to build Canadian tax support into MakersHub properly. GST, HST, PST, calculated at the line-item level, the way CRA actually requires it, pulling tax codes directly from the customer's existing QuickBooks setup without any reconfiguration on their end.
When our implementation lead got on the call with the controller at a multi-entity Ontario construction company processing 500-plus bills a month, multiple project managers spread across jobs, a small finance team trying to hold the line on a very large QuickBooks Desktop install, he asked her: "How long have you been waiting for a tool to properly support Canadian taxes?"
Eight years. That's how long she'd been waiting for an AP platform that could actually handle it.
Handling Canadian tax correctly in QuickBooks Desktop is an architectural decision about where in the bill processing workflow you do the calculation, at what level of granularity, whether your integration with QuickBooks is deep enough to pull the existing tax codes rather than ask the customer to rebuild them from scratch, and is your document extraction capability smart enough to read, understand the purchase, and then automate the tax assignment.
We did the work. The tax codes come over from QuickBooks exactly as configured. GST and HST calculate at the line level. PST exceptions for specific vendors and purchases run through mapping rules that the system learns and applies automatically. The finance team stays in control of the books. Project managers can see their own job costs without anyone handing them QuickBooks access. And the bills actually reconcile, at the line level, the first time.
She'd been managing that gap manually for eight years. That's the part that stays with me.
Why Eight Years Is Not an Edge Case
What we heard over and over before we built Canadian tax support explains why eight years is a completely normal number and not the outlier it sounds like.
Every Canadian construction company we talked to had been through the same sequence. They found an AP platform. The platform said it supported QuickBooks Desktop. They went through the sales process, the demo, the implementation. And somewhere in month two or three, they found the ceiling. The platform read their invoices at the header level. It extracted a vendor name, an invoice total, a date. It posted a lump sum to QuickBooks. The custom fields where Canadian tax codes actually live, the ones the finance team had spent weeks building, were invisible to it.
The Canada Revenue Agency doesn't care what a platform can do at the invoice header level. GST and HST require line-item level calculation and reporting. PST varies by province, by vendor category, and by the nature of the purchase. A single subcontractor invoice covering labor, materials, and equipment rental across two job sites isn't one tax event. It's several. Each line needs to be read, understood, and taxed correctly before anything touches QuickBooks. If the platform reads the bill at the header level and posts a lump sum, the controller is doing the compliance work manually because the tool isn't.
That's what eight years looks like in practice. Not one bad implementation. A recurring gap between what the vendor promised in the demo and what the CRA actually requires.
Why Multi-Entity Construction Eliminates Nearly Every Platform That Remains
I sometimes joke that we are the one thousand and first AP automation company. Then I worry I'm perhaps misrepresenting that number on the low side.
The platforms that survive the Canadian tax conversation usually don't survive the multi-entity conversation.
Multi-entity construction AP isn't just high volume. It's high variability at every level. The same vendor gets coded differently across entities. A bill belonging to one entity routes for approval to a completely different set of people than a bill belonging to another. Project managers need visibility into their own job costs without anyone handing them access to the full accounting system. Approval workflows need to understand not just the dollar amount but which entity owns the bill, which project it touches, and who in that project structure can sign off.
Most platforms handle one accounting system per company. Multi-entity construction on QuickBooks Desktop, with Canadian tax, across multiple project managers and approval hierarchies, isn't the customer they designed for. It's the customer they tell is too complex.
That phrase, too complex, is the one I hear most often from the businesses we end up working with. Not that their problem is unsolvable. That someone decided it wasn't worth solving.
The Question That Separates Platforms That Handle Canadian Tax From Platforms That Say They Do
There's a specific moment in every conversation with a Canadian construction company where you can tell whether a platform actually handles this or not. It's when you ask how the integration with QuickBooks Desktop works.
The platforms that don't handle it describe the integration at the invoice level. They tell you about the sync. They tell you about the connection. "Data flows into QuickBooks," they say.
The platforms that handle it describe the integration at the field level. They tell you which fields they read, which fields they write to, how tax codes are pulled from the existing chart of accounts, and how line-item tax treatment is calculated before anything is posted.
MakersHub integrates at the custom field and line level because that's the only place Canadian tax actually lives. We pull existing tax codes exactly as configured in the customer's QuickBooks setup. No rebuilding the tax structure. No reconfiguring the chart of accounts. The work the finance team already did in QuickBooks is the work we use. GST and HST calculate at the line level. PST exceptions run through mapping rules the system learns and applies automatically, by vendor, by purchase category, by province.
What Running AP Looks Like After Eight Years of Doing It Manually
Before, she touched every bill. She corrected the tax treatment. She made the coding decisions the platform couldn't make. She reconciled the discrepancies at month end. She was the gap-closing mechanism because nothing else was.
After, bills arrive by email, by vendor upload, or through a forwarded inbox. Each line item is read and understood, the correct tax treatment applied for that specific line, coded to the right project and cost code for the right entity, routed to the right approver based on entity, project, and dollar amount. The completed, tax-compliant bill syncs to QuickBooks exactly as the finance team configured it. Project managers see their own costs. The finance team sees everything across all entities from one place. The bills reconcile at the line level the first time.
Who We Built MakersHub For
If you're running AP for a Canadian construction company on QuickBooks Desktop, across multiple entities, with GST, HST, and PST obligations that vary by vendor and purchase category, and you've been told by other platforms that your situation is too complex or something they'll address in a future release, this is for you.
MakersHub isn't for every business. It's specifically for businesses that have hit the wall described above.
If that's your situation, we'd like to hear about it. makershub.com/get-started
-Charley Howe, Co-Founder and President, MakersHub