A different vendor population, and a different set of rules
Withholding tax on payments to a non-resident vendor is often discussed as though it were one obligation. It is not. The Income Tax Act 1967 splits it by the character of the payment and by who is receiving it, and the split determines the rate, the form and the remittance route. It is worth separating this population clearly from the domestic one: section 107D applies to qualifying payments to resident individual agents, dealers or distributors under separate conditions and reporting requirements. A vendor configuration built for one will not correctly handle the other, and an organisation that pays both will need both.
This article is about the non-resident side, and about the specific configuration decision it creates in Dynamics 365 Business Central: how vendors are classified before any posting group is applied, and how deferment-eligible payments are identified inside an otherwise ordinary payment run.
Check the payment type, rate and form
The Inland Revenue Board of Malaysia publishes the position directly on its withholding tax page, as a table of payment types against the relevant section, rate and form. Contract payments to a non-resident under section 107A carry rates of 10% and 3% and are reported on Form CP37A. Interest payments to non-resident persons under section 109 carry 15%, and royalty payments to non-resident persons under the same section carry 10%; both use Form CP37. Payments of special classes of income to a non-resident under section 109B carry 10% and use Form CP37D. Income under paragraph 4(f) falls under section 109F and uses Form CP37F. These are the domestic rates published by the Board; where a double taxation agreement applies, a different rate may be prescribed, which is a determination about the particular payee and payment rather than a system setting. Confirm the current position directly with the Board.
The 10% and 3% on a section 107A contract payment deserve a moment on their own, because they are the clearest example of why a single rate field is not enough. They are two amounts collected on account of two different taxpayers: the non-resident contractor, and that contractor's employees. One payment line produces two remittance components, and a configuration that stores a single combined percentage has lost the distinction that the form itself requires.
The decision that happens before any posting group
Confirm the payment classification with the responsible tax decision-maker before configuring the workflow, taking professional advice where needed. Is the payee non-resident for the relevant basis period? Is the payment a royalty, interest, a contract payment for services performed in Malaysia, or a special class of income? Is there a treaty position, and is the evidence supporting it held? Those are determinations about facts and law. The approved workflow should make the decision explicit, link the evidence to the vendor and payment, and route an unclassified payment for review. Whether that review is enforced by a configured approval, an extension or a manual payment control must be agreed and tested.
One practical risk is that an overseas vendor is created like any other, no withholding classification is attached, and a payment requiring review passes through the ordinary payment run. A reconciliation that only totals what was already flagged cannot, by definition, find what was never flagged.
Keep a concise decision record
Before configuration, the organisation and its tax adviser should approve a record for each relevant payee and payment category. Keep the evidence reference alongside the conclusion so that the implementation team receives an approved input rather than an unresolved tax question.
- Treatment: the reviewed residence and payment classification, applicable section, rate, form and any treaty evidence.
- Timing: the legal paid-or-credited date, remittance deadline and the reason for any approved small-value deferment.
- Control: the Business Central mapping or manual schedule, separate remittance components where required, and the reconciliation owner.
- Approval: who reviewed the decision, when it takes effect and what change requires a fresh review.
What Business Central's withholding tax framework provides
Microsoft documents a withholding tax capability in the base application. Its own setup guidance opens by stating that companies in some countries or regions must pay withholding tax to the government for certain services or vendor purchases, and describes a general mechanism: an Enable Withholding Tax toggle on the General Ledger Setup page, Withholding Tax Revenue Types used to categorise entries and support withholding tax certificates, Withholding Tax Business and Product Posting Groups assigned to vendors, items and general ledger accounts, and a Withholding Tax Posting Setup combining the two to carry the Withholding Tax %, the accounts and the sequence.
Nothing in that documentation refers to Malaysia, to any section of the Income Tax Act 1967, or to any CP37-series form, and Microsoft's local functionality documentation lists the countries for which Microsoft publishes local compliance functionality, with Malaysia not among them. The framework provides somewhere to hold a rate and a realisation point. Mapping Malaysian rules onto it is configuration work done by the implementer, and should never be described as Microsoft supporting Malaysian withholding tax.
Realized Withholding Type determines whether the system recognises withholding at invoice posting, payment posting or the earlier event. The legal paid-or-credited date must be identified separately: it is not necessarily identical to a posting date. Test that the approved design records the legal trigger and remits on time rather than assuming a field option settles the tax question.
Where the threshold field does not do what it looks like it does
The Board's current withholding tax guidance describes a small-value payment deferment for sections 109 and 109B. The withholding tax must not exceed RM500 for one payment transaction, and small-value payment transactions must occur more than once in the relevant six-month period. Its deadlines are 30 June for transactions from 1 December of the preceding year to 31 May, and 31 December for transactions from 1 June to 30 November. CP37S and CP37DS are the corresponding small-value forms. Outside an applicable concession, the general remittance deadline is one month after payment or credit. Have the responsible tax adviser confirm eligibility and the current remittance procedure before a payment is assigned to a deferred batch.
Microsoft’s current withholding-tax setup guidance, updated on 1 October 2026, describes Withholding Threshold Type and Withholding Threshold Amount. It also describes period-based threshold options specifically for employee transactions. These are not evidence that the vendor setup automatically implements Malaysia’s RM500 tax-amount deferment concession. Confirm the installed version and test the tax amount, eligibility classification and remittance schedule separately; do not treat a calculation threshold as a filing deferment.
The repeated-payment condition requires a view of the relevant period, not just the value of the invoice being posted. Keep the supporting payment schedule and the reviewed eligibility decision together, and reassess the treatment if the expected transaction pattern changes.
What the deferment does not cover
The Board's current small-value guidance names sections 109 and 109B. It does not extend that concession to section 107A contract payments or their 3% component. An organisation paying an overseas contractor for work performed in Malaysia remains on the ordinary remittance cycle for those amounts even if every individual deduction is small. A configuration that applies one deferred batch to every non-resident vendor has quietly extended a concession beyond its terms.
Reconciling what was withheld against what was remitted
The control design should cover three reconciliations. Reconcile withholding tax postings, opening and closing liabilities, and remittances on the relevant forms. Explain timing differences, including amounts not yet due for remittance. Deferred amounts should sit visibly as an accumulating balance across the six-month window, rather than disappearing between periods and reappearing at the deadline. And payments flagged by indicators such as an overseas address or foreign currency should be checked for a recorded tax review, alongside any other indicators approved by the tax adviser. Those indicators help find omissions; they do not determine residence or liability.
Decisions to settle before configuration starts
- How each vendor's residence status and payment character are established, recorded on the vendor record, and reviewed when either changes.
- Whether any treaty position applies to a given payee, what evidence supports it, and who confirms it before a reduced rate is used.
- How the two components of a section 107A contract payment are held separately rather than as one combined percentage.
- Which vendors meet both deferment conditions, how that assessment is recorded, and how the resulting batch is assembled and released within the correct six-month window.
- What standing reconciliation ties posted withholding tax entries, deferred balances and remitted forms back to the same payments.
When this can be managed without outside help
An organisation with two or three recurring overseas subscriptions and a stable, short list of non-resident payees may reasonably track this on a schedule maintained alongside the payment run, working directly from the Board's published table, without configuring the withholding framework at all. A manual schedule may be proportionate where the population is small, responsibilities are clear and deadlines and completeness are reliably checked. The case for configuring it inside Business Central grows with the number of non-resident vendors, with a mix of payment characters attracting different sections and rates, with treaty positions in play, and with a payment volume at which a manual review has stopped being a reliable control.
What to do next
Confirm the applicable section, rate, form and remittance position directly against the Inland Revenue Board of Malaysia's current published material before configuring anything; the organisation and its tax adviser must approve the treatment against those requirements before the implementation team configures it. Where the requirement is to build this vendor classification and payment workflow inside Dynamics 365 Business Central, Business Central implementation services can be discussed within an agreed scope.
General-information limitation
This article is general technical information about vendor and withholding tax configuration concepts in Dynamics 365 Business Central. It is not tax, legal or accounting advice, does not determine any organisation's withholding obligations, any payee's residence status, or the availability of any deferment or treaty rate, and does not confirm that a particular configuration satisfies the Inland Revenue Board of Malaysia's current requirements. The Board's guidance and the Income Tax Act 1967, and Business Central's own functionality, are set by their respective publishers and are revised over time. Confirm the current position against the Board's published material and Microsoft's current Business Central documentation before implementation.
Dynamics 365 Business Central and Microsoft are trademarks of the Microsoft group of companies.