October 1, 1999 Added Information DRAFT Version 3.1b Moved the adjustment definitions from the data dictionary to the notes section of the implementation guide. November 4, 1999 This is a FINAL version for and Version 3.2 November 1999 Add use to document will not use the 568 when the market opens. – Draft version 3.2MD1 Table of Contents Added Data Dictionary January 17, 2000 Clarified N9*45 is only used if LDC is sending transaction. Version 3.2MD2 June 26, 2000 Corrected description for Customer name in Data Dictionary Version 3.2MD3 September 10, 2000 This transaction is a new version for , , , and (Delmarva only). Version 3.3 October 19, 2001 Incorporate Delaware Electric Coop (DEC) information for Version 3.3rev01 January 9, 2002 This transaction is a new FINAL version for , , , and . Version 4.0 February 22, 2009 Incorporate PA Change Control 048. Version 4.0.1 January 24, 2010 This transaction is a new FINAL version for , , , and . Version 4.1 September 8, 2010 Incorporate PA Change Control 060 (PA Admin/Cleanup changes) Version 4.1.1D Incorporate MD Change Control Admin (Admin/Cleanup changes for MD) – February 28, 2011 This transaction is a new FINAL version for , , , and . Version 5.0 February 16, 2011 This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Version 5.0 Delaware. No changes since last version. 8, 2013 Moving to v6.0 to align versions across all transaction sets Version 6.0 Cleaned up references to Allegheny and APS throughout document March 17, 2014 Incorporated PA EDI Change Control 113 (PPLEU doesn’t send 568) Version 6.1 May 18, 2018 Incorporated PA Change Control 146 (Citizens & Wellsboro doesn’t send 568) Version 6.2 General Notes Use of 568 transaction PA Rules: The 568 Collections transaction will be used in all cases for the billing party to notify the non-billing party of payments received from the customer. The transaction must be sent regardless of whether the billing is making the other party whole or not. Special exceptions may be made by the PUC if the billing party is remitting the money received to the non-billing party in a timely manner.
October 1, 1999 DRAFT Version 3.1b Added Information Moved the adjustment definitions from the data dictionary to the notes section of the implementation guide. November 4, 1999 Version 3.2 This is a FINAL version for and November 1999 Draft version 3.2MD1 Add use to document – will not use the 568 when the market opens. Table of Contents Added Data Dictionary January 17, 2000 Version 3.2MD2 Clarified N9*45 is only used if LDC is sending transaction. June 26, 2000 Version 3.2MD3 Corrected description for Customer name in Data Dictionary September 10, 2000 Version 3.3 This transaction is a new version for , , , and (Delmarva only). October 19, 2001 Version 3.3rev01 Incorporate Delaware Electric Coop (DEC) information for January 9, 2002 Version 4.0 This transaction is a new FINAL version for , , , and . February 22, 2009 Version 4.0.1 Incorporate PA Change Control 048. January 24, 2010 Version 4.1 This transaction is a new FINAL version for , , , and . September 8, 2010 Version 4.1.1D Incorporate PA Change Control 060 (PA Admin/Cleanup changes) Incorporate MD Change Control – Admin (Admin/Cleanup changes for MD) February 28, 2011 Version 5.0 This transaction is a new FINAL version for , , , and . February 16, 2011 Version 5.0 This transaction is a new FINAL version for Pennsylvania, New Jersey, Maryland, and Delaware. No changes since last version. 8, 2013 Version 6.0 Moving to v6.0 to align versions across all transaction sets Cleaned up references to Allegheny and APS throughout document March 17, 2014 Version 6.1 Incorporated PA EDI Change Control 113 (PPLEU doesn’t send 568) May 18, 2018 Version 6.2 Incorporated PA Change Control 146 (Citizens & Wellsboro doesn’t send 568) General Notes Use of 568 transaction PA Rules: The 568 Collections transaction will be used in all cases for the billing party to notify the non-billing party of payments received from the customer. The transaction must be sent regardless of whether the billing is making the other party whole or not. Special exceptions may be made by the PUC if the billing party is remitting the money received to the non-billing party in a timely manner.
IG568v6-2.docx