Скачать презентацию Response messaging Contributions Implementation Working Group Presented by Скачать презентацию Response messaging Contributions Implementation Working Group Presented by

8a13d97d8ae0a51455d84010a538bf48.ppt

  • Количество слайдов: 8

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

Delivery vs business errors n Message delivery error is an event where a message Delivery vs business errors n 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 Super. Stream contain these receipts (which are either a positive or negative confirmation that message has been delivered). This is always a synchronous event. n 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). Super Stream 2

Published timetable for response messaging Member registration outcome response message Phase 1 - Pilot 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. Super Stream 3

Member registration outcome response (MROR) Key principles underlying the approach to messaging n Purpose Member registration outcome response (MROR) Key principles underlying the approach to messaging n Purpose is to confirm that the fund has accepted the member’s registration – or not as the case may be n 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 n Where an automated response cannot be sent, any exceptions/errors in processing member registrations will be handled ‘out of band’ – Super Stream no requirement for positive confirmation out of band. 4

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

Contributions error response Key principles underlying the approach to messaging n First priority must Contributions error response Key principles underlying the approach to messaging n 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 n Main area of focus will be on ‘high value’ errors where automated responses are most likely to produce the desired outcome n Most exceptions/errors are therefore likely to be handled ‘out of band’ during this first stage of implementation n 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. Super Stream 6

Business error messaging Phase 3: Pilot group - proposed activity n Select set of Business error messaging Phase 3: Pilot group - proposed activity n 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 Super. Stream process ‒ progress this in workshop today n Define business scenarios that outline expected behaviour of fund and employer n Define success criteria for scenarios/pilot n Document learnings and best practices n Exit to Phase 4. Super Stream 7

Business error messaging Phase 4 - All inducted solutions n All cross-certified solutions (including Business error messaging Phase 4 - All inducted solutions n 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 n 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 (Q 3 onwards) Super Stream 8