Financial Management Blog Posts by SAP
cancel
Showing results for 
Search instead for 
Did you mean: 
AliceKang
Product and Topic Expert
Product and Topic Expert
10,789

You are in the process of implementing electronic invoices for Malaysia. One of the key implementation activities is to integrate your business system (for example, SAP S/4HANA Cloud) with SAP Document and Reporting Compliance, cloud edition. The cloud edition acts as a bridge between your business system and the Inland Revenue Board of Malaysia (IRBM), the tax authorities in Malaysia. Among other settings, you must configure communication settings in the Manage Communication Settings - External Parties app in the cloud edition to connect to the IRBM. This blog guides you through configuring these communication settings.

Getting Started

Start your journey by reading the following documentation, which describes how to configure communication settings:

The communication settings primarily involve maintaining the credentials that you've obtained from the IRBM or another authority, including a pair of client ID and client secret as well as a digital certificate. You should get these credentials ready for use before proceeding to configure communication settings in the cloud edition. You can find out the Malaysia-specific settings from the Process-Specific Settings page:

Product Guide: Process Specific SettingsProduct Guide: Process Specific Settings

Step 1: Create Communication Settings

You need to first retrieve your taxpayer identification number (TIN) as described at How to retrieve and verify company TIN number? and then create communication settings using this TIN.

Note: Before performing this step, you must first activate the E-Invoices (MY) process in the Activate Processes app.

Create communication typeCreate communication type


Step 2: Add an Authentication Setting for Consuming the IRBM APIs

For the communication type created in step 1, add an authentication setting that is used to consume the IRBM APIs, as follows:

  1. Select the Basic type.
  2. Enter your client ID as the username and your client secret as the password.
    See How to obtain Client ID and Client Secret?.

Add basic authentication typeAdd basic authentication type

Step 3: Add an Authentication Setting for Signing Electronic Invoices

For the communication type created in step 1, add another authentication setting that is used to sign electronic invoices, as follows:

  1. Select the Key Pair X.509 type.
  2. Upload the certificate you generated from one of the certified service providers.
  3. Enter the password for your digital certificate.
    You need to purchase a digital certificate from a certificate authority (CA) in Malaysia. See How to acquire Digital Signature?.

Note: SAP supports soft certificates only, roaming certificates are not supported. The digital certificate extensions supported are PFX and P12.

Add KeypairAdd Keypair

More Information

Suppose that your company has several company codes representing headquarters and subsidiary units. In this case, you can choose to use only one digital certificate, which is registered with the TIN of headquarters or a leading subsidiary. The TIN associated with the common certificate is referred to as intermediary or intermediary representative. See For companies that have subsidiaries, does digital certificate need to be registered for each subsid....

If you use different SAP systems at the same time, such as SAP ERP and SAP S/4HANA, you can still use the same digital certificate.

Also remember that a digital certificate has an expiration date. You must renew your certificate when it's expiring soon. See Do I need to renew a digital certificate?. Otherwise, you'll encounter the following errors:

  • Certificate is not valid according to the chain of trust validation or has been issued by an untrusted certificate authority.
  • Signing time is not within validity period.

We hope that you find this information useful. Feel free to leave a comment on this blog or follow SAP Document and Reporting Compliance | SAP Community.

SAP Document and Reporting Compliance 

12 Comments