Shared information about a bug that was discovered in the
used as part of the AUNZ BIS relating to a VAT specific element. While this doesn't necessarily affect A-NZ providers, as the element
is VAT specific, it is used in the Interoperability test files which now all fail. Simon asked the group whether they have identified
any problems with this, or otherwise, through interoperability testing. The group shared that they had run into a few issues due to
everyone's implementations being different and that the process does help to fix some of these issues.
Reminder that the Industry Practice Statements are available on the A-NZ
Peppol GitHub. Simon shared that others are interested in what Australia is doing in this space and is presenting this work at the global service
providers meeting. The group asked about whether Peppol have any plans to make invoice response mandatory and it was noted that the
new agreements are taking the focus away from this and other work. The group then discussed remittance advice and while it is not
currently supported by Peppol, any Peppol Authority can propose to get remittance advice included. After the meeting, ABSIA clarified with
the ATO that they are intending to request remittance advice as a new Peppol document type, and that Invoice Response PD Status (Paid)
along with the Note field for further details (bank, payment ID) could be used as a simple remittance advice along with any existing
email/PDF based process. See also Best Practice Principle 6 in the Invoice Status Industry Practice Statement.
While work on the new Peppol agreements has been progressing well, those on the working groups shared that there is still a lot of work to
do. More recently, work has focused on Digital Identity and customer verification in the Internal Regulations working group from the
Agreement Task Force. It was noted that the customer verification piece is very similar to what the ATO has produced for Operational
Framework. The group then discussed how they handle customer verification considering the new agreements are going to require
intermediaries to have something in their contacts about it. The group then talked about payments via ABN.
Provided an update on the Treasury consultation after ABSIA attended a roundtable with other industry stakeholders. We understand that the
report is being delivered to the Government and the hope is that something will be included in the budget for May.
The group continued a discussion from the Service Provider Forum about multiple identifiers and routing. Simon shared two possible
alternatives to using the 0151 ABN ICD in order to have multiple identifiers. The 0203 eDelivery Network Participant Identifier (which
uses email address) and 0195 Singapore IMDA. Further investigation after the meeting determined that the 0203 ICD is not yet
permissible as a Peppol Identifier. The error occurred as there are two ICD code lists as part of the Peppol Invoice BIS - full
and the more limited Electronic Address Scheme (EAS). Note the Usage
section of each list which describes where they can be used, EAS being for "Endpoint" or Peppol ID. This list is derived from
the Participant Identifier Schemes code list which formally describes the
permissible address schemes. The IMDA 0195 ICD allows any international identifier with up to 3 extra digits (allowing for
another 999 identifiers). Specifications are available here.
Rick Harvey then provided on issues with the SMP and certificates issued by Peppol that have now been fixed. He also noted that the
testbed 2 is now expected to be released in March as they are still working through a few problems. There are no plans from Peppol to
make everyone re-validate against it but at the country level, they may make it mandatory.
The PINT work has been impacted by the work on the new agreements but it was on the agenda for the most recent cross-community
meeting. It is expected that there will be more information to share at the next meeting.