SCSB Guide to SST Workflows in Business Central

SST automation in Business Central: controls before promises

Sales and service tax treatment in Malaysia depends on the transaction, the goods or services supplied, the supplier's registration position, current rates, exemptions and Royal Malaysian Customs Department (RMCD) policy. A Business Central configuration can support this work, but it cannot decide the legal treatment without accurate business rules and ongoing review.

SCSB helps Malaysian organisations design controlled SST workflows in Dynamics 365 Business Central. The implementation should make the organisation's approved treatment easier to apply, review, reconcile and evidence. Software configuration alone cannot determine the organisation's SST obligations.

Use current RMCD material

MySST publishes legislation, orders, industry guides, service-tax policies and operational information. Those sources change as new sectors, rates, exemptions and transitional rules are introduced. At the time of this review, the MySST service-tax policy list included amendments and policies published through July 2026, and the orders list included a 2026 amendment to the Service Tax Rate of Tax Order.

The current MySST service-tax FAQ states a general 8% rate with specified categories at 6% and a separate treatment for credit or charge card services. That summary does not replace the detailed rules. Rental or leasing, construction, logistics, food and beverage, telecommunications, parking and other categories may require more specific analysis under current orders, policies and guides.

Sales tax treatment also depends on the classification of goods and the current rates and exemption orders. Do not rely on a short website list or an old spreadsheet as the sole classification authority. Review the latest sales tax and service tax orders, the relevant industry guide and professional advice for the organisation's facts.

Do not apply one threshold to every business

Registration thresholds and calculation methods can vary by taxable service or activity. MySST describes historical and future methods for determining threshold value, while category-specific thresholds appear in the regulations and guidance. A system should therefore store the organisation's approved registration and monitoring rules rather than assuming one RM500,000 or RM1.5 million threshold applies universally.

Threshold monitoring is a useful management alert, not a legal conclusion. The workflow should show the transactions included, the measurement period, exclusions, adjustments and the person responsible for reviewing the result.

Business Central readiness checklist

Before configuring tax codes, review the source data and operating processes that determine SST treatment.

• Entity and registration data: registration numbers, effective dates, taxable periods, branches and approved accounting basis.
• Customer and supplier data: location, registration status, exemption documentation and related-party information where relevant.
• Item and service data: classification, description, tax group, effective date and supporting RMCD reference.
• Transaction data: supply date, invoice date, payment date, location, currency, discount, credit or debit adjustment and exemption evidence.
• Approval ownership: who approves classifications, rates, exemptions, changes and return adjustments.
• Reporting requirements: reconciliation fields, SST-02 preparation data, payment tracking and record-retention evidence.

Resolve recurring master-data weaknesses before automating. A tax engine that receives incomplete or misclassified data can apply the wrong rule consistently and at scale.

Design a controlled SST workflow

1. Approved tax-rule mapping

Map each relevant transaction type to the organisation's approved tax code, rate, exemption or out-of-scope treatment. Record the source, effective date, reviewer and evidence for each mapping. Separate configuration by legal entity where registrations or activities differ.

2. Effective-date control

Rates and treatments can change. Configuration should respect effective dates and prevent users from applying a future or expired rule to the wrong transaction period. Changes should be tested against open orders, recurring invoices, credit notes and transactions that span a transition date.

3. Exception review

Create review queues for missing classification, unusual tax combinations, expired exemption evidence, manual overrides and transactions that exceed a monitoring threshold. Exceptions should identify the responsible user and retain the resolution.

4. Reconciliation and return preparation

Finance teams should reconcile taxable sales or services, tax amounts, adjustments and payments to the general ledger and the data used for SST-02 preparation. MySST's service-tax FAQ states that registered persons generally submit SST-02 for each taxable period and retain proper records for seven years. Confirm the current requirements and the organisation's approved taxable period.

Implementation approach

A practical implementation is usually organised into discovery, configuration, testing and controlled go-live. The duration depends on data quality, transaction variety, entity count, customisations and the availability of tax decisions.

Discovery and tax decision register

Identify the entities, registrations, products, services, locations, exemptions, transaction types and reporting obligations in scope. Record unresolved tax questions separately from system requirements. SCSB can facilitate the workflow design, while the organisation and its tax adviser remain responsible for approving tax treatment.

Configuration and migration

Configure tax business groups, product groups, posting combinations, effective dates and exception rules. Clean or enrich master data before migration. Document any extensions needed where standard Business Central fields cannot represent the approved treatment.

Scenario testing

Test representative and adverse cases: standard and reduced rates, exemptions, mixed supplies, imports or exports where relevant, foreign currency, deposits, partial payments, credit notes, cancellations, transition dates, manual overrides and missing data. Compare expected outcomes to both the posted accounting entries and the reporting extract.

Go-live and monitoring

Limit configuration access, provide user guidance and monitor the first taxable periods closely. Track unresolved exceptions, manual adjustments and reconciliation differences. A successful posting is not enough; the organisation must also be able to explain the treatment and retrieve the supporting evidence.

Governance and audit support

• Maintain a version-controlled tax decision register with source references and effective dates.
• Restrict tax-code and mapping changes to authorised users.
• Record who reviewed classifications, exemptions and overrides.
• Reconcile tax reports to the general ledger before return preparation.
• Retain relevant invoices, adjustments, calculations and approval evidence.
• Review MySST updates and assess whether configuration changes are required.

Dashboards can highlight thresholds, exceptions and deadlines, but a dashboard does not prove the underlying treatment is correct. Management review and documented tax decisions remain essential.

How SCSB supports SST workflow implementation

SCSB can assist with Business Central discovery, data mapping, configuration, testing, user training, reporting design and post-go-live support. The engagement scope should name the entities, activities, transaction types, reports, integrations and responsibilities included.

SCSB does not replace RMCD guidance or professional tax advice. Before production use, the organisation should approve the tax decision register and confirm that configuration reflects its current registrations, activities and obligations.

Questions to resolve during discovery

• Which entities and registrations are in scope?
• Which goods, services and transaction locations occur in practice?
• Which current orders, policies and guides support each treatment?
• Which exemptions require documents or periodic renewal?
• How are credit notes, bad debts, deposits and transition dates handled?
• Who owns classification, return preparation and regulatory monitoring?
• What reconciliations and evidence are required before SST-02 submission?

Official references and review date

Review the MySST portal, the current service-tax policy list, the orders list and the relevant industry guides before making tax or configuration decisions.

Last reviewed: July 2026. SST rules and RMCD publications can change. Confirm the current position for the organisation's facts before production use or return submission.

Discuss your Business Central SST requirements

Request a consultation with SCSB to review your Business Central environment, SST processes and reporting needs. The first step is to define the approved tax decisions and evidence that the system must support.

‍