Tax Code Settings
Excel Import Tips
Audit Checklist
Authorized Dealer Support

How to Setup and Update SST Codes in AutoCount Accounting

Wrong SST codes create wrong returns. This guide shows how to set up and update SST codes in AutoCount Accounting, import changes via Excel with fewer surprises, and audit documents before your filing deadline.

Request a Free Demo

Malaysian business professional holding an open laptop with AutoCount accounting software

AutoCount pages SST Setup Guide

SST codes in AutoCount — what “correct” looks like

In AutoCount Accounting, SST codes drive how sales and purchase documents calculate tax and how reports summarise taxable, exempt, and out-of-scope lines. Correct setup means every item, debtor, and voucher default points to an intentional code—not a leftover from an old GST migration. Work from certified licensing via AutoCount Accounting Malaysia so your edition and tax modules match what this guide assumes.

Before You Change Any SST Code

Protect the live company file. SST mistakes propagate into every invoice you print this month.

Take a verified backup of the AutoCount company database before mass updates. Note your current SST return period dates and whether any documents are still unposted. If you are mid-filing, finish or park that return before redesigning codes.

List the tax treatments you actually sell and buy: standard-rated, exempt, designated areas, out-of-scope, and any special schemes your advisor confirmed. Do not invent codes “just in case.” Every active code should map to a filing line your accountant recognises.

If your deployment was purchased through an AutoCount Authorized Dealer, confirm edition features and that tax modules are enabled. Orphaned GST-era codes leftover from migrations are a common source of silent misposting—plan to retire them deliberately.

How to Setup SST Tax Code Settings in AutoCount

Create or edit tax codes with rates, accounts, and descriptions that reporting can trust.

Open AutoCount tax maintenance (exact menu labels vary slightly by edition) and review existing SST codes before adding duplicates. Prefer a short, stable code list over dozens of near-identical entries that clerks misuse.

For each SST code, set the rate, tax account mapping, and a plain-language description staff will understand at voucher entry. Align output tax and input tax accounts with your chart of accounts so trial balance and SST worksheets reconcile without manual journals every quarter.

Set defaults carefully: stock item tax codes, debtor/creditor defaults, and document tax behaviour. A correct master data default prevents hundreds of wrong lines; a wrong default multiplies them. After changes, create one sales invoice and one purchase invoice in a test series and verify the tax amount and GL impact.

1. Inventory existing codes — Export or screenshot the current tax code list. Mark which codes appear on open documents and which are unused leftovers.
2. Define the target code set — Agree with your tax advisor which SST treatments you need. Name codes consistently (for example SR-6, ES, OS) and document when each applies.
3. Map GL accounts — Assign output/input tax control accounts and confirm they are not mixed with unrelated liabilities or expenses.
4. Update masters — Apply defaults on items and parties in batches—start with high-volume SKUs and key customers/suppliers.
5. Smoke-test documents — Post sample AR and AP documents, then check tax enquiry/reports against expected rates before releasing to all users.

How to Update SST Codes When Rates or Policies Change

Updates are not just editing a percentage—they are a controlled cut-over.

When SST rates or applicability change, decide whether to edit an existing code or introduce a new code effective from a date. Editing a live code can retrospectively confuse reports if historical documents should keep the old treatment for audit narrative. Many finance teams prefer new codes for rate changes and freeze old codes from new entry.

Communicate the cut-over date to every branch and to any integration that stamps tax codes—POS, ecommerce middleware, or AutoCount API bridges. A plugin or API that hard-codes an obsolete tax code will silently recreate the problem you just fixed in the UI.

After the update window, run an exception report: documents dated after cut-over that still use retired codes. Fix those before they hit your SST return. Pair operational training with your AutoCount training plan so cashiers and AP clerks know the new defaults.

Excel Import Tips for SST and Master Data Updates

Imports save hours—and can corrupt thousands of items in minutes. Use a disciplined template.

Always import into a restored training company first. Validate row counts, tax code spellings, and sample items before touching production. Keep the original Excel file versioned with a date stamp and owner name.

Normalise codes in the spreadsheet: trim spaces, enforce uppercase/lowercase rules matching AutoCount, and reject blank tax fields for taxable item categories. Watch for CSV encoding issues that turn codes into scientific notation or drop leading zeros.

Import in slices—top sellers first—then reconcile stock enquiry samples. If AutoCount rejects rows, fix the source file; do not “force through” by clearing validations. After a successful production import, freeze the template as the only approved update channel for the next cycle.

Use a locked template

Protect header columns and provide a dropdown list of allowed SST codes so users cannot invent spellings.

Reconcile counts

Compare expected vs imported row counts and spot-check high-value SKUs and major debtors.

Retain evidence

Store pre-import backup, import file, and post-import exception list with your SST working papers.

Auditing Steps Before You File SST

Treat AutoCount reports as working papers—not a last-minute surprise.

Run SST or tax summary reports for the exact return period. Tie output tax to sales documents and input tax to purchase documents. Investigate credit notes, debit notes, and cancelled vouchers that may reverse or adjust tax without obvious narrative.

Sample invoices across branches and tax codes. Confirm the printed tax amount matches the posted tax and that exempt or out-of-scope lines are not accidentally rated. Check that zero-rated/exempt descriptions (where applicable to your scheme) are used intentionally.

Reconcile tax control accounts in the GL to the SST worksheet total. Differences often come from manual journals, imported opening balances, or documents posted to the wrong period. Resolve them before submission—not after Customs queries arrive.

If e-Invoice is live, confirm SST treatment on AR documents remains consistent with AIP submission expectations. Tax code and MyInvois classification problems compound when fixed in only one place.

Period lock awareness — Know which periods are open. Do not “fix” historical SST by editing locked months without advisor approval.
Document sampling — Pull a mixed sample of B2B, B2C, credit notes, and inter-branch documents for each active tax code.
GL vs tax report — Match tax payable/receivable control accounts to AutoCount SST summaries; document every reconciling item.
Exception clearance — Clear unmatched imports, suspense postings, and retired-code usage before filing.

Keep SST Codes Healthy After Go-Live

Assign an owner for tax code changes—usually finance, not IT alone. New items and new suppliers should not go live without a tax code checklist. Review dormant codes quarterly and disable entry where safe.

When in doubt, escalate to your advisor and to Xantec through AutoCount Accounting Malaysia support channels. Configuration help is cheaper than amending returns. For hands-on enablement, schedule a focused tax-coding lab via our training programmes.

Frequently Asked Questions

How do I setup SST codes in AutoCount Accounting?

Back up the company file, define the tax treatments you need with your advisor, create or tidy SST codes with correct rates and GL mappings, then update item and party defaults. Smoke-test sales and purchase documents before releasing changes company-wide. Full guide: https://xantec.com.my/software/autocount-sst-guide

Should I edit an existing SST code or create a new one when rates change?

Often it is safer to create a new code for a rate or policy change and stop using the old code for new documents, so historical reports remain intelligible. Confirm the approach with your tax advisor, especially around open return periods. See https://xantec.com.my/software/autocount-sst-guide

Can I update AutoCount SST codes using Excel import?

Yes—many teams import item or master updates that include tax codes. Always test on a restored company first, normalise code spellings, import in batches, and keep the file plus backup as audit evidence. Steps: https://xantec.com.my/software/autocount-sst-guide

What should I audit before filing SST from AutoCount?

Run period tax summaries, sample documents per tax code, reconcile tax control accounts to worksheets, and clear exceptions such as retired codes on new documents or unmatched imports. Finish corrections before submission. Checklist: https://xantec.com.my/software/autocount-sst-guide

Does Xantec help with AutoCount SST configuration?

Yes. As an AutoCount Authorized Dealer, Xantec supports SST code setup reviews, import dry-runs, and pre-filing checks—alongside licensing and training. Contact https://xantec.com.my/contact or WhatsApp the team for a working session. Hub: https://xantec.com.my/software/autocount-accounting-malaysia

How does SST setup relate to LHDN e-Invoice in AutoCount?

SST codes and e-Invoice classification must stay consistent. Fixing tax codes in AutoCount without aligning AIP document behaviour—or the reverse—creates mismatched reporting. Coordinate both workstreams when you enable MyInvois: https://xantec.com.my/software/autocount-e-invoice

Get Help Setting Up SST Codes in AutoCount

If you want a guided setup, import dry-run, or pre-filing audit, request a session with Xantec—or WhatsApp us with your edition details.

Request SST Support WhatsApp Our Team