GST/HST Registry Search: 6 Services Compared

Six GST/HST registry search options at a glance

A GST/HST registry search can answer several different questions, so the shortlist should start with the evidence required. The Canada Revenue Agency service checks whether a supplier was registered on a specified transaction date. A company-data service helps identify the legal entity behind a number. An API or tax platform makes validation easier to run inside onboarding, invoicing or checkout. Those outcomes support one control, but they are not interchangeable.

This is a VATFind-published comparison, not an independent ranking. The CRA service appears first as the official baseline, followed by VATFind and Global Database under the article's stated ordering rules. Capabilities and public prices were reviewed on 11 October 2026. Where documentation does not confirm Canadian fields, source behaviour or contract terms, this guide labels the point for a proof of concept rather than inferring a feature.

What a GST/HST Registry result proves

A standard CRA GST/HST program account has a nine-digit business number, the RT program identifier and a four-digit reference number. The public registry asks for only the first nine digits, plus the supplier's legal, operating or trading name and the date shown on the invoice, receipt or contract. That date input is important: registration status is assessed for the transaction being supported, not merely today.

The CRA describes the registry as a free service for checking whether the business charging GST/HST is registered. After a successful search, its guidance tells purchasers to print the Search Details screen so input tax credit claims include tax charged by registered suppliers. For supplies of $100 or more, the supplier's GST/HST number is among the documentary fields the CRA lists for supporting an input tax credit. Other invoice requirements still apply.

Treat the response language precisely. ‘Insufficient information entered’ means the submitted name, number, date or name order did not match CRA records. ‘Not registered on the transaction date entered’ reports the status for that date. Neither message, by itself, proves that the supplier is fictitious or dishonest. Recheck the invoice data, ask the supplier for the registered name and escalate unresolved cases through the CRA channel documented for businesses.

Use the correct Canadian registry

The normal GST/HST Registry is not the only Canadian tax-ID route. The CRA maintains a separate simplified registry for certain non-resident digital-economy businesses. That list covers businesses registered under the simplified rules for cross-border digital products and services or platform-based short-term accommodation. A buyer should not send a normal domestic account to the simplified list, or treat an absence there as a failed normal registration.

Quebec sales tax is also distinct. The CRA directs users to Revenu Québec to confirm a QST number. Revenu Québec documents both an online service and an API that can return registration status, a status description, effective date, business name and commercial name. An unusual nine-digit QST situation involving a selected listed financial institution requires the CRA business enquiry route instead of either public validator.

This routing problem explains why ‘global coverage’ needs careful wording. A service may cover Canadian companies without offering live GST/HST status, or may validate GST/HST but not QST. Ask providers to name the authority, identifier type, result fields, date semantics, cache rules and failure states for every Canadian route you intend to use.

Official status and legal-company identity

The first three options represent the key architectural choice. The CRA service provides the official dated registration result. VATFind adds company-record context without labelling that record as a live CRA decision. Global Database publishes a wider tax-ID and company-intelligence workflow, but buyers should confirm the exact Canadian authority path and returned evidence in a controlled pilot.

VATFind monthly plans

Use the control to compare included company-record checks with monthly price. These allowances do not represent CRA Registry calls. Failed data-source operations do not consume a check, while custom API volume and bulk company-data delivery are quoted separately.

APIs for validation and tax workflows

The remaining providers wrap validation into different operating models. Fonoa exposes Canada in its tax-ID lookup and batch documentation. LookupTax routes Canadian checks to documented official sources and publishes entry-level allowances. Stripe validates supported customer tax IDs inside its billing and tax stack. None should be compared solely by country count: buyers need to test the Canadian response, date handling, evidence and outage states they will actually rely on.

LookupTax annual-plan allowances

This control compares the advertised per-month price when billed annually with the corresponding validation allowance. It does not treat free trials as ongoing capacity, and it keeps unconfirmed overages outside the arithmetic. Batch and CSV tools are documented for Enterprise.

A buyer checklist for GST/HST verification

Build the proof of concept from real Canadian records. Include a normal account with the full RT reference, a legal-name difference, a trading name, a historical transaction date, an invalid format, a date before registration and a simulated source outage. Test the raw response, timestamp, source label, evidence export, retry rules and human-review queue—not just the green result in the interface.

For an illustrative accounts-payable case, a supplier can present a familiar trading name while the CRA file uses a legal name. An insufficient-information response should trigger confirmation of the registered name and date, not automatic rejection. Preserve the attempted query, retry with corrected data, retain the official Search Details output when successful, and compare the legal entity to the supplier master. Keep bank-account-change verification separate.

• Define whether the control needs current status, status on the invoice date, legal identity or all three.
• Confirm normal GST/HST, simplified digital-economy and QST routing separately.
• Demand explicit unavailable, mismatch and not-registered states instead of one false value.
• Record source, retrieval time, submitted fields, raw outcome and reviewer decision.
• Compare monthly commitment, included calls, overages, batch limits, retention and exit rights.
• Ask how cached results expire and whether monitoring reruns the authority check or only company data.

Failure modes to design out

The most common design error is collapsing multiple meanings into one boolean. A syntactically correct number can fail the CRA name-and-date match. An authority can be unavailable. A valid GST/HST account can belong to a different legal company than the supplier record. Each state needs its own code, next action and audit trail.

The second error is losing time context. A lookup run today does not answer whether the supplier was registered on last quarter's invoice date unless the service actually submits and evaluates that date. The third is scope drift: a platform that calculates Canadian tax may not return company identity, while a company-data record may not prove active GST/HST registration. Write acceptance tests against claims, not feature labels.

Finally, avoid silent automation. Rate limits, source downtime, spelling differences and newly registered accounts will create exceptions. Set retry windows, cap automatic attempts, preserve the original evidence and route unresolved cases to a named owner. This article is general operational information, not personalised tax or legal advice.