Recommended Free Tools
A Canadian sales-tax API needs to do more than return a province’s headline rate: it must account for the kind of supply, place-of-supply rules, separate provincial taxes, and the date of the transaction. The headline says the author built an API for all 13 provinces and territories, but the available evidence does not independently verify its code, tests, or actual coverage. The practical guide below explains what that coverage needs to mean.
Which sales-tax rates apply across Canada?
Canada does not use one uniform provincial sales-tax system. The Canada Revenue Agency’s general rate table, current on or after April 1, 2025 and accessed in 2026, distinguishes GST-only jurisdictions, HST provinces, and jurisdictions where a separate provincial tax is listed. These are general rates, not a complete decision about whether a particular transaction is taxable or which rules apply.
As an Amazon Associate I earn from qualifying purchases.
| Jurisdiction | General rate structure |
|---|---|
| Alberta | 5% GST |
| British Columbia | 5% GST plus 7% PST |
| Manitoba | 5% GST plus 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 plus 9.975% QST |
| Saskatchewan | 5% GST plus 6% PST |
| Yukon | 5% GST |
Rates in the table are the general rates listed by the CRA, not a promise that every product or customer is subject to them. The CRA identifies place of supply and type of supply as factors in determining the rate. Recipient status can also affect whether tax is payable. A rate lookup is therefore only one part of a calculation.
How does place of supply affect sales tax?
Place-of-supply rules determine where a supply is made for GST/HST purposes. For a taxable supply, that can determine whether a participating province’s HST applies and which provincial rate is relevant. The CRA’s April 2026 place-of-supply memorandum discusses the rules in Schedule IX of the Excise Tax Act and the New Harmonized Value-added Tax System Regulations. A customer’s address may be an important input, but an API should not treat a province field as the entire legal analysis.
#1 Best Overall
For software and subscriptions, the CRA’s e-commerce guidance says software or a website subscription can be intangible personal property. It describes the broad distinction that supplies in participating provinces may attract that province’s HST, while non-participating provinces use 5% GST; detailed rules depend on the supply. The API’s supported inputs and categories should make clear what it can determine and what it cannot.
Inputs a calculation may need
- The transaction date, so the applicable rate can be selected for that date.
- The customer’s relevant location details, rather than an assumed location derived from an incomplete address.
- The supply category, such as a digital subscription or software, where rules differ by type.
- Facts about the recipient or transaction that affect whether tax is payable.
- The taxable amount and any separately stated provincial tax, so each tax can be calculated on the correct base.
Why does an API need effective-dated rates?
Tax calculations should be reproducible for the date of the transaction, not just use the rate current when someone later views an invoice. Nova Scotia’s HST changed to 14% effective April 1, 2025, according to the CRA. A system that overwrites a single “current rate” can return a different answer for an older transaction after an update.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
A robust rate record should carry at least the jurisdiction, tax type, rate, and start date, with an end date or equivalent rule when a rate stops applying. Historical calculations should retain the transaction date and the rule version used. That makes it possible to explain why an earlier invoice differs from a new one without pretending the newer rate applied all along.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How do GST and a separate provincial tax interact?
In British Columbia, Manitoba, Quebec, and Saskatchewan, the CRA table lists GST alongside a separate provincial tax. Those figures should not automatically be treated as a single tax applied to the same base. The CRA says to calculate GST on the price excluding PST when both apply. For example, a calculation engine needs to represent the taxable price and the separate provincial-tax amount independently, then apply the GST base rule rather than multiplying both rates by the same amount by default.
That distinction affects both the returned breakdown and the total. An API should document which base it used for each tax, and its tests should check the separate-tax calculation rather than only compare a final combined percentage.
What should “handles all 13” mean in practice?
A coverage claim is meaningful only when it defines the cases supported. The headline does not establish which transaction types the author’s API accepts, how it determines place of supply, or whether it retains historical rates. Those are questions a developer evaluating the API should ask, not features that can be assumed from the jurisdiction count.
Rank #4
- Jurisdiction coverage: Does it return the relevant federal and provincial tax components for every province and territory, including separate PST or QST where listed?
- Effective dates: Can it calculate both current and historical transactions using rates that applied on the transaction date?
- Supply rules: Which place-of-supply inputs and supply categories does it support, and what happens when required facts are missing?
- Tax bases: Does it calculate GST on the amount excluding PST where required and expose each component?
- Tax treatment boundaries: Does it distinguish taxable, exempt, and zero-rated cases, and state how it handles digital-economy measures and other special cases?
- Transparency: Does the result identify the rate or rule applied, its effective date, rounding behavior, and any assumptions?
- Verification: Are there published tests or examples for each jurisdiction, rate change, tax-base interaction, and supported supply type?
Where do CRA tools fit—and where do they stop?
The CRA’s rate table and calculator are useful references for general rates and estimates; they are not evidence that a third-party API is correct or complete. The CRA notes that calculator results are estimates and rounding can produce a one- or two-cent difference. An API should state its precision and rounding method so users can reconcile results rather than assume every displayed total is an official assessment.
The CRA’s April 2026 overview also says it does not provide detailed information about certain digital-economy measures that apply to specified digital-economy businesses and platform operators. It says provincial taxes are generally administered by provincial authorities, subject to its stated exception for selected listed financial institutions. As a result, the general rate table and overview should not be presented as exhaustive logic for every digital or provincial tax situation. An API’s scope should identify where its rules stop and when a business needs jurisdiction-specific advice.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
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.
