parties in the flow? ok... developers of any invoice app <-> providers servers / have differents api and flow every time <-> gov api (only for providers)
If you can't draw the flow chart, can you listed out the parties from Left to Right indicate Start to End for each steps?
Since you didn't provide answers for these questions and I could not ask your government for the answers, I can only make my own assumptions.
I assume the flow is as following:
Scenario 1
1. End User (Buyer/Customer/usually consumer of the products and services) makes a purchase with -->
2. Providers (Seller/Merchant/usually business owners providing products or services) generate and send e-Invoice in the form of JSON/XML to --> 3. Government e-Invoicing API Server (MYDATA?) and the server validate the e-Invoice then send back the validated e-Invoice back to --> 4. Providers and generate a validated e-Invoice to 5. End User (who may use ERP system, apps or custom software developed by Developers).
Scenario 2
The process continues from #5 where the End User can accept or reject the e-Invoice...
There are many other scenarios but let us focus on Scenario 1 at this point.
I assume Providers are the one who concern about sales profit.
Hence they are also the party that making request or consuming the APIs provided by the government API server (MYDATA?).
Meanwhile End User concern about tax submission or claim the tax refund where the e-Invoice is a proof of purchase.
Here you want to slot in as an intermediate Middleware provider so the flow changed to this:
2. Providers (Seller/Merchant/usually business owners providing products or services) generate and send e-Invoice in the form of JSON/XML to
3. Middleware provider that accepts different types or non standard types of e-invoices then output the correct format required by the API of --> 4. Government e-Invoicing API Server (MYDATA?)
So your actual concern is to make the Providers' life easier for providing an intermediate service to make the API submission smoother.
Am I right so far?