Compare India SuiteTax Output Tax After a Ship-To Change

Preview one India sales order for Karnataka and Delhi destinations, then compare the returned output-tax rows without relabeling generic partner-engine codes.

The quick answer

Changing the ship-to address can change the tax inputs, but the old Tax Details remain only a prior calculation until you run Preview Tax again. Compare the refreshed tax types, codes, bases, rates, and amounts with the first preview. Check Place of Supply if the form exposes it. Generic partner-engine output labels do not by themselves identify statutory GST components.

The screens use sample data. Person and operating-company names are fictional; use your own records and values.

Before you start

This example uses a configured SuiteTax partner engine, an India Operations subsidiary with an effective Karnataka registration, prepared tax rules, a taxable industrial fastener set, and two complete customer addresses. The seller location remains Bengaluru Distribution. The sales order is dated October 1, 2026 in INR; three units at ₹760 yield a ₹2,280 subtotal. There is no exemption, export treatment, reverse charge, or manual override.

01. Check the Karnataka inputs

Open the prepared sales order. Confirm the customer, India Operations, Bengaluru Distribution, date, INR currency, and three industrial fastener sets at ₹760. On Shipping, select the Karnataka address. If India Tax Information exposes Place of Supply, verify that field separately; the selected address does not prove its value. Check customer registration and GSTIN, item classification, and HSN/SAC mapping where this account or engine uses them.

Start with the prepared Karnataka address.

02. Preview the first result

Click Preview Tax and wait for Tax Details to refresh. Record the returned Tax Type, Tax Code, Tax Basis, Tax Rate when shown, and Tax Amount for the item. The configured partner engine shows two generic output-tax components totaling ₹410.40 for the first address. Use their displayed names; do not rename them as statutory components without the account’s rules.

Record the first preview’s output-tax rows.

03. Change only the ship-to destination

Return to Shipping and choose the prepared Delhi address. Confirm the state and postal code. Keep seller location, customer, item classification, quantity, price, transaction and tax point dates, currency, and overrides unchanged. Verify Place of Supply under the account’s India tax procedure if the form exposes it. Run Preview Tax again.

Change the destination while keeping the basket and seller location fixed.

04. Compare the recalculated rows

Read the refreshed Tax Details. In this partner-engine example one country-level output-tax row replaces the earlier two generic rows, while the displayed tax total remains ₹410.40. The matching total does not establish identical tax treatment. Compare types, codes, bases, rates, amounts, and total; check the account’s tax rule and registration before assigning a statutory meaning. A sales-order preview does not prove the later invoice or filed return.

Compare the refreshed row structure with the first preview.

Product reference: Applying India GST on Transactions.

Common questions

Does changing Ship To recalculate tax automatically?

Run Preview Tax again and wait for refreshed Tax Details before treating the rows as a new calculation.

Can I call the generic rows CGST, SGST, or IGST?

Only if your configured tax types, codes, and rules establish that mapping. The generic labels in this partner-engine example do not.

Is Ship To always the Place of Supply?

No. Check the account’s explicit Place of Supply and supply classification where those fields are available.