How to Map NCR’s Tax Codes to Modern Sales Tax Automation Tools

NCR Retail Online connected ecommerce stores with inventory and business-management systems through synchronised catalogues, automated operations and security controls. Its discontinuation changes where stores operate, but not the tax meaning embedded in existing products, orders and customers. Australian retailers moving to Magento or WooCommerce through NCR Counterpoint partners need a translation layer that preserves legacy behaviour while rebuilding it around modern GST rules.

Australia adds complexity. The Australian Taxation Office administers a 10% GST, many supplies are GST-free or exempt, and shelf prices normally include tax. State and territory governments also administer liquor licensing, tobacco sales and other local operating rules. The goal is not to copy NCR’s codes literally, but to turn them into governed, testable rules that reflect Australian retail.

Why legacy tax codes need a translation layer

An NCR tax code can carry several assumptions: jurisdiction, taxable status, rate, tax-inclusive pricing, exemption eligibility and product category. Food, alcohol and general merchandise may look equivalent in an export but require different Australian treatment. Treat the code as a rule set, not a label, because copying it can lose meaning when the destination uses different product classes, zones and customer flags.

Build a canonical tax profile for every active code. Record its effective dates, jurisdiction, rate, price basis, exemption handling and linked product types, then retain the NCR code and description as source evidence. Add the replacement platform’s zone, class, rule and customer fields beside it. This creates an audit trail from historic orders to new calculations and prevents a rename during migration from silently altering tax treatment.

Build a clean NCR tax crosswalk

Export active Counterpoint or NCR Retail Online records, then compare them with product classes, prices and customer exemptions in the destination. Remove discontinued products, test records and one-off codes before designing the map. Give every canonical profile an owner and approval status so unknown combinations are resolved rather than inherited.

Map to stable concepts: jurisdiction, tax category, numeric rate and currency, inclusive or exclusive display, exemption basis, product type, effective date and rule precedence. Keep percentages separate from descriptions, and split mixed codes into distinct rules with a documented reason. Product examples can expose gaps: NCR’s food and wine catalogue tests varied GST and excise processes, while its gift basket examples show how food, alcohol, packaging and delivery complicate one basket. Validate them against current law and the actual configuration.

Configure the replacement platform for GST

In Magento or WooCommerce, configure the tax engine before importing prices or opening a sales channel. Decide whether catalogue prices include GST, whether checkout displays it separately and which customer records qualify for an exemption. Connect product tax classes, zones, rates and customer flags to the canonical profiles, then test discounts, shipping, refunds and rounding.

After import, reconcile subtotal, GST, shipping and total with an independent expected result. Keep a manual override path for unusual baskets, but log every override with a reason code. Reports must separate taxable, GST-free, exempt and zero-rated amounts, or the new checkout will be faster without improving tax visibility.

Handle Australian GST and state differences

Begin with the federal layer. Most taxable sales carry 10% GST, while GST-free supplies, zero-rated exports and exempt supplies have different reporting treatment. Australian shoppers are used to seeing “GST included” on labels, and trade quotes may say “ex GST”; invoices must still meet GST requirements. Finance should specify whether catalogue prices are inclusive or exclusive rather than accepting a platform default.

Then model state and territory realities. GST is national, but liquor licensing and rules for products such as tobacco and accommodation can vary by state or territory, while excise and regulatory charges sit outside a simple GST percentage. Stores in Melbourne, Sydney and Brisbane may share a price file while facing different delivery, age-restricted product or restricted-fulfilment requirements. Put location, product and fulfilment logic in the crosswalk instead of hiding it inside a rate field.

Seller and customer circumstances also change the result. GST registration generally applies once current GST turnover reaches $75,000, subject to particular organisational rules, and invoices may require an ABN. An exempt customer needs a recorded basis, such as a valid exemption certificate; typing “exempt” in a note is not evidence. Treat overseas purchases, marketplaces and imports as separate test cases.

Move products and customer records with tax intent intact

A clean product import carries more than a SKU and price. Preserve the old tax code, unit, description, product type, price basis, discount rules and every attribute affecting taxability. For bundles, record contents and whether the item is sold as one product or separate taxable lines. Gift cards, deposits, memberships and shipping may need their own profiles.

Operational data can expose problems hidden by a straightforward export. In food businesses, a dish size estimator may help distinguish a plated catering service from a packaged meal. That does not decide GST by itself, but it helps prevent materially different products from sharing one profile. The same clarity applies to alcohol bundles, hampers and mixed baskets, where contents and delivery terms matter.

Migrate customer data with restraint: capture ABNs and exemption evidence only where needed, retain source identifiers and stop old customer classes from overriding a newer exemption review. Use a controlled importer or an NCR Counterpoint partner’s integration for Magento or WooCommerce rather than editing thousands of records manually. Re-import after major catalogue changes and compare affected SKUs, since a category edit can leave the tax rule behind.

Validate the mapping through real order flows

Create a test set from the greatest tax exposures: standard-rated goods, GST-free groceries, exempt customers, alcohol, mixed gift baskets, shipping, discounts and refunds. Include an order fulfilled outside the home state and one manual override. Compare the result with both the NCR calculation and an independent spreadsheet, not just the displayed total; small discrepancies can hide in line rounding or shipping allocation.

Test the back office as well as checkout. Place and cancel orders, apply full and partial refunds, and confirm that the invoice, order export and accounting report use the same profile. Multi-location retailers should use representative transactions from Melbourne, Sydney and Brisbane to verify fulfilment location, restricted-product rules and local charges.

Training should show tested behaviour, not legacy assumptions. A recorded walkthrough can be split into focused clips using a video splitting guide, giving store staff one sequence for overrides and finance another for reconciliation. NCR’s abandoned cart sequence also warrants review: saved carts may retain tax inputs, but checkout should refresh the calculation so a changed rate, address or exemption cannot leave stale GST in the message.

Put tax governance into the operating rhythm

Make the crosswalk a controlled record with named owners in retail operations, ecommerce and finance. Review it whenever a category, store, tax rate, exemption process or fulfilment rule changes. Keep old and new values together, retain approval history and reconcile platform tax reports with the general ledger monthly. Automated checks should flag unmapped profiles, unusual overrides and material differences from NCR results.

After cutover, choose one system as the operational source for tax rules while retaining the NCR export as historical evidence. Document which settings migrated automatically and which required manual work, especially customer exemptions and state-specific products. If Counterpoint stays active during a parallel run, compare outputs continuously and resolve discrepancies before the old code list leaves any integration.

The next concrete step is to export the active NCR tax codes, assign an owner to each one, map them to canonical profiles, and schedule a parallel-run review against three historical Australian orders and one new mixed basket before the next catalogue import.