Business Process and Procedures Workstream. Role Requirements Paper. SMI Network billing process. Version Number: Version 0.1. Status: Draft Author:

Transcription

1 Business Process and Procedures Workstream Role Requirements Paper SMI Network billing process (BP13) Version Number: Version 0.1 Status: Draft Author: P Egger Date Published: 10 September 2010 File Name: 05_bppwg rrp smi network billing process paper v0.1 (initial).docx

2 [Table of s] Version History: Version Date Description of change Amended by v Sept 2010 Initial paper arising from discussions at workshop#18. Objective, Scope, Functions, Process Entities, Limitations, Role Related Principles, Flowcharts, Attachments A, B and C. P Egger Typical RRP Preparation Process: Step# Process steps Progress Date 01 WGL provides skeleton RRP (the principles would be extracted from the Completed 10/09/10 process maps, there would be no flowchart, and there would be no Control Point Records 02 A workshop would be held on the principles and flowchart Completed Wkshop#18 03 WGL would update the RRP and republish the skeleton post-workshop Completed 10/09/10. (revised principles, new flowchart, skeleton CPR) 04 Working Group members (out-of-session) will: Review the principles, flowchart and CPR. Provide feedback on these sections. 05 WGL to update the Feedback Register based on the comments, and: Update the RRP based on the Secretariat response. Prepare a skeleton of Unique Needs for each entity and the NSMP Requirements. Publish the revised Feedback Register and RRP. 06 WG members to provide feedback on the reworked RRP 07 WGL to update the Feedback Register based on the comments, and Update the RRP based on the Secretariat response. Publish the revised Feedback Register and RRP. 08 A workshop is to be held on any priority suggestions (in the Feedback Register) that receive majority support or are specifically requested by a WG member 09 WGL to rework the RRP based on workshop outcomes and republish the RRP 10 A period of time is allowed for WG members to complete a detailed internal review of the RRP and provide Stakeholder feedback to WGL 11 WGL to revise the Feedback Register and the RRP with the stakeholder feedback comments and republish 12 A workshop is to be held on the Service Levels, Service Standards and any priority suggestions raised by WG members 13 WGL to update the RRP based on the workshop outcomes and reissue 14 A workshop is to be held once the resolution of the dependency information has been provided 15 WGL to update the RRP based on the workshop outcomes and reissue for final review ( final draft RRP ) 16 WG members to provide feedback on the final draft RRP 17 WGL to update the RRP based on the Stakeholder Feedback and reissue Page 2 of 24

3 for final endorsement ( draft final RRP ) 18 A workshop is to be held to finalise endorsement of draft final PPR Legend: WGL: Blue Workshop: Dark red WG member review: Green WIP means Work In Progress Page 3 of 24

4 s: [Version History] 1. RRP No: 2. Long Title: 3. Short Title: 4. References: 5. Objective: 6. Scope: 7. SMI Functions: 8. Process Entities: 9. SMI visual context: 10. Limitations with existing NEM Procedures: 11. Role Functionality Tables: 12. Role Related Principles: 13. NSMP business process flowchart: 14. Current FRMP unique needs: 15. CSFP unique needs: 16. MDP unique needs: 17. Responsible Person unique needs: 18. DNSP unique needs: 19. Customer unique needs: 20. AEMO unique needs: 21. NSMP Requirements: 22. Infrastructure Performance Level: 23. Participant Service Levels: 24. Customer Service Standards: 25. Progress reporting: 26. Endorsement: Attachment A Flowchart Attachment B Control Point Records Attachment C Description of process steps within each entity The hyperlinks can be used to navigate to and from a chosen Line Item in the paper. 1. RRP No: NSMP BP 13 [back] 2. Long Title [back] NSMP Business Process Network billing using the SMI 3. Short Title [back] SMI Network billing process 4. References: [back] The following documents have been referred to in preparing the SMI Network billing process: (a) SMI Functional Specification (draft v0.26, dated 22 April 2010); (b) NSSC Access and Contestability Policy Principles (draft v5, dated 21 April 2010); (c) Chapter 7 Rules changes (draft vxxx, dated xxx 2010); (d) NSSC Load Management and Network Security protocol <<to be provided>> (e) NSSC Communications and Data Security protocol <<to be provided>> (f) VIC AMI Process Model, as discussed and presented by WG members.[pe] Comment [PE1]: PE to locate specific Section of the Process Model that applies to this RRP Page 4 of 24

5 5. Objective: [back] The objective of the SMI Network billing process is to ensure that there is a transparent nationally consistent approach in billing, reconciling and disputing charges relating to the SMI. 6. Scope: [back] (a) (b) The SMI Network billing process includes (workshop#18, photo#10): (i) (ii) The BAU Network billing process. The CSFP billing process. (iii) The SMI customer service charges. (iv) Billing, reconciling and disputing of SMI charges. The SMI Network billing process does not include (workshop#18, photo#10): (i) Nil. 7. SMI Functions: [back] The SMI Network billing process is supported by the following SMI function: (a) Function 7.22 Setup Conditions. 8. Process entities: [back] The following entities are involved in the SMI Network billing process: (a) Current FRMP; (b) Prospective FRMP (c) New FRMP (d) Local Retailer; (e) Responsible person; (f) DNSP; (g) Metering Data Provider; (h) Customer Service Function Provider; (i) (j) Customer; Smart Meter; (k) Market Systems; (l) MSATS; (m) AEMO. 9. SMI visual context: [back] There is no Schematic Diagram for the SMI Network billing process. 10. Limitations with existing NEM Procedures: [back] GRAPL NSMP22 details the anticipated limitations for the SMI Network billing process. The document is embedded against its title: NSMP22 Setup Conditions [GRAPL22] 11. Role Functionality Tables: [back] There are no facilities and features in the SMI Functional Specification that support this business process. 12. Role Related Principles: [back] The role related principles for the FRMP and the DNSP are as follows: Page 5 of 24

6 FRMP: (a) Nil. DNSP: (a) Nil. Common: (a) Transition to the national Network billing process must be aligned to the date of the SMI designation (workshop#18, photo#23). 13. NSMP business process flowchart: [back] The major points of interaction within and between entities for the SMI Network billing process are shown in the flowchart contained in Attachment A. In particular, the flowchart shows the transactions that are external to an entity. It is these transactions that are of most interest in formulating new NEM procedures and in making changes to existing NEM procedures. Each of these transactions cross the interface between the sending entity and the receiving entity. Control points can be established at these interfaces to enable the details of the transaction at that point to be recorded. Control Point Records are the facility for recording this information. The Control Point Records for the SMI Network billing process are contained in Attachment B. 14. Current FRMP unique needs: [back] <<to be determined>>. 15. CSFP unique needs: [back] <<to be determined>>. 16. MDP unique needs: [back] <<to be determined>>. 17. Responsible Person unique needs: [back] <<to be determined>>. 18. DNSP unique needs: [back] <<to be determined>>. 19. Customer unique needs: [back] <<to be determined>>. 20. AEMO unique needs: [back] <<to be determined>>. 21. NSMP Requirements: [back] <<to be determined>> TEST needs: The NSMP Requirements are to be tested against the following comments: Test 01: <<to be determined>> 22. Infrastructure Performance Levels: [back] There are no indicative Participant Service Levels for the SMI Network billing process contained in the Functional Specification <<<BPPWG to prepare an acceptable Role related set of performacne levels>>> 23. Participant Service Levels: [back] Page 6 of 24

7 There are no indicative Participant Service Levels for the SMI Network billing process contained in the Functional Specification. <<<BPPWG to prepare an acceptable Role related set of service levels>>> 24. Customer Service Standards: [back] <<<Identify and record the service standards that are to apply to the services provided by a Role to its customer>>>. (Commence with acceptable standards identified by Roles and refine these standards through discussion with customer advocates.) 25. Progress reporting: [back] List the dates and version each time a progress report is provided to the NSSC, IEC/RMEC and/or AEMO. 26. Endorsement: [back] Record the entity that endorsed this paper (including date and version). Legend: Working Group Leader Workshop discussion WGL with assistance from WG members Template comment - to be reworked Page 7 of 24

8 start start end end National Smart Metering Program ATTACHMENT A Flowchart [ Back to Table of s] [Back to Item 13] AEMO SMI NMI billing flowchart - Network Undefined MARKET SYSTEMS CUSTOMER SMI Metering Data C,P,D process BAU internal systems input SMI Event Log C,P,D process CURRENT FRMP current FRMP No Prospective FRMP New FRMP Responsible Person and DNSP MP(B) BP13.04 Send invoice SMI Metering Data C,P,D process SMI Event Log C,P,D process Wrapped on B2B Daily metering data BP13.05 Process inputs Daily Event Log BP13.08 Receive invoice CP#02 BP13.07 Send invoice BP13.06 Billing engine BP13.09 Reconcile invoice By Line item Network bill NUOS charge Direct service charges Retailer SO Reference # Close out date Network product code NPC rate CSFP service charges CSFP bill Service charges BP10.a Is invoice disputed? Yes BP13.10 Send disputed claim CP#03 BP13.11 Receive disputed claim CP#04 Agree to change invoice as per claim BP13.12 Review dispute Yes BP10.c Agree with dispute? No No BP10.d Is dispute resolved? BP13.19 Receive response CP#06 BP13.18 Send response BP13.17 Identify relevant information Yes Reasons why invoice is correct BP13.20 Pay invoice CP#07 BP13.21 Receive payment B2B Remittance EFT funds transfer BP13.22 Reconcile payment No BP10.e Agree with payment? Reasons why payment is incorrect Yes BP13.23 Pay CSFP invoice CP#08 MDP MDP CP#01 CP#05 CSFP Daily Event Log BP13.01 Process inputs Internal systems SMI Event Log C,P,D process BP13.02 BP13.03 Billing Send engine invoice Dynamic peak pricing events Load management switching Demand limiting events By Line item BP13.13 Receive disputed claim Agree to change invoice as per claim Yes BP13.14 BP10.b Review Agree with dispute dispute? No BP13.16 Send response Reasons why invoice is correct BP13.15 Identify relevant information BP13.25 Reconcile payment No BP10.f Yes Agree with payment? Reasons why payment is incorrect BP13.24 Receive payment SMART METER BPPWG RRP SMI NMI billing flowchart v01 Page 1/2 Flowchart 1: SMI Network billing - Network AEMO SMI NMI billing flowchart CSFP Undefined MARKET SYSTEMS CUSTOMER SMI Metering Data C,P,D process BAU internal systems input SMI Event Log C,P,D process CURRENT FRMP current FRMP No Prospective FRMP New FRMP Network bill NUOS charge Direct service charges BP13.06 Receive invoice BP13.07 Reconcile invoice BP10.a Is invoice disputed? Yes BP13.08 Send disputed claim CP#02 No BP10.c Yes Is dispute resolved? BP13.13 Receive response BP13.14 Pay invoice B2B Remittance EFT funds transfer CP#04 BP13.05 Send invoice Responsible Person and DNSP MP(B) BP13.04 Send invoice CSFP bill Service charges MDP MDP Wrapped on B2B CP#01 CP#03 CSFP start BP13.01 Process inputs Internal Daily Event Log systems SMI Event Log C,P,D process BP13.02 Billing engine Dynamic peak pricing events Load management switching Demand limiting events BP13.03 Send invoice By Line item BP13.09 Receive disputed claim Agree to change invoice as per claim Yes BP13.10 BP10.b Review Agree with dispute dispute? No BP13.12 Send response Reasons why invoice is correct BP13.11 Identify relevant information BP13.15 Receive payment Reasons why payment is incorrect No BP13.16 Reconcile payment BP10.d Yes Agree with payment? end SMART METER BPPWG RRP SMI NMI billing flowchart v01 Page 1/2 Flowchart 2: SMI Network billing - CSFP Page 8 of 24

9 Noteworthy conditions for the SMI Network billing process are: Constraints: <<to be assessed>>. Limitations: <<to be assessed>>.. Manual interventions: <<to be assessed>>.. Transitional considerations: <<to be assessed>>.. Page 9 of 24

10 ATTACHMENT B Control Point Records [ Back to Table of s] [Back to Item 13] [Forward to Attachment C] The hyperlinks may be used to navigate to and from a selected Control Point Record. s of Attachment B for the SMI Network billing Network: CP#01 An invoice is sent from CSFP to the DNSP CP#02 An invoice is sent from DNSP to the Retailer CP#03 The Retailer sends the disputed claim to the DNSP CP#04 The DNSP sends the disputed claim to the CSFP CP#05 The CSFP sends a response to the DNSP CP#06 The DNSP sends a response to the Retailer CP#07 The Retailer pays the DNSP invoice CP#08 The DNSP pays the CSFP invoice [Control Point Comparison] for the SMI Network billing Network s of Attachment B for the SMI Network billing CSFP: CP#01 An invoice is sent from CSFP to the Retailer CP#02 The Retailer sends the disputed claim to the CSFP CP#03 The CSFP sends a response to the Retailer CP#04 The Retailer pays the CSFP invoice [Control Point Comparison] for the SMI Network billing CSFP Page 10 of 24

11 CONTROL POINT RECORD CPR#01 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#01 Control Point transaction An invoice is sent from CSFP to the DNSP WHO Sending Entity: CSFP WHO Receiving Entity: DNSP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective CSFP to send a <<monthly>> invoice to the DNSP for services rendered. Outbound Inbound Outcome Transaction to include the following information: All FRMPs to whom the charges apply; NMI to which the services apply (segregated by FRMP); Meter serial number to which the services apply (segregated by NMI); Type of service rendered (segregated by meter); Charge code for each service; Service charge rate. Acknowledgements: Handshake; Transaction (technical). The DNSP receives the request. WHEN: Sending Timing Frequency One occasion per month. Receiver timing WHERE: Location ID DNSP internal systems WHY: Explanation Payment for services rendered. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 11 of 24

12 CONTROL POINT RECORD CPR#02 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#02 Control Point transaction An invoice is sent from DNSP to the Retailer WHO Sending Entity: DNSP WHO Receiving Entity: Current FRMP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective DNSP to send a <<monthly>> invoice to the current FRMP for services rendered. Outbound Inbound Outcome Transaction to include the following information: NUOS charges; Network direct charges (with breakdown as shown): o All NMIs to which the services apply; o Meter serial number to which the services apply (segregated by NMI); o Type of service rendered (segregated by meter); o Charge code for each service; o Service charge rate. CSFP charges (with breakdown as shown): o All NMIs to which the services apply; o Meter serial number to which the services apply (segregated by NMI); o Type of service rendered (segregated by meter); o Charge code for each service; o Service charge rate. Acknowledgements: Handshake; Transaction (technical). The current FRMP receives the request. WHEN: Sending Timing Frequency One occasion per month. Receiver timing WHERE: Location ID Current FRMP internal systems WHY: Explanation Payment for services rendered. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 12 of 24

13 CONTROL POINT RECORD CPR#03 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#03 Control Point transaction The Retailer sends the disputed claim to the DNSP WHO Sending Entity: Current FRMP WHO Receiving Entity: DNSP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective Current FRMP to send a disputed claim to the DNSP for the rendered invoice. Outbound Inbound Outcome Transaction to include the following information: Invoice and supporting statement that identify the disputed claim; Reason for disputing the invoice: Description of disputed information; Supporting analysis and additional information; Corrected values in accordance with current FRMP reasoning. Acknowledgements: Handshake; Transaction (technical). The DNSP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID DNSP internal systems WHY: Explanation In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 13 of 24

14 CONTROL POINT RECORD CPR#04 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#04 Control Point transaction The DNSP sends the disputed claim to the CSFP WHO Sending Entity: DNSP WHO Receiving Entity: CSFP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective DNSP to send a disputed claim to the CSFP for the rendered invoice. Outbound Inbound Outcome Transaction to include the following information: CSFP invoice and supporting statement that identify the disputed claim; Retailer s reason for disputing the invoice: Retailer s description of disputed information; Retailer s supporting analysis and additional information; DNSP s supporting analysis and additional information (if appropriate) Retailer s corrected values in accordance with current FRMP reasoning. Acknowledgements: Handshake; Transaction (technical). The DNSP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID DNSP internal systems WHY: Explanation In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 14 of 24

15 CONTROL POINT RECORD CPR#05 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#05 Control Point transaction The CSFP sends a response to the DNSP WHO Sending Entity: CSFP WHO Receiving Entity: DNSP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective CSFP to send a response to the DNSP for the disputed claim. Outbound Inbound Outcome Transaction to include the following information: Invoice and supporting statement that identify the disputed claim; Summary of the CSFP findings; Reasons for accepting that the dispute is correct or not; Correct values to apply to the invoice (revised invoice if appropriate). Acknowledgements: Handshake; Transaction (technical). The DNSP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID DNSP internal systems WHY: In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 15 of 24

16 CONTROL POINT RECORD CPR#06 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#06 Control Point transaction The DNSP sends a response to the Retailer WHO Sending Entity: DNSP WHO Receiving Entity: Current FRMP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective DNSP to send a response to the current FRMP for the disputed claim. Outbound Inbound Outcome Transaction to include the following information: Invoice and supporting statement that identify the disputed claim; Summary of the NDSP / CSFP findings; Reasons for accepting that the dispute is correct or not; Correct values to apply to the invoice (revised invoice if appropriate). Acknowledgements: Handshake; Transaction (technical). The current FRMP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID current FRMP internal systems WHY: In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 16 of 24

17 CONTROL POINT RECORD CPR#07 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#07 Control Point transaction The Retailer pays the DNSP invoice WHO Sending Entity: Current FRMP WHO Receiving Entity: DNSP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective Current FRMP to transfer the funds to pay the invoice and send a remittance notice to the DNSP. Outbound Inbound Outcome EFT payment Remittance notice Acknowledgements for remittance notice: Handshake; Transaction (technical). The current FRMP pays the invoice. WHEN: Sending Timing Within <<5 days>> of receiving invoice, or Within <<1 day>> after disputed claim resolved. One occasion per month. Frequency Receiver timing WHERE: Location ID DNSP internal systems WHY: Explanation In accordance with services contract. HOW: Outbound EFT payment arrangements Remittal transaction sent by B2B Inbound EFT payment arrangements Acknowledgement transaction sent by B2B HOW MANY Number of One transaction per month. transactions per day Page 17 of 24

18 CONTROL POINT RECORD CPR#08 Network [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#08 Control Point transaction The DNSP pays the CSFP invoice WHO Sending Entity: DNSP WHO Receiving Entity: CSFP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective DNSP to transfer the funds to pay the invoice and send a remittance notice to the CSFP. Outbound Inbound Outcome EFT payment Remittance notice Acknowledgements for remittance notice: Handshake; Transaction (technical). The DNSP pays the invoice. WHEN: Sending Timing Within <<10 days>> of receiving invoice, or Within <<4 days>> after disputed claim resolved. One occasion per month. Frequency Receiver timing WHERE: Location ID CSFP internal systems WHY: Explanation In accordance with services contract. HOW: Outbound EFT payment arrangements Remittal transaction sent by B2B Inbound EFT payment arrangements Acknowledgement transaction sent by B2B HOW MANY Number of One transaction per month. transactions per day Page 18 of 24

19 CONTROL POINT RECORD CPR#01 CSFP [Back to Attachment B ] BP13 Business Process SMI Network billing process CP#01 Control Point transaction An invoice is sent from CSFP to the Retailer WHO Sending Entity: CSFP WHO Receiving Entity: Current FRMP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective CSFP to send a <<monthly>> invoice to the current FRMP for services rendered. Outbound Inbound Outcome Transaction to include the following information: All FRMPs to whom the charges apply; NMI to which the services apply (segregated by FRMP); Meter serial number to which the services apply (segregated by NMI); Type of service rendered (segregated by meter); Charge code for each service; Service charge rate. Acknowledgements: Handshake; Transaction (technical). The current FRMP receives the request. WHEN: Sending Timing Frequency One occasion per month. Receiver timing WHERE: Location ID Current FRMP internal systems WHY: Explanation Payment for services rendered. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of transactions per day One transaction per month. Page 19 of 24

20 CONTROL POINT RECORD CPR#02 CSFP [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#02 Control Point transaction The Retailer sends the disputed claim to the CSFP WHO Sending Entity: Current FRMP WHO Receiving Entity: CSFP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective Current FRMP to send a disputed claim to the CSFP for the rendered invoice. Outbound Inbound Outcome Transaction to include the following information: Invoice and supporting statement that identify the disputed claim; Reason for disputing the invoice: Description of disputed information; Supporting analysis and additional information; Corrected values in accordance with current FRMP reasoning. Acknowledgements: Handshake; Transaction (technical). The CSFP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID CSFP internal systems WHY: Explanation In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of commands per day One transaction per month. Page 20 of 24

21 CONTROL POINT RECORD CPR#03 CSFP [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#03 Control Point transaction The CSFP sends a response to the Retailer WHO Sending Entity: CSFP WHO Receiving Entity: Current FRMP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective CSFP to send a response to the current FRMP for the disputed claim. Outbound Inbound Outcome Transaction to include the following information: Invoice and supporting statement that identify the disputed claim; Summary of the CSFP findings; Reasons for accepting that the dispute is correct or not; Correct values to apply to the invoice (revised invoice if appropriate). Acknowledgements: Handshake; Transaction (technical). The current FRMP receives the request. WHEN: Sending Timing Within <<2 days>> of receiving disputed claim. Frequency One occasion per month. Receiver timing WHERE: Location ID Current FRMP internal systems WHY: Explanation In accordance with the agreed disputes resolution process. HOW: Outbound Transaction sent by B2B Inbound Acknowledgement sent by B2B HOW MANY Number of messages per day One transaction per month. Page 21 of 24

22 CONTROL POINT RECORD CPR#04 CSFP [Back to Attachment B Conten t] BP13 Business Process SMI Network billing process CP#04 Control Point transaction The Retailer pays the invoice WHO Sending Entity: Current FRMP WHO Receiving Entity: CSFP Details: (refer to Control Point Record Template for definitions of the following points) WHAT: Objective Current FRMP to transfer the funds to pay the invoice and send a remittance notice to the CSFP. Outbound Inbound Outcome EFT payment Remittance notice Acknowledgements for remittance notice: Handshake; Transaction (technical). The current FRMP pays the invoice. WHEN: Sending Timing Within <<5 days>> of receiving invoice, or Within <<1 day>> after disputed claim resolved. One occasion per month. Frequency Receiver timing WHERE: Location ID CSFP internal systems WHY: Explanation In accordance with services contract. HOW: Outbound EFT payment arrangements Remittal transaction sent by B2B Inbound EFT payment arrangements Acknowledgement transaction sent by B2B HOW MANY Number of One transaction per month. transactions per day Page 22 of 24

23 ATTACHMENT C Description of process steps within each entity [ Back to Table of s] [Back to Attachment B] Description of process steps within each entity for the SMI Network billing process Network: Ref # Flowchart name for step Description of step BP13.01 Process inputs CSFP processes inputs from internal systems and daily Event Logs BP13.02 Billing engine CSFP prepares bills for each party BP13.03 Send invoice CSFP sends its invoice to the DNSP BP13.04 Send invoice MDP sends its invoice to the current FRMP BP13.05 Process inputs DNSP processes inputs from internal systems and daily Event Logs BP13.06 Billing engine DNSP prepares bills for each party BP13.07 Send invoice DNSP sends its invoice to the DNSP BP13.08 Receive invoice Current FRMP receives the DNSP invoice BP13.09 Reconcile invoice Current FRMP processes DNSP invoice BP13.a Is invoice disputed? Yes proceed to BP13.11 No proceed to BP13.20 BP13.10 Send disputed claim Current FRMP sends the disputed claim to the DNSP BP13.11 Receive disputed claim DNSP receives the disputed claim BP13.12 Review dispute DNSP reviews the disputed claim and decides if it relates to the Network or the CSFP. If it relates to the CSFP then the claim is sent to that party BP13.13 Receive disputed claim CSFP receives the disputed claim BP13.14 Review dispute CSFP reviews the disputed claim and determines if the dispute is accepted or not BP13.b Agree with dispute? Yes proceed to BP13.16 Continue proceed to BP13.15 BP13.15 Identify relevant information If not accepted, the CSFP gathers together the relevant information BP13.16 Send response The CSFP sends a response to the DNSP advising that they accept the disputed claim as incorrect or advise that they do not accept the disputed claim and provide reasons why the claim is correct. BP13.c Agree with dispute? Yes proceed to BP13.18 No proceed to BP13.17 BP13.17 Identify relevant information If not accepted, the DNSP gathers together the relevant information BP13.18 Send response The DNSP sends a response to the current FRMP advising that they accept the disputed claim as incorrect or advise that they do not accept the disputed claim and provide reasons why the claim is correct. BP13.19 Receive response The current FRMP receives the response from the DNSP and determines if the dispute has been resolved or not BP13.d Is dispute resolved? Yes proceed to BP13.20 No proceed to BP13.a BP13.20 Pay invoice The current FRMP pays the DNSP invoice BP13.21 Receive payment The DNSP receives the payment from the current FRMP BP13.22 Reconcile payment The DNSP undertakes a reconciliation of the payment BP13.e Agree with payment? Yes proceed to BP13.23 No proceed to BP13.18 BP13.23 Pay invoice The DNSP pays the CSFP invoice BP13.24 Receive payment The CSFP receives the payment from the DNSP BP13.25 Reconcile payment The CSFP undertakes a reconciliation of the payment BP13.f Agree with payment? Yes end No proceed to BP13.16 Description of process steps within each entity for the SMI Network billing process CSFP: [Top of Attachment C] Ref # Flowchart name for step Description of step BP13.01 Process inputs CSFP processes inputs from internal systems and daily Event Logs BP13.02 Billing engine CSFP prepares bills for each party Page 23 of 24

24 BP13.03 Send invoice CSFP sends its invoice to the DNSP BP13.04 Send invoice MDP sends its invoice to the current FRMP BP13.05 Send invoice DNSP sends its invoice to the DNSP BP13.06 Receive invoice Current FRMP receives the DNSP invoice BP13.07 Reconcile invoice Current FRMP processes DNSP invoice BP13.a Is invoice disputed? Yes proceed to BP13.08 No proceed to BP13.14 BP13.08 Send disputed claim Current FRMP sends the disputed claim to the CSFP BP13.09 Receive disputed claim CSFP receives the disputed claim BP13.10 Review dispute CSFP reviews the disputed claim and determines if the dispute is accepted or not BP13.b Agree with dispute? Yes proceed to BP13.12 No proceed to BP13.11 BP13.11 Identify relevant information If not accepted, the CSFP gathers together the relevant information BP13.12 Send response The CSFP sends a response to the current FRMP advising that they accept the disputed claim as incorrect or advise that they do not accept the disputed claim and provide reasons why the claim is correct. BP13.13 Receive response The current FRMP receives the response from the CSFP and determines if the dispute has been resolved or not BP13.c Is dispute resolved? Yes proceed to BP13.14 No proceed to BP13.a BP13.14 Pay invoice The current FRMP pays the CSFP invoice BP13.15 Receive payment The CSFP receives the payment from the current FRMP BP13.16 Reconcile payment The CSFP undertakes a reconciliation of the payment BP13.d Agree with payment? Yes end No proceed to BP13.12 Page 24 of 24