π Problem Statement
Currently, tax amounts are aggregated into a single total field "tax total" in the exports, which makes it difficult to distinguish between different tax types (e.g., GST, PST, QST, HST) in the invoices/fulfillments export. This lack of granularity reduces clarity in financial reporting and limits usability for accounting and compliance purposes.
π‘ User Story
As a Pelcro client,
I want tax amounts to be separated by type (e.g., GST, PST, QST, HST) in the invoices/ fulfillments exports,
so that I can clearly understand, report, and reconcile taxes for accounting and compliance needs.
π― Definition of Done
β Tax amounts are exposed as separate fields by tax type (e.g., GST, PST, QST, HST) instead of a single aggregated value.
β All exports containing tax data (CSV, reports, etc.) include separate columns for each tax type
All new columns are added to the end of export.
Make sure taxes & its breakdowns are available on the invoices/fulfillments exports.
β The total tax amount, if still present, is clearly derived as the sum of individual tax fields
β Existing workflows that rely on total tax are not broken
β Proper handling is defined for cases where certain tax types do not apply (e.g., null or 0 values)
β Changes are validated to ensure accuracy of tax calculations across all outputs
β Documentation is updated to reflect the new tax structure and export format
Please authenticate to join the conversation.
In Progress
Pelcro Product
28 days ago

Rana Haleem
Get notified by email when there are changes.
In Progress
Pelcro Product
28 days ago

Rana Haleem
Get notified by email when there are changes.