Official Integration Basis
The Ministry of Finance Guidelines require businesses to select and onboard with an ASP, agree how invoice data will be transmitted, ensure their systems can send and receive invoice data, test end-to-end exchange and reporting, and establish governance with the ASP for error resolution.
Select an Accredited Service Provider, complete onboarding and obtain the required Peppol participant identifier arrangements.
Agree with the ASP how Electronic Invoice data will be transmitted to and from the ASP.
Complete the required ERP/ASP integrations and test Electronic Invoice exchange and reporting.
Establish roles and responsibilities with the ASP for transmission oversight and resolution of errors.
Integration Lifecycle
Tool 05 examines the integration boundaries between the source ERP, the organisation’s transformation logic, the selected ASP and the operational response loop. Tool 04 answers whether the required data exists; Tool 05 answers whether that data can move reliably through the integration.
01
Invoice source data
02
Source / canonical structure
03
API / connector / middleware
04
Exchange & reporting cycle
05
Confirmation, errors, reconciliation
Assessment Method
Select ERP, ASP status, transmission approach and project context so results are interpreted within the intended implementation design.
Use the broad guided assessment, review an ASP API/specification, or compare an ERP submission sample with an ASP response.
The engine evaluates transmission, authentication, payload, response, retry, reconciliation, testing and governance evidence.
Receive readiness gates, technical findings and an implementation remediation register for ERP, IT, Finance and ASP follow-up.
Three-in-One Integration Review
MODE 01
For Finance, ERP and IT teams. Evaluates the full client-side integration model even when API documentation is not yet available.
MODE 02
For technical implementation teams. Reviews sanitized OpenAPI, Swagger, Postman, XML/WSDL or technical files for integration capability evidence.
MODE 03
For active integrations. Compares ERP/submission identifiers with the ASP response to assess status handling and operational traceability.
Interactive Integration Assessment
Result Interpretation
The numeric result is an indicative PTG engineering-readiness score. The MoF-aligned gates should be read separately because a high technical score should not override an unresolved onboarding, transmission, testing or governance requirement.
Most required client-side controls are evidenced. Complete outstanding testing and production evidence before go-live reliance.
Several technical or operational controls require remediation before dependable end-to-end testing.
The integration approach, controls or evidence require substantial development and coordination.
Understand whether the organisation has moved beyond ASP selection into actual operational integration readiness.
Identify missing authentication, endpoint, status, retry, idempotency and reconciliation controls that need development.
Convert technical gaps into an owner-based remediation register for ERP, Integration, Finance and ASP follow-up.
Identify whether testing, negative scenarios, monitoring and error-resolution governance are sufficiently established.
Practical User Value
PTG can review the client-side ERP architecture, source payload, ASP API or connector documentation, authentication design, response/status handling, retry and duplicate controls, reconciliation model, sandbox test evidence and operational governance, and prepare an implementation-ready remediation plan.
No. The tool assesses client-side readiness and sanitized integration evidence. Actual Electronic Invoice exchange and reporting are performed through the organisation’s selected Accredited Service Provider.
No. Mode 01 can be used during planning. However, final integration readiness depends on the selected ASP’s actual onboarding, transmission, authentication, response and testing requirements.
Yes, provided the file is sanitized. Never upload passwords, client secrets, private keys, bearer tokens or production credentials. “Not detected” means the capability was not identified in the uploaded material; it does not prove the ASP lacks it.
Tool 04 checks whether the ERP/source data contains and maps the required invoice information. Tool 05 checks whether that information can be transmitted to the ASP, responses can be handled, and the integration can be reconciled and operated reliably.
No. The PTG score is an indicative engineering-readiness measure. The MoF-aligned readiness gates, ASP onboarding, end-to-end testing, governance and the latest official requirements must also be satisfied.
These controls help an organisation trace an ERP invoice through submission, ASP processing and response handling. They are important operational integration practices for monitoring and resolving failures.
No. Tool 05 focuses on ERP–ASP integration readiness. Full PINT-AE syntax, Schematron, code-list, arithmetic and business-rule validation belongs in Tool 06 — Testing & Validation.
