Presented by Ty Winmill Australian Taxation Office 20 February 2015

1. Response messaging Contributions Implementation Working Group • Presented by Ty Winmill • Australian Taxation Office • 20 February 2015

2. Delivery vs business errors • Message delivery error is an event where a message fails to be delivered or cannot be processed by the intended receiver (results in eb:Receipt going back to sender) • Note: All existing messages delivered in SuperStream contain these receipts (which are either a positive or negative confirmation that message has been delivered). This is always a synchronous event. • Business errors are messages resulting from the detection of a defined error event in the processing of a contribution (payload or message) • Note: Error message can be reported back at any time and will normally be processed in a progressive sequence (asynchronous pattern).

3. Published timetable for response messaging • Member registration outcome response message • Phase 1 - Pilot Group A 2 February 2015 – 2 March 2015 • Phase 2 - Inducted solutions* 3 March 2015 onwards • Business error messages • Phase 3 - Pilot Group B 3 March 2015 – 12 April 2015 • Phase 4 - All inducted solutions 13 April 2015 onwards • Note: Pilots are being run on an ‘opt-in’ voluntary basis. • * Completed induction to that point and others as they join.

4. Member registration outcome response (MROR) • Key principles underlying the approach to messaging • Purpose is to confirm that the fund has accepted the member’s registration • or not as the case may be • Response messages can only be sent where the message sender has agreed to receive such messages • not agreed if the sender has an ultra-light profile • agreed if ‘error messaging‘ flag set to TRUE by sender • Where an automated response cannot be sent, any exceptions/errors in processing member registrations will be handled ‘out of band’ • no requirement for positive confirmation out of band.

5. MROR – sequencing of activity • Phase 1: Pilot group - current activity • AAS/Westpac and ADP/OzEDI have formed a pilot group • Parties are undertaking testing only at this stage • Expected to be exchanging production messages next week • Success criteria • Messages can be executed successfully from fund to employer (or their agent’s system) • Where applicable, a member ID can be communicated back to the relevant source system • Exit to Phase 2 • Publish any learnings – not expecting anything significant • Confirm start-up dates for rest of inducted solutions – likely to be second week of March (bit later than published timetable)

6. Contributions error response • Key principles underlying the approach to messaging • First priority must be to process contribution (if at all possible) • if an error has occurred in processing the intent is to support the primary goal, not flood the response channel with low value error messages • Main area of focus will be on ‘high value’ errors where automated responses are most likely to produce the desired outcome • Most exceptions/errors are therefore likely to be handled ‘out of band’ during this first stage of implementation • Remembering: error messages can only be sent where the message sender has agreed to receive such messages • not agreed if the sender has an ultra-light profile • agreed if ‘error messaging‘ flag set to TRUE by sender.

7. Business error messaging • Phase 3: Pilot group - proposed activity • Select set of business error messages to respond to employer • selecting “high value” business exceptions/errors that are “do-able” and will provide efficiencies within the SuperStreamprocess • progress this in workshop today • Define business scenarios that outline expected behaviour of fund and employer • Define success criteria for scenarios/pilot • Document learnings and best practices • Exit to Phase 4.

8. Business error messaging • Phase 4 - All inducted solutions • All cross-certified solutions (including APRA fund products in active receiving mode) must begin processing business messages as part of normal operations. • Revisit start date next month when status and progress of pilot is clearer • As new solutions enter induction from this date onwards, they will be expected to handle both types of response messages and report activity to the Nerve Centre accordingly. Note: Additional error codes will be trialled and added in due course (Q3 onwards)