Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Canada has 13 provincial and territorial jurisdictions, but there is no single provincial sales-tax rate or rule to apply across them. A Canadian sales-tax API needs to resolve the place and type of supply, apply the rates effective on the transaction date, and calculate each applicable tax using its proper base. I describe the API behind this article as handling all 13 jurisdictions; the details below explain what that coverage must account for, not an independently verified test of the API.
What “all 13 jurisdictions” means for sales tax
The Canada Revenue Agency (CRA) rate table groups jurisdictions into different tax arrangements: some have GST alone, some use HST, and some have a separate provincial tax alongside GST. Those arrangements affect both the rate a customer sees and how a calculation must be performed.
General rates listed by the CRA
The following are the general rates in the CRA table, current on or after April 1, 2025. They are a reference for ordinary cases, not a complete determination of tax payable on every transaction.
| Jurisdiction | General rate arrangement |
|---|---|
| Alberta | 5% GST |
| British Columbia | 5% GST + 7% PST |
| Manitoba | 5% GST + 7% PST |
| New Brunswick | 15% HST |
| Newfoundland and Labrador | 15% HST |
| Northwest Territories | 5% GST |
| Nova Scotia | 14% HST |
| Nunavut | 5% GST |
| Ontario | 13% HST |
| Prince Edward Island | 15% HST |
| Quebec | 5% GST + 9.975% QST |
| Saskatchewan | 5% GST + 6% PST |
| Yukon | 5% GST |
These figures come from the CRA’s general rate table. Separate provincial taxes and special cases may require checking the relevant provincial authority and the rules for the particular supply.
#1 Best Overall
Which rate should an API charge?
A customer’s address is an important input, but a postal code lookup alone is not a complete tax decision. CRA guidance says the rate depends on the place of supply and the type of supply. Place-of-supply rules determine where a supply is made and whether the provincial component of HST applies. Whether tax is payable can also depend on the recipient’s status.
For an API, this means the calculation should not assume that every purchase is taxed solely according to a billing address or that every product follows the same location rule. Its inputs and supported categories need to reflect the applicable rules; if the API cannot classify a case, it should make that limit clear rather than silently return a confident-looking rate.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
How GST and separate provincial taxes interact
In provinces with a separate provincial tax, a calculation may need to return more than one tax component. The base matters: CRA guidance says to calculate GST on the price excluding PST when both apply. An API that simply adds the displayed rates and applies the combined percentage to the same amount can produce the wrong result.
For example, if both GST and PST apply to a taxable sale, the API should preserve the taxable price and the separate tax components in its calculation so that GST is applied to the price before PST, rather than to a total that already includes PST. Provincial rules may have additional details, so this general treatment should not be presented as the complete logic for every transaction.
Why rates need effective dates
Rates change, so a reliable calculation needs to use the rate in force on the transaction date—not merely the rate that happens to be current when an invoice is viewed or a refund is processed. CRA lists Nova Scotia’s HST at 14% effective April 1, 2025; before that date, the applicable rate was different. Historical calculations therefore need date-aware rules if they are to reproduce the original transaction.
A practical API design should associate each rate and rule with its effective period, then use the transaction date to select the applicable version. This matters for refunds, adjustments, audit trails, and correcting old invoices. The response should also make the date basis visible so that a caller can tell whether the calculation used the sale date, invoice date, or another date supplied to the API.
Rank #4
How e-commerce and digital sales complicate the answer
CRA e-commerce guidance describes software and a subscription to a website as examples of intangible personal property. Its broad explanation is that supplies in participating provinces may attract that province’s HST, while non-participating provinces use 5% GST; detailed rules vary with the kind of supply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
That broad distinction is useful, but it does not establish a complete rule engine for every digital transaction. CRA’s April 2026 overview says it does not provide detailed information about certain digital-economy measures applying to specified digital-economy businesses and platform operators. It also explains that provincial taxes are generally administered by provincial authorities, subject to an exception for selected listed financial institutions. An API should state which digital-supply and platform cases it supports and which require separate analysis, rather than treating a general rate table as exhaustive.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
What “handles” should mean in an API claim
Supporting all 13 jurisdictions can mean anything from returning a general rate by location to calculating transaction-specific tax. The headline claim is mine; the tax authorities cited here establish the surrounding rules, not the implementation, coverage, or accuracy of my API. To evaluate any API making this claim, ask what it actually accepts, calculates, and exposes.
- Jurisdiction coverage: Does it return the right tax components for each province and territory, including separate GST and provincial tax where applicable?
- Place-of-supply inputs: Which customer, seller, delivery, and supply details can affect the result, and which supply categories are supported?
- Effective dating: Can it calculate using a past transaction date and preserve the rule version used?
- Tax treatment: Are taxable, exempt, zero-rated, and other special cases within scope, or must the caller classify them?
- Digital and cross-border boundaries: Does the documentation explain platform and digital-economy cases that may require rules beyond a general rate lookup?
- Calculation transparency: Does the result show the tax components, taxable bases, rounding method, and source or update provenance?
- Verification: Are there published tests for every jurisdiction, rate-change dates, separate tax bases, and supported supply types?
These questions distinguish a lookup utility from a fuller calculation service. A claim of jurisdiction coverage by itself does not answer them.
Rounding and official references
The CRA calculator describes its results as estimates and notes that rounding can produce a difference of one or two cents. An API should document its precision and rounding behavior, especially where separate taxes are calculated, and should not imply that its output is an official tax assessment. The CRA rate table and calculator are useful reference points for general rates and estimates; they do not establish that a third-party API uses the correct inputs or rules for a particular sale.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
