PST reporting
WooCommerce PST reports for BC and Saskatchewan
A store-wide PST total can hide two different questions: which recorded rate produced the amount, and which province the order is attributed to. For a BC or Saskatchewan reporting handoff, keep the tax type and province as separate columns.
The short answer
In TaxPack, classify the recorded PST rate IDs as PST, choose a shipping or billing address basis, and generate the period. Read the BC–PST and SK–PST groups separately from GST and from each other. Use recorded amounts, including signed refunds; do not recreate the tax from sales and a percentage.
PST is a type; BC and SK are province groups
TaxPack does not treat the text “PST” as proof of an order’s province. A rate ID is classified by you, while the province comes from the address you selected. This avoids collapsing every similarly named tax line into one location.
For example, a store may have different historical rate IDs with the same PST label. Map each known ID after checking your configuration and records. The reporting label does not establish whether a transaction should have been taxed; investigate that separately with the person responsible for your books.
Build the PST breakdown
- Open WooCommerce → TaxPack Free → Rate mappings. Identify the recorded rate IDs that belong in PST and classify them explicitly.
- Map GST IDs separately. Leave uncertain IDs unmapped until you can confirm them.
- Choose the reporting dates, current order statuses, and shipping or billing attribution. Use one documented address basis consistently.
- Generate the summary. Review BC/PST, SK/PST, and any UNRESOLVED or UNMAPPED groups, keeping each currency separate.
- Open flagged source records before handing off the CSV. A recorded province does not validate the tax treatment.
Read signed refunds without combining provinces
The following fictional rows are already-recorded CAD tax amounts. They illustrate report arithmetic, not tax rates or amounts to remit.
| Province | Type | Order tax | Refund tax | Net recorded tax |
|---|---|---|---|---|
| BC | PST | 84.00 | −7.00 | 77.00 |
| SK | PST | 42.00 | −6.00 | 36.00 |
| BC | GST | 60.00 | −5.00 | 55.00 |
The BC GST row stays separate from BC PST. Refund values are signed: 84.00 plus −7.00 gives 77.00. Shipping tax is already part of the tax-line total; its separate column is not another amount to add.
Investigate a missing refund allocation
A monetary refund can exist without any recorded tax lines. In that case there is no defensible PST allocation for TaxPack to recover by arithmetic. It flags the refund instead of dividing the amount between GST and PST.
The free CSV carries that event in a review_event row even when it has no summary group. Keep it with the file and explain it in your handoff. Do not add exception rows to the summary totals, or remove them to make a spreadsheet appear reconciled.
Choose a current summary or a retained snapshot
Free TaxPack exports a new reading of the selected period. Record the generation time and keep the downloaded file. If someone changes an order between the page view and download, the file can differ. A changed mapping revision requires generating a fresh summary first.
Paid TaxPack saves the original report and provides detailed tax-line and order/refund CSVs. This is useful when the reviewer needs the exact historical rate IDs and amounts behind every group. Neither edition calculates your filing obligations.
Official references
These guides explain reporting workflows. TaxPack does not provide tax advice, calculate tax payable, or file returns.