Ask any AP automation vendor to scroll to the tax block on a Quebec restaurant receipt. If GST and QST come back as two separate amounts, and the tip sits on its own line with no tax applied to it, the product was built for Canadian documents. If you get one blended tax figure, it was not, and you will find that out in month two rather than month one.
That test takes about fifteen seconds. It is worth running, because tax extraction is the failure that compounds most quietly. Invoices still post. Nothing errors. The variance surfaces later, at reconciliation, at filing, or when someone reviews input tax credit recovery and discovers the recoverable portion was never separated correctly in the first place.
A distributor with entities in Alberta and Quebec learned this at their first quarter close, when a day and a half disappeared into pulling blended tax figures apart by hand. Their story is below. It matters most if you operate in more than one province, process a meaningful volume of meal and travel receipts, or reclaim input tax credits across entities with different recovery treatment. If that is you, the tax block is the first thing to check in any evaluation.
The problem is not reading the tax. It is reading it as components.
Header level tax capture works fine on a clean, single rate document, and most AP tools clear that bar comfortably. The difficulty starts with documents carrying more than one tax.
A Quebec invoice shows GST at 5 percent and QST at 9.975 percent. Two separate taxes, different filing destinations, and for some entities different recoverability. A tool architected around a single national sales tax has one field to put them in. So it blends them, or it captures one and drops the other, or it captures the total and back solves a rate that matches neither tax.
Then there is the restaurant receipt, which is where tax logic tends to break quietly. The taxable subtotal is one number. The tip is another, and it is not subject to GST or QST. If the system applies the tax rate to the full amount including gratuity, every meal expense carries a small overstatement. Individually trivial. Collectively, a reconciliation exercise nobody scheduled.
Controllers who have been through this describe the same pattern. The demo looked fine, because the demo used a clean Ontario invoice with a single HST line. Production was Quebec, Saskatchewan, British Columbia, and a stack of restaurant receipts from a sales team. The tools that fail this way were designed for a single sales tax and adapted for Canada afterwards, which is a different thing from being built here.
What tax errors actually cost
Tax mistakes do not sit in their own bucket. They land in the exception pile, and exceptions are the most expensive thing in accounts payable.
According to Ardent Partners’ Accounts Payable Metrics That Matter in 2025, the average invoice exception rate is 14 percent. Top performing teams run at 9 percent. Teams without automation sit closer to 22 percent. The same research puts the average cost to process an invoice at $9.40 against $2.78 for top performing teams, and average processing time at 9.2 days against 3.1 days.
The gap between those columns is not keystroke speed. It is how much work never has to happen. An invoice that extracts cleanly and posts straight through costs a fraction of one that gets pulled out, investigated, corrected and re-approved. Ardent also found AP teams spend roughly 21.8 percent of staff time handling supplier inquiries, a figure that grows every time a payment goes out with the wrong tax treatment and a vendor asks why.
A blended tax field does not cause one exception. It causes an exception on every multi tax document you process, indefinitely, until someone rebuilds the mapping. And because the same receipts flow through expense management as well as AP, a tool that gets this wrong gets it wrong twice, in two systems, reconciled by the same team.
A fifteen second test you can run on any vendor
Bring three documents to the demo. Not the vendor’s sample data. Your own, redacted if you need to.
That last row matters more than the first three. A system that quietly guesses is worse than one that admits uncertainty, because you find the guess months later with no record of where it came from.
Where the blended field showed up
The distributor mentioned at the top was running roughly 350 vendor invoices and 120 card receipts a month across the two entities, with about a third of supplier billing coming from Quebec. Their AP tool at the time captured tax as a single field, and for the first few months nothing looked wrong.
The first quarter close surfaced the problem. Input tax credit reconciliation took a day and a half because every Quebec invoice needed the blended figure pulled apart by hand before GST and QST could be filed to the right place. Restaurant receipts from the sales team had been overstating recoverable GST on every meal, small amounts that added up to a correcting entry nobody had budgeted time for. And the Quebec entity’s tax treatment differed from Alberta’s, which a single field could not express at all.
Once the same documents were running through line level extraction, GST and QST arrived already separated and mapped to their own codes, the tip identified as its own untaxed line, and each entity’s recoverability applied before anything posted. Card receipts got the same treatment as vendor invoices because they ran through the same engine. The reconciliation that took a day and a half became a review of flagged variances. The correcting entry stopped existing because the error never reached the ledger.
The tool did not get smarter about tax. It stopped throwing away information the document already contained.
How Finofo handles Canadian tax, and the decision behind it
Finofo extracts Canadian tax at the line level, including dual tax documents, and keeps GST or HST separate from QST or PST rather than collapsing them into one field. On restaurant receipts, an identifiable tip is treated as its own line with no tax applied, so gratuity is never taxed. Recoverable and non recoverable tax groups are handled per jurisdiction, so what reaches the ERP already reflects how each province and each entity treats the amount.
That is not an adaptation. Finofo was built in Calgary as an AI native platform from the first line of code, for the documents Canadian finance teams actually process: multi province invoices, dual tax receipts, PSB rebate splits, cross border supplier bills. It is the only Canadian built, AI native platform that runs accounts payable, expense management and purchasing on one engine, so a Quebec receipt gets the same tax treatment whether it arrived as a vendor invoice or as an employee’s texted photo of a restaurant bill.
The decision underneath the tax handling has less to do with tax than with where corrections happen. A tax error caught before the bill posts to the ERP is a short fix in a review queue. The same error caught after posting is a journal entry, an approval, and an explanation to someone. So variances surface before posting, and any coding the system inferred by resemblance to past invoices is marked as inferred, because “the AI filled this in” should not quietly become “this must be right”. Finofo does the verification. Your team keeps the judgment.
We also decided not to build a tax engine. Determining the correct treatment for a given transaction in a given jurisdiction is a different category of software, and pretending otherwise is how a vendor ends up confidently wrong at scale. Finofo gets the right amounts, correctly separated, onto the right lines. Your ERP tax configuration and your tax advisor decide what those amounts mean.
What stays with your team
Finofo is designed so that the people who sign off on the numbers stay in control of them. A few things are deliberately yours.
Tax status is configured, not guessed. Organisations with GST only registration, or nonprofit rebate treatment, set those rules explicitly, and Finofo applies them consistently rather than inferring your filing position from a document.
Your ERP tax setup remains the source of truth. Tax groups, recoverable versus non recoverable treatment, and entity level defaults live where they always have. What Finofo changes is how clean the data is when it arrives there, and how early you find out when something does not reconcile.
A genuinely ambiguous document still gets a human look. An illegible handwritten tip or a smudged total is flagged for review rather than resolved by a guess. That is the point of marking uncertainty instead of hiding it.
And none of this is tax advice. When a recovery position is genuinely uncertain, that is a conversation with your advisor. Finofo makes sure the numbers in front of them are right.
Back to the tax block
The reason to scroll to the tax block in a demo is not that tax is the most important feature in AP automation. It is that a vendor’s handling of Canadian dual tax tells you whether the product was designed for the documents you actually process, or adapted for them afterwards.
One blended field is an answer. It is just not the one you want to be living with in month two. If you want to run the test on Finofo, bring your own Quebec receipt to the demo. We would rather you saw the tax block yourself.
Frequently asked questions
Does AP automation software handle GST and QST separately?
Some does and plenty does not. Tools built primarily for the US market often have a single sales tax field, which forces GST and QST into one blended value. Finofo captures each tax as its own line level field with its own code. Ask any vendor to show a Quebec document during the demo and confirm two distinct, separately mapped amounts before signing anything.
Should tips be taxed on a Canadian restaurant receipt?
No. Gratuity is not subject to GST, HST or QST. Extraction that applies the tax rate to a total including the tip overstates recoverable tax on every meal receipt, which accumulates into a reconciliation problem rather than announcing itself as an error. Finofo identifies the tip as its own untaxed line, on receipts arriving through AP or through expense management.
What is a normal invoice exception rate?
Ardent Partners’ 2025 research puts the average at 14 percent, with top performers at 9 percent and teams without automation nearer 22 percent. Tax mismatches are a recurring contributor because they repeat on every document from an affected vendor or province, which is why line level tax handling is one of the fastest ways to move toward the top performing column.
About Finofo
Finofo is the AI native platform built in Calgary for Canadian finance teams. It brings accounts payable, expense management and purchasing onto one engine, on the cards, bank and ERP a business already uses, with line level extraction, Canadian tax handling and approval workflows designed for multi entity, multi province operations. Finofo does the verification. Finance keeps the judgment. Learn more at finofo.com.
