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.
How to select the best “car” that is fit for purpose?
Whether you go with a Formula 1 car (direct integration) or sports car (middleware), this depends on your current system setup and operation requirements, as they may be complex and require further considerations. Here is a non-exhaustive list of solution features that you may want to think about: