It makes more sense to me now.
So the Providers concept is very similar to what we have here call Service Providers.
Would I scare you that not only 30+ but maybe we have 3,000 or 30,000+ of service providers?
As you said above, actually companies don't really need these providers.
In fact, anyone can also become one of the service providers.
Since I already registered myself as one with my country's inland revenue bureau (IRB), I can do testing in sandbox environment.
When I want, I can provide a service to help companies to submit their e-Invoice.
This also mean some companies can also submit their e-Invoice without engaging any third party service providers if they have an in-house software team.
If I understand, MYDATA used to be the only authorized provider but by time goes by, now more and more providers are available.
So let say I am in your situation, to become a middleware provider, is that mean I need to deal with 30,000+ of service providers?
The different situation between what happen in your country vs what we have here, that I can see is:
In Greece, different service providers have different "pre" e-Invoice format.
I don't know why is this happening.
By right, they (so called the Provider) should "provide" or adhere to the format required by the government API server. You call it AADE server?
They should become the Solution Provider who should "Solve" the Problem.
A Middleware provider is not required.
The government should enforce a standard API format documented in a SDK guideline where a list of mandatory fields need to be provided.
Optional fields are accepted.
If the providers are not providing the correct format then it means they are not compliant or eligible to call providers.
In Malaysia, each service providers should follow the SDK guideline or else end up their e-Invoice getting validation failure.
The role of Middleware providers are different here.
I am not 100% sure what they are doing but I see there is a company who claim its product name associated with AI can help any business or company convert their legacy ERP system or excel format invoices into e-Invoice compliant with the government API standard.
Back to your case, I have an idea to solve your problem. (maybe 2 ideas)
Idea #1
Become a Middleware provider
Either you need to communicate with the providers to get their "pre" formatted e-invoice or you get from the companies that engage services from these providers.
You need to map their fields to AADE format.
Every time there is a change of key names involving the "mandatory" fields, you need to update your middleware system.
This mean you have a database to store each provider "template" and associate with their client id.
Idea #2
Don't need to become a Middleware provider
Because your target are not service providers, so why need to focus or concern about the providers format?
Straight away build one product that can generate the e-Invoice compliant to AADE format
You can sell this product at a very minimum price or have a different business model
Lastly, I can say for both Ideas, you can use B4J to develop the server or even a standalone system.
You may also consider to build using one of my frameworks.