Learn why VAT changes may not display correctly in Paytrail reports and how to resolve the issue. Common reasons include incorrect decimal separators, unsupported field formats, or outdated e-commerce platform versions. You will also find platform-specific details for Shopify and MyCashflow. Following these checks helps ensure VAT data is transmitted accurately and settlement reporting remains reliable.
Check the following points
- Decimal separator: Always use a period. Using a comma can cause JSON conversion errors and distort VAT data (for example, 25.5 could incorrectly convert to 25).
- Decimal places: VAT percentage values must have one decimal place (for example, 25.5).
- vatPercentage field: Enter this field as a number, not a string (without quotation marks).
- Platform version: If using a ready-made e-commerce platform such as WooCommerce, confirm that you have the latest plugin version installed.
E-commerce platform specific information
Shopify made system updates in June 2022 that temporarily stopped VAT information from being sent to Paytrail’s API. The issue has since been resolved, and VAT data can now be imported, but only a single VAT rate is supported for all products.
You can choose the correct VAT rate in your store’s settings, which Shopify will then include in reports. This feature does not apply retroactively, so for earlier periods (such as June 2022) and for stores using multiple VAT rates, we recommend relying on Shopify’s own reports, as they display product-level VAT data.
Due to technical reasons, VAT rates are currently not transferred to Paytrail’s settlement reports for merchants using the MyCashflow e-commerce platform. As a result, orders appear as single line items in the report.
We recommend tracking your VAT information directly in MyCashflow’s own reports. More details about order archiving and accounting reports can be found in the MyCashflow guide.
Improvements are being planned so that correct VAT rates will be reflected in Paytrail’s settlement reports in the future. However, this requires significant API updates, and a precise timeline is not yet available.