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
14,295

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 

21 Comments
Bernhard
Product and Topic Expert
Product and Topic Expert

Great stuff, so helpful!!

kevin_qiu
Explorer
0 Kudos

Thank you, Alice, this is very helpful for configuring DRCCE.

But is there any document on the corresponding SOA manager configuration in SAP for Malaysia? I've been searching for a couple of days but no luck so far. The help portal only has per process configuration for Poland, Romania, Serbia and Slovakia.

https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/integrat...

MRA
Explorer

Hello Alice,

Thank you - your blog is helpful. But on our DRCCE instance we not found the communication type for Malaysia (E-Invoices (MY)). If this is the case then you need to go back and check the title "Activate Processes" under Configuration. In our case the available process for E-Invoices (MY) was "Inactive":

MRA_0-1729671326969.png

After we activate the process we can proceed with the configuration part.

Kind regards,

Mike

BhavinS
Discoverer
0 Kudos

Thank you, Alice.  The article mentions that we need to purchase a digital certificate from a CA authority in Malaysia and refers us here: How to acquire Digital Signature?.

Will the digital certificate from other, global issuer, e.g. DigiCert, not work? 

AliceKang
Product and Topic Expert
Product and Topic Expert

@MRA Thanks a lot for your feedback and sorry for my late response. I've added a note about this prerequisite into the blog.

AliceKang
Product and Topic Expert
Product and Topic Expert

@kevin_qiu Sorry for my late response. SOA manager configuration isn't required for the tax authority clearance process. I saw that Pritish had already shared the documentation link for the other settings in the cloud edition.

ChloeXu
Associate
Associate

@BhavinS  In the answer of How to acquire Digital Signature? There's a list of certification authorities, only the authority listed can work.

kevin_qiu
Explorer
0 Kudos

Hi, All,

I have followed the instructions in this link Establishing Connection from Cloud Edition to Business System (Electronic Documents Only) | SAP Help... to establish the connection from DRCCE back to SAP Business system, which is required for Malaysia. We followed all the steps and created the destination in the sub-account and verified it could connect to our SAP Business sytem, then went to "Manage Destination Mapping", the "Create" button is still greyed out as if the destination is not there. Is anybody else facing this issue?

update 11/25: in case anybody is interested, the issue is resolved. In the "Additional Properties" of the destination, only "sap-client" is on the drop-down list. It turns out that you have to add another one by just typing in "drccSystemType" and give it value "Other". I couldn't find it in the drop-down list, so I thought that was some kind of explanation of the "sap-client" = client_id, instead of another property by itself.

Thanks!
Kevin

gerhardhoebinger
Explorer
0 Kudos

Hi Alice,

thank you for this helpful blog! When registering on the MyInvois Portal you get the client-ID, client secret 1 and client secret 2 --> which secret do we need to enter in the BTP app "Manage communication settings"?

Thanks!

Best regards,
Gerhard

kevin_qiu
Explorer

Hi, @gerhardhoebinger looks like either one works. We are using secret 1, but I just tried secret 2 using POSTMAN and I could get an access token too.

AliceKang
Product and Topic Expert
Product and Topic Expert
0 Kudos

@gerhardhoebinger@kevin_qiu: I've consulted the expert about Gerhard's question. See her answer below:

Either secret 1 or 2 should work. Just pick one to maintain on BTP.

The reason MY government gave more than one secret was to provide a backup mechanism when call rate of API exceeds limit.

 

Kedar_Pagire
Discoverer

Hello team,

With reference to the question in the below link we have a question on the setup of the communication to the DRC to Public cloud and also the IRBM 

SAP Document and Reporting Compliance Malaysia Dig... - SAP Community

As per the SAP recommendation we have generated the self signed certificate as per the reply which we got in the above community question which we posted.

Step 1 & Step 2 is already created and for the step 3 we have create a self signed certificate as our certificate purchase from the vendor is in progress so as per SAP recommendation we  created a self signed certificate but now we are getting error as below @AliceKang @ChloeXu 

did you encounter any such issue in your implementation @kevin_qiu @gerhardhoebinger @BhavinS 

" HTTP Client is not connected"

gerhardhoebinger
Explorer
0 Kudos

@Kedar_Pagire we didn't have such an issue - after we got the certificate from one of the certified vendors we have uploaded the credentials in BTP platform and it was working.

NajAminuddin
Explorer
0 Kudos

Hi @gerhardhoebinger, the certificate from certified vendors, did it include Digital Signature capabilities? and were you connecting to IRBM Malaysia XML version 1.1 or 1.0? Coz our understanding is that version 1.0 does not include Digital Signature capabilities, hence would not require certificate configuration. Version 1.1 is the IRBM version that includes Digital Signature capabilities that would require Digital Signature Certificate from certified vendors.

gerhardhoebinger
Explorer
0 Kudos

@NajAminuddin unfortunately I don't know the details if it is version 1 or 1.1 --> we are running the latest available solution provided by SAP and BTP DRC cloud to connect to the government.

our business obtained the soft certificate from one of the listed providers: https://www.mcmc.gov.my/en/sectors/digital-signature/list-of-licensees and we have uploaded it according to the steps provided in this blog - no issues encountered.

below also the process flow:

gerhardhoebinger_0-1757483026622.png

 

a validated document contains also the XML segment UBLDocumentSignatures (see below example)

gerhardhoebinger_1-1757483136092.png

 

NajAminuddin
Explorer
0 Kudos

Hi @gerhardhoebinger, thanks heaps for your response. really helpful. Please note that you are able to confirm on the version by scrolling up to the top of your XML. It will mention if XML version is 1.0 or 1.1. Mind letting us know?

NajAminuddin
Explorer
0 Kudos

Hi @gerhardhoebinger, did you manage to scroll up to the top of your XML to confirm if it is version 1.0 or 1.1?

gerhardhoebinger
Explorer
0 Kudos

@NajAminuddin this is the information in the XML - there is 1 segment called "InvoiceTypeCode" indication 1.1 but not in the header segment of the XML --> we are using version 1.1

according to the SAP-Note 3487313 - Electronic Document Processing Malaysia Troubleshooting Guide the above mentioned segment is the indicator for LHDN 

gerhardhoebinger_0-1758105425326.png

 

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">

...

<cbc:InvoiceTypeCode listVersionID="1.1">01</cbc:InvoiceTypeCode>

...

 

NajAminuddin
Explorer
0 Kudos

Hi @gerhardhoebinger, thank you very much for your swift response and confirmation. May I know if this DRC MY implementation was on Private or Public Cloud? To clarify why I've asked, we're currently facing issue with DRC MY implementation on Public Cloud, whereby DRC is defaulted to connect to version 1.0 against the client requirement of 1.1 - due to Public Cloud latest release design. Just need to understand if you are on the Public Cloud as well and is able to connect to v1.1.

gerhardhoebinger
Explorer
0 Kudos

@NajAminuddin we are using S/4HANA onPrem + BTP DRC public Cloud subscription