When taxes are not setup to sync, tax calculations may become inconsistent on records uploaded to your Point of Sale. This may be noticed in different ways according to your POS solution.
- The Migration Variance payment method is in use. You can ignore cases where the variance is only a few pennies as that accounts for rounding differences between Lightspeed and Magento.
- When the tax name associated to Lightspeed Sales is the Shop's default tax instead of the correct tax name, this usually means that the tax name the integration is instructing Lightspeed to use doesn't exist. Lightspeed defaults to the Shop's default tax in those cases.
- The Sale doesn't exist in Lightspeed, or you receive error notifications indicating a Sale couldn't be created. This may mean an integration placeholder product "Magento Taxes" is missing from Lightspeed, or the tax calculation is so inconsistent Lightspeed is encountering an error.
- The tax rate or rate name on Orders or Invoices is inconsistent with the rate or rate name from Magento Orders.
- The order/invoice doesn't exist in Lightspeed, or you receive error notifications indicating an order/invoice couldn't be created. This may mean an integration placeholder product "Magento Taxes" is missing form Lightspeed, or the tax calculation is so inconsistent Lightspeed is encountering an error.
For Heartland Users: Heartland provides a streamlined tax sync process. We're not aware of any known issues with tax sync for Heartland users.
Please contact our Support Team if you need assistance resolving any tax inconsistency.