myIR, payments and more
All KiwiSaver scheme providers will need to comply with technical requirements outlined in schedules B and D of the scheme provider agreement (SPA).
KiwiSaver requires that information is sent to and received from you in a secure and timely manner, using automated processes and a single standard for B2B communications with all scheme providers.
If you don't meet the technical requirements at the time of signing the SPA you must provide a system development plan, which outlines the steps you will take to achieve systems development milestones.
The KiwiSaver B2B interface with Inland Revenue uses:
- AS2 for transmission
- XML-RPC for wrapping, and
- the following XML specifications for data exchange:
- extensible Party Information Language (xPIL)
- extensible Address Language (xAL)
- extensible Name Language Types (xNL).
A copy of the SPA documentation can be obtained by emailing firstname.lastname@example.org
Integration and compatibility testing
Every scheme provider will need to go through a systems integration and compatibility testing process to ensure that the data exchange functions correctly. Schedule D of the SPA sets out the testing requirements in more detail.
Testing is the final, formal component of provider integration. It verifies functional and technical integration between your system and the KiwiSaver B2B gateway.
Testing does not assess nor certify the capability of your organisation's back-end processing systems. Timeframes for systems testing will be on a case-by-case basis.