Three obligations, one payment
When a Malaysian company pays commission to an agent, dealer or distributor, one purchase transaction can trigger three separate compliance obligations at once: a self-billed e-Invoice submitted to MyInvois, a CP58 statement issued to the agent under the Income Tax Act 1967, and a 2% withholding tax deducted under section 107D of the same Act. Each obligation has a different owner, a different deadline and a different piece of evidence it needs to produce, and all three arise from the same underlying payment. This article maps that intersection onto SCSB's implementation approach for configuring Dynamics 365 Business Central to handle it as one workflow rather than three disconnected tasks.
What Business Central's new self-billing feature actually does
Business Central 2026 release wave 1 introduced native support for self-billed invoices, generally available from 5 June 2026. A Boolean field on the Vendor Card enables a self-billing agreement for a given vendor; once set, purchase invoices created for that vendor, whether from a purchase order or directly, are automatically marked as self-billed and can be assigned a dedicated number series. A new report layout, formatted to align with the sales invoice style, presents the buyer's company information, the vendor's details and the VAT data the document needs. Vendors with a self-billing agreement can no longer receive inbound e-documents for accounts payable, which prevents a buyer-issued self-billed record and a supplier-issued document arriving for the same transaction.
Microsoft's own release documentation names one country-specific behaviour for this feature: for Danish localisations, posting a self-billed invoice can automatically generate a Digital Voucher to satisfy local audit rules. Malaysia is not mentioned. The feature is a generic purchase-process mechanism, a vendor flag, a numbering rule and a report layout, with no awareness of MyInvois, HASiL's classification codes, or the CP58 and section 107D obligations that a Malaysian agent, dealer or distributor payment actually carries. Mapping those requirements onto the feature is SCSB's configuration work, not a capability Business Central ships out of the box.
Obligation one: the self-billed e-Invoice
HASiL's e-Invoice Specific Guideline requires certain payments to agents, dealers or distributors to be issued as self-billed e-Invoices: classification code 037 for a monetary payment, and code 045 where the incentive is non-monetary, such as an incentive trip rather than cash. The guideline allows the self-billing arrangement to run on either an accrual or a paid basis, provided the organisation applies its chosen basis consistently and it matches the statements it gives the agent, and it permits the submission to be prepared on a net commission basis where reversals are shown as separate lines. Withholding tax is a separate calculation and is not itself entered into the e-Invoice submission.
Inside Business Central, the self-billing Boolean only identifies which vendors are self-billed. It says nothing about which classification code applies, whether a payment is monetary or non-monetary, or which basis, accrual or paid, the organisation has committed to. That mapping has to be built as a deliberate configuration decision against each vendor's actual commission arrangement, tested against the same evidentiary basis the organisation reports to the agent.
Obligation two: CP58, a different document for a different purpose
Separately from the e-Invoice, section 83A(1) of the Income Tax Act 1967 requires a company to prepare a CP58 statement, the Statement of Monetary and Non-Monetary Incentive Payment to an Agent, Dealer or Distributor, for each agent to whom it pays more than RM5,000 in monetary or non-monetary incentives within a calendar year, and to provide it to that agent by 31 March of the following year. CP58 is not routinely filed with HASiL; the company retains it and produces it on request.
CP58 and the self-billed e-Invoice answer different questions on different clocks. The e-Invoice is a transaction-level document validated by MyInvois close to the point of payment. CP58 is an annual statement, aggregating a full calendar year's payments to one agent, delivered directly to that agent rather than submitted to a portal. A Business Central configuration that only tracks the e-Invoice side has not covered the CP58 obligation, and the two should be reconciled against the same underlying payment population rather than built from separate, unrelated reports.
Obligation three: 2% withholding under section 107D
Section 107D requires a company paying monetary commission to a Malaysian tax-resident individual agent, dealer or distributor to deduct 2% withholding tax from the gross payment, where that recipient received more than RM100,000 in total payments, monetary and non-monetary, from the company in the immediately preceding year of assessment. The company deducts the tax when it pays or credits the amount and, under HASiL's current administrative practice, remits the accumulated deduction by the last day of the month following the month of payment, reported through Form CP107D, with the appendix Lampiran CP107D(1) where several agents are involved.
Business Central 2026 release wave 1 also introduced a generic, global Withholding Tax framework in the same release as self-billing, configured through Withholding Tax Revenue Types, Withholding Tax Business and Product Posting Groups, and a Withholding Tax % rate applied at invoice posting, payment posting, or the earlier of the two. Nothing in Microsoft's documentation for this framework mentions Malaysia, and, as with the self-billing feature, its published country-specific configuration guides currently cover other markets. The framework gives a company a native place to hold a 2% rate and a realisation point; it does not know that section 107D's threshold is a test of the agent's cumulative receipts across the preceding year of assessment, not a per-invoice minimum. Business Central's native minimum-invoice-amount field for withholding tax tests each transaction against a fixed value, a mechanism built for a per-invoice threshold, not an annual, vendor-level one. Applying section 107D correctly means classifying each agent, dealer or distributor vendor against the RM100,000 test as a standing, annually reviewed decision, and only then assigning that vendor to the withholding tax posting group carrying the 2% rate, rather than expecting the invoice-level minimum-amount field to perform a test it was never built to perform.
Configuring one transaction to carry all three
A commission payment that triggers all three obligations needs, at minimum: a vendor record correctly classified as an agent, dealer or distributor and tested against the RM100,000 preceding-year threshold; the self-billing agreement enabled with the appropriate classification code and monetary or non-monetary basis recorded; the withholding tax posting group and 2% rate applied to that vendor, realised at the point that matches when section 107D treats the payment as made; and a running total of payments to that agent for the calendar year, so the RM5,000 CP58 threshold can be evaluated without a manual year-end reconstruction. None of these elements is automatic once the self-billing Boolean is switched on; each is a separate configuration decision that has to be made deliberately and tested against the agent's actual payment pattern.
Reconciliation: what should tie back to what
A workflow built around these three obligations is only as reliable as the reconciliation behind it. At minimum, the population of self-billed e-Invoices submitted to MyInvois for a period should tie back to the posted purchase invoices flagged as self-billed in Business Central; the CP58 statements issued for the year should tie back to the same population, aggregated by agent; and the withholding tax remitted through CP107D should reconcile against the withholding tax entries Business Central posted for the period. A variance in any one of the three is evidence that a vendor was misclassified, a threshold test was missed, or a payment was recorded on the wrong basis, not a rounding error to write off.
Decisions to settle before configuration starts
- Whether each agent, dealer or distributor vendor has crossed the RM100,000 preceding-year threshold, and who reviews that classification annually.
- Which self-billed e-Invoice classification code applies to each payment type, and whether the arrangement runs on an accrual or paid basis.
- Where the 2% withholding tax rate and its realisation point are configured, and how remittance by month end is tracked against actual payment dates.
- How cumulative payments to each agent are tracked against the RM5,000 CP58 threshold across the calendar year.
- What reconciliation ties the self-billed e-Invoice population, the CP58 statements and the withholding tax remittance back to the same underlying payments.
A business paying a small number of agents modest, predictable commissions, with no vendor currently near the RM100,000 or RM5,000 thresholds, may be able to configure this directly from HASiL's guideline and Business Central's standard vendor and purchasing setup. The case for outside implementation support grows where agent numbers are large, where commission arrangements vary between net and gross bases, where several vendors are approaching the withholding tax threshold for the first time, or where the three obligations have so far been tracked in separate spreadsheets that were never reconciled against each other.
What to do next
Confirm the current classification code, threshold and remittance position directly against HASiL's e-Invoice guidelines and the Income Tax Act 1967 before configuring anything; those determinations sit with HASiL and the Inland Revenue Board of Malaysia, not with this article or with Business Central. Where the organisation has confirmed it needs self-billed e-Invoice submission configured inside Dynamics 365 Business Central, the SAC E-Invoice App can be discussed within an agreed implementation scope.
General-information limitation
This article is general technical information about configuring self-billing, e-Invoice and withholding tax mechanisms in Dynamics 365 Business Central. It is not tax, legal or accounting advice, does not determine any organisation's obligations under section 83A, section 107D or the e-Invoice guideline, and does not confirm that a particular configuration meets HASiL's current requirements. HASiL's guidelines and thresholds, 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 HASiL'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.