The Malaysian Inland Revenue Board issued the e-Invoice Guideline Year 2023 on 21 July 2023, which provides further clarification in terms of the scope, coverage, and data fields required, amongst others. PWC has used the analogy of choosing a car to outline the key steps business owners need to take for a ‘fast and furious’ implementation of e-Invoicing.
Based on the IRB’s latest e-Invoicing implementation timeline, e-Invoice compliance will be applied to all taxpayers, including individuals and legal entities. To ensure a smooth transition and provide taxpayers with sufficient time to adopt e-Invoicing, the implementation will be mandatory based on annual turnover or revenue (either based on the numbers reported in audited financial statements for financial year 2022 or tax returns for year of assessment 2022). For more information, please refer to our latest TaXavvy Issue 15/2023.
Test drive – Your e-Invoicing checklist
The introduction of the e-Invoicing framework triggers these key changes in the Accounts Receivable and Accounts Payable functions:
e-Invoicing – Invoice needs to be validated by MyInvois portal
Buyers who receive foreign invoices will be required to self-e-Invoice
This is also an opportunity for you to further optimise both functions in its entirety through process and technology intervention.
Which are the best cars? Evaluating your options for data integration in your e-Invoice flow
Based on IRB’s guideline, there are two mechanisms to transmit e-Invoices to IRB’s database, which are as follows:
- MyInvois Portal (a free solution/portal hosted by IRB)
- Application Programming Interface (API)
While we await the release of IRB’s Software Development Kit (SDK), which will be available in the fourth quarter of 2023, there are two integration options for API that you may be considering.
Option 1 (the Formula 1 car): Direct integration (via API)
From our experience with other countries, we understand that there are e-Invoice solutions available for some of the more established Enterprise Resource Planning or billing systems (e.g. SAP, Oracle, etc.). Many multinational companies (MNCs) embarking on digital transformation with SAP S/4HANA have taken a global approach for e-reporting and e-Invoicing.
One of the benefits of direct integration is that e-Invoices are generated in real time in the ERP system and sent directly to the IRB database without human intervention. The e-Invoice is also immediately available for further processing (e.g validation and approval).
However, as e-Invoice requirements are likely to continue evolving, your in-house IT team would have to update the ERP/billing system frequently. It may be costly and require more resources e.g. setting up and reconfiguring the ERP systems
due to regulatory updates which is anticipated to incur multiple one-time development costs, and maintaining a stable connection as a recurring expense. As some ERP systems’ infrastructure are set up to meet global requirements, getting the systems to reflect local requirements may present further challenges for the adoption timelines for Malaysian organisations when it comes to e-Invoicing.
Option 2 (the sports car): Integration through middleware
Middleware is a commonly used software, where the primary purpose of the solution is to facilitate the exchange of invoices between the supplier’s accounts receivable and buyer’s accounts payable. The supplier does not own the platform, nor does the buyer.
One of the benefits of this option is that there will likely be limited changes that you’ll need to make on the ERP/billing system. The middleware will be updated
on a regular basis to meet compliance requirements. As long as mandatory data is available, middleware will be able to consolidate the information in line with the e-Invoice requirements. It provides various convenient and interactive modes, including desktop application and cloud-based application, some even offering further customisation for your own use.
Some middleware have comprehensive offerings for end-to-end e-Invoicing compliance, and some may have e-reporting capabilities. Previously, we shared that there are requirements for suppliers to print a QR code on the invoice provided to the buyers, and some middleware would be able to support this requirement.
Switching gears: what’s next
Many taxpayers, especially businesses with complex billing processes, have found the implementation timing proposed by IRB challenging. Based on our experience in other territories, we believe that steps taken correctly from the start can set you up for a swift and smooth implementation experience. Regardless of which option you take for API integration, here are some non-technology considerations to take into account:
Do you have a diverse project team who has relevant experience, e.g. IT, tax, finance, project management, etc. to drive change in the organisation to ensure a seamless e-Invoice roll-out?
Are you aware of the full aspects of your current AR billing processes? Would the timing of issuance of e-Invoice be a challenge in terms of submission of e-Invoice data to IRB?
Do you issue invoices to foreign customers? What is your game plan for self e-Invoice for foreign transactions? How does your system account for these transactions?
How are you going to collate the mandatory e-Invoice data fields, e.g. tax identification number (TIN) of your buyers which we understand most companies may not have in the system?
How can you upskill your AR and AP teams to understand their roles and take on the additional responsibilities to comply with e-Invoice requirements?
Commentary from Jeannie Shee Managing Consultant for Tax at PWC
