From CJ5 to Schedule C — same exemption, familiar search term
Malaysian manufacturers searching for help with sales tax exemption on raw materials often still use the term "CJ5" — the old quarterly declaration used under the pre-2018 sales tax regime. The Sales Tax Act 2018 replaced that mechanism with Schedule C of the Sales Tax (Persons Exempted From Payment of Tax) Order 2018, and the exemption itself now runs through the MySST portal rather than a paper form. The underlying idea has not changed: a registered manufacturer may acquire raw materials, components and packaging materials — RMCD's own published guide excludes petroleum from this specific item — without paying sales tax, provided the goods are sourced from a registered manufacturer, a licensed warehouse or a licensed manufacturing warehouse, and used solely to manufacture taxable finished goods. These are general statements of the mechanism, not a determination of any organisation's eligibility; check RMCD's current guidance directly, and obtain tax advice where the position is unclear.
Schedule C also extends further exemptions — for petroleum-product manufacturers, for purchases made on a registered manufacturer's behalf, and for goods returned by a subcontractor after further processing — but the raw-material purchase exemption is the one that drives day-to-day purchase-order volume, and the one this article focuses on.
The practical question this raises for a Dynamics 365 Business Central configuration is not whether the exemption applies — that is RMCD's determination — but what the purchasing workflow has to track once it does.
An exemption granted by quantity, not by category
RMCD's guide describes the exemption as being granted against a stated quantity of goods, set according to the applicant's own declared requirement when the certificate is applied for — not a blanket approval to purchase an unlimited amount of a category of material tax-free. A registered manufacturer's certificate for this exemption item carries no expiry date and does not need to be renewed, which removes one obvious trigger — a renewal date — that might otherwise have forced a periodic review of whether purchases were still within the approved amount.
That absence of a renewal cycle makes the underlying condition more important, not less: RMCD's guide states that sales tax becomes payable on any exempted goods that cannot be accounted for. The exemption is not a permanent write-off of tax on a category of purchase; it is a conditional relief that depends on the manufacturer being able to show, at any point, that the exempted goods were actually used for the approved manufacturing purpose — and an inability to account for them converts the relief back into a tax liability.
Purchased is not the same as accounted for
A quantity that has been purchased tax-exempt under the certificate is not automatically a quantity that has been accounted for. Raw material can be purchased, held in stock, consumed in production, scrapped, or transferred to a subcontractor for further processing — and RMCD's condition attaches to being able to show what actually happened to it, not merely to having a purchase record that matches the certificate. A workflow that tracks purchase quantity against the certificate but stops there has covered only half the condition.
RMCD's own guide requires registered manufacturers to keep records of local purchases and usage for inspection, even though the record itself does not need to be submitted unless requested. That is a standing obligation to be able to reconstruct the position on demand, not a one-off filing — and it sits on top of, not instead of, the day-to-day purchasing control a manufacturer needs simply to avoid exceeding the approved quantity in the first place.
What Business Central's native purchase controls offer, and where the gap sits
Business Central has genuine, native functionality for tracking a quantity against an agreement over time. Microsoft's documentation on working with blanket sales and purchase orders describes a Blanket Purchase Order that records a total agreed quantity for a vendor and item, and reduces the outstanding quantity automatically as individual purchase orders are created and received against it — so at any point, the blanket order shows how much of the agreed total has been drawn down and how much remains.
The structural gap is that a Blanket Purchase Order tracks a quantity against one agreement with one vendor. RMCD's Schedule C certificate approves a quantity of an item, which a manufacturer may draw down through purchases from any registered-manufacturer vendor, or through import, not from a single counterparty. Business Central has no native feature that aggregates purchases of the same exempted raw material across every vendor and import transaction against one external, item-level regulatory limit — that aggregation is a design decision SCSB and its clients make deliberately, not a setting Business Central switches on.
What Business Central does offer natively is the posting-group mechanism already used to calculate tax by combination of vendor and item: a dedicated VAT Product Posting Group for items purchased under the exemption, combined in the VAT Posting Setup with the appropriate vendor classification to calculate no sales tax for that combination. Microsoft's documentation on setting up value-added tax also describes VAT Clauses, assignable by document type through the VAT Clauses by Document Type page, which can print the exemption reference on the relevant purchase document rather than leaving the reason for a zero-tax purchase undocumented on the face of the record.
The control that actually matters: reconciling approved against consumed
None of the native features above, on their own, tell a manufacturer how close a purchase is bringing them to the approved quantity on the certificate. That has to be a standing extraction, built deliberately: a running total of purchases of each exempted item, across every vendor and import declaration flagged with the relevant posting group, compared against the quantity approved on the certificate for that item — not against a single vendor's blanket order, and not just at year-end when a return happens to be prepared.
The reconciliation matters in both directions. If cumulative purchases are approaching the approved quantity, someone needs to know before the next purchase order is raised, so the choice — request additional approved quantity, or accept that the next unit will not qualify for exemption — is made deliberately rather than discovered after the fact. If the certificate quantity was set generously and purchases have been running comfortably below it, that gap is exactly the kind of detail RMCD's own guide expects a manufacturer to be able to explain if asked, alongside where the exempted material actually went.
Decisions to settle before configuration starts
- Which items are flagged against the Schedule C certificate — through a dedicated VAT Product Posting Group or item category — and who owns keeping new raw-material records correctly flagged as they are created.
- Where the approved quantity for each certified item is recorded as a reference point, since Business Central holds no native field for an external regulatory quantity limit.
- How cumulative purchases of a flagged item are totalled across every vendor and import transaction, not just tracked within a single Blanket Purchase Order.
- Who monitors the gap between approved and consumed quantity closely enough to request additional approved quantity, or stop buying exempt, before the certificate limit is reached.
- What record supports the local purchase and usage detail RMCD expects a manufacturer to produce on request, and who reconciles it before an inspection asks for it.
When this can be tracked directly, and when it usually can't
A manufacturer with a short list of exempted raw materials, a single approved certificate and one or two supplying vendors may track the running total directly against RMCD's own record, using a straightforward spreadsheet alongside the purchase ledger. The case for configuring this reconciliation inside Business Central grows with a wider range of exempted materials, several vendors supplying the same exempted item, high purchase volumes, or a certificate history that has never actually been reconciled against what was purchased.
What to do next
Confirm the current exemption status, approved quantity and conditions attached to the certificate directly against RMCD's current MySST guidance before relying on this article for anything beyond the mechanics of workflow design. Where the requirement is to configure this purchase-tracking and reconciliation workflow inside Dynamics 365 Business Central, the SAC SST App can be discussed within an agreed implementation scope.
General-information limitation
This article is general technical information about Schedule C sales tax exemption tracking concepts in Dynamics 365 Business Central. It is not tax, legal or accounting advice, does not determine any organisation's exemption eligibility, approved quantity or tax treatment, and does not confirm that a particular configuration satisfies RMCD's current requirements. RMCD's guidance and Business Central's own functionality are set by their respective publishers and change over time. Confirm the current position against RMCD's published material before implementation.
Dynamics 365 Business Central and Microsoft are trademarks of the Microsoft group of companies.