Province reporting
WooCommerce tax reports by Canadian province
Build a Canadian WooCommerce tax report by province and tax type. Review address attribution, unmapped rates, refunds, and order-level reconciliation.
TaxPack field notes / Canadian WooCommerce stores
Make the numbers
easier to explain.
Start with a complete reporting guide, or find a focused answer to a specific WooCommerce tax-record question. Every field note links back to the source record and explains what the report can—and cannot—tell you.
Start with the full guides
Accountant exports
How to export a WooCommerce tax report for your accountant
Export WooCommerce tax reports to CSV using native Analytics or TaxPack. Learn which files, date settings, and reconciliation details to send your accountant.
GST / HST
Preparing a GST/HST report from WooCommerce orders
Separate recorded GST and HST in WooCommerce, review refunds and dates, and export traceable totals for your accountant without recalculating historical taxes.
Reconciliation
Why WooCommerce tax reports differ: refunds, shipping, and discounts
Trace WooCommerce tax-report differences caused by refund dates, shipping tax, discounts, missing allocations, and report settings. Includes worked examples.
Québec / GST / QST
Separating GST and QST in a WooCommerce report
Prepare separate GST and QST totals from recorded WooCommerce tax lines. Review Québec attribution, refunds, rate mappings, and English/French worksheets.
PST reporting
WooCommerce PST reports for BC and Saskatchewan
Separate recorded PST from GST in WooCommerce, keep BC and Saskatchewan groups distinct, and review refunds and unmapped rates before exporting.
Manitoba RST
How to get a Manitoba RST report from WooCommerce
Build a Manitoba RST and GST breakdown from recorded WooCommerce taxes. Classify rate IDs, review missing allocations, and export a clear summary.
Native reports
Using WooCommerce Analytics Taxes for a Canadian store
Compare WooCommerce’s built-in Taxes report with Canadian province and tax-type reporting. Check date settings, refunds, exports, and source traceability.
Reconciliation
A WooCommerce tax reconciliation checklist for Canada
Trace a WooCommerce tax summary to stored tax lines and refund records. Work through date, mapping, shipping, currency, and missing-allocation differences.
Getting started
Your first WooCommerce tax report with TaxPack
A first report should answer one narrow question before you try to reconcile an entire year of store activity.
Run a one-day WooCommerce tax report test
A one-day test isolates date, status, and address settings before a full month introduces many different records.
Where to find TaxPack after installing it
A plugin can be active while its report screen is hard to find among WooCommerce's many admin menus.
When to use WooCommerce Taxes or TaxPack
The built-in Taxes report may already answer a tax-code question, while a Canadian province review needs a different grouping.
Trace one WooCommerce order through a tax summary
A store-wide total is easier to trust when you can follow one source order through the summary and detailed files.
Why an order with no tax line is absent from totals
Some WooCommerce orders have no recorded tax lines, so a tax summary can be empty even though orders exist.
Read a WooCommerce tax report with two currencies
A multi-currency store can show similar province and tax-type rows that are not mathematically combinable.
Choose shipping or billing for a first report
TaxPack asks for one province attribution source because WooCommerce orders can carry both shipping and billing addresses.
What to save after your first free report
The free edition regenerates data when you download, so preserving the original files matters if records later change.
Start a WooCommerce tax review with the flagged events
A tidy summary can hide unresolved source questions unless you look at the review section before exporting totals.
Tax-rate mapping
Map tax rate IDs instead of names
Two WooCommerce rates can share a label while representing different historical configurations or tax types.
Keep historical WooCommerce rate IDs visible
An old rate ID can remain on past orders after the live tax table changes, and it still matters to historical reports.
Handle two WooCommerce rates with the same label
Duplicate tax labels make a summary ambiguous unless the underlying rate IDs are reviewed separately.
What a renamed WooCommerce tax rate does to reports
Renaming a current tax-rate row can change what an administrator sees without rewriting every historical order line.
Why TaxPack shows an UNMAPPED group
UNMAPPED means a stored tax line references a rate ID without a verified reporting classification.
Why a mapping change requires a new TaxPack summary
TaxPack rejects a download from a report screen whose mapping revision has changed since the screen was generated.
Tax class versus TaxPack reporting type
A WooCommerce tax class controls checkout configuration, while TaxPack's type is a reporting label for a stored rate ID.
Review mappings after importing tax rates
A tax-rate CSV import may introduce new IDs even when the imported labels look familiar.
Check a GST or HST mapping against source lines
A rate name containing GST or HST is a clue, but the source order and rate ID should decide the reporting label.
How free and paid TaxPack share rate mappings
A store can begin with the free plugin and later use the paid edition without reclassifying every existing rate ID.
Province attribution
Shipping versus billing province in a tax report
WooCommerce can store different shipping and billing provinces on one order, so a report needs a stated attribution rule.
A missing shipping province in WooCommerce
A digital or pickup order may have no shipping province even though it has a valid billing address.
Check province attribution on guest orders
A guest checkout can still contain order address fields, but the customer account cannot be used as a substitute for them.
Report a digital order with no shipping address
Digital-only WooCommerce orders often lack shipping details, which changes what a shipping-based report can show.
What happens to a non-Canadian order address
A store selling internationally may have tax lines on orders whose selected address is outside Canada.
Review conflicting billing and shipping provinces
A conflict flag helps you find orders whose two stored province fields disagree.
Why country matters to province grouping
A province code alone is ambiguous when an order's selected country is missing or not Canada.
Check a WooCommerce province code against its label
WooCommerce stores province codes while an administrator may see a full province name in an address form.
Compare two province report bases without mixing them
Running both shipping-based and billing-based reports can show how sensitive a breakdown is to the chosen address.
How to work through UNRESOLVED province rows
UNRESOLVED keeps tax-bearing events visible when the selected address cannot support a Canadian province group.
Refund review
Read a full WooCommerce refund in a tax report
A full refund is a separate recorded event whose tax should be read with its own date and sign.
Trace tax on a partial WooCommerce refund
A partial refund may reverse only selected item or shipping tax lines rather than the whole order's tax.
Why an amount-only refund may have no tax allocation
WooCommerce can record a refund amount without matching tax-line allocation when the operator enters only a value.
Manual WooCommerce refunds and the payment record
A manual refund entry in WooCommerce does not by itself prove that funds returned through a gateway.
Report a refund of an older WooCommerce order
A refund created this month can refer to an order created months earlier, so order and refund periods need separate treatment.
A refund posted in a later reporting month
Month-end reconciliation can differ when the shopper purchase and its refund cross the reporting boundary.
Read several refunds against one WooCommerce order
A single order can have multiple refund events with different dates, items, and tax allocations.
Why a refunded parent status does not remove a refund
Order status filters apply to current orders, while refunds are queried as their own dated events.
Find shipping tax in a WooCommerce refund
A refund can reverse shipping tax as well as product tax, but only when that allocation is stored on the refund.
Investigate a refund total that differs from tax lines
A refund's recorded tax total and summed tax lines can disagree when its allocation is incomplete or unusual.
WooCommerce tax settings
Read taxes when WooCommerce prices include tax
An inclusive catalog price can make the customer-facing amount look different from an exported tax-line amount.
Investigate a small WooCommerce tax rounding difference
WooCommerce can round at line or subtotal level, so visible prices and stored tax detail can differ slightly.
Review shipping tax class in a report
WooCommerce's shipping tax class setting affects checkout calculations before TaxPack reads the completed order.
Understand a coupon's effect on recorded tax
A WooCommerce discount can change the tax stored on an order, but the discount itself is not a second tax adjustment.
Read taxable WooCommerce fee lines in TaxPack
An order fee can carry its own tax line, which may be easy to miss when reviewing only products.
Review compound tax lines without recalculating them
WooCommerce can mark a tax rate as compound, which affects its checkout calculation order.
Why a zero-rate order has no tax amount
A zero-rate or exempt order may contribute no tax even while the sale itself appears in order records.
Report an order with more than one tax class
A mixed cart can produce several tax rate IDs on one order, not a single universal category.
Compare reports before and after a tax setting change
A change to checkout tax settings affects new orders but should not cause TaxPack to reprice historical orders.
Audit orders after a WooCommerce tax-rate import
A rate-table import can add or replace rows that later appear under unfamiliar IDs in report detail.
CSV exports
Summary CSV versus detailed TaxPack exports
The three free CSV downloads describe different levels of the same recorded WooCommerce events.
How to read a TaxPack tax-line CSV
The tax-line CSV is the place to inspect stored rate IDs, labels, mapped types, and item-level tax components.
How to read the TaxPack order/refund CSV
The order/refund file includes source events that may have no tax-line row, making it essential for exception review.
Why summary CSV has review_event rows
The summary export includes separate exception rows so unresolved source events are not hidden behind grouped totals.
What a period_info row means in an empty report
An empty, unflagged selection still needs metadata showing which period and filters were run.
Use source event IDs to audit a TaxPack total
A province/type total is easier to verify when its contributing order and refund event IDs remain visible.
Read TaxPack's date and timezone CSV metadata
A CSV date range is ambiguous if the store timezone and event-date rule are lost during sharing.
Open a TaxPack CSV with accented labels intact
Tax-rate labels and other exported text can contain accented characters that spreadsheets may misread if encoding is guessed.
Preserve exact tax decimals in a spreadsheet
A spreadsheet can display fewer decimal places than TaxPack exported, hiding small differences during reconciliation.
Why TaxPack escapes formula-like CSV text
A stored label or identifier beginning with a formula character can be interpreted as a command by spreadsheet software.
Reconciliation
Why WooCommerce Taxes and TaxPack totals differ
Two tax reports can use different dates, statuses, refund handling, and grouping even when they read the same store.
Investigate order tax versus summed tax lines
WooCommerce stores an event tax total and tax-line detail that should be compared when reviewing exceptions.
Why a processor payout differs from recorded tax
A payout statement combines settlement timing, fees, and possibly currency conversion, while TaxPack reads order tax events.
Reconcile two adjacent WooCommerce tax months
An order near month-end and a later refund can make adjacent monthly reports look asymmetric.
Why sales revenue is not a TaxPack tax total
Sales reports and tax reports measure different fields, so their grand totals should not be compared as if equivalent.
Reconcile shipping tax without adding it twice
TaxPack shows shipping tax as an included component so reviewers can explain a net tax amount.
Treat discount fields as explanatory, not extra tax
Discount fields can explain why a stored tax amount is lower than a full-price expectation.
Reconcile tax without combining currencies
A store with CAD and USD orders needs separate tax totals before any external conversion policy is considered.
Reconcile recorded tax with missing tax lines
An order-level tax amount without matching tax-line detail creates a traceability gap.
Build a reviewable WooCommerce tax evidence pack
A reviewer needs filters, source IDs, and exceptions, not just a screenshot of a grand total.
Report periods
Are TaxPack report From and Through dates inclusive?
Date pickers can cause off-by-one errors if a store owner assumes the Through date is excluded.
Why a midnight order appears on a different report day
The store timezone, not a UTC email timestamp, determines the local date used by TaxPack.
Create a repeatable monthly WooCommerce tax pack
A monthly review is easier to reproduce when every run records the same set of filters and source files.
Choose a non-overlapping quarterly report range
Adjacent quarterly reports should cover every local day once without sharing a boundary day.
Why TaxPack uses order creation date, not payment date
A payment can settle after an order is created, so a payout period need not match the order report period.
How current order statuses affect a past period
TaxPack filters orders by their current status when a report is generated, not by a historical status snapshot.
Refund date independent of parent order date
A refund should be found by its own creation date even when its parent order is outside the selected period.
Check year-end WooCommerce order and refund boundaries
Year-end reviews need special attention to events created around midnight and refunds of prior-year orders.
Use one-day periods for a source-order investigation
A very short period is useful when you need to isolate one confusing order or refund without thousands of other events.
Split a report that exceeds 5,000 events
TaxPack has a 5,000 order/refund event limit per report to avoid unsafe resource use on shared hosting.
Store operations
Use TaxPack with WooCommerce HPOS
WooCommerce stores orders in dedicated tables under HPOS, so a reporting plugin must use WooCommerce order APIs.
Use TaxPack on legacy WooCommerce order storage
An older WooCommerce store may still use WordPress posts tables as its authoritative order storage.
Verify tax reports after an HPOS migration
A storage migration is a good moment to compare a few known order and refund events before relying on a full period.
Check a sample report after a WooCommerce update
A WooCommerce update can change admin presentation or data APIs, so a sampled report is a useful operational check.
Separate staging and production tax reports
A staging copy can contain old, synthetic, or partially synchronized orders that should not be mixed with production evidence.
What order data leaves the store when using TaxPack
A store owner may need to understand whether creating a tax summary uploads customer or order records.
Who can open TaxPack reports in WordPress?
TaxPack reporting is an admin task that requires the WooCommerce management capability.
What happens to mappings when TaxPack is deactivated?
A temporary plugin deactivation should not erase the store's reporting classifications.
Include a custom WooCommerce order status deliberately
Extensions can add order statuses, and TaxPack presents current statuses as selectable checkboxes.
Back up before changing tax-report inputs
A report is read-only, but edits to source orders, rates, or mappings can affect future generated exports.
Troubleshooting
Why a TaxPack summary is empty
An empty summary can result from a date or status filter, no tax lines, or a period with no matching events.
Why a historical rate is absent from the live mapping list
A deleted or replaced WooCommerce rate may no longer be in today's tax table even though old orders reference it.
Fix a TaxPack export blocked by a mapping revision
An export can be refused when rate mappings changed after the displayed summary was generated.
Retry an expired TaxPack report or download form
A long-open WordPress admin tab can have an expired security nonce when you finally submit a form.
Troubleshoot a missing TaxPack admin menu
The TaxPack menu may be absent when the plugin or WooCommerce is inactive, or when the user lacks permission.
Shorten a TaxPack report that times out
A host can run out of PHP time or memory before reaching the plugin's 5,000-event ceiling.
What to do with unsupported tax precision
Some imported order data can contain tax values outside the precision TaxPack's exact arithmetic supports.
Investigate an unexpected province in a TaxPack group
A surprising province may come from the selected address basis rather than a tax-rate mapping error.
Find a refund missing from a selected period
A refund that seems absent may have a creation date outside the store-local range or no stored tax allocation.
Fix a spreadsheet view with shifted CSV columns
A spreadsheet may guess the wrong delimiter or encoding and make a valid CSV look misaligned.