Manitoba RST
How to get a Manitoba RST report from WooCommerce
When a reviewer asks for RST separately from GST, a generic “sales tax” column is not enough. The useful starting point is the store’s recorded tax lines, with a clear classification and an explicit province choice.
The short answer
Map the confirmed RST rate IDs to RST and GST IDs to GST in TaxPack. Generate a period using your chosen address basis, then review the MB/RST and MB/GST groups independently. Labels alone do not classify a tax line; uncertain IDs stay UNMAPPED.
Start with rate IDs, including older labels
A WooCommerce store can have a rate named “PST,” “Sales tax,” or a custom label even when the reporting category the bookkeeper wants is RST. TaxPack therefore asks you to classify the rate ID explicitly. It does not guess the category from the text or percentage.
Check the relevant store configuration and source records before mapping an ID to RST. If a historical rate no longer exists in the current rate table, the tax line on an old order may still reference its ID. Add that known ID in Rate mappings rather than creating a replacement WooCommerce rate.
Generate the Manitoba summary
- Open WooCommerce → TaxPack Free → Rate mappings and classify confirmed RST and GST IDs.
- Choose From and Through dates. TaxPack uses order creation dates in the store timezone.
- Choose the included current order statuses and a shipping or billing province basis.
- Read the MB/RST and MB/GST rows in each currency. Include UNMAPPED and UNRESOLVED groups in your review.
- Inspect the Items to review section, especially refunds without allocations or differences between event tax and tax-line totals.
Keep the two tax categories visible
Suppose a fictional CAD report contains the following amounts already stored in WooCommerce. The amounts below are examples of report rows, not rate calculations.
| Province | Type | Order tax | Refund tax | Net tax |
|---|---|---|---|---|
| MB | GST | 50.00 | −5.00 | 45.00 |
| MB | RST | 70.00 | −7.00 | 63.00 |
Keep 45.00 of GST and 63.00 of RST in their own columns or rows. A single combined tax total would lose the distinction the reviewer requested. Do not merge another currency into either amount.
Check period boundaries and unresolved addresses
A refund in the selected month is included using its own creation date, even if the original sale was in a previous month. The parent order’s current status does not remove that refund. A changed status can, however, affect which sale orders appear in a new report.
If you select shipping attribution and an order has no shipping province, TaxPack leaves it unresolved rather than substituting billing. A different billing address can also create a conflict flag. Make the reporting choice visible to the reviewer; the plugin is not deciding the legal jurisdiction of the sale.
Send the summary with its exceptions
The free CSV records filters, mapping revision, source event IDs and review flags. Its review_event rows retain flagged amounts even when there are no tax lines to group. Treat those rows as explanations, not extra tax to add.
If you need a retained report with detailed tax lines, order/refund records and worksheets, use paid TaxPack. A free download is rebuilt from current records; a paid saved report preserves the values read during generation. Neither is an official return or a calculation of tax payable.
Official references
These guides explain reporting workflows. TaxPack does not provide tax advice, calculate tax payable, or file returns.