Unanswered

Malaysia e-invoicing with Middleware

(1) Share

Report

Posted on by CU11090252-0

In Microsoft doc, Client ID and Client secret values in the Inland Revenue Board of Malaysia (IRBN) are mandatory for sending invoices to IRBN protal.

However, we would like to send the D365 invoices file to a middleware before sending to IRBN.

Is it possible to set up dummy CLient ID and Client secert and get the XML file befroe submitting to IRBM?

https://learn.microsoft.com/en-us/dynamics365/finance/localizations/malaysia/apac-mys-e-invoices

Categories:

Integrations

All responses (5)

Answers (0)

CU11090252-0 10 on at

Like (0)

Report

Malaysia e-invoicing with Middleware

Thanks Martin,

As we are in testing phase, the environment type is set as Sandbox.

Web service URL and Login service URL are set up as NA and Client ID and Secert are set up as dummy value.

Those are expected to set up as the web service URL and login details of the middle-tier service with your suggestions.

However, we already encountered below error after submitting the electronic document.

We checked the applicability rule setup of the sales invoice but have no idea of how to fix the issue.
Martin Dráb 228,501 Most Valuable Professional on at

Like (0)

Report

Malaysia e-invoicing with Middleware

What problem do you see that would prevent you from doing it? It's difficult to address your concerns without knowing what they're.

As I'm looking into the documentation, the key difference seems to be that you'll set Web service URL and login details to your middle-tier service instead of a MyInvois environment.
CU11090252-0 10 on at

Like (0)

Report

Malaysia e-invoicing with Middleware

I am wondering if it is possible to configure the Malaysia e-invoicing with Middleware in D365?
CU11090252-0 10 on at

Like (0)

Report

Malaysia e-invoicing with Middleware

Thanks Martin Drab,

That's exactly what I want,
Martin Dráb 228,501 Most Valuable Professional on at

Like (1)

Report

Malaysia e-invoicing with Middleware

I don't know the particular scenario regarding IRBN, but it sounds like you want the middleware to communicate with IRBN (using its Client ID and Client secret), while F&O will communicate with the middleware (using middleware's client ID/secret or some other authorization mechanism).