An online order with two different tax outcomes
A distributor sells through an online storefront. A customer in a province with more than one sales tax orders a few cases of product and pays for shipping. Both taxes apply to the goods. Only one of them applies to the shipping charge. When the order flows into the accounting software, the tax amounts do not match what the business expects, and someone on the finance side has to work out which line should have carried which tax.
Why workarounds get uncomfortable
When the storefront and the accounting software cannot treat each line of an order differently, the practical fixes are manual. Someone edits the tax after the order arrives. Or the business leaves the shipping charge without the second tax so the order total looks right. Or an accountant corrects amounts at month end.
Each of these puts a judgment call on a person at the moment volume is highest. The order team sees the mismatch, the bookkeeper reconciles it, and the owner signs off on the return. The workaround also leaves a thin trail. If the question later becomes why a given order was taxed the way it was, the answer lives in someone’s memory rather than in the record.
What is at stake
Tax amounts that cannot differ by line may be collected incorrectly on shipping, which could raise questions if the business is ever audited. Finance time may go to correcting orders instead of reviewing results. Confidence in the liability figure may drop, which can make filing slower and more cautious.
None of this requires a dramatic failure. It is the slow cost of a process where the answer to ‘what tax applies to this line?’ depends on who happens to be looking.
What a better process has to do
For a business with this pattern, the buying criteria are fairly concrete:
- Tax decisions are made line by line, so goods and shipping can carry different treatment on the same order.
- Rates are tied to dates, so an order is taxed at the rate that applied when it was placed.
- The ship-to location and any customer exemption feed the result, rather than someone choosing by hand.
- When tax is suppressed, there is a recorded reason.
- Collected tax lands in a liability account, so the amount owed and the amount remitted can be compared.
It is also fair to ask where tax is calculated: inside the ERP, or by an outside tax service. Both approaches are legitimate, and the right answer depends on how complex the jurisdictions are.
How Versa approaches tax treatment
Versa is an established ERP that handles orders, invoicing, inventory and accounting in one system. Tax is part of how a sales document is built rather than something added afterward.
Versa supports tax definitions with effective-dated rates, so a document is taxed at the rate that applied on its date. Taxes can be grouped by jurisdiction. Tax codes are assigned to products and to customers, and the ship-to address and any customer exemption are inputs to the result. When a line is not taxed, Versa supports recording a documented reason, so an explanation is attached to the record. Tax collected posts to a tax liability account until it is remitted, and Versa supports recording remittances against that balance.
For businesses that prefer an outside tax engine, Versa also offers an optional Avalara integration for tax lookup. Which approach fits depends on the business.
Two practical points matter for the decision. Tax outcomes depend on how taxes, codes and products are set up, so the first design choice is how your goods and shipping charges should be classified. And some tax settings that span multiple legal entities are choices made at initial setup, so they are worth deciding before master data is loaded.
The same order, handled differently
Return to the opening order: a few cases of product, plus shipping, going to a province where both taxes apply to the goods and only one applies to shipping. With tax determined from the classification of each line, the customer and the ship-to location, the goods line and the shipping line each pick up the tax that applies to them.
The order team does not need to adjust tax after the order arrives. The bookkeeper sees the tax on each line and, where tax was suppressed, the reason. The owner reviews a liability balance built from those lines and compares it with what has been remitted. The judgment call moves from the busiest moment of the day to a one-time classification decision, made on purpose and visible in the record.
See this workflow in Versa
A focused conversation can make this concrete. We would be glad to walk through a representative online order with goods and shipping under different tax treatment, showing how each line is taxed, how the liability is recorded, and how an optional external tax service would fit. It clarifies what Versa does for this pattern and where setup decisions come in, and it needs no preparation on your side.
Request a Versa demo focused on line-level tax treatment for goods and shipping.
If you would rather explore first, you can ask about this workflow before deciding whether to speak with sales: Explore this topic with Versa AI Advisor.
Request a Versa demo focused on line-level tax treatment for goods and shipping: https://www.versaclouderp.com/contact-us