Sei sulla pagina 1di 96

Effective 19 July 2011 Version E045

AUSTRALIAN PAYMENTS CLEARING ASSOCIATION LIMITED


ABN 12 055 136 519

A Company limited by Guarantee

PROCEDURES
for

BULK ELECTRONIC CLEARING SYSTEM


(CS2)

Commenced 12 December 1994

Copyright 1994 Australian Payments Clearing Association Limited ABN 12 055 136 519

Australian Payments Clearing Association Limited


Level 6, 14 Martin Place, SYDNEY NSW 2000 Telephone: (02) 9221 8944 Facsimile: (02) 9221 8057

PROCEDURES FOR BULK ELECTRONIC CLEARING SYSTEM (CS2)

INDEX

Item

Page Number

1.

PRELIMINARY 1.1 1.2 1.7 1.9 1.10 1.11 Definitions Interpretation Inconsistency with Constitution or Regulations Governing Law Copyright Application of Procedures

1.1 1.1 1.8 1.9 1.10 1.10 1.10 2.1 3.1 3.1 3.1 4.1 4.1 4.1 4.1 4.2 4.2

2. 3.

EFFECT PROCEDURES AND AMENDMENT 3.1 3.2 Conduct of Clearings Amendment

4.

GENERAL OPERATIONAL REQUIREMENTS 4.1 4.1A 4.2 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.20 4.21 Centralised Contact Point Details in Appendix B BSB Number Times of Exchange DE File Specifications Transaction Codes Clauses 4.7 to 4.16 are Confidential Return Codes Refusal Codes Tracing Requests/Missing Items Incorrectly Applied Items Errors and Adjustments to Totals of Exchanges Missorted Items Interest Adjustments Further Provisions Relating to Interest Losses Returning/Refusing FI ID Number Reversing FI ID Number Processing by account number only Summary File Specifications Encryption of Direct Connection

4.3 4.3 4.3 4.3

Bulk Electronic Clearing System (CS2) PROCEDURES Index

5.

GENERAL REQUIREMENTS IN RELATION TO USERS 5.1 5.2 5.3 5.7 5.8 5.9 5.11 5.12 5.14 5.15 5.16 5.16A 5.17 5.18 5.19 5.20 5.21 5.22 Approval and Termination Compliance by Users Notification of User Details to the Chief Executive Officer Change of Credit User FI or Debit User Sponsor Liquidation or Insolvency of User Change of User's Name and/or Transfer of Business Trace Record User Identification Numbers Clauses 5.14 to 5.22 are Confidential Recall Requests Recall Requests Processed via a Bureau Return Requests Reversals Unposted Items
Returns where Trace Record Institution is not Specified or is Incorrect

5.1 5.1 5.1 5.1 5.2 5.2 5.3 5.4 5.4

Refusals Direct Entry Returned or Refused - Voucher Specifications Notification to User of Transfer or Change to Customer's Account Transitional 6.1 6.1 6.1 6.1 6.2 6.4 6.4 6.5 6.6 6.7 6.7 7.1 7.1 7.1 7.1 7.2 7.3 7.4 7.5 7.5 7.8 7.8 7.11 7.12 Deleted Deleted 7.14 Deleted

6.

DIRECT CREDIT SYSTEM 6.1 6.2 6.5 6.7 6.8 6.9 6.10 6.11 6.12 6.13 Persons Authorised to Approve Credit Users User FI Approval User FI Responsibilities Ledger FI Responsibilities Lodgement FI Responsibilities Transaction Negotiation Authority (TNA) Change of Lodgement FI by a User or Bureau Credit Users who are Responsible Entities/Trustees/Managers of Trusts, Superannuation Funds etc. Credit User Application - Stamp Duty Notification of an Unapplied Credit Item and Request for Information (Superannuation Entities)

7.

DIRECT DEBIT SYSTEM 7.1 7.2 7.3A 7.4A 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 * * 7.13 * Participating Members Authorised to Sponsor Debit Users Sponsor Approval Direct Debit Requests Transitional Sponsor Responsibilities Sponsor Indemnification Representative Indemnification Claim Procedures under Sponsor Indemnification and Representative Indemnification Cancellation of Sponsor Indemnification and Representative Indemnification Debit User Responsibilities DDR Service Agreement Ledger FI's Responsibilities Debit Users who are Responsible Entities/Trustees/Managers of Trusts, Superannuation Funds, etc Debit User Indemnity - Stamp Duty Lodgement FI's Responsibilities Form PD-C

ii

Bulk Electronic Clearing System (CS2) PROCEDURES Index

7.14 7.15 8.

Printing/Publication of Direct Debit Requests Unpaid Direct Debits

7.15 7.15 8.1

FILE/ITEM REJECTION (Confidential) 8.1 8.2 8.3 8.4 8.5 Rejection of Individual Items by Receiving Member Errors Causing File Rejection Notification of File Rejection Treatment of Unacceptable Files Technical or Transmission Difficulties

9.

SETTLEMENT 9.1 9.2 9.3 9.4 9.5 9.6 Date of Settlement Method of Settlement Variations to Normal Settlement Interest Adjustment Settlement Contact Points (Confidential) Exchange Summary Data File Transfer Facility

9.1 9.1 9.1 9.2 9.3 9.3 10.1 10.1 10.1 Deleted 10.2 10.2 10.2 Deleted 10.3 10.3 10.4 10.4 10.5 11.1 11.1 12.1 12.1 12.1 12.2 12.2 12.3 13.1

10.

CONTINGENCY PROCEDURES 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 Responsibilities Options Magnetic Tape Handling (Confidential) Physical Medium Exchange Standards Read/Write Format Standards For Physical Medium Structure of File Blocking Factor Contact Points (Confidential) Contingency Exchange Arrangements Bilateral Testing of Contingency Exchange Arrangements Contingency Procedures Testing Certificate Standards for Email File Exchange and Security Email File Exchange Contacts Database

11.

LIABILITY OF PARTICIPATING MEMBERS IN THE EVENT OF FRAUD 11.1 Fraudulent Items

12.

DE FILE SPECIFICATIONS 12.1 12.3 12.4 12.5 12.6 Overview Character Bit Structure Structure of File Record Format Publication of DE User Item File Specifications

13.

USER RECORDS (Confidential) 13.1 13.2 13.3 13.7 Overview of User Database System Sending Data to the Company Multiple Lodgement Web Browser BUDS User FI Interface

14.

SUMMARY FILE SPECIFICATION 14.1 Overview

14.1 14.1

iii

Bulk Electronic Clearing System (CS2) PROCEDURES Index

14.3 14.4 14.5 14.6

Character BIT Structure Structure of Summary File Record Format Publication of Summary File Specification

14.1 14.1 14.1 14.2

APPENDIX A A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A12 A13 A14

DOCUMENTS A1.1 A2.1 A3.1 A4.1 Deleted Deleted A7.1 A8.1 Deleted A10.1 Deleted A12.1 Deleted

Confirmation of Recall (Confidential) Credit User Application Daily Summary Report (Confidential) Direct Entry System Advice (Confidential) Direct Entry Returned or Refused - Debit & Credit Vouchers Direct Entry Returned or Refused - Credit Voucher Form PD-C Transaction Negotiation Authority (Confidential) Debit User Indemnity Notice of Redirection of Direct Entry Item(s) Linking Indemnity Exchange Summary Error Adjustment Vouchers (Confidential) User's Indemnity Direct Debit System Image Processing of Form PD-C Direct Debit System Customer Claim Direct Debit System Claim Request (Confidential) Debit User - Change of Name or Other Details Advice Debit User - Transfer of Business Advice Notification of Reversal of Item(s) Sent In Error Direct Entry Trace Request Cancellation Request Request for Return of Item(s) Sent in Error Authorised TNA Signatories Switch of Financial Institution and Account Details

Deleted Deleted A16.1 A17.1 A18.1 A19.1 A20.1 A21.1 A22.1 A23.1 A24.1

A15 A16 A17 A18 A19 A20 A21 A22 A23 A24

iv

Bulk Electronic Clearing System (CS2) PROCEDURES Index

A25 A26 A27 A28

Regular Arrangements List Notice of Unapplied Credit Item (Superannuation) Direct Debit Request Direct Debit Request Service Agreement CONTACT POINTS (Confidential)

A25.1 A26.1 A27.1 A28.1

APPENDIX B B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13

Operational Contacts Recall Initiating Contacts Processing Centre TNA Excesses Electronic Return/Refusal Settlement Contact DDR Claims Contact and Claims Account Details Trace Requests Inter-organisation Compensation Contact Transaction Negotiation Authority Contact Point Request for Return Contact Point Account Switching Contact Point Unapplied Credit Item (Superannuation) Contact Point DE FILE SPECIFICATIONS (Confidential)

B1.1 B2.1 B3.1 B4.1 B5.1 B6.1 B7.1 B8.1 B9.1 B10.1 B11.1 B12.1 B13.1

APPENDIX C C1 C2 C3 C4 C5 C6 C7

DE File User Item Specifications DE File Return Specifications DE File Refusal Specifications DE File Claim Specifications DE File Reversal Specifications Summary File Specification BECS Character Set SPECIFIED LOCATIONS APPROVED REPRESENTATION ARRANGEMENTS APPROVED ELECTRONIC EXCHANGE ARRANGEMENTS Approved Arrangements (Tier 1)

C1.1 C2.1 C3.1 C4.1 C5.1 C6.1 C7.1 Deleted Deleted

APPENDIX D APPENDIX E APPENDIX F Table 1A:

F.1

Bulk Electronic Clearing System (CS2) PROCEDURES Index

Table 1B: Table 2:

Approved Representation Arrangements (Tier 2) Electronic Exchange Arrangements between Tier 1PMs (Confidential) FINANCIAL INSTITUTION IDENTIFICATION NUMBERS Returning/ Refusing FI ID Numbers and Reversing FI ID Numbers (Confidential) Claiming FI ID Numbers (Confidential) LEDGER FIs REQUIRING PD-C LISTS CONTINGENCY PROCEDURES FOR DISABLING EVENTS Executive Summary Roles and Responsibilities Communications Contingency Procedures For Disabling Events Disabling Events PROCESSING DIFFICULTY NOTIFICATION FORMS APCS and BECS Processing Difficulty Notification Form BECS Processing Difficulty Notification Form PRIMARY EXCHANGE ARRANGEMENTS MATRIX CONTINGENCY EXCHANGE ARRANGEMENTS MATRIX CONTINGENCY FILE EXCHANGE BECS Contingency File Exchange Form Email File Exchange Contacts Lodgement Form Email File Exchange Public Key Lodgement Form Contingency Procedures Testing Certificate

F.2 F.4

APPENDIX G G1

G1.1

G2 APPENDIX H APPENDIX I I1 I2 I3 I4 I5 APPENDIX J J1 J2 APPENDIX K APPENDIX L APPENDIX M M1 M2

G2.1 Deleted

I1.2 I2.1 I3.1 I4.1 I5.1

J1.1 J2.1 K1.1 L1.1

M1.1 M2.1 M2.2 M3.1

M3

vi

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

AUSTRALIAN PAYMENTS CLEARING ASSOCIATION LIMITED


ABN 12 055 136 519

A Company limited by Guarantee

PROCEDURES for BULK ELECTRONIC CLEARING SYSTEM (CS2)


PART 1 Definitions 1.1 The following words have these meanings in these Procedures unless the contrary intention appears. Appointor means a Participating Member or a Non-member which enters into a Representation Arrangement with a Representative and (in the case of a Non-member) provides an undertaking to the Company substantially in the form of Annexure 2 of the Regulations. BECS means Bulk Electronic Clearing System (CS2). BSB Number means a BSB Number assigned to a financial institution. BSB Numbers, titles and abbreviations are set out in the Company's current publication entitled "BSB Numbers in Australia". Bulk Electronic Clearing System (CS2) means the systems and procedures contained in the Regulations for: (a) the purpose of co-ordinating, facilitating and protecting the conduct and settlement of exchanges of Items between Participating Members and all aspects of the related clearing cycle; and the exchange of financial data. PRELIMINARY

(b)

Bureau means a person which either creates a File on behalf of a single User and lodges it with a Lodgement FI or creates Multi-User Files on behalf of more than one User and lodges these with a Lodgement FI on behalf of those Users. Cancellation Request means a document in the form of Appendix A21. Chief Executive Officer means the person appointed as a chief executive officer of the Company under Article 14.20 and a reference in these Procedures to the Chief Executive Officer includes a reference to a person nominated by the chief executive officer to be responsible for the matter referred to in that reference.
Inserted effective 20/7/2001

Australian Payments Clearing Association Limited 1.1

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Claim Request means a document in the form of Appendix A16.


Commonwealth Government File: Deleted effective 1/04/02, refer Government File Commonwealth Government Payment: Deleted effective 1/04/02, refer Government Payment

Company means Australian Payments Clearing Association Limited (ABN 12 055 136 519). Confirmation of Recall means a document in the form of Appendix A1. Contingency means any Disabling Event and any other event or circumstance specified by the Management Committee for the purposes of Regulation 9.1. Contingency Exchange Testing Schedule means the schedule published by the Company and approved by the Management Committee as required but certainly at a minimum of every four years, showing testing partners for all BECS Tier 1 Participating Members for mandatory testing, each calendar half year, of contingency exchange arrangements pursuant to clause 10.10 of these Procedures. The schedule will be published on the Companys extranet. Contingency File Exchange Form means a document, substantially in the form of Appendix M1, used by a sending or Disabled Tier 1 Participating Member to advise a receiving Tier 1 Participating Member that a pending/expected file exchange will take place using a bilaterally agreed contingency exchange arrangement (as set out in Appendix L). Contingency Procedures means the procedures in Part 10 and in any contingency plans formulated and approved by the Management Committee under Regulation 9.1. Credit Items includes all credit payment instructions contained in a File, addressed to a Ledger FI, except as may be specifically excluded by the Regulations or these Procedures. Credit User means a person who issues Credit Items through a User FI for distribution to a Ledger FI. Note: A person does not become a Credit User by reason only of issuing Reversing Items. Credit User Application means an application in the form of Appendix A2. Customer means the customer of the Ledger FI: (a) (b) (c) into whose account(s) a Users Record Type 1 Credit Items are credited; or from whose account(s) a Users Record Type 1 Debit Items are debited; or in respect of whose account(s) a combination of (a) and (b) occurs.
Last amended effective 11/6/08 Last amended effective 28/10/96 Last amended effective 4/8/2000 Inserted effective 28/10/96

Last amended effective 1/11/08

Inserted effective 30/6/03

Inserted effective 28/10/96

Customer Claim means a document in such form as the relevant Ledger FI may approve and, at a minimum, satisfying the requirements of clause 7.8(a)(iii). Daily Summary Report means a report containing any additions, deletions or other changes to Users' details, an example of which is set out in Appendix A3. DDR means a Direct Debit Request. DDR Compliance Date means the date approved and published by the Management Committee on and from which Debit Users will be required to ensure that all debit authorities for BECS given by Customers are Direct Debit Requests.

Inserted effective 31/3/2000

Inserted effective 31/3/2000

Australian Payments Clearing Association Limited 1.2

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

DDR Implementation Date means the date approved and published by the Management Committee for the introduction of Direct Debit Requests. DDR Service Agreement means a Debit Users binding agreement given for the benefit of a Customer as to the basis on which it will provide direct debit services to that Customer through BECS, in such form as the relevant Sponsor may approve, which if given in writing is substantially in the form of Appendix A28 and, at a minimum, satisfying the requirements of clause 7.11. DDR Transitional Period means the period commencing on the DDR Implementation Date and ending on the day immediately preceding the DDR Compliance Date. Debit Items includes all debit payment instructions, contained in a File, addressed to a Ledger FI, except as may be specifically excluded by the Regulations or these Procedures. Debit User means a person who issues Debit Items through a User FI for distribution to a Ledger FI. Note: A person does not become a Debit User by reason only of issuing Reversing Items. Debit User - Change of Name or Other Details Advice means an advice of supplementary change of name or other details for a Debit User in the form of Appendix A17.
Debit User Indemnity: Deleted effective 31/3/2000.

Inserted Effective 31/3/2000

Last amended effective 23/12/09

Inserted effective 31/3/2000

Last amended effective 4/8/2000

Inserted effective 14/12/95

Debit User - Transfer of Business Advice means an advice of supplementary transfer of business details for a Debit User in the form of Appendix A18. DE File Reversal Specifications means the technical specifications set out in Appendix C5 for Reversal Files. DE File Specifications means DE File User Item Specifications, DE File Return Specifications, DE File Refusal Specifications and DE File Reversal Specifications. (See Part 12 and Appendices C1, C2, C3 and C5). DE File User Item Specifications means the technical specifications set out in Appendix C1 for Record Type 1 Credit Items and Debit Items issued by Users. DES Advice means a Direct Entry System Advice in the form of Appendix A4. Detail Record in relation to any Item, means the record on the relevant File which contains information on that Item. (See Appendices C1, C2, C3 and C5). DE File Refusal Specifications means the technical specifications set out in Appendix C3 for Refusal Files. DE File Return Specifications means the technical specifications set out in Appendix C2 for Return Files. Direct Debit Request means an authority and request to debit amounts to a specified account of a Customer with the Ledger FI satisfying the requirements of clause 7.4 and which, if given in writing, is substantially in the form of Appendix A27. (Note: a requirement for writing is interpreted in clause 1.2 (Interpretation).
.

Inserted effective 14/12/95

Inserted effective 4/8/2000

Last amended effective 4/8/2000

Inserted effective 28/10/96

Last amended effective 4/8/2000

Inserted effective 28/10/96

Inserted effective 28/10/96

Last amended effective 23/12/09

Australian Payments Clearing Association Limited 1.3

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Direct Entry Returned or Refused - Debit Voucher: Deleted effective 31/03/04.

Disabling Event means any: (a) (b) (c) processing, communications or other failure of a technical nature; inaccessibility (total or partial) of facilities by means of which exchanges are conducted; or manifestation of industrial action,

Last amended effective 4/8/2000

which affects, or may affect, the ability of any Participating Member to participate to the normal and usual extent in exchanges of Items (including Record Type 1 Items issued by any User, Returned Items, Refused Items and Reversing Items). Disabled Participating Member means a Participating Member experiencing a disabling event which affects their ability to participate in the normal (primary) exchange and/or processing of data file(s) in the Clearing System.
Error Adjustment Voucher: Deleted effective 31/03/04.
Inserted effective 23/09/02

Error of Magnitude is an error (or a series of errors on the one exchange) of or exceeding $2 million. Exchange Summary means a file complying with the specifications for the Exchange Summary Data File Transfer Facility which can be found on the Companys extranet or a summary document in the form of Appendix A12. "Exchange Summary Data File Transfer Facility" means the Reserve Bank of Australia's electronic file transfer facility that must be used to: (a) send provisional settlement figures and / or revised settlement figures to the Collator; and (b) receive reconciled provisional settlement figures, reconciled revised settlement figures, schedules of revised settlement figures, final settlement figures and final net cross Clearing System settlement figures from the Collator. (Note: the specifications for the Exchange Summary Data File Transfer Facility can be found on the Companys extranet.) Failure to Match Rules has the meaning ascribed to that term in clause 9.2.
File Cleansing: Deleted effective 14/12/95 File Cleansing Lists: Deleted effective 14/12/95

Last amended effective 12/7/09

Last amended effective 5/12/07

Last amended effective 5/12/07

File means one or more Items in an electronic format (and, for the avoidance of doubt, includes Files containing Record Type 1 Items issued by any User, Return Files, Refusal Files and Reversal Files). (See Part 12 and Appendices C1, C2, C3 and C5 for required specifications). Form PD-C means a request and authority so termed made in writing by a Customer before the DDR Compliance Date to and in favour of a Ledger FI, substantially in the form of Appendix A7. Government File means a File containing Government Payments.

Last amended effective 4/8/2000

Last amended effective 31/3/2000

Last amended effective 1/04/02

Australian Payments Clearing Association Limited 1.4

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Government Payment means a Credit Item which is:

Last amended effective 1/04/02

(a)

initiated by a Credit User which is: (i) a Commonwealth or State Government department, instrumentality or agency, or

(ii) some other statutory body wholly owned or controlled, directly or indirectly, by the Commonwealth Government or a State Government and approved by the Management Committee, and (b) subject to arrangements to the contrary under any bilateral agreement, transmitted in a File which specifies as the PD Day the next business day after the date of the exchange of the File and with a Receiving Dataset nominated under clause 6.7(f).
Inserted effective 31/03/04

Guidelines for Establishing Direct Debit Requests over the Internet means the document entitled as such issued and varied by the Company from time to time including any substitute document howsoever entitled. Inter-bank Settlement Interest Rate means the interest rate determined in accordance with clause 9.4. Inter-organisation Compensation Rules means the document (as amended or replaced) known as the Inter-organisation Compensation Rules, Publication No. 6.1 of the Company. Items means Credit Items and Debit Items (and, for the avoidance of doubt, includes Record Type 1 Items issued by any User, Returned Items, Refused Items and Reversing Items). Ledger FI means in relation to an Item, the Participating Member or Appointor to which the Item is addressed.
Linking Indemnity: Deleted effective 31/3/2000.

Inserted effective 13/06/01

Last amended effective 4/8/2000

Lodgement FI means a Participating Member or Appointor with which Files are lodged. Management Committee means the committee constituted pursuant to Part 7 of the Regulations. Missorted Item means an Item received in an exchange and for which the BSB Number does not belong to the Receiving Member or any Appointor of that Receiving Member. Morning Settlement Session means the settlement session conducted through the Reserve Bank Information and Transfer System between 7.30 am to 8.45 am, Monday to Friday. Multi-User File means media containing more than one File.
National Collator: Deleted effective 20/08/04.
Inserted effective 28/10/96

Inserted effective 18/01/02

National Public Holiday means any day which is gazetted as a public holiday in each State and Territory in Australia.
Notification of Reversal of Items Sent in Error: Deleted effective 11/6/08.

Inserted effective 17/01/11

Notice of Redirection of a Direct Entry Item means a notice in the form set out in Appendix A10.

Australian Payments Clearing Association Limited 1.5

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Notice of Unapplied Credit Item (Superannuation) means a document substantially in the form of Appendix A26. 9.00am Funds has the same meaning as 9am Funds in the RITS regulations. Official Government File Exchange Time means the times referred to as such in clause 4.2. Official Exchange Times means the times referred to as such in clause 4.2. Participating Member means a body corporate who in accordance with the Regulations is a participant in BECS. Personal Account means an account that is owned by one or more persons (either individually or jointly) for non-business purposes. Any account owned by a corporation is not a Personal Account. PD Day means in relation to a File the day on which that File is to be processed, following exchange of the File by the Lodgement FI, and in relation to an Item, the day on which the File containing that Item is to be processed following exchange of the File by the Lodgement FI. PDN means a Processing Difficulty Notification form, substantially in the form of Appendix J, used by a Participating Member to notify APCA of a Disabling Event in accordance with paragraph 3.3 of Appendix I. Recall means a recall of the entire amount of an Item or File prior to the exchange of the Item or File. Receiving Dataset means, in relation to the transmission of a File, the receiving destination details for that File, nominated by the Ledger FI to which that File is addressed. Receiving Member in relation to any Item (including Record Type 1 Items issued by any User, Returned Items and Refused Items), means the Participating Member (whether or not it is the institution to which that Item is addressed) to which such Item is in fact delivered by the Sending Member. Record Type has the same meaning as in clause 12.2 and Appendices C1, C2, C3 and C5, and clause 14.2 and Appendix C6. Any reference to any particular Record Type means that particular Record Type specified in clause 12.2 and, as applicable, the DE File User Item Specifications (Appendix C1), DE File Return Specifications (Appendix C2), DE File Refusal Specifications (Appendix C3) and DE File Reversal Specifications (Appendix C5), and in clause 14.2 and, as applicable, the Summary File Specification (Appendix C6). Refusal means refusal to accept a Returned Item. Refusal Codes means the codes specified as such in clause 4.8. Any reference to a particular Refusal Code means that particular Refusal Code specified in clause 4.8. Refusal File means a File containing Refused Items. (See Part 12 and Appendix C3 for required Specifications). Refused Item means, in relation to any Returned Item, an Item which is used to effect Refusal (using Record Type 3) by the Receiving Member of that Returned Item. Regular Arrangements List means a list of Debit Items and Credit Items applied to an account within the last 13 months substantially in the form of Appendix A25. Regulations means the regulations of BECS as prescribed by the Company.

Inserted effective 1/12/08

Last amended effective 1/04/02

Inserted effective 28/10/96

Inserted effective 29/12/08

Last amended effective 18/01/02

Inserted effective 23/09/02

Inserted effective 18/01/02

Last amended effective 28/10/96

Last amended effective 28/10/05

Inserted effected 28/10/96

Inserted effective 28/10/96

Inserted effective 28/10/96

Inserted effective 28/10/96

Inserted effective 1/11/08

Australian Payments Clearing Association Limited 1.6

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Return means return of the value of a Credit Item or Debit Item, in accordance with clause 5.16, to the person entitled to receive such value after the exchange of that Item. Return File means a File containing Returned Items (See Part 12 and Appendix C2 for required specifications). Returned Item means, in relation to any Record Type 1 Item issued by a User, an Item which is used to effect return (using Record Type 2) by the Receiving Member of that Users Item. Returning/Refusing FI ID Number means the special identification number assigned to a Participating Member by the Company under clause 4.16. Reversal means the reversal, in accordance with clause 5.16A, of a Record Type 1 Item, issued by a User, Bureau or Sending Member that has been sent in error. Reversal File means a File containing Reversing Items (see Part 12 and Appendix C5 for required specifications). Reversing FI means a Participating Member that initiates a Reversal File. Note: The Reversing FI ID Number of that Participating Member appears in the Reversal File. Reversing FI ID Number means the special identification number assigned to a Participating Member by the Company under clause 4.17. Reversing Item means an Item which is used to effect a Reversal. RITS means the Reserve Bank Information and Transfer System. Sending Member in relation to any Item (including Record Type 1 Items issued by any User, Returned Items and Refused Items), means the Participating Member which delivers that Item to a Receiving Member. Settlement Session has the same meaning as in the RITS regulations.
Specified Location: Deleted effective 28/10/96

Last amended effective 24/11/03

Inserted effective 25/5/07

Inserted effective 4/8/2000

Inserted effective 28/10/96

Last amended effective 25/5/07

Inserted effective 25/5/07

Inserted effective 4/8/2000

Inserted effective 4/8/2000

Inserted effective 4/8/2000

Last amended effective 28/10/96

Sponsor means a Participating Member which sponsors a Debit User pursuant to Part 7. Summary File means a File containing summary information relating to a File or Government File (see Part 14 and Appendix C6 for required specification). Summary File Specification means the technical specification set out in Appendix C6 for a Summary File. Superannuation Entity has meaning given to that term in the Superannuation Industry (Supervision) Act 1993. Switch of Financial Institution and Account Details means a direction to a Debit User or Credit User to change the account to be debited or credited substantially in the form of Appendix A24 that has been signed by the Customer. TNA means an authority entitled "Transaction Negotiation Authority" given by a TNA Issuer to a Lodgement FI to process a File containing a User's Credit Items, the total of which do not exceed a specified amount during a specified frequency in the form set out in Appendix A8. TNA Issuer in relation to a TNA in support of a Credit User's File means the relevant User FI or, to the extent that the Credit User's funding account is held with a Participating Member or Appointor which is not the User FI, that Participating Member or Appointor.
Inserted effective 28/10/05

Inserted effective 28/10/05

Inserted effective 1/12/08

Inserted effective 1/11/08

Last amended effective 14/12/95

Inserted effective 14/12/95

Australian Payments Clearing Association Limited 1.7

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Trace Record means the BSB Number and account number to which an Item (including any Record Type 1 Item issued by any User, any Returned Item, any Refused Item and any Reversing Item) must be returned if it cannot be applied. A Trace Record must be the Users own account or an account which the User has authority to operate and/or use as a Trace Record. The Trace Record is to be included in character positions 81 to 96 inclusive of a Detail Record (refer clause 5.11 and Appendix C1). (Note: In many cases the Trace Record is also used to satisfy the requirements of the AntiMoney Laundering and Counter-Terrorism Financing Act 2006 (Cth) concerning the inclusion of Tracing Information in electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) Trace Record Institution in relation to any Item (including Record Type 1 Items issued by any User, Returned Items, Refused Items and Reversing Items) means the financial institution specified (by reference to its BSB Number) in the Trace Record for that Item. User means a Debit User or a Credit User. User FI means, in respect of a User at any time, the Participating Member or Appointor which at that time represents the User in BECS. User Identification Number means in relation to a User, its User Identification Number assigned to it in accordance with clause 5.12. Valid Claim has the meaning ascribed to that term in clause 7.6. Interpretation 1.2 In these Procedures, except where the context requires otherwise: (a) (b) (c) (d) words importing any gender include the other genders; person includes a firm, a body corporate, an unincorporated association or an authority; the singular includes the plural and vice versa; and a reference to a statute, code or the Corporations Law (or to a provision of a statute, code or the Corporations Law) means the statute, the code, the Corporations Law or the provision as modified or amended and in operation for the time being, or any statute, code or provision enacted in lieu thereof and includes any regulation or rule for the time being in force under the statute, the code, the Corporations Law or the provision; a requirement to: (i) (ii) (iii) give any information in writing (which, without limitation, includes making a claim or request or providing an authority, notification or advice); retain a document; or produce or deliver a document,

Last amended effective 27/07/07

Last amended effective 4/8/2000

Last amended effective 31/3/2000

Last amended effective 31/3/2000

(e)

Inserted effective 31/3/2000

may be done by means of an electronic communication generated by a method which enables that information or the information contained in that document to be readily accessible so as to be useable for subsequent reference and which provides a reasonable means of assuring the integrity of that information or the information contained in that document, except to the extent the validity of that means of electronic communication is otherwise limited by any applicable law;

Last amended effective 31/03/04

Australian Payments Clearing Association Limited 1.8

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

(f)

a requirement for a signature of a person may be met in relation to an electronic communication if a method is used to identify that person and indicate that persons approval of the information communicated, provided that: (i) the person to whom the signature is required to be given consents to the signature being given by way of that method (The requirement in this clause 1.2(f)(i) does not apply if a reproduction of the Customers signature appears in the electronic communication); and either: (A) having regard to all the relevant circumstances at the time the method was used, the method was as reliable as reasonably appropriate for the purposes for which the information was communicated; or if the Management Committee has specified that such method be in accordance with particular information technology requirements (including whether hardware, software or otherwise) or procedural/process requirements, these requirements have been met.

Last amended effective 10/09/2001

Last amended effective 1/11/08

(ii)

Last amended effective 31/03/04

Last amended effective 31/03/04

(B)

Last amended effective 31/03/04

(g)

a reference to a Direct Debit Request in relation to a Debit User is to be taken to include: (i) (ii) a Form PD-C referable to that Debit User; and a Form PD-C or a Direct Debit Request referable to a third-party Debit User from which the relevant Debit User has acquired a business involving direct debit arrangements under BECS, which continued after that acquisition for the benefit of the relevant Debit User; and

Inserted effective 31/3/2000

(h)

a reference to a Debit User making payment otherwise than in accordance with a Direct Debit Request or failing to make payment in accordance with a Direct Debit Request is to be taken to include any failure on the part of the Debit User to debit in accordance with the debit arrangements set out in the Debit User's DDR Service Agreement applicable to it at the relevant time.

Inserted effective 31/3/2000

1.3

Words defined in the Corporations Law have, unless the contrary intention appears, the same meaning in these Procedures. Words defined in the Regulations have, unless the contrary intention appears, the same meaning in these Procedures. These Procedures have been determined by the Management Committee and take effect on the date specified by the Chief Executive Officer pursuant to Regulation 1.6. Headings are inserted for convenience and do not affect the interpretation of these Procedures.

1.4

1.5

1.6

Inconsistency with Articles or Regulations 1.7 If a provision of the Regulations or these Procedures is inconsistent with a provision of the Articles, the provision of the Articles prevails. If a provision of these Procedures is inconsistent with a provision of the Regulations, the provision of the Regulations prevails.

1.8

Australian Payments Clearing Association Limited 1.9

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 1 Preliminary

Governing Law 1.9 These Procedures are to be interpreted in accordance with the same laws which govern the interpretation of the Articles.

Copyright 1.10 Copyright in these Procedures is vested in the Company.

Application of Procedures 1.11 The procedures contained in these Procedures apply to the clearing system commonly known or referred to as the direct entry system, whereby payment instructions are exchanged electronically in bulk. If any other bulk electronic clearing systems evolve over time which are subject to the Regulations and for which the Management Committee becomes responsible, additional separate procedures will be required for those systems. The next page is 2.1

Australian Payments Clearing Association Limited 1.10

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 2 Effect

PART 2

EFFECT

These Procedures have the effect set out in Part 2 of the Regulations.

The next page is 3.1

Australian Payments Clearing Association Limited 2.1

[ABN 12 055 136 519] Amendment No. E004, issued as CS2/r&p/004.01

Bulk Electronic Clearing System (CS2) PROCEDURES Part 3 Procedures and Amendment

PART 3

PROCEDURES AND AMENDMENT

Conduct of Clearings 3.1 Pursuant to Regulation 11.1 and in addition to and subject to the Regulations, the conduct of clearings effected between Participating Members and the settlement of balances arising as a result of the exchange of Items must be undertaken in accordance with the practices, procedures, standards and specifications specified in these Procedures.

Amendment 3.2 These Procedures may be varied by the Management Committee in accordance with Regulation 11.2 and clause 3.3 of these Procedures. Any variation to these Procedures must contain an editorial note setting out the effective date of such variation. Each: (a) Participating Member must notify the Company of any changes to its contact points as specified in Appendix B in accordance with clause 4.1; and (b) Tier 1 Participating Member must notify the Company of any changes to its Primary Exchange Arrangements as specified in Appendix K or its Contingency Exchange Arrangements in Appendix L in accordance with clause 10.2. The Chief Executive Officer may vary Appendix B, Appendix K and Appendix L in accordance with any such notification without the need to obtain the approval of the Management Committee or any other person, provided that a variation to Appendix K or Appendix L may only be made if both of the relevant Tier 1 Participating Members have notified the Company of the change. The Chief Executive Officer may vary Appendix F, Appendix G1 and Appendix G2 as may be required to ensure that they are accurate and up to date without the need to obtain the approval of the Management Committee or any other person. A variation made by the Chief Executive Officer pursuant to this clause 3.3 will, upon publication by the Company, be binding on Participating Members.
Last amended effective 11/6/08

3.3

Last amended effective 11/6/08

Last amended effective 11/6/08

Last amended effective 11/6/08

Last amended effective 11/6/08

The next page is 4.1

Australian Payments Clearing Association Limited 3.1

[ABN 12 055 136 519] Amendment No. E038, issued as CS2/r&p/004.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 4 General Operational Requirements

PART 4

GENERAL OPERATIONAL REQUIREMENTS


Last amended effective 11/6/08

Centralised Contact Point Details in Appendix B 4.1 Each Participating Member must nominate, in writing to the Company, contact points for the handling of various operational issues or processes as specified in these Procedures. Details for these contact points are published in Appendix B Centralized Contact Points. Participating Members must advise the Company, in writing, of changes to these contact details, not less than 15 business days prior to such changes taking effect, clearly identifying the effective date in their advice. BSB Number 4.1A To facilitate participation in BECS each Participating Member and each other financial institution which participates in BECS must have a BSB Number. If a Participating Member or other financial institution has not already been allocated a BSB Number by virtue of its participation in another clearing system managed by the Company (which BSB Number is also valid for BECS), a prospective Participating Member must request allocation of a BSB Number from the Company when applying to join BECS. Any other financial institution must have or receive a BSB Number from the Company before it takes any action in connection with BECS. Times of Exchange 4.2 Official Exchange Times for Files other than Government Files are 10.30pm on the business day prior to PD Day, and 10.00am, 1.00pm, 4.00pm, 6.30pm and 8.15 pm Sydney time on PD Day each Monday to Friday, excluding National Public Holidays. Official Exchange Times for Government Files are 7.00 am, 6.15 pm and 8.00 pm Sydney time each Monday to Friday excluding National Public Holidays on the business day prior to PD Day. Exchanges on any day on which they are permitted must be completed by 8.30 pm. Each Tier 1 Participating Member may only commence transmitting Files (including Files containing Record Type 1 Items issued by any User, any Return Files, any Refusal Files): (a) (b) (c) with respect to Files other than Government Files, at any Official Exchange Time; with respect to Government Files, at any Official Government File Exchange Time; or otherwise by bilateral agreement.

Last amended effective 11/6/08

Last amended effective 11/6/08

Last amended effective 11/6/08

Last amended effective 17/01/11

Last amended effective 1/04/02

Last amended effective 1/04/02

Inserted effective 18/01/02

Each Tier 1 Participating Member must be ready and able to receive transmissions of Files commenced at any Official Exchange Time or Official Government File Exchange Time. Each Tier 1 Participating Member is encouraged to transmit Files other than Government Files at each of the Official Exchange Times, in particular at 4.00pm and 6.30pm Sydney time each Monday to Friday excluding National Public Holidays. Each Tier 1 Participating Member should ensure that each File transmitted by the Tier 1 Participating Member contains all Items available for exchange at that time.

Last amended effective 3/10/06

Last amended effective 17/01/11

Last amended effective 3/10/06

Australian Payments Clearing Association Limited 4.1

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 4 General Operational Requirements

For the avoidance of doubt and notwithstanding any other provision in these Procedures, if a File is exchanged at the 10.30pm Official Exchange Time then: (a) (b) the PD Day for that File is the business day after it is exchanged; and settlement for that File is to be effected, in accordance with Part 9, on the business day after PD Day.

Last amended effective 14/9/09

Tier 1 Participating Members may agree bilaterally to exchange Files at other times, provided the Tier 1 Participating Members observe all other provisions of the Regulations and these Procedures. 4.3 Settlement of obligations arising from exchange of Files, other than Government Files, will be effected in terms of Part 9 of these Procedures regardless whether exchanges are conducted at Official Exchange Times or by bilateral agreement. Settlement of obligations arising from exchange of Government Files will be effected in terms of clause 9.1A of these Procedures, regardless of whether exchanges are conducted at Official Government File Exchange Times or by bilateral agreement. Exchange of Items (other than by bilateral agreement) will not take place on National Public Holidays. On any day other than a National Public Holiday, Tier 1 Participating Members in those States/Territories which are closed (for example, because of State/Territory public holidays) must be available to receive transmissions from all other Tier 1 Participating Members. 4.4 Where normal operations have been adversely affected by extraordinary circumstances, the Chief Executive Officer may vary the Official Exchange Times, Official Government File Exchange Times and/or the time by which exchanges must be completed. The Chief Executive Officer will notify all Participating Members in writing of any variations under this clause which apply overnight or longer.

Last amended effective 3/10/06

Last amended effective 1/04/02

Last amended effective 17/01/11

Last amended effective 1/04/02

DE File Specifications 4.5 All Items (including Record Type 1 Items issued by any User, Returned Items, Refused Items, and Reversing Items) and Files (including Files containing Record Type 1 Items issued by any User, Return Files, Refusal Files and Reversal Files) exchanged between Participating Members must conform with requirements set out in Part 12 and the applicable DE File Specifications in Appendices C1, C2, C3 and C5.
Last amended effective 4/8/2000

Transaction Codes 4.6 The following transaction codes form part of the DE File User Item Specifications and apply to Record Type 1 Items issued by Users and exchanged in BECS. All Participating Members must ensure that these transaction codes are used where applicable: 13 50 51 52 53 54 55 56 57 externally initiated Debit Items externally initiated Credit Items with the exception of those bearing transaction codes 51-57 inclusive Australian government security interest basic family payments/additional family payment pay pension allotment dividend debenture/note interest.
Inserted effective 28/10/96

Australian Payments Clearing Association Limited 4.2

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 4 General Operational Requirements

Clauses 4.7 to 4.16 inclusive are Confidential

Reversing FI ID Number 4.17 To facilitate Reversals, each Participating Member must have a special identification number in the form 997XXX (where XXX is the relevant BSB Number). That number is referred to in these Procedures as the Reversing FI ID Number. The Company assigns the Reversing FI ID Numbers to Participating Members (see Appendix G1).
Inserted effective 4/8/2000

Processing by Account Number Details only 4.18 Ledger FIs are entitled to rely solely on Account Number Details in all circumstances when processing Items received by them, regardless of whether any account name details are transmitted with the Account Number Details or are otherwise known to the Ledger FI. Ledger FIs are not obliged (including under any duty to the Lodgement FI which may but for this clause 4.18 arise at law or in equity) to check whether the Account Number Details are correct. (a) Subject to clause 4.19(b), if an amount has been credited or debited by the Ledger FI in accordance with the Account Number Details provided by the Lodgement FI but the amount has been credited or debited to the wrong account, then as between the Lodgement FI and the Ledger FI, the Ledger FI is not liable to compensate the Lodgement FI, any person on whose behalf the Lodgement FI exchanges an Item, the intended beneficiary of a Credit Item, a customer whose account has been wrongly debited or any other person for any loss or damage. In these circumstances, liability, if any, for compensating any person for any loss or damage which a person may suffer directly or indirectly in connection with the wrong crediting or debiting is the responsibility of the Lodgement FI. If a Ledger FI suffers loss or damage, or receives any claim for loss or damage arising because the Ledger FI has relied solely on Account Number Details provided by the Lodgement FI when processing an Item, the Lodgement FI must fully indemnify the Ledger FI in relation to such loss, damage or claim. If an amount has been credited or debited by the Ledger FI in accordance with the Account Number Details provided by the Lodgement FI but the amount has been credited or debited to the wrong account due to an account number being reissued or duplicated by the Ledger FI, then as between the Lodgement FI and the Ledger FI, the Lodgement FI is not liable to compensate the Ledger FI, any person on whose behalf the Lodgement FI exchanges an Item, the intended beneficiary of a Credit Item, a customer whose account has been wrongly debited or any other person for any loss or damage. In these circumstances, liability, if any, for compensating any person for any loss or damage which a person may suffer directly or indirectly in connection with the wrong crediting or debiting is the responsibility of the Ledger FI. If a Lodgement FI suffers loss or damage, or receives any claim for loss or damage arising because the Ledger FI has relied solely on Account Number Details provided by the Lodgement FI when processing an Item, but the loss, damage or claim arises because the relevant account number had been reissued or duplicated by the Ledger FI, the Ledger FI must fully indemnify the Lodgement FI in relation to such loss, damage or claim. For the purposes of clauses 4.18 and 4.19, Account Number Details means the BSB number and the account number or, in the case of a Ledger FI which has a unique account numbers system, the account number only. The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) requires that certain information must be included in electronic funds transfer instructions. Please refer to Part 5 of the Act for details.)

Last amended effective 3/05/04

Last amended effective 3/05/04

4.19

Last amended effective 3/05/04

(b)

Inserted effective 3/05/04

(Note: 1.

2.

Inserted effective 16/04/07

Australian Payments Clearing Association Limited 4.3

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 4 General Operational Requirements

Summary File Specification 4.20 A Summary File must accompany each File and Government File. A Summary File must conform with requirements set out in Part 14 and the Summary File Specification in Appendix C6.

Inserted effective 28/10/05

Inserted effective 28/10/05

Encryption of Direct Connection 4.21 Each Tier 1 Participating Member must ensure that all of its Direct Connections to Tier 1 Participating Members are encrypted using triple DES or its equivalent. (Note: It is recommended that Direct Connections between each Representative and Appointor should be encrypted using triple DES or its equivalent.) The next page is 5.1

Inserted effective 23/12/2009

Inserted effective 23/12/2009

Australian Payments Clearing Association Limited 4.4

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 5 General Requirements in Relation to Users

PART 5

GENERAL REQUIREMENTS IN RELATION TO USERS

Approval and Termination 5.1 A User FI must ensure that a prospective User is approved in accordance with these Procedures before the processing of any Items belonging to that User takes place. See clause 5.2 below. If the User FI gives written notice of termination of its arrangements with a User to the User then the arrangements between the User and its User FI will be terminated as to future Items but without prejudice to any right or liability arising under the terms of any proprietary arrangements with regard to Debit Items between them or under any Credit User Application in force in accordance with these Procedures. A User FI must notify the details of any of its new Users, any changes to any existing User and termination of any arrangements with its Users to the Chief Executive Officer in accordance with clause 5.3. A Lodgement FI must give at least 30 days prior written notice to all Tier 1 Participating Members before it exchanges any Government Files for the first time in BECS. The notice must specify the date on which the Lodgement FI will commence exchanging Government Files in BECS (which must not be sooner than 30 days after the expected date of receipt of the notice by all Tier 1 Participating Members). Compliance by Users 5.2 User FIs must ensure that Users wishing to: (a) issue Credit Items (including by using a Bureau), comply with the requirements specified in Part 6; and issue Debit Items, comply with the requirements specified in Part 7.
Inserted effective 22/04/02 Last amended effective 31/3/00

(b)

Notification of User Details to the Chief Executive Officer 5.3 In the case of a Credit User, the User FI, and in the case of a Debit User, the Sponsor, must notify the details of any new User, any changes to any existing User and any termination of arrangements with a User to the Chief Executive Officer. Notification must be given using: (a) the DES Advice or by way of input to the Company's records using the Company's software program (see Part 13); or the Debit User - Change of Name or Other Details Advice (Appendix A17) and/or a Debit User - Transfer of Business Advice (Appendix A18) if the notification is by facsimile transmission; or an electronic version of Appendix A17 and/or Appendix A18 if the notification is by either e-mail or using the secure file transfer facility available on the APCA Extranet.
Last amended effective 24/11/97

Last amended effective 1/07/02

(b)

Last amended effective 1/07/02

(c)

Last amended effective 30/06/05

Upon receipt of any notifications referred to above, the Chief Executive Officer will in turn notify all Participating Members by means of a Daily Summary Report, which will issue no later than the following business day after such receipt.

Australian Payments Clearing Association Limited 5.1

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 5 General Requirements in Relation to Users

A User FI must ensure that a Credit User does not, and a Sponsor must ensure that a Debit User does not, commence lodging Items or Items reflecting changed details until 3 business days (inclusive of State/Territory public holidays where these fall on a business day) after the issue of the relevant Daily Summary Report.
Paragraph (including sub-clauses (a) and (b) deleted. Effective 31/3/00.

Last amended effective 26.07.10

That period is to be inclusive of State/Territory public holidays where these fall on a business day. 5.4 5.5 5.6 [Deleted] [Deleted] [Deleted]

Last amended effective 04/03/08

Deleted effective 14/12/95

Deleted effective 14/12/95

Deleted effective 14/12/95

Change of Credit User FI or Debit User Sponsor 5.7 If a Credit User changes its User FI, the new User FI must ensure that the Credit User executes fresh Credit User documentation as required by these Procedures. If a Debit User changes its Sponsor, the new Sponsor must promptly notify the Chief Executive Officer using a Debit User - Change of Name or Other Details Advice. The outgoing Sponsor (for Debit Users only) must notify the Company in writing of it ceasing to be a Sponsor in addition to notifying details of termination of arrangements with a User in accordance with clause 5.3. The outgoing User FI (for Credit Users only) is not required to notify the Company of it ceasing to be the User FI. Any person making a claim under a Credit User Application must make a claim under the most recently executed Credit User Application existing as at the date of the occurrence of the event or circumstance in respect of which the claim is being made. When a User changes to a new User FI (irrespective of whether that User FI is also the relevant Sponsor), some operational aspects which should be considered by the new User FI include: (a) establishing a new TNA in accordance with clause 6.9 for those Users lodging Credit Items through a Bureau or Lodgement FI; changing the name of the User FI on the descriptive record of the User's File; and changing the BSB Number and account number in the Trace Record on the User's File.

Last amended effective 23/12/09

Last amended effective 31/3/00

Last amended effective 23/12/09

Inserted effective 23/12/09

Last amended effective 31/3/00

Last amended effective 1/4/96

(b) (c)

Cancellation of the existing TNA is the responsibility of the outgoing User FI. Liquidation or Insolvency of User 5.8 In the event of the liquidation or insolvency of a User, the User may continue to have access to BECS if: (a) the User FI and, in the case of the Debit User, the Sponsor is prepared to continue its arrangements with the User. If a Sponsor is prepared to continue to permit a Debit User access to BECS it does so at its own risk under these Procedures, in particular, clauses 7.5 and 7.6 of these Procedures; and Australian Payments Clearing Association Limited 5.2
Last amended effective 31/3/00

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 5 General Requirements in Relation to Users

(b)

the liquidator, trustee in bankruptcy or other person responsible for the administration ("Administrator") of that User confirms that the User, under the administration of the Administrator, wishes to continue using BECS and, in the case of a Credit User, confirms the terms of the Credit User Application.

Last amended effective 31/3/00

If the relevant Sponsor is prepared to continue its arrangements with the Debit User, it must notify the Chief Executive Officer as soon as practicable, using a Debit User - Change of Name or Other Details Advice. Change of User's Name and/or Transfer of Business 5.9 The following provisions apply whenever there is a change of a User's name or where business of a User, being business which involves direct debit or credit arrangements under BECS, is transferred to another User (for example as a result of a takeover or merger of the User by or with another User or a sale of the business or part of the business of the User to another User) (in this clause 5.9 a transfer of business of the kind referred to above is called a "transfer of business" and the User to which business is transferred is called the "transferee User"): (a) if the User which changes its name or transfers business is a Credit User: (i) (ii) (b) the User FI must ensure that the User or the transferee User, as the case may be, executes and delivers to the User FI a Credit User Application; and the User FI must replace the TNA (if applicable);

Inserted effective 14/12/95

Last amended effective 31/3/00

if the User which changes its name or transfers its business is a Debit User, the arrangements between the Sponsor and the User, or the transferee User (as applicable) will be proprietary (including without limitation indemnity arrangements between the transferee User and the Sponsor in respect of claims arising in connection with Direct Debit Requests originally given to the User). The Sponsor should advise the User or the transferee User (as applicable) to notify all of its clients of the circumstances of the change as soon as practicable and in any case within a period specified by the Sponsor. The relevant Sponsor must also assess, and is solely accountable for determining, the transferee Users suitability for continued access to BECS as Debit User; the relevant User FI or Sponsor (as the case may be) must notify appropriate details of the change in name or transfer of business (using, in the case of a Debit User, a Debit User Change of Name or Other Details Advice or a Debit User - Transfer of Business Advice, as applicable) to the Chief Executive Officer who will then notify all Participating Members in accordance with clause 5.3; and the relevant user FI or Sponsor (as the case may be) in respect of Credit Users and Debit Users is to instruct: (i) (ii) the User, in the event of a change of name; or the transferee User, in the event of a transfer of business,

Last amended effective 31/3/00

(c)

Last amended effective 14/12/95

(d)

to change the details on the User's, or transferee User's, File (for example, the User Identification Number, name of remitter, User preferred name and Trace Record). Each of the things required to be done under paragraphs (a), (b), (c) and (d) of this clause 5.9 should ideally be done within a reasonable time prior to lodgement of the first File under the User's new name (in the case of a name change only) or the transferee User's name (in the case of a transfer of business).

Australian Payments Clearing Association Limited 5.3

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 5 General Requirements in Relation to Users

5.10

[Deleted]

Deleted effective 31/3/00

Trace Record 5.11 Each User FI must ensure that each User which it represents in BECS includes in each of that Users Files in character positions 81 - 96 of Record Type 1 a correct Trace Record to which an Item must be returned electronically if it cannot be applied. A Trace Record is usually the same for each Item on any one File but may be different for some Items or for groups of Items if required by the User. A financial institution which is not the User FI may be specified in the Trace Record, but only if it has given its prior written consent to the User FI. (Note: In many cases the Trace Record is also used to satisfy the requirements of the AntiMoney Laundering and Counter-Terrorism Financing Act 2006 (Cth) concerning the inclusion of Tracing Information in electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) User Identification Numbers 5.12 Each User must have a unique User Identification Number issued to it. A Participating Member may from time to time contact the Chief Executive Officer and request a block allocation of User Identification Numbers. The Chief Executive Officer will, upon such request, make a block allocation available if satisfied that the Participating Member's annual usage justifies it. Where a block allocation is made available, the Participating Member will issue User Identification Numbers from the block allocation to its new Users. Alternatively, a request must be made to the Chief Executive Officer for the issue of a User Identification Number to each individual User and such request must include the full User name and other relevant details. In all cases, advices of newly approved Users and their User Identification Numbers must be notified to the Chief Executive Officer in accordance with clause 5.3. Details of Users and their User Identification Numbers will be recorded by the Company on its database system. Participating Members which issue User Identification Numbers from a block allocation must: (a) establish an appropriate central point or points within their institutions for assignment of User Identification Numbers. Where more than one point issues User Identification Numbers, schedules must be separated; guard against losing/misplacing schedules by placing these in a suitable binder/cover and retaining schedules at a readily locatable point; before issuing a User Identification Number, ensure that the User is not already recorded on the Company's database system as a User. If it is, consider treatment as an extension of usage of the system under the previously issued User Identification Number; and in the case of a proposed User which does not proceed to use BECS and whose details have not been notified to the Company, rule through the name of the User in the schedule and reissue the User Identification Number to another User.
Last amended effective 27/07/07

(b)

(c)

(d)

5.13

The Chief Executive Officer will arrange for periodic provision of updated diskettes containing User data from the Company's database, to any Participating Member which has formally requested it.
Clauses 5.14 to 5.22 inclusive are Confidential

The next page is 6.1 Australian Payments Clearing Association Limited 5.4
[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

PART 6

DIRECT CREDIT SYSTEM

Persons Authorised to Approve Credit Users 6.1 Any User FI may approve a person as a Credit User.

User FI Approval 6.2 A User FI must ensure that a prospective Credit User makes application to the User FI by lodging Credit User documentation in accordance with these Procedures and such other documentation as the User FI requires. Upon receipt of such documentation and if the User FI approves of the application, the User FI must obtain for, or issue to, the prospective Credit User a User Identification Number in accordance with clause 5.12 and notify the details of the prospective Credit User (including the name of any Bureau) to the Chief Executive Officer in accordance with clause 5.3. The User FI is not obliged to approve any application by a prospective Credit User. A User FI may approve a Credit User without reference to any Participating Members but before that approval it must: (a) subject to clause 6.4, ensure the proper completion, execution, stamping (where relevant) and maintenance of legally binding Credit User documentation (including a Credit User Application) prior to the prospective Credit User being permitted to lodge Credit Items in BECS. Credit User documentation must be made available by the User FI (by way of certified copy) to the Company and any Participating Member upon request; and if the User FI is not also the Lodgement FI, ensure the completion of a TNA prior to the prospective Credit User being permitted to lodge Credit Items in BECS.
Last amended effective 14/12/95

6.3

(b) 6.4

The requirement set out in clause 6.3(a) may be waived or varied with the prior written consent of the Management Committee. The Management Committee will provide its consent where the User FI undertakes to the satisfaction of the Management Committee to fulfil the obligations of both a Credit User and a User FI whether or not a Credit User Application is or has been obtained from the Credit User. In these circumstances, the documentation which exists between the User FI and the Credit User is proprietary.

User FI Responsibilities 6.5 A User FI which approves a Credit User must: (a) ensure that the Credit User: (i) completes and executes in a legally authorised manner all Credit User documentation as required by the User FI; and (ii) promptly verifies (by signature comparison or other means) and if verified processes a Switch of Financial Institution and Account Details. If there is any doubt as to the Customers authorisation, then the Credit User must contact the Customer to verify. (b) maintain control over the Credit User's lodgement of Credit Items and be solely accountable for terminating the Credit User's right to lodge Credit Items as it sees fit;
Inserted effective 1/11/08 Last amended effective 1/11/08

Australian Payments Clearing Association Limited 6.1

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

ensure that: (i) the Credit User has a correct Trace Record for each transaction on its File; and (ii) if the Trace Record Institution specified or to be specified in respect of the Credit Users Credit Items is not the User FI, that Trace Record Institution has consented in writing to be specified as the Trace Record Institution for that Users Credit Items. (c) If the User FI conducts the account nominated in the Trace Record, the User FI must accept every Returned Item which is sent to it electronically by the Ledger FI as a Record Type 2 in accordance with the Regulations and these Procedures (see in particular clauses 5.16A(f), 5.17, 5.18 and 8.1); except in relation to Government Payments, not exchange Credit Users Credit Items with a "Date to be Processed" in Record Type "0" other than on the date which is the date specified in that field (although future dated Credit Items may be exchanged with other financial institutions in accordance with bilateral arrangements); accept Returned Items on behalf of the Credit User where such Items were incorrectly applied to a Ledger FI account by virtue of incorrect details being supplied by the Credit User; notify the Company within the appropriate time frame prior to change of Credit User name, mergers and the like taking effect in accordance with clause 5.3; keep copies of all Credit User documentation while the Credit User remains a Credit User and for a period of seven years from the date that Credit User ceases to be a Credit User; promptly forward to the Credit User any Notice of Redirection of a Direct Entry Item received (addressed to the Credit User) from a Ledger FI (as referred to in clause 5.21); and forward a Switch of Financial Institution and Account Details (addressed to the Credit User) to the Credit User within 3 business days of receipt.

Inserted effective 28/10/96

Last amended effective 11/6/08

(d)

Last amended effective 1/04/02

(e)

(f)

Last amended effective 1/11/08

(g)

Last amended effective 1/11/08

(h)

Inserted effective 1/11/08

(i)

Inserted effective 1/11/08

6.6

Each User FI agrees that upon exchange of Credit Items, each such Credit Item represents cleared funds and that Recalls and Returns of the Credit Items cannot be made without consent of the Ledger FI or its Representative. See clauses 5.14, 5.16 and 5.17. Each User FI also agrees that Reversals may only be made in accordance with the procedures set out in clause 5.16A.

Last amended effective 18/01/02

Ledger FI Responsibilities 6.7 A Ledger FI must: (a) subject to Regulation 2.9: (i) receive each Credit Users Credit Items sent by the Sending Member, apply funds to the relevant Customers' accounts as at a date no later than the PD Day (or the next business day after the PD Day if the PD Day is a public holiday in the relevant State/Territory) and effect settlement in accordance with the Regulations and these Procedures;
Last amended effective 28/10/96

Last amended effective 08/01/07

Last amended effective 5/12/07

Australian Payments Clearing Association Limited 6.2

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

(ii)

unless otherwise agreed bilaterally between the User FI and the Ledger FI, Credit Items received by the Ledger FI must be posted to the Ledger FI's accounts dated as at PD Day (or the next business day after PD Day if the PD Day is a public holiday in the relevant State/Territory); subject to clause 6.7A, make Credit Items which have been posted to the Ledger FIs accounts pursuant to clause 6.7(a)(ii), other than Government Payments, available to the Customer in the normal course of operations by 9.00 am local time on the next business day after PD Day (or the second business day after PD Day if the PD Day is a public holiday in the relevant State/Territory); and subject to clause 6.7A, with respect to Government Payments, use reasonable endeavours to make Credit Items which have been posted on the Ledger FIs accounts pursuant to clause 6.7(a)(ii) available to the Customer by 9.00 am on PD Day (or the next business day after PD Day if the PD Day is a public holiday in the relevant State/Territory);

Last amended effective 5/12/07

(iii)

Last amended effective 5/12/07

(iv)

Last amended effective 5/12/07

(Note: The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) imposes pre-conditions which must be satisfied before financial institutions may initiate, pass on or take any other action to carry out electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) (b) return any Credit Users Credit Items electronically which cannot or will not be applied, no later than the close of business on the next business day after the PD Day (or the second business day after PD Day if the PD Day is a public holiday in the relevant State/Territory); assist its Customers with enquiries on Credit Items made to the Customers' accounts; ensure that the name of remitter and, where present, the lodgement reference details from the Detail Record are printed on all Customer statements; if it receives any Refused Item (Record Type 3) which it cannot accept, ascertain from the Detail Record for that Refused Item the identity of the relevant User FI and arrange onforwarding of the Refused Item in accordance with that User FIs directions; nominate a Receiving Dataset for transmission of Government Files; upon request, to provide a Customer with a Regular Arrangements List as soon as practicable and in any event within 5 business days of receiving the request; and upon request, assist a Customer to notify Credit Users of a change in the account to be credited by: (i) (ii) (iii) assisting the Customer to identify the Credit Users on the Regular Arrangements List that need to receive a Switch of Financial Institution and Account Details; completing a Switch of Financial Institution and Account Details for each Credit User identified pursuant to clause 6.7(h)(i) for the Customer to sign; and forwarding a Switch of Financial Institution and Account Details to the applicable User FIs Account Switching Contact Point (specified in Appendix B12) within 2 business days of the Customer signing it.

Inserted effective 16/04/07

Last amended effective 5/12/07

(c) (d) (e)

Last amended effective 1/11/08

(f) (g) (h)

Last amended effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

The obligations in clauses 6.7(g) and 6.7(h) only apply to a Personal Account. 6.7A A Ledger FI is only obliged to make Credit Items available to the Customer for which it has received value settlement in accordance with Part 9 of these Procedures.

Inserted effective 29/12/08

Inserted effective 08/01/07

Australian Payments Clearing Association Limited 6.3

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

Lodgement FI Responsibilities 6.8 The Lodgement FI must ensure that: (a) each Credit Users Files and Items which are exchanged conform with the DE File User Item Specifications (see Appendix C1) prior to them being exchanged; the Credit User has a correct Trace Record for each transaction on the Credit Files lodged by the Lodgement FI; and when Government Files are exchanged, they are not transmitted with other Files except pursuant to a bilateral agreement (see clause 4.2 for exchange times).
Last amended effective 18/01/02

Last amended effective 27/07/07

(b)

Last amended effective 27/07/07

(c)

Last amended effective 27/07/07

(Note: The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) requires that certain information must be included in electronic funds transfer instructions and that certain information must be obtained in respect of those instructions before financial institutions may initiate, pass on or take any other action to carry out the electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) Lodgement FIs processing and receiving transactions for a third party should agree with that third party as to who is to check Files received for correctness and who will create any necessary Return Files, Refusal Files and Reversal Files. The Lodgement FI must check that, if a TNA is required in accordance with clause 6.9, a TNA is held for the relevant Credit User's File and that the total value of such File is within the amount authorised by the TNA. Where the Lodgement FI is not the User FI and the Lodgement FI processes a File for a User where the total value of the File exceeds the amount authorised by the current TNA for that User, the File is processed at the risk of the Lodgement FI unless the excess is first approved by the User FI. The Lodgement FI should seek the User FI's approval in writing or by some other mutually agreed method through the TNA Excesses Contact Point of the User FI specified in Appendix B4. It is the Lodgement FI's responsibility to satisfy itself that any File received from a Bureau or User for processing under TNA drawings is genuine (ie that it has in fact been provided by the Bureau or User). Transaction Negotiation Authority (TNA) 6.9 Establishment of a TNA by the User FI is mandatory whenever a Credit User's File (prepared either by the Credit User or a Bureau) is to be processed by a Lodgement FI which is other than the User FI. Each relevant TNA Issuer is to supply the necessary TNA (see Appendix A8) to the Lodgement FIs TNA Contact Point specified in Appendix B10. For the avoidance of doubt, nothing in these Procedures requires a TNA to be obtained where the Lodgement FI is also the User FI but the funding account is held with another financial institution. The TNA, which is to be prepared in accordance with the relevant TNA Issuer's internal requirements, authorises processing of a File up to the value of a specified processing limit, limit frequency and period and guarantees payment of the drawing for the total value of such File plus any charges levied by the Lodgement FI, as applicable.

Inserted effective 16/04/07

Last amended effective 4/8/2000

Last amended effective 27/07/07

Last amended effective 25/6/07

Last amended effective 25/6/07

Last amended effective 14/12/95

Australian Payments Clearing Association Limited 6.4

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

A TNA Issuer may temporarily increase the authorised amount of a TNA, in order to accommodate certain extraordinary payments (eg Christmas payroll), by issuing formal advices in writing to the Lodgement FI's TNA Contact Point. A TNA or an advice of temporary increase in authorised amount, must be confirmed by a properly authorised officer of the relevant TNA Issuer. Following confirmation, the TNA or advice of temporary increase is to be forwarded to the Lodgement FI's TNA Contact Point applicable to the State/Territory nominated for lodgement of the File. For the purposes of confirming TNAs, each User FI's TNA Contact Point will, as appropriate from time to time, supply to each other User FI's TNA Contact Point, a list of authorised signatories using the Authorised TNA Signatories form set out in Appendix A21. Subject to clause 6.10, where there is any change to the instructions contained in the original TNA, a replacement TNA must be prepared, authorised and forwarded to the Lodgement FIs TNA Contact Point. A TNA may only be terminated by the Lodgement FI or the relevant TNA Issuer. Advice of termination must be in writing to the other party's TNA Contact Point. Termination is effective upon receipt by the other party of the written termination advice, provided that a Lodgement FI may be unable to immediately act on advice of termination of a TNA which is received after commencement of processing of the User's File to which the TNA relates. (Note: A TNA Issuer should be aware of its obligations with respect to blocked accounts pursuant to Part III of the Financial Transactions Reports Act (the FTRA). In particular when an account is blocked TNA Issuers should consider whether it is necessary to terminate the TNAs in respect of the blocked account to ensure compliance with the FTRA.) Change of Lodgement FI by a User or Bureau 6.10 If a User or Bureau wishes to change its Lodgement FI, the relevant TNAs must be transferred or replaced at the relevant TNA Issuer's option prior to any Files being processed by the new Lodgement FI. If transfer is the preferred method the following procedures must be followed and a suitable start date arranged that allows for at least four weeks for the transfer process to be completed: (a) the proposed Lodgement FI must ensure that the User or Bureau provides it with a letter requesting it to take over the existing Lodgement FI's processing role together with a list of the existing TNAs held by the Bureau specifying: (b) (c) Credit User name Credit User Identification Number BSB Number account number processing limit frequency;

Last amended Effective 25/6/07

Last amended effective 25/6/07

Last amended effective 25/6/07

Last amended effective 25/6/07

Last amended effective 29/6/05

Inserted effective 11/10/06

Last amended effective 14/12/95

a separate listing in BSB Number order is to be provided for each TNA Issuer; the proposed Lodgement FI must write to the existing Lodgement FI and request transfer of business and assignment of the benefit of the existing TNAs. A copy of the User/Bureau's request (referred to in paragraph (a) above) must be enclosed;

Last amended effective 14/12/95

Australian Payments Clearing Association Limited 6.5

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

(d)

the existing Lodgement FI must reply by forwarding a letter to the proposed Lodgement FI, enclosing the originals of all existing TNAs. The existing Lodgement FI must retain a copy of the existing TNAs sent to the proposed Lodgement FI; on receipt, the proposed Lodgement FI must check the TNAs received against the list provided by the User or Bureau, confirm any discrepancies and forward a letter to each TNA Issuer together with a schedule of TNAs showing details outlined above. A copy of the existing Lodgement FI's reply should be forwarded to each TNA Issuer; the TNA Issuer must confirm each TNA to the proposed Lodgement FI; the TNA Issuer must ensure that the Credit User is aware of the change if the change is initiated by the Bureau; the proposed Lodgement FI must ensure that the Record Type 1 (Detail Record) field is amended as necessary; and the TNA Issuer must notify the Chief Executive Officer of individual changes in accordance with clause 5.3.
Last amended effective 14/12/95

(e)

(f) (g)

Last amended effective 14/12/95

Last amended effective 14/12/95

(h)

Last amended effective 28/10/96

(i)

Last amended effective 14/12/95

Credit Users who are Responsible Entities/Trustees/Managers of Trusts, Superannuation Funds etc. 6.11 Where a prospective Credit User is a responsible entity/trustee/manager of a managed investment scheme, trust, superannuation fund or other fund, the User FI must, with the help of such legal expertise as appropriate, ascertain from the Memorandum and Articles of Association of the Credit User (if a corporate Credit User) and the trust deed/constitution (as appropriate) establishing the managed investment scheme, trust, superannuation fund or other fund whether the responsible entity/trustee/manager is empowered to give an indemnity under the Credit User Application. If it is not, the application cannot proceed. Where the responsible entity/trustee/manager has the power to give but has insufficient assets of its own to support such an indemnity, or otherwise refuses personal liability under such an indemnity, the User FI must ascertain whether the responsible entity/trustee/manager is entitled under the trust deed/constitution (as appropriate) to recover from the assets of the managed investment scheme, trust, superannuation fund or other fund any amount which it may become liable to pay under the indemnity given under a Credit User Application. If the responsible entity/trustee/manager has recourse to the assets of the managed investment scheme, trust, superannuation fund or other fund, the application may be supported by the balance sheet of the managed investment scheme, trust, superannuation fund or other fund and the following clause may be added to the Credit User application (without the need to obtain the consent of the Management Committee): "8. The indemnity contained in Clause 3 of this Credit User Application is given by the Credit User as responsible entity/trustee/manager of the ...... (Managed Investment Scheme/Trust/Fund) and, except in the case of fraud, negligence, breach of trust or breach of duty by the Credit User, liability under that Clause 3 is limited to the value of the assets of the said . (Managed Investment Scheme/Trust/Fund) under its administration from time to time."

Last amended effective 15/10/99

Last amended effective 15/10/99

Last amended effective 15/10/99

Last amended effective 15/10/99

Last amended effective 15/10/99

Australian Payments Clearing Association Limited 6.6

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

If the responsible entity/trustee/manager has no recourse to the assets of the managed investment scheme, trust, superannuation fund or other fund under the trust deed/constitution (as appropriate), this clause must not be included, the responsible entity/trustee/manager will be liable in its own right, and any Credit User Application must be supported by the responsible entity/trustee/manager's own balance sheet. Credit User Application - Stamp Duty 6.12 It is the responsibility of the User FI to appropriately stamp the Credit User Application in the relevant stamp duty jurisdiction. (In this regard note that at the date these Procedures come into effect all State and Territories of Australia apply their respective stamp duty laws to instruments signed in those States or Territories, and there are additional nexus provisions (which vary from State to State and Territory to Territory) which may apply if a Credit User Application signed in one State or Territory is physically held in another State or Territory or relates to a matter to be done in another State or Territory)."

Last amended effective 15/10/99

Inserted effective 21/3/95

Notification of an Unapplied Credit Item and Request for Information (Superannuation Entities) 6.13 If a Credit Item is posted by a Ledger FI to the account of a Superannuation Entity on or after 1 December 2008 and the funds cannot be: (a) applied by the Superannuation Entity to a superannuation fund maintained by the Superannuation Entity; and returned electronically in accordance with clause 6.7 (b),

Inserted effective 1/12/08

(b)

then the Ledger FI may seek further particulars of the Credit Item from the Credit User by sending a Notice of Unapplied Credit Item (Superannuation) form set out in Appendix A26 to the Lodgement FIs Notice of Unapplied Credit Item (Superannuation) Contact Point specified in Appendix B13 by facsimile or email (as a rich text format attached). On receipt of a Notice of Unapplied Credit Item (Superannuation) a Lodgement FI must: (a) (b) contact the Credit User to obtain further particulars; and within 20 business days from the date of receipt of the Notice of Unapplied Credit Item (Superannuation), send a written response to the Ledger FI (to the fax number or email address specified in the Notice of Unapplied Credit Item (Superannuation)).

If on receipt of any further particulars supplied by the Credit User the funds still cannot be applied or if no response to the Notice of Unapplied Credit Item (Superannuation) is received within 20 business days from the date of sending the Notice of Unapplied Credit Item (Superannuation) to the Lodgement FI, then the unapplied Credit Item may be returned by the Superannuation Entity to the Trace Record account as a new Record Type 1 using transaction code 50 and quoting the: (a) reference details from Notice of Unapplied Credit Item (Superannuation) in the lodgement reference field; and title of account from the original Credit Item in the name of remitter field.

(b)

Any return of an unapplied Credit Item by a Superannuation Entity pursuant to this clause 6.13 must be sent to the Trace Record account within 90 business days of receipt of the Credit Item.

Australian Payments Clearing Association Limited 6.7

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 6 Direct Credit System

If the unapplied Credit Item is returned by the Superannuation Entity to the Trace Record account and the account has been closed then the Credit Item must be returned with the answer Account Closed. The Superannuation Entity should then treat the funds as Unclaimed Moneys. Changes to contact details in Appendix B13 must be promptly notified to the Company in accordance with clause 4.1 (Note: Clause 6.13 is only to be used as a last resort. Superannuation Entities should have appropriate reconciliation systems in place, so that a Notice of Unapplied Credit Item (Superannuation) is only issued when absolutely necessary (for example due to a Credit User (Employer) error.)

The next page is 7.1

Australian Payments Clearing Association Limited 6.8

[ABN 12 055 136 519] Amendment No. E040, issued as CS2/r&p/007.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

PART 7

DIRECT DEBIT SYSTEM

Participating Members Authorised to Sponsor Debit Users 7.1 Any Participating Member may sponsor a person as a Debit User. A Tier 2 Participating Member must, however, have the agreement of its Representative to sponsor a person as a Debit User. Where a Tier 2 Participating Member has the agreement of its Representative to sponsor a person as a Debit User, the Representative will be deemed to have given the indemnification set out in clause 7.7. The arrangements under which a Tier 2 Participating Member's Representative agrees to the Tier 2 Participating Member sponsoring a person as a Debit User are proprietary.

Sponsor Approval 7.2 A Sponsor may approve a person as a Debit User without reference to any other Participating Members, but before that approval it must carry out a credit risk assessment of the prospective Debit User and satisfy itself that the financial strength, integrity and reliability of the prospective Debit User qualify it as a suitable Debit User in BECS. A Sponsor is not obliged to approve any prospective Debit User. Documentation brought into effect between the Sponsor and a Debit User in connection with the Debit User's participation in BECS in that capacity and the Sponsor's obligation, as Sponsor, to ensure the Debit User meets certain obligations and responsibilities required of it under this Part 7 (see, for example, clauses 7.5, 7.10 and 7.11) is proprietary. (Note: Ledger FIs have recourse against a Sponsor for claims arising pursuant to the Debit User's participation in BECS: see clauses 7.5(b) and 7.6.) Each Participating Member may use a logo approved by the Company in connection with direct debits in BECS on any of that Participating Members proprietary documentation published in accordance with these Procedures and relating to the provision by it of direct debit services through BECS. Each Participating Member acknowledges and agrees for the benefit of the Company that its entitlement to use any such logo ceases immediately upon its ceasing to act in the capacity of a Participating Member in BECS, and that subsequent use of the logo by it will be taken to be an infringement of the Companys rights in that mark. 7.3 If a Sponsor approves a person as a Debit User, the Sponsor must obtain for, or assign to, the prospective Debit User a User Identification Number in accordance with clause 5.12. The Sponsor must notify the details of the prospective Debit User and, in the case of a Sponsor which is a Tier 2 Participating Member, its Representative's agreement to the Tier 2 Participating Member sponsoring the prospective Debit User, to the Chief Executive Officer in accordance with clause 5.3.
Inserted effective 31/3/00 Last amended effective 31/3/00

Inserted effective 31/3/00

Last amended effective 31/3/00

Direct Debit Requests 7.3A Subject to clause 7.4A, a Direct Debit Request may only be given in writing or by telephone by the relevant Customer to and in favour of a Debit User (or to a third party in its capacity as agent for that named Debit User). (Note: A DDR may be given in writing by electronic communication see clauses 1.2 (e) and (f) and 7.10 (a).)

Inserted effective 31/3/00

Amended effective date 03/03/06

Inserted effective date 03/03/06

Australian Payments Clearing Association Limited 7.1

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

7.4

A Direct Debit Request must: (a) (b) (c) (d) (e) (f) be identified as a Direct Debit Request; authorise and request a Debit User to debit a Customer's account through BECS; identify (by name and BSB Number) the Ledger FI to which the relevant debit payment instructions are to be given. Provision of domicile (ie. physical address) is optional; identify (by name and account number) the Customer's account to be debited; identify (by name and User Identification Number) the Debit User in favour of which the Customer's authority is given; and if given: (i) in writing be in such form as the relevant Sponsor may approve, substantially in the terms of Appendix A27 and be dated and contain the Customers signature (if the Direct Debit Request is given in writing by electronic communication then the requirements specified in clauses 1.2(e) and (f) must be satisfied); or by telephone be given by a procedure that the relevant Sponsor has approved which must: (A) identify the Customer and indicate the Customers approval of the information communicated (including the authority and request to the Debit User to debit the Customers account through BECS), by a method that is in accordance with clause 1.2(f)(ii); and provide the Customer with written confirmation of the Direct Debit Request (which must include the information described in 7.4(c), (d) and (e) above) and the terms and conditions of the applicable DDR Service Agreement within 7 days.

Amended effective date 03/03/06

Last amended effective 31/03/04

Last amended effective 30/6/03

Amended effective date 03/03/06

Amended effective date 17/01/11

(ii)

Inserted effective date 03/03/06

Inserted effective date 03/03/06

(B)

Inserted effective date 03/03/06

(Note: 1. 2.

Clause 7.14 sets out further requirements in relation to the printing/ publication of written Direct Debit Requests and use of the Company logo. A Debit User must obtain written authorisation from its Sponsor BEFORE it may obtain DDRs in writing by electronic communication or by telephone see clause 7.10(b). Appendix A27 is provided to assist Sponsors with preparation of their DDRs insofar as it suggests a form of DDR incorporating all required content. Notwithstanding any implied or express statement to the contrary in these Procedures, provided DDRs comply with substantive content provisions of these Procedures, a Sponsor may determine the form of DDR it uses in its absolute discretion.)

Amended effective date 03/03/06

3.

Inserted Effective 17/01/11

Transitional 7.4A A Sponsor may approve a Debit User's use, in the DDR Transitional Period, of Forms PD-C in a format previously approved by the Sponsor under these Procedures, in lieu of Direct Debit Requests in the form required by clause 7.4.

Inserted effective 31/3/00

Inserted effective 31/3/00

Australian Payments Clearing Association Limited 7.2

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

Any Form PD-C so approved for use in the DDR Transitional Period will be treated in all respects for the purposes of these Procedures as if it were a Direct Debit Request EXCEPT THAT the Sponsor must require the Debit User to deliver each such Form PD-C to the Ledger FI to which it is addressed, and retain a copy for the Debit Users records. Each Ledger FI which receives a Form PD-C completed by a Customer during the DDR Transitional Period must retain it for a period of not less than 7 years from the date of the last debit effected under it. On and from the DDR Compliance Date, each Sponsor must ensure that its Debit Users do not permit Customers to enter into direct debit arrangements in BECS using Forms PD-C. Sponsor Responsibilities 7.5 A Sponsor which approves a Debit User must: (a) (b) (c) ensure that the Debit User complies with its responsibilities as set out in these Procedures; indemnify each Ledger FI against claims arising from the Debit User issuing Debit Items through BECS, in the terms set out in clause 7.6; ensure that: (i) (ii) the Debit User has a correct Trace Record for each transaction on its File; and if the Trace Record Institution specified or to be specified in respect of the Debit Users Debit Items is not the Sponsor, that Trace Record Institution has consented in writing to be specified as the Trace Record Institution for that Debit Users Debit Items.

Inserted effective 31/3/00

Inserted effective 31/3/00

Inserted effective 31/3/00

Last amended effective 31/3/00

Inserted effective 28/10/96

If the Sponsor conducts the account nominated in the Trace Record, the Sponsor must accept every Returned Item which is sent to it electronically as a Record Type 2 in accordance with the Regulations and these Procedures (see in particular clauses 5.16A(f), 5.17, 5.18 and 8.1). The Sponsor must inform the Debit User promptly of each such Returned Item referable to that Debit User; (d) manage the on-going conduct of the Debit User by ensuring that the Debit Users lodgements are consistent with the Debit User's normal business practice or needs and install a "User Profile" to monitor File lodgements and manage unusual variations to lodgement patterns on an on-going basis. In monitoring File lodgements by its Debit Users, a Sponsor must have regard to: (i) (ii) (iii) (e) the total value of Debit Items contained in any one File being in excess of the agreed figure or in excess of the normal pattern; the frequency of lodgements; and any other relevant matters;

Last amended effective 11/6/08

Last amended effective 28/10/96

be satisfied as to the Debit Users continued financial stability and continued suitability for access to BECS and, where required, undertake reviews to the extent necessary; be solely accountable for terminating the Debit User's right to lodge Debit Items as it sees fit;

Last amended effective 31/3/00

(f)

Last amended effective 28/10/96

Australian Payments Clearing Association Limited 7.3

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(g)

immediately review a Debit User's suitability if the Sponsor becomes aware of any material change in the Debit User's circumstances. If, as a result of the review, the Sponsor cancels the Debit Users access to BECS as a Debit User, the Sponsor must notify the Company and the Debit User immediately of such cancellation (and the Debit User should also be notified of the withdrawal of its entitlement and access to any logo of the Company relating to direct debits). The Company will then issue a cancellation advice to the Participating Members according to the urgency of the request. A change to a Debit User's circumstances may include, without limitation, reduced financial standing, integrity or reliability; notify the Company within the appropriate time-frame prior to change of Debit User name, mergers, and the like taking effect in accordance with clause 5.3; notify the Company not less than 15 business days before making any change to its DDR Claims Contact or Claims Account details as published in Appendix B7, nominating an effective date for the change, to enable the Company to publish any amended details to Participating Members before they take effect; promptly forward to the Debit User a Cancellation Request received from a Ledger FI (as referred to in clause 7.12(h)); promptly forward to the Debit User any Notice of Redirection of a Direct Entry Item received (addressed to the Debit User) from a Ledger FI (as referred to in clause 5.21); forward a Switch of Financial Institution and Account Details (addressed to the Debit User) to the Debit User within 3 business days of receipt; and notify the Debit User that before obtaining Direct Debit Requests in writing by electronic communication or by telephone the Sponsor must review and approve the format, content, medium and procedures proposed for obtaining Direct Debit Requests in writing by electronic communication or by telephone.

Last amended effective 2/04/04

(h) (i)

Last amended effective 20/7/2001

Last amended effective 11/6/08

(j)

Last amended effective 1/11/08

(k)

Inserted effective 1/11/08

(l)

Inserted effective 1/11/08

(m)

Last amended effective 1/11/08

Sponsor Indemnification 7.6 A Sponsor which approves a Debit User indemnifies all Participating Members on behalf of themselves and on behalf of each Non-member Appointor for which that Participating Member is a Representative in respect of all claims, liabilities, expenses and losses suffered or incurred by the Participating Member and each Non-member Appointor in respect of all Valid Claims in accordance with this clause. In this clause, a "Valid Claim" is a claim, supported by full particulars, made in writing by a Participating Member, addressed to the Sponsor in relation to the Participating Member's Customer or its Non-member Appointor's Customer to whose account a Debit Item is debited, that: (a) the account of any such Customer has been debited with, and payment made to the Debit User of, amounts not at the time authorised by a Direct Debit Request from that Customer, or to which the Debit User was not at the time legally entitled; the account of any such Customer has been debited with, and payment made otherwise than in accordance with a Direct Debit Request in force at that time from that Customer; or
Last amended effective 31/3/00

Last amended effective 31/3/00

(b)

Inserted effective 31/3/00

Australian Payments Clearing Association Limited 7.4

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(c)

payment has failed to be made in accordance with a Direct Debit Request in force at that time from that Customer,

Inserted effective 31/3/00

and includes any claim: (d) (e) (f) that the Sponsor has accepted as meeting all conditions under this clause; or that the Sponsor has accepted liability for irrespective of the circumstances; or where any relevant industry ombudsman or a court makes a decision or an order that the Sponsor make a payment in respect of the claim.
Last amended effective 31/3/00

Last amended effective 31/3/00

Last amended effective 31/3/00

The indemnification contained in this clause 7.6 shall apply to each Debit User which has or should have been advised to be a Debit User by the Sponsor to the Company in accordance with these Procedures whether such advice was given on or before the commencement of BECS. In the case of a Debit User which was not using the direct entry system operating immediately prior to the commencement of BECS this indemnification commences to apply to that Debit User upon the Debit User lodging Files in accordance with these Procedures. Representative Indemnification 7.7 A Representative which has agreed to allow a Tier 2 Participating Member to sponsor a person as a Debit User indemnifies all Participating Members (other than the Tier 2 Participating Member), on behalf of themselves and on behalf of each Non-member Appointor for which that Participating Member is a Representative, in respect of any loss caused by or arising from the Tier 2 Participating Member's failure to comply with the indemnity which it has given under clause 7.6 as a Sponsor and its failure to comply with any other aspect of Sponsor obligations in clause 7.

Claim Procedures under Sponsor Indemnification and Representative Indemnification 7.8 The procedures for Ledger FIs to claim under the Sponsor's indemnification as set out in clause 7.6 and the Representative's indemnification as set out in clause 7.7 are as follows: [Previous sub-paragraph (a) deleted.] (a) when a Customer approaches a Ledger FI to make a claim the Ledger FI must: (i) (ii) make reasonable enquiries as to the circumstances of the claim; determine whether, in its reasonable opinion, the claim appears to be a Valid Claim;
Inserted effective 31/3/00 Last amended effective 1/3/2002

Deleted effective 1/3/2002

(Note: as far as practicable, Ledger FIs are encouraged to include a check of their own PD-C files (ie. pre-DDR Compliance Date) as part of this determination.) (iii) if it determines that the claim appears to be a Valid Claim, obtain from the Customer a completed Customer Claim which must: (A) (B) be identified on its face as a "Direct Debit Customer Claim"; identify (by name and address) the Customer;

Last amended effective 31/3/00

Inserted effective 31/3/00

Inserted effective 31/3/00

Australian Payments Clearing Association Limited 7.5

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(C)

identify the Debit User or, if different, remitter named on the Customers account statement; identify (by date, amount, BSB Number and account number) the disputed debit transaction and include the lodgement reference details printed on the Customer's account statement; set out the basis on which the Customer disputes the Debit User's authority to debit; and be dated and contain the Customer's signature, and

Inserted effective 31/3/00

(D)

Inserted effective 31/3/00

(E)

Inserted effective 31/3/00

(F) (iv) (b)

Inserted effective 31/3/00

advise the Customer that the claim may be disputed;


Last amended effective 11/6/08

after receiving a completed Customer Claim, if the Ledger FI decides to make a claim under clause 7.6 and/or clause 7.7, the Ledger FI's DDR Claims Contact specified in Appendix B7 must, before close of business on the business day (in the State/Territory where that DDR Claims Contact is located) which next follows the date of the Customer Claim: (i) forward by facsimile or by e-mail (as a rich text format attachment) to the Sponsor's DDR Claims Contact specified in Appendix B7, the completed Customer Claim (or alternatively full particulars of the claim in another form, provided such form includes the information referred to in clause 7.8(a)(iii)(B)-(E) inclusive, and the date of the claim), together with a completed Claim Request, demanding payment by the Sponsor, under the indemnity given by the Sponsor pursuant to clause 7.6, of the amount of the claim; and at the same time, if the Sponsor is a Tier 2 Participating Member, also send to the Sponsor's Representative full particulars of the claim with a demand for payment by the Representative, under the indemnity which the Representative has given under clause 7.7, of the amount of the claim in the event that payment is not received by the Ledger FI from the Sponsor under the Sponsor's indemnity;

Last amended effective 04/03/08

(ii)

Last amended effective 31/3/00

(c)

the Sponsor's DDR Claims Contact must: (i) forward the claim to the Debit User as soon as practicable and require it to produce evidence of its authority to effect the disputed debit transaction; and respond in writing to the Ledger FI's DDR Claims Contact (with a copy to the Sponsor's Representative, if any) as to whether the claim is accepted or refused (and if it is refused, written reasons for that, together with evidence of the Debit User's authority to effect the disputed debit): (A) in the case of disputed debits made no earlier than 12 months before the date of the Customer Claim (apart from disputed debits involving a Debit User that is under the administration of an Administrator (as defined in clause 5.8)), by no later than close of business on the fifth business day (in the State/Territory where the Sponsor's DDR Claims Contact is located) after its receipt of the claim; and in the case of all other disputed debits, within one month of its receipt of the claim;

Last amended effective 11/6/08

Inserted effective 31/3/00

(ii)

Last amended effective 11/6/08

Last amended effective 1/11/08

(B)

Inserted effective 31/3/00

Australian Payments Clearing Association Limited 7.6

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(Note: the intention is to allow the Sponsor's DDR Claims Contact 5 clear business days to process a claim under (A) above. Ledger FIs must ensure, in calculating the date by which a response is required from the Sponsor, that they exclude public holidays in the State/Territory where the Sponsor's DDR Claims Contact is located.) (d) the Ledger FI must inform the Customer of the Sponsor's response no later than the morning of the next business day (being a business day in each of the States/Territories (if different) where the Ledger FI and the Ledger FI's DDR Claims Contact are located) following the expiry of the period allowed for the Sponsor's response under clause 7.8(c)(ii)(A) or (B); if the Sponsor accepts any claim or if it fails to respond to the Ledger FI's DDR Claims Contact within the specified period under clause 7.8(c)(ii)(A) or (B), the Ledger FI may: (i) (ii) refund to the Customer the amount of the claim; and draw on the Sponsor's (or if applicable, Sponsors Representatives) claims account nominated for that purpose in Appendix B7, for an equivalent amount,

Last amended effective 11/6/08

Last amended effective 11/6/08

(e)

Last amended effective 11/6/08

Inserted effective 31/3/00

Last amended effective 04/03/08

at the time it notifies the Customer under clause 7.8(d). The Ledger FI must confirm its drawing by facsimile to the Sponsors DDR Claims Contact on the same business day that it effects the drawing, providing in that facsimile adequate information to enable the Sponsor to identify the claim which is the basis of that drawing. On and from the DDR Compliance Date all drawings pursuant to clause 7.8(e)(ii) must be made electronically in accordance with the specifications set out in Appendix C4; (f) if in relation to any claim, the Sponsor's DDR Claims Contact notifies the Ledger FI's DDR Claims Contact in writing within the required period pursuant to clause 7.8(c)(ii) that the claim is refused, it must at that time produce to the Ledger FI's DDR Claims Contact evidence of the authority of the Debit User to have made the disputed debit (DDR Claims Evidence), and: (i) (ii) the Customer wants to contest refusal of the claim; and the Ledger FI determines, in its reasonable opinion, that the claim is still appropriate, then

Last amended effective 11/6/08

Last amended effective 11/6/08

the Ledger FI must give written notice that rejection of the claim is disputed to the Sponsor, and if the Sponsor is a Tier 2 Participating Member, copied to the Sponsor's Representative; (g) upon receipt by the Sponsor and, if applicable, its Representative of notice under clause 7.8(f), the Sponsor and the Ledger FI and, if applicable, the Representative must use reasonable endeavours to resolve the dispute; if a disputed claim is not resolved under clause 7.8(g) within 30 days from the date on which the Sponsor (or if applicable, the later of the respective dates on which the Sponsor and its Representative) received notice of the dispute under clause 7.8(f), the disputed claim may be referred to the Management Committee, pursuant to Regulation 13, by the Ledger FI or the Sponsor or, if applicable, the Sponsor's Representative;

Last amended effective 31/3/00

Amended effective date 03/03/06

(h)

Amended effective date 03/03/06

Australian Payments Clearing Association Limited 7.7

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(i)

any claim in respect of which the DDR Claims Evidence does not include a copy of a valid and binding written Direct Debit Request with a signature that has been handwritten by the Customer shall be determined in favour of the Ledger FI unless the Sponsor can establish conclusively that the Debit User has obtained a valid and binding Direct Debit Request from the Customer in writing by electronic communication or by telephone.

Inserted effective date 03/03/06

For the avoidance of doubt, nothing in the preceding provisions of this clause 7.8 will be taken to prevent a Ledger FI, having determined that in its opinion a claim is a Valid Claim, from refunding, from its own funds, to the Customer the amount of the disputed Debit Item before making its claim on the Sponsor in accordance with clause 7.8(b). In that case, once the Ledger FI makes a claim on the Sponsor under clause 7.8(b), clauses 7.8(c)-(i) inclusive will then apply in accordance with their terms EXCEPT THAT risk as to whether the claim will be accepted by the Sponsor (or, if disputed, as to whether it will ultimately be determined to be a Valid Claim) rests solely with the Ledger FI and any funds subsequently refunded to the Ledger FI pursuant to this clause 7.8 will be taken to be received or drawn by it for its own benefit. If the Customer commences legal action against the Ledger FI, the Ledger FI must keep the Sponsor and, if applicable, the Sponsor Representative reasonably informed about that legal action. Each Sponsor consents to being joined as a party to any such action if the Ledger FI so requires, with each party to be responsible in the first instance for its own costs. It may also be that the Sponsor and/or the Sponsor's Representative will wish to become involved in the legal action to defend its involvement in processing the transaction. Cancellation of Sponsor Indemnification and Representative Indemnification 7.9 Upon notification to the Company of the cancellation of a Debit User's right of access to BECS as a Debit User, the Sponsor indemnification given under clause 7.6 and, if applicable, the Representative indemnification under clause 7.7 shall cease to apply in respect of that Debit User in relation to Items of that Debit User exchanged by it after that notification, but without prejudice to any right or liability arising under the Sponsor indemnification given under clause 7.6 in relation to that Debit User prior to such cancellation or in relation to any other Debit Users lodging for whom that Sponsor is responsible and, if applicable, the Representative indemnification given under clause 7.7.

Amended effective date 03/03/06

Last amended effective 31/3/00

Last amended effective 31/3/00

Last amended effective 31/3/00

Debit User Responsibilities 7.10 A Sponsor must not approve a prospective Debit User unless the Debit User agrees to comply with all the conditions, accountabilities and responsibilities required of a Debit User in these Procedures. Therefore, a Sponsor must ensure that its Debit Users: (a) in respect of each new Customer on or after the DDR Implementation Date: (i) obtain a valid and binding Direct Debit Request that meets the requirements specified in clause 7.4; enter into a DDR Service Agreement that meets the requirements specified in clause 7.11 either in writing or by telephone and if the DDR Service Agreement is entered into: (A) in writing by electronic communication then the information described in clause 7.11 must be communicated to the Customer in writing and the requirements specified in clause 1.2(e) and (f) must be satisfied in respect of that information; or
Last amended effective 31/3/00

Amended effective date 03/03/06

(ii)

Amended effective date 03/03/06

Inserted effective date 03/03/06

Australian Payments Clearing Association Limited 7.8

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(B)

by telephone then the information described in: (1) (2) clause 7.11(b); and unless the Customer elects not to receive it the remainder of clause 7.11;

Inserted effective date 03/03/06

must be communicated to the Customer by a procedure that the Sponsor has approved which must identify the Customer and indicate the Customers approval of the information communicated by a method that is in accordance with clause 1.2(f)(ii); (iii) provide the Customer with the terms and conditions of the DDR Service Agreement in writing. If the terms and conditions of DDR Service Agreement are provided to the Customer in writing by electronic communication then the requirements specified in clause 1.2(e) must be satisfied; and with respect to Direct Debit Requests obtained in writing by electronic communication or by telephone, use its best endeavours to comply with the Guidelines for Establishing Direct Debit Requests Electronically or by Telephone to the extent to which such guidelines are applicable.
Inserted effective date 03/03/06

(iv)

Amended effective date 03/03/06

(Note: If a DDR is obtained by telephone then written confirmation of the DDR and the terms and conditions of the applicable DDR Service Agreement must be provided to the Customer within 7 days see clause 7.4(f)(ii)(B).) (b) only obtain Direct Debit Requests in writing by electronic communication or by telephone if the Sponsor has authorised them in writing to do so and then subject to such conditions as the Sponsor may impose; in respect of each existing Customer as at the DDR Implementation Date who has not received a DDR Service Agreement: (i) agree to apply, for the benefit of those Customers, the procedures and policies set out in the Debit User's standard DDR Service Agreement applicable at the relevant time; and agree, on inquiry by any such Customer, to make available general descriptive information on those procedures and policies;

Inserted effective date 03/03/06

Inserted effective date 03/03/06

(c)

Amended effective date 03/03/06

Inserted effective 31/3/00

(ii)

Inserted effective 31/3/00

(d)

issue Debit Items strictly in accordance with the Direct Debit Request provided by the Customer to the Debit User, honour the spirit of the commitment made to the Customer under the Debit User's applicable DDR Service Agreement and do not exceed the conditions (if any) specified in the Direct Debit Request provided by the Customer; inform Customers of any change in the terms of the debit arrangements agreed between them (in the case of new Customers on and from the DDR Implementation Date, as set out in the Debit User's DDR Service Agreement and Direct Debit Request and includes, without limitation, any change to the Debit User's details as set out in the Direct Debit Request), at least 14 days before the change is implemented; inform the Sponsor (within any notification period specified by the Sponsor) of any significant changes in arrangements made in relation to the issue of Debit Items including changes to File values and/or frequency;

Amended effective date 03/03/06

(e)

Amended effective date 03/03/06

(f)

Amended effective date 03/03/06

Australian Payments Clearing Association Limited 7.9

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(g)

inform the Sponsor of any proposed change to Debit User name, mergers, and the like in accordance with any notification period specified by the Sponsor; (Note: such a notification period may be necessary to enable the Sponsor to evaluate the nature of the proposed change and to determine whether or not to agree to it and, in the event that it agrees, to act in accordance with clauses 5.3 and 5.9.)

Amended effective date 03/03/06

Inserted effective 31/3/00

(h)

promptly verify (by signature comparison or other means) a Switch of Financial Institution and Account Details prior to processing. If there is any doubt as to the Customers authorisation, then the Debit User must contact the Customer to verify; act promptly in accordance with any instruction given by a Customer to it directly or received from the Customer via the Ledger FI and the Sponsor to: (i) (ii) (iii) (iv) cancel or suspend a Direct Debit Request; stop or defer individual Debit Items from time to time; vary a Direct Debit Request in accordance with a verified Switch of Financial Institution and Account Details; or vary a Direct Debit Request in accordance with a Notice of Redirection of a Direct Entry Item.

Inserted effective 1/11/08

(i)

Last amended effective 1/11/08

Last amended effective 1/11/08

Last amended effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

(Note: In relation to any Returned Item referable to a Debit User, the Debit User must act promptly to take such action as may be necessary, which may include referring to the Customer, to ensure the continuing accuracy of each Direct Debit Request.) (j) investigate and deal promptly and in good faith with any query, claim or complaint relating to alleged incorrect or wrongful debits that is received from a Sponsor, assist the Sponsor to deal with all such queries, claims or complaints and respond to the Sponsor within any period specified by the Sponsor, by either (i) (ii) (k) accepting the claim and paying the disputed amount to the Sponsor in any manner agreed between them; or disputing the claim and providing the Sponsor with full particulars of reasons for disputing the claim, which must include evidence of its authority to debit;

Inserted effective 26.07.10

Last amended effective 1/11/08

are made aware of: (i) (ii) the Debit Users responsibility to ensure that correct account information appears on any Direct Debit Request given to it; and the Sponsors potential liability under its indemnity in clause 7.6 (and the implications in terms of any liability of the Debit User to that Sponsor under their proprietary documentation) in circumstances where the Debit User has initiated debits in reliance on incorrect account information provided by a Customer in a Direct Debit Request;

Last amended effective 1/11/08

(l)

ensure the correct User Identification Number for the Debit User appears on each Direct Debit Request, and all correspondence to the Customer which the Debit User initiates;

Last amended effective 1/11/08

Australian Payments Clearing Association Limited 7.10

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(m)

retain all Direct Debit Requests, Switch of Financial Institution and Account Details, Notices of Redirection of a Direct Entry Item and instructions from Customers (whether received directly from a Customer or via a Ledger FI and Sponsor) to cancel or suspend a Direct Debit Request given to the Debit User in writing (other than by electronic communication or by telephone) and reliable records of all such requests, forms or instructions given to the Debit User in writing by electronic communication or by telephone on or after the DDR Implementation Date (including copies of all Forms PD-C which are required to be delivered to the Ledger FI (see clause 7.4A)) for a period of not less than 7 years from the date of the last debit made under the relevant Direct Debit Request, and produce these on request by the Sponsor or the Ledger FI for verification of the Debit User's authority to debit; acknowledge and agree, for the benefit of the Company, that the Debit Users entitlement to use a logo approved by the Company on its form of Direct Debit Request and related material (in each case as approved by the Sponsor), is contingent on the Debit Users continuing to act in the capacity of a Debit User in BECS and to comply fully with its obligations in that capacity, such that if: (i) (ii) the Debit Users access to BECS is withdrawn by the Sponsor; or the Debit User otherwise ceases to be a Debit User in BECS,

Last amended effective 1/11/08

(n)

Last amended effective 1/11/08

the Debit Users entitlement to use that logo will cease immediately and any further use of the logo by the Debit User will be taken to be an infringement of the Companys rights in that mark; and (o) acknowledge and agree that Customers are entitled to cancel or suspend Direct Debit Requests addressed by those Customers to those Debit Users by notice to the Ledger FIs in accordance with sub-paragraph 7.12(h).

Last amended effective 20/7/2001

Last amended effective 1/11/08

DDR Service Agreement 7.11 Each DDR Service Agreement must: (a) be identified as a DDR Service Agreement and, if given in writing, be substantially in the terms of Appendix A28; set out reasonable details (or, if such details are contained in the DDR, refer the Customer to it) of the terms of the debit arrangements to apply between the Debit User and the Customer including, if applicable, the basis on which the Debit User will issue billing advices to the Customer; provide for not less than 14 days' notice to the Customer if the Debit User proposes to vary any of the terms of those debit arrangements; set out in reasonable detail the procedure available to the Customer to request deferment of, or alteration to, any of those arrangements; set out in reasonable detail the procedure available to the Customer to stop any Debit Item or cancel a Direct Debit Request with the Debit User, and advise the Customer that all requests for such stops or cancellations may be directed to the Debit User or the Ledger FI;

Inserted effective 31/3/00

Inserted effective 31/3/00

Last amended effective 17/01/11

(b)

Inserted effective 31/3/00

(c)

Inserted effective 31/3/00

(d)

Inserted effective 31/3/00

(e)

Last amended effective 19/2/04

Australian Payments Clearing Association Limited 7.11

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(f)

set out in reasonable detail the procedure available to the Customer to dispute any Debit Item with the Debit User and the dispute resolution process to apply between them, and advise the Customer that claims may also be directed to the Ledger FI; indicate: (i) (ii) that direct debiting through BECS may not be available on all accounts; and that the Customer is advised to check account details against a recent statement from the Ledger FI,

Last amended effective 19/2/04

(g)

Inserted effective 31/3/00

and direct the Customer, if uncertain, to check with the Ledger FI before completing the DDR; (h) state that it is the responsibility of the Customer to have sufficient clear funds available in the relevant account by the due date to permit the payment of Debit Items initiated in accordance with the relevant Direct Debit Request; state its policy when the due date for payment falls on a day which is not a Business Day in the place of lodgement, and indicate that if the Customer is uncertain as to when the debit will be processed to the Customer's account, he or she should enquire direct of the Ledger FI; state its policy when Debit Items are returned unpaid by the Ledger FI, including the application by the Debit User of any related fees; and state its policy on the privacy to be accorded to the Customer's records and account details, while noting that the Sponsor may require such information to be provided in connection with a claim made on it relating to an alleged incorrect or wrongful debit. A DDR Service Agreement may be entered into in writing, in writing by electronic communication or by telephone see clauses 1.2(e) and (f) and 7.10(a). Appendix A28 is provided to assist Sponsors with preparation of their DDR Service Agreements, insofar as it suggests a form of DDR Service Agreement incorporating all required content. Notwithstanding any implied or express statement to the contrary in these Procedures, provided DDR Service Agreements comply with substantive content provisions of these Procedures, a Sponsor may determine the form of DDR Service Agreement it uses in its absolute discretion.)

Inserted effective 31/3/00

Inserted effective 31/3/00

(i)

Inserted effective 31/3/00

(j)

Inserted effective 31/3/00

(k)

Inserted effective 31/3/00

(Note: 1.

Amended effective date 03/03/06

2.

Inserted Effective date 17/01/11

Ledger FI's Responsibilities 7.12 A Ledger FI must: (a) receive Debit Users Debit Items from a Sending Member, draw funds from the relevant Customers' accounts as at a date no later than PD Day (or the next business day after PD Day if the PD Day is a public holiday in the relevant State/Territory) and effect settlement in accordance with the Regulations and these Procedures. Unless otherwise agreed bilaterally between the User FI and Ledger FI, Debit Items received by the Ledger FI must be posted to the Customers account as at PD Day (or the next business day after PD Day if the PD Day is a public holiday in the relevant State/Territory).
Last amended effective 5/12/07

Australian Payments Clearing Association Limited 7.12

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

(Note: The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) requires that certain information must be included in electronic funds transfer instructions and imposes pre-conditions which must be satisfied before financial institutions may initiate, pass on or take any other action to carry out the electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) (b) return any Debit Items which cannot or will not be paid, no later than the close of business on the next business day after the PD Day (or the second business day after PD Day if the PD Day is a public holiday in the relevant State/Territory) in accordance with clause 7.15; assist its Customers with enquiries on Debit Items made to the Customers' accounts; process claims on behalf of Customers to the relevant Sponsors and, if applicable, Representatives of Sponsors which are Tier 2 Participating Members, in each case through the relevant DDR Claims Contact listed in Appendix B7 and otherwise in accordance with these Procedures; ensure that the name of remitter and, where present, the lodgement reference details from the Detail Record are printed on all Customer statements; if it receives any Refused Item (Record Type 3) which it cannot accept, ascertain from the Detail Record for that Refused Item the identity of the relevant Sponsor and arrange onforwarding of that Refused Item in accordance with that Sponsors directions; notify the Company not less than 15 business days before making any change to its DDR Claims Contact or Claims Account details as published in Appendix B7, nominating an effective date for the change, to enable the Company to publish any amended details to Participating Members before they take effect; accept a written instruction, or an instruction in such other form as it determines, that it receives from a Customer to cancel a Direct Debit Request addressed by that Customer to a Debit User and act on that instruction by promptly forwarding to the Sponsors DDR Claims Contact specified in Appendix B7 a Cancellation Request and ensuring, as far as practicable (having regard to the fact that some Debit Items may already have been exchanged and/or partly processed), that no further Debit Items under the Direct Debit Request which is the subject of the Customers instruction to cancel are posted to the Customers account; upon request, provide a Customer with a Regular Arrangements List as soon as practicable and in any event within 5 business days of receiving the request; and upon request, assist a Customer to notify Debit Users of a change in the account to be debited by: (i) (ii) (iii) assisting the Customer to identify the Debit Users on the Regular Arrangements List that need to receive a Switch of Financial Institution and Account Details; completing a Switch of Financial Institution and Account Details for each Debit User identified pursuant to clause 7.12(j)(i) for the Customer to sign; and forwarding a Switch of Financial Institution and Account Details to the applicable Sponsors Account Switching Contact Point (specified in Appendix B12) within 2 business days of the Customer signing it.

Inserted effective 16/04/07

Last amended Effective 5/12/07

(c) (d)

Last amended effective 31/3/00

Last amended effective 04/03/08

(e)

Last amended effective 31/3/00

(f)

Last amended effective 31/3/00

(g)

Last amended effective 11/6/08

(h)

Last amended effective 1/11/08

(i) (j)

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

Inserted effective 1/11/08

The obligations in clauses 7.12(i) and 7.12(j) only apply to a Personal Account. Australian Payments Clearing Association Limited 7.13

Inserted effective 29/12/08

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

But nothing in this Part 7 is to be taken to require a Ledger FI to accept and post Debit Items to a Customer's account when: (i) (ii) to do so would be contrary to the Customer's formal instructions to it; or the Debit Item will be returned in accordance with clause 7.15(b) because it will not be paid.

Last amended effective 1/11/08

Last amended effective 1/11/08

Inserted effective 1/11/08

A Ledger FI that does not post a Debit Item to a Customers account because of the circumstances described in (i) or (ii) above is not relieved of the obligation to effect settlement for that Debit Item in accordance with the Regulations and these Procedures. [Previous note to paragraph deleted.] Debit Users who are Responsible Entities/Trustees/Managers of Trusts, Superannuation Funds etc. [Previous clause 7.12 deleted.] Debit User Indemnity - Stamp Duty [Previous clause 7.13 deleted.] Lodgement FIs responsibilities 7.13 A Lodgement FI must ensure that: (a) each Debit Users Files and Items which are exchanged conform with the DE File User Item Specifications (see Appendix C1) prior to their being exchanged;

Inserted effective 1/11/08

Deleted effective 20/7/2001

Deleted effective 31/3/00

Deleted effective 31/3/00

Inserted effective 31/3/00

Inserted effective 31/3/00

(Note: The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) requires that certain information must be included in electronic funds transfer instructions and that certain information must be obtained in respect of those instructions before financial institutions may initiate, pass on or take any other action to carry out the electronic funds transfer instructions. Please refer to Part 5 of the Act for details.) (b) if it is not itself the Sponsor, approval in writing has been obtained from the Sponsor prior to lodging the Debit Files on behalf of the User; the Debit User has a correct Trace Record for each transaction on the Debit Files lodged by the Lodgement FI ; if the Trace Record Institution specified or to be specified in respect of the Debit Users Debit Items is not the Sponsor, that Trace Record Institution has consented in writing to be specified as the Trace Record Institution for that Debit Users Debit Items; and the Debit Users lodgements are consistent with the Debit Users normal business practice or needs and systems are in place to monitor File lodgements and manage unusual variations to lodgement patterns on an on-going basis.

Inserted effective 16/04/07

(c)

(d)

(e)

Australian Payments Clearing Association Limited 7.14

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 7 Direct Debit System

If the Lodgement FI is not itself the Sponsor and lodges Debit Files for a User without having obtained prior approval from the Sponsor of that User for the time being, the Lodgement FI is held liable in respect of all Debit Items lodged by it, for all purposes under these Procedures as if it were the Sponsor, that is, for all responsibilities as prescribed in clause 7.5 of the Procedures (including without limitation the Sponsors indemnity referred to in clause 7.5(b)). For this purpose, any such Lodgement FI must ensure its DDR Claims Contact and Claims Account details are published in Appendix B7 and that it notifies the Company not less than 15 business days before making any change to those details, nominating an effective date for the change, to enable the Company to publish any amended details to Participating Members before they take effect. Form PD-C [deleted]

Last amended effective 11/6/08

Deleted effective 31/3/00

Printing/Publication of Direct Debit Request 7.14 A Sponsor must notify a prospective Debit User and, where relevant, an existing Debit User : (a) that the Sponsor must check and approve the format, content and medium proposed for a Direct Debit Request and any information which these Procedures require a Sponsor to ensure is given to Customers in connection with the Direct Debit Request (including without limitation the DDR Service Agreement) BEFORE printing or other formal means of publication to Customers is undertaken by the Debit User; that the Debit User may include its logo on the Direct Debit Request or other related material approved by the Sponsor for the purposes of, and in accordance with, these Procedures; that the Debit User may include a logo approved by the Company for use in connection with the provision of direct debit services in BECS (as notified by the Sponsor) on the Direct Debit Request and other related material approved by the Sponsor for the purposes of, and in accordance with, these Procedures BUT ONLY for as long as the Debit User continues to comply fully with its obligations as a Debit User.

Inserted effective 31/3/00

Last amended effective 31/3/00

(b)

(c)

The Sponsor, on behalf of the Company, must ensure that the Debit User uses any logo of the Company strictly as required by clause 7.14(c) and ceases to use any such logo immediately upon its access to BECS as a Debit User being withdrawn by the Sponsor or otherwise ceasing. Unpaid Direct Debits 7.15 Every Debit Item received by a Participating Member must be: (a) (b) paid; or returned electronically to the Trace Record Institution by no later than the close of business on the next business day after the PD Day (or the second business day after PD Day if the PD Day is a public holiday in the relevant State/Territory).
Last amended effective 5/12/07 Last amended effective 28/10/96

For the avoidance of doubt, the electronic return of a Debit Item to the BSB Number and account number in character positions 81 to 96 inclusive of the Detail Record for that Debit Item is sufficient for the purposes of clause 7.15(b) above.

Inserted effective 27/07/07

The next page is 8.1 Part 8 is Confidential

Australian Payments Clearing Association Limited 7.15

[ABN 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 8 Confidential File/Item Rejection

PART 8

FILE/ITEM REJECTION (Confidential) The next page is 9.1

Australian Payments Clearing Association Limited 8.1

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 9 Settlement

PART 9

SETTLEMENT

Date of Settlement 9.1 Subject to clause 9.1A, settlement between Tier 1 Participating Members must be effected by 9.00am Sydney time on the business day after the relevant Items are exchanged unless otherwise agreed bilaterally, with an interest adjustment on balances owing being passed between Tier 1 Participating Members at such times and in such manner and at such rates and in respect of such type or types of Items as may be determined from time to time by the Management Committee. Subject to Regulation 12.8 and the regulations and procedures or manual governing any other Clearing System, Tier 1 Participating Members may also incorporate into an Exchange Summary produced pursuant to this Part 9 with respect to value settlement for Items exchanged in BECS, value settlement amounts which relate to payment instructions which are exchanged between Participating Members but which payment instructions are not Items exchanged in BECS. If such value settlement amounts for payment instructions which are exchanged between Participating Members but which are not Items are incorporated into an Exchange Summary with respect to value settlement for Items exchanged in BECS, then settlement of such amounts must be performed in accordance with the provisions of the Regulations and these Procedures (including without limitation the Failure to Match Rules and any provisions applicable where an FTS Event occurs) as though those payment instructions are Items exchanged in BECS. 9.1A Settlement in respect of Government Payments is effected by posting to Tier 1 Participating Members Exchange Settlement Accounts or equivalent accounts in the Morning Settlement Session on the PD Day, in accordance with the procedures advised by the Reserve Bank of Australia from time to time.
Last amended effective 18/01/02

Inserted effective 20/08/04

Inserted effective 20/08/04

Last amended effective 1/04/02

Method of Settlement 9.2 The procedures detailed in this clause 9.2 do not apply to settlements of the type referred to in clause 9.1A. Subject to clause 9.3, settlement must be effected in Sydney by 9.00am Sydney time for the net amount owing between each Tier 1 Participating Member and all other Tier 1 Participating Members in Exchange Settlement Account funds. From 12 December 1995, each Tier 1 Participating Member is responsible for separately identifying the amounts which are payable or receivable in respect of all Items exchanged by it or on its behalf, and for notifying the relevant settlement figures to the Collator in the manner provided for in this clause 9.2. Tier 1 Participating Members must transcribe inward/outward credits/debits values, volumes and net balances as set out in the File Exchange Summaries to net positions on an Exchange Summary and agree settlement figures. The agreed settlement figures must be sent to the Collator by 11.00pm Sydney eastern standard time or 12.00 midnight Sydney eastern summer time on the day of exchange as an Exchange Summary by using the Exchange Summary Data File Transfer Facility. The specifications for, and file formats required by, the Exchange Summary Data File Transfer Facility can be found on the Companys extranet.
Last amended effective 04/03/08 Inserted effective 16/4/99

Last amended effective 11/6/08

Australian Payments Clearing Association Limited 9.1

[ABN 12 055 136 519] Amendment No. E038, issued as CS2/r&p/004.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 9 Settlement

Any Tier 1 Participating Member may at any time before 11.00pm Sydney eastern standard time or 12.00 midnight Sydney eastern summer time call for reconciled provisional settlement figures showing all the settlement figures for its counterparties up to the time of preparation. In such a case, the Tier 1 Participating Member must immediately verify that the settlement figures provided by it to the Collator have been reflected in the reconciled provisional settlement figures and notify the Collator of any error. This process may also be used for adjustments of clearing errors between Tier 1 Participating Members. After 11.00pm or 12.00 midnight (as the case may be), the Collator will send reconciled revised settlement figures to each Tier 1 Participating Member showing settlement figures for all counterparties received by the cut-off time. If those reconciled revised settlement figures reflect input errors, the Tier 1 Participating Member must immediately notify the Collator, but may not at that time make any further adjustments of clearing errors. If the counterparty settlement figures do not agree, the Collator will apply the Failure to Match Rules. The Collator will then calculate for each Tier 1 Participating Member a final settlement figure to be payable to or receivable by that Tier 1 Participating Member (if applicable derived from the application of the Failure to Match Rules) and after computing and making adjustments for (on a multilateral net basis) the final net cross Clearing System settlement figure for that Tier 1 Participating Member as a consequence of its participation in the Bulk Electronic Clearing System (CS2) and any other Clearing System operating on a deferred net settlement basis (including but not limited to the High Value Clearing System (CS4) if that system is settling on a deferred net basis in fall back mode because settlements cannot occur in real time as a result of some contingency) notify that Tier 1 Participating Member of its final net cross Clearing System settlement figure. The Tier 1 Participating Member must then immediately confirm this final net cross Clearing System settlement figure to the Collator following which the Collator will immediately advise the Reserve Bank of Australia of the final net cross Clearing System settlement figure. On the day of notification the Tier 1 Participating Member must settle its final net cross Clearing System settlement figure. The Failure to Match Rules are as follows: (a) if the amount that one Tier 1 Participating Member claims is owed to it by another Tier 1 Participating member is larger than the amount admitted by that other Tier 1 Participating Member, the lesser amount will be accepted as the final settlement figure; in particular, if one Tier 1 Participating Member does not admit that any amount is owing, or fails to provide settlement figures by the latest time allowed, the final settlement figure in that instance will be zero; similarly, if each of two Tier 1 Participating Members claims that the balance between them is in its favour, or if each of two Tier 1 Participating Members claims that the balance between them is in favour of the other, the final settlement figure in that instance will be zero.

Last amended effective 5/12/07

Last amended effective 5/12/07

(b)

(c)

The Reserve Bank of Australia will directly apply to the Exchange Settlement Accounts of Tier 1 Participating Members entries in accordance with the final net cross Clearing System settlement figures provided to it by the Collator. Variations to Normal Settlement 9.3 On any day which is a holiday in both Sydney and Melbourne, settlement will be deferred to the next day which is a business day in Sydney or Melbourne or both.

Last amended effective 5/12/07

Last amended effective 28/10/96

Australian Payments Clearing Association Limited 9.2

[ABN 12 055 136 519] Amendment No. E038, issued as CS2/r&p/004.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 9 Settlement

Interest Adjustment 9.4 Where settlement in respect of any exchange of any Item is (for whatever reason) effected on a day other than the day on which that Item is exchanged for value, an adjustment of interest will be made between the creditor and debtor Tier 1 Participating Members in respect of that Item calculated at the interest rate (termed the ESR by the Reserve Bank of Australia) payable by the Reserve Bank of Australia on overnight credit balances of Exchange Settlement Accounts held with the Reserve Bank of Australia. The Collator will record the net balance owing to or by each Tier 1 Participating Member for each day on which it despatched settlement figures and calculate the interest on the net balance owing for the number of days elapsed until the day of settlement using the ESR applicable to each of those days during that period. The Collator will notify each Tier 1 Participating Member of the net amount due to or by it on account of such interest and include such interest each day in the 9am settlement amount of each Tier 1 Participating Member.
Clause 9.5 is Confidential
Last amended effective 13/06/01

Last amended effective 20/08/04

Last amended effective 1/7/05

Exchange Summary Data File Transfer Facility 9.6 The Exchange Summary Data File Transfer Facility must (subject to the following sentence) be used to send and receive the settlement figures required by these Procedures to/from the Collator. Tier 1 Participating Members may bilaterally agree with the Collator to send/receive settlement figures (or parts thereof) to/from the Collator by other means. Tier 1 Participating Members must have facsimile capability for fallback purposes. If the Exchange Summary Data File Transfer Facility is unavailable then affected Tier 1 Participating Members must immediately advise the Collator by telephone and send/receive settlement figures to/from the Collator by facsimile. As soon as an applicant is advised by the Secretary that its application for BECS Tier 1 membership has been accepted it must contact the Collator to arrange testing and implementation of the Exchange Summary Data File Transfer Facility. The specifications for the Exchange Summary Data File Transfer Facility can be found on the Companys extranet.

Inserted effective 30/01/06

Last amended effective 5/12/07

The next page is 10.1

Australian Payments Clearing Association Limited 9.3

[ABN 12 055 136 519] Amendment No. E038, issued as CS2/r&p/004.08

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

PART 10

CONTINGENCY PROCEDURES

Responsibilities 10.1 Participating Members have a responsibility to each other and to BECS as a whole, to co-operate in resolving any processing difficulties including during Contingencies. To the extent that such co-operation does not adversely affect its own processing environment, a Participating Member receiving a request for assistance may not unreasonably withhold such assistance. All Tier 1 Participating Members must include the use of email as a minimum contingency exchange arrangement. 10.1A If bilaterally agreed contingency exchange arrangements are invoked as part of the half yearly testing of such contingency arrangements, the Sending Institution must ensure that files sent are not duplicated. If bilaterally agreed contingency exchange arrangements are invoked in an actual Disabling Event (that is, not a test), it is the responsibility of the Receiving Institution to ensure that it does not process duplicated files received over the primary link.
Inserted effective 30/06/03

Last amended effective 1/11/08

10.1.B

Inserted effective 03/04/06

Options 10.2 Where processing difficulties occur, depending upon the circumstances, remedial action could include: (a) (b) (c) (d) agreeing to delay transmission pending resolution of the problem; invoking bilaterally agreed arrangements which are in place and recorded in Appendix L; invoking the contingency procedures (as set out in Appendix I); or invoking use of bilaterally agreed physical medium for contingency exchanges where the use of electronic communications for primary and contingency exchange arrangements are rendered unusable.
Last amended effective 30/06/03

Last amended effective 30/06/03

Last amended effective 30/06/03

Last amended effective 30/06/03

Inserted effective 23/09/02

If bilaterally agreed contingency exchange arrangements are invoked, the sending or Disabled Tier 1 Participating Member must complete and forward a Contingency File Exchange Form (as set out in Appendix M1) to the receiving Tier 1 Participating Member. All Tier 1 Participating Members are required to record all agreed primary exchange arrangements in the BECS Procedures Appendix K and immediately notify the Company of any changes to these arrangements. All Tier 1 Participating Members are required to record all bilaterally agreed contingency exchange arrangements in the BECS Procedures Appendix L and immediately notify the Company of any changes to these arrangements. 10.3 [Magnetic Tape Handling Deleted]

Inserted effective 30/06/03

Last amended effective 30/06/03

Last amended effective 30/06/03

Deleted effective 23/09/02

Australian Payments Clearing Association Limited 10.1

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

Physical Medium Exchange Standards 10.4 Full identifying information relating to ownership of the physical medium and the details of contents must be marked on each piece of physical medium exchanged. Such information is to include the following: creation date; Item number n of Total Items (eg. cartridge 1 of 3); date to be processed; and Sending or Disabled Tier 1 Participating Members full name and return address.

Last amended effective 23/09/02

Last amended effective 23/09/02

Last amended effective 23/09/02

Last amended effective 30/06/03

Read/Write Format Standards for Physical Medium 10.5 The industry standard for physical medium is compact disc. The following read/write format standards apply unless other formatting is bilaterally agreed between exchanging parties: CD-ROM CD-ROM, 600 Megabyte (MB)

Last amended effective 23/09/02

Last amended effective 30/06/03

Other forms of physical medium used must be bilaterally agreed between exchanging parties. Structure of File 10.6 File header - unspecified Descriptive record (one per User) Detail records File total record (one per User) Trailer labels - unspecified Example of File formats:
Last amended effective 23/09/02

Multi User
Descriptive Detail File Total (0) (1) (7)

Single User
Descriptive Detail File Total (0) (1) (7)

Descriptive Detail File Total

(0) (1) (7)

Australian Payments Clearing Association Limited 10.2

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

Return/Refusal Files

Descriptive Detail File Total

(0) (2) (7)

Descriptive Detail File Total

(0) (3) (7)

Descriptive Detail Detail File Total

(0) (2) (3) (7)

Descriptive Detail Detail File Total

(0) (3) (2) (7)

10.7

[Blocking Factor - Deleted]


Clause 10.8 is Confidential

Deleted effective 23/09/02

Contingency Exchange Arrangements 10.9 Tier 1 Participating Members who experience partial or total loss of primary exchange arrangements, resulting in a Disabling Event (see Appendix I, clause 5.2), may be required to invoke contingency exchange arrangements with other Tier 1 Participating Members. The industry standard for these arrangements is bilaterally agreed alternate electronic communications.

Inserted effective 23/09/02

Last amended effective 04/03/08

Bilateral Testing of Contingency Exchange Arrangements 10.10 A Tier 1 Participating Member must bilaterally test its contingency exchange arrangements, which may be alternate electronic communications or a secondary method of contingency exchange arrangements, with a minimum of one other Tier 1 Participating Members at least once each calendar half year and in accordance with the Contingency Exchange Testing Schedule. The Contingency Exchange Testing Schedule specifies the Tier 1 Participating Members with which to conduct testing on a rotating regular basis to ensure that the contingency exchange arrangements with all Tier 1 Participating Members are tested over a period of time that is no more than four calendar years apart. TheContingency Exchange Testing Schedule will be revised in the event of the admission or resignation of a Tier 1 Participating Member or a change in the capacity in which a Tier 1 Participating Member participates in the Bulk Electronic Clearing System (CS2).

Inserted effective 23/09/02

Last amended effective 11/6/08

Last amended effective 1/11/08

Australian Payments Clearing Association Limited 10.3

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

A Tier 1 Participating Member must send live data (DE transaction data and the associated DE summary file) using the contingency exchange arrangement and the data received must be used to process actual live transactions. Transmitting duplicate data during the test using primary exchange arrangements is not permitted. In addition, Tier 1 Participating Members using physical medium for contingency exchange arrangements must complete a successful test of each bilateral arrangement at least once each calendar half year until replaced with alternate electronic communications. Contingency Procedures Testing Certificate 10.11 All Tier 1 Participating Members must sign a Contingency Procedures Testing Certificate each calendar half year to certify that the Tier 1 Participating Member has successfully tested its contingency exchange arrangements in accordance with clause 10.10. The Company will issue all Tier 1 Participating Members with a memorandum and Contingency Procedures Testing Certificate each calendar half year requesting Tier 1 Participating Members to finalise all bilateral testing and sign the Certificate. The Certificate must be returned to the Company in the time frames specified. The Management Committee will be advised of all outcomes including any Tier 1 Participating Member who fails to provide a signed Certificate. The Management Committee will determine the course of action required. Standards For Email File Exchange and Security 10.12 Each sending Tier 1 Participating Member must comply with the following minimum standards for the exchange of files: (a) (b) the email must be flagged as High Priority or High Importance; the maximum file size which can be attached to the email must not exceed 5 Megabytes (MB); the email security package must, at a minimum, include the following encryption features: (i) the ability to prevent viewing of email and its attachments by outside parties other than the intended recipient; the ability to prevent the email and its attachments being read by unauthorised persons within your organisation; the ability to prevent viewing of email and its attachments by outside parties other than the intended recipient; the ability to prevent the email and its attachments being read by unauthorised persons within your organisation; the ability to securely send the email and its attachments locked with a public key; the ability of the recipient to open the email and its attachments by unlocking the transmission with a securely generated private key; the ability of the sender to digitally sign the email transmission; and

Inserted effective 03/04/06

Last amended effective 11/6/08

Inserted effective 23/09/02

Last amended effective 1/11/08

Last amended effective 11/6/08

Inserted effective 30/06/03

(c)

(ii)

(iii)

(iv)

(v) (vi)

(vii)

Australian Payments Clearing Association Limited 10.4

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

(d) the following naming conventions for the email are recommended, however members may bilaterally agree to variations: (i) The format of the file name is: DE_F_xx_SSS_RRR_CCC (ii) F = the file type as follows: T = Direct Entry transaction file S = Direct Entry summary file G = Government Direct Entry transaction file H = Government Direct Entry summary file (iii) xx = file number 01-99. For each Disabling Event the file number commences at 01 and increases by 1 for each file (irrespective of file type), until processing returns to normal, even if the Disabling Event spans several days. This ensures that each file has a unique file number. SSS = 3 character Sending Member mnemonic. A Member sending Files on behalf of another Member must, with respect to those files, use the mnemonic belonging to the Member on whose behalf it is sending those Files. RRR = 3 character Receiving Member mnemonic. A Member receiving Files on behalf of another Member must, with respect to those Files, use the mnemonic belonging to the Member on whose behalf it is receiving those Files. CCC = 3 character financial institution mnemonic of the courier, if applicable. The email subject line must include the file name.

Amended effective 19/07/11

Amended effective 19/07/11

(iv)

(v)

(vi) (vii)

(viii) Each email must contain one file only. Members can agree to include more than one File by bilateral agreement and in this case the File names in the subject line must be separated by a slash (/). (ix) The Sending Member must send the email to the nominated email address provided by the Receiving Member on the email file exchange contacts database managed by the Company. The email address should preferably be a generic address (eg. operations@FI.com.au) rather than an individuals address (eg. Mike@FI.com.au). Members can agree to exchange zipped files by bilateral agreement. The file name will have an extension of .zip.
Inserted effective 30/06/03

(x)

Email File Exchange Contacts Database 10.13 Where a Tier 1 Participating Member uses an email security package which requires the exchange of public keys to securely send and read emails, the Tier 1 Participating Member must have lodged any of its public keys in the email file exchange contacts database maintained by the Company. The email file exchange contacts database is managed by the Company and Tier 1 Participating Members are required to nominate an authorised contact to access the database for lodgement and downloading of public keys and provide the following details:

Australian Payments Clearing Association Limited 10.5

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 10 Contingency Procedures

the Tier 1 Participating Members: clearing system; full name; ACN/ARBN/ABN; mnemonic; public key; authorised contact name and title; authorised contact email and telephone details; target email address for file transmissions; contact name and telephone number to confirm receipt of email; and the date the Tier 1 Participating Members details were added/updated on the database.

All Tier 1 Participating Members must complete and lodge an online Email File Exchange Contacts Lodgement Form (as set out in Appendix M2) including attachment of the public keys for use by other Tier 1 Participating Members. The lodgement form is available on the Companys extranet. When a Tier 1 Participating Member makes changes to its public keys or contact details, the Email File Exchange Contacts Lodgement Form must be completed and lodged noting the changes to contact details and/or attaching new public keys. Tier 1 Participating Members will be advised of changes to the database by CS2 operational memorandum. The Email File Exchange Contacts Lodgement Form (as set out in Appendix M2) is used for lodging or amending public keys or contact details which effect only Tier 1 Participating Members.

The next page is 11.1

Australian Payments Clearing Association Limited 10.6

[ABN 12 055 136 519] Amendment No. E045, issued as CS2/r&p/003.11

Bulk Electronic Clearing System (CS2) PROCEDURES Part 11 Liability in the Event of Fraud

PART 11

LIABILITY OF PARTICIPATING MEMBERS IN THE EVENT OF FRAUD

Fraudulent Items 11.1 Tier 1 Participating Members must ensure that their systems and procedures give adequate protection in regard to fraud in connection with Items. Tier 1 Participating Members may return an Item or resort to the dispute resolution process specified in Regulation 13 to resolve any situation with regard to a fraudulent Item.
Clause 11.2 is Confidential

The next page is 12.1

Australian Payments Clearing Association Limited 11.1

[ABN 12 055 136 519] Amendment No. E004, issued as CS2/r&p/004.01

Bulk Electronic Clearing System (CS2) PROCEDURES Part 12 DE File Specifications

PART 12

DE FILE SPECIFICATIONS

Overview 12.1 The DE File Specifications cover the format for electronic exchanges of Files (including Files containing Record Type 1 Items issued by Users, Return Files, Refusal Files and Reversal Files) between Participating Members. All Files exchanged between Participating Members must conform with these specifications. The DE File User Item Specifications cover the normal electronic exchange of Users Record Type 1 Credit Items and Debit Items (detailed in Appendix C1), electronic return of those Users Items (detailed in Appendix C2), electronic Refusal of Returned Items (detailed in Appendix C3) and electronic Reversal of duplicated Items (detailed in Appendix C5). The format is the same regardless of whether the Sending Member uses normal electronic transmission or, if exchanges are done under Contingency Procedures. Items and Files not conforming with the applicable DE File Specifications may be rejected by Receiving Members in accordance with clauses 8.1 and 8.2. Nothing in this clause 12.1 prevents a Sending Member accepting non-standard data (which does not conform with the applicable DE File Specifications) from a User or Bureau or a Lodgement FI, and converting it to the required format for exchange. 12.2 (a) Descriptive Record (Record Type 0) : Except for minor variations in some Field Descriptions, this record type is common to all Files (including Files containing Record Type 1 Items issued by Users, Return Files, Refusal Files and Reversal Files). Detail Record Type 1 : this Record Type is used for both Credit Items and Debit Items issued by a User and credit and debit Reversing Items and contains the required details to enable posting to Customers accounts at the Ledger FI. Detail Record Type 2 : this Record Type is used by the Ledger FI to electronically return a Users (Record Type 1) Item to the Trace Record Institution if that Item cannot be applied. Detail Record Type 3 : this Record Type is used when the financial institution holding the Trace Record account is not prepared to accept a Returned Item and sends it back electronically to the Ledger FI. File Total Record (Record Type 7) is common to all Files (including Files containing Record Type 1 Items issued by Users, Return Files, Refusal Files and Reversal Files) and shows the respective totals of Record Type 1, 2 or 3 Items, as applicable, and the net difference between Credit Items and Debit Items and the totals of each as well as the total number of these Records on the File.
Last amended effective 4/8/2000 Last amended effective 4/8/2000 Last amended effective 4/8/2000

Last amended Effective 25/5/07

(b)

Last amended effective 4/8/2000

(c)

Last amended Effective 25/5/07

(d)

(e)

Character Bit Structure 12.3 Files exchanged between Participating Members are to be in EBCDIC format. Any translation made to or from the EBCDIC format must ensure that the same characters are represented in both the source file and the output file and that the characters comply with the BECS Character Set.
Last amended effective 26/07/10

Australian Payments Clearing Association Limited 12.1

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 12 DE File Specifications

Structure of File 12.4 Descriptive Record (one per User) Detail Records File Total Record (one per User) Example of File formats: Multi User
Descriptive Detail File Total (0) (1) (7)

Single User
Descriptive Detail File Total (0) (1) (7)

Descriptive Detail File Total

(0) (1) (7)

Return/Refusal Files

Descriptive Detail File Total

(0) (2) (7)

Descriptive Detail File Total

(0) (3) (7)

Descriptive Detail Detail File Total

(0) (2) (3) (7)

Descriptive Detail Detail File Total

(0) (3) (2) (7)

Record Format 12.5 Commonly used terms associated with File formatting, and their meanings, are as follows: left justified start input in the first character position of that field.

Australian Payments Clearing Association Limited 12.2

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 12 DE File Specifications

right justified end input in the last character position of that field. blank filled zero filled unsigned fills the unused portion of that field with blank spaces. fills the unused portion of that field with zeros. used in amount field. Amount will not be specified as debit or credit. Descriptive Record, Detail Record, Returned Item Record; Refusal Record; and File Total Record
Last amended Effective 25/5/07

Record Type "0" Record Type "1" Record Type 2 Record Type 3 Record Type "7

Are set out in Appendix C.

Publication of DE User Item File Specifications 12.6 Participating Members may publish and disseminate the DE User Item File Specifications to third parties provided that the column headed "Validation Standard (financial institution use only)" and the information contained in that column are not included in any such publication.

The next page is 13.1 Part 13 is Confidential

Australian Payments Clearing Association Limited 12.3

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 13 Confidential User Records

PART 13

USER RECORDS (Confidential)

The next page is 14.1

Australian Payments Clearing Association Limited 13.1

[ABN 12 055 136 519] Amendment No. E026, issued as CS2/r&p/005.05

Bulk Electronic Clearing System (CS2) PROCEDURES Part 14 Summary File Specification

PART 14

SUMMARY FILE SPECIFICATION

Overview 14.1 All Summary Files exchanged between Participating Members must conform with the Summary File Specification detailed in Appendix C6. The format is the same regardless of whether the Sending Member uses normal electronic transmission or, if exchanges are done under Contingency Procedures. Summary Files not conforming with the applicable Summary File Specification may be rejected by Receiving Members. 14.2 (a) (b) Header Record (Record Type H) : This Record Type is common to all Summary Files. Summary Record (Record Type S) : This Record Type contains summary information for a User as set out in Appendix C6. Trailer Record (Record Type T) : This Record Type is common to all Summary Files.

(c)

Character Bit Structure 14.3 Files exchanged between Participating Members are to be in EBCDIC format. Any translation made to or from the EBCDIC format must ensure that the same characters are represented in both the source file and the output file and that the characters comply with the BECS Character Set.
Last amended effective 26/07/10

Structure of Summary File 14.4 Header Record (one per Summary File) Summary Record (one per User) Trailer Record (one per Summary File) Record Format 14.5 Commonly used terms associated with File formatting, and their meanings, are as follows: left justified : start input in the first character position of that field. right justified : end input in the last character position of that field. blank filled : zero filled : unsigned : fills the unused portion of that field with blank spaces. fills the unused portion of that field with zeros. used in amount field. Amount will not be specified as debit or credit. Header Record; Summary Record; and Trailer Record,

Record Type "H" Record Type "S" Record Type T

are set out in Appendix C6.

Australian Payments Clearing Association Limited 14.1

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Part 14 Summary File Specification

Publication of Summary File Specification 14.6 Participating Members may publish and disseminate the Summary File Specification to third parties provided that the column headed "Validation Standard (financial institution use only)" and the information contained in that column are not included in any such publication.

The next page is A1.1 Appendix A1.1 is Confidential

Australian Payments Clearing Association Limited 14.2

[ABN 12 055 136 519] Amendment No. E043, issued as CS2/r&p/001.10

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix A1

Appendix A is located separately The next page is B1.1

Australian Payments Clearing Association Limited A1.1

[A.B.N. 12 055 136 519] Amendment No. E044, issued as CS2/r&p/004.10

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix B1 Operational Contacts Confidential

Appendix B is located separately The next page is C1.1

Australian Payments Clearing Association Limited B.1

[A.B.N. 12 055 136 519] Amendment No. E037, issued as CS2/r&p/002.08

Amendment No. E043, issued as CS2/r&p/001.10

(Confidential) The next page is D.1

Australian Payments Clearing Association Limited [ABN 12 055 136 519] C1.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix C1 DE File User Item Specifications

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix D Specified Locations

APPENDIX D

Deleted effective 28/10/96

[deleted]

The next page is E.1

Australian Payments Clearing Association Limited [A.B.N. 12 055 136 519] D.1
Amendment No. E037, issued as CS2/r&p/002.08

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix E Approved Representation & Courier Arrangements

APPENDIX E
[deleted]

Appendix E: Deleted effective 28/10/96

The next page is F.1

Australian Payments Clearing Association Limited [ABN 12 055 136 519] E.1
Amendment No. E037, issued as CS2/r&p/002.08

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix F Confidential Approved Electronic Exchange Arrangements

APPENDIX F

APPENDIX F IS LOCATED SEPARATELY

The next page is G1.1 Appendix G1 is confidential

Australian Payments Clearing Association Limited [ABN 12 055 136 519] F.1
Amendment No. E021, issued as CS2/r&p/006.04

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix G1Claiming FI Identification Numbers
(Clause 7.8, Appendix C4)

Confidential

APPENDIX G1 RETURNING/REFUSING FI ID NUMBERS AND REVERSING FI ID NUMBERS

APPENDIX G2 DIRECT DEBIT REQUEST CLAIMING FINANCIAL INSTITUTION IDENTIFICATION NUMBERS APPENDICES G1 & G2 ARE LOCATED SEPARATELY

The next page is H.1

Australian Payments Clearing Association Limited G1.1

[ABN 12 055 136 519] Amendment No. E021, issued as CS2/r&p/006.04

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix H Ledger FIs Requiring PD-C Lists
(Clause 3.3, 5.3, 5.10(f))

APPENDIX H LEDGER FI REQUIRING PD-C LISTS

Deleted Effective 31/3/2000

[Deleted]

The next page is I1.1

Australian Payments Clearing Association Limited H.1

[ABN 12 055 136 519] Amendment No. E013 issued as CS2/r&p/007.02

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 1 Executive Summary

Disabling Events Guidelines

Section 1 Section 2 Section 3 Section 4 Section 5

Executive Summary Roles and Responsibilities Communications Contingency Procedures Disabling Events

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E037, issued as CS2/r&p/002.08

I1.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 1 Executive Summary

1. 1.1

EXECUTIVE SUMMARY Overview These guidelines have been prepared and endorsed by the Management Committee. They are not mandatory rules but intended to guide the Tier 1 Participating Members when exercising discretion to determine what action is to be taken in response to a Disabling Event. Each Disabling Event should be treated on its merits.

1.2

Settlement Unless specifically deferred, settlement will not be affected by the occurrence of a Disabling Event. Settlement will always be effected on the exchange balances. Should a Tier 1 Participating Member fail to provide settlement figures to the Collator, the Failure To Match Rules (Part 9, clause 9.2) will be invoked.
Last amended effective 04/03/08

1.3

Interest As covered in Part 9, clause 9.4, interest will be payable (as normal) on any exchanged Item in respect of which, settlement is effected later than the day on which that Item is exchanged for value. Debit Items Where a Disabling Event occurs and other Tier 1 Participating Members are asked, by a Disabled Participating Member, to hold Debit Files that would have been exchanged in those other Members outward exchanges if not for a Disabling Event, those held Debit Files should retain the original PD-Day. When those Files are actually exchanged, interest will be payable by the Disabled Participating Member from the PD-Day until the date settlement of those Debit Items is effected. No interest is payable with respect to any Debit Items held unexchanged by a Disabled Participating Member where the Disabled Participating Member holds the Items because of a Disabling Event affecting its outward exchanges. Credit Items Where a Disabling Event occurs and other Tier 1 Participating Members are asked, by a Disabled Participating Member, to hold Credit Items that would have been exchanged in those other Members outward exchanges if not for a Disabling Event, no interest will be payable to the Disabled Participating Member. No interest is payable with respect to any Credit Items held unexchanged by a Disabled Participating Member where the Disabled Participating Member holds the Items because of a Disabling Event affecting its outward exchanges.
Last amended effective 04/03/08

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E037, issued as CS2/r&p/002.08

I1.2

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 2 Roles and Responsibilities

2. 2.1

ROLES AND RESPONSIBILITIES Australian Payments Clearing Association Limited (the Company) The roles and responsibilities of the Company, in relation to a Disabling Event, are as follows: to provide support and recommend appropriate actions to be taken by the Disabled Tier 1 Participating Member and impacted Participating Members; and to communicate with Participating Members on matters that affect industry payments and clearing arrangements.

2.2

Participating Members The roles and responsibilities of Participating Members in relation to a Disabling Event are as follows: to ensure that their internal contingency plans are consistent with these industry Contingency Procedures (Part 10); to implement internal contingency procedures in response to a Disabling Event and manage the impact on their internal operations; to assist in implementing industry contingency procedures, if applicable; and communicate directly with their customers, the Company and other relevant parties.

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E013, issued as CS2/r&p/007.02

I2.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 3 Communications

3 3.1

COMMUNICATIONS Overview of Contingency Communication Process This section defines the communications process between the Company and Tier 1 Participating Members in the event of a Disabling Event.

3.2

Tier 1 Participating Member Activates Contingency Arrangements When a Tier 1 Participating Member reports a Disabling Event, they may invoke internal contingency plans, which include invoking Contingency Arrangements as required by BECS Regulations and Procedures.

3.3

Tier 1 Participating Member Advises the Company of a Disabling Event If a Tier 1 Participating Member experiences a Disabling Event, they may complete a PDN (see Appendix J) on the Companys Extranet. The Disabled Tier 1 Participating Member keeps the Company updated on any change concerning the Disabling Event by completing and forwarding subsequent PDN.

3.4

The Company Actions Tier 1 Participating Members Advice If the Company receives a PDN from a Tier 1 Participating Member, sent in accordance with paragraph 3.3, the Company will endeavour to broadcast details of the Disabling Event specified in the PDN to all Participating Members on receipt. All subsequent communications relating to the Disabling Event, (with the consent of the affected Tier 1 Participating Member), would be broadcast at regular intervals to other Participating Members for update purposes.

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E013, issued as CS2/r&p/007.02

I3.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 4 Contingency Procedures for Disabling Events 4. 4.1 CONTINGENCY PROCEDURES FOR DISABLING EVENTS The Companys Contingency Role This procedure may be followed by the Company in the event of a Tier 1 Participating Member experiencing a Disabling Event: receive and record PDN from the Disabled Tier 1 Participating Member; request the Disabled Tier 1 Participating Member to implement Contingency Procedures, if appropriate, detailed in Appendix I; initiate a broadcast announcement to all Participating Members after receiving a PDN during business hours1; and broadcast additional updates to all Participating Members at regular intervals, where appropriate, on behalf of the Disabled Tier 1 Participating Member.

4.2

Tier 1 Participating Members Contingency Procedure This procedure may be followed by Tier 1 Participating Members where a Disabling Event occurs: actively pursue the identification and appropriate resolution of problem causing the Disabling Event; invoke the appropriate internal contingency plans which may include invoking the Contingency Procedures set out in the BECS Procedures (Part 10) and Appendix I; notify the Company of the internal assessment that a Disabling Event may directly or indirectly impact other Participating Members by completing a PDN (Appendix J); consider and take appropriate action on the advice and recommendations given by the Company regarding the Disabling Event, if appropriate; and keep the Company updated of any change concerning the Disabling Event by completing and forwarding subsequent PDNs at two (2) hourly intervals, or more frequently if appropriate, during business hours2.

1 2

Monday to Friday, 8.30am to 5.30pm Monday to Friday, 8.30am to 5.30pm

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E013, issued as CS2/r&p/007.02

I4.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 5 Disabling Events

DISABLING EVENTS 5.1 Overview This section describes each identified Disabling Event that may occur and appropriate actions that the Company and Tier 1 Participating Members may undertake to address them. Each Disabling Event covered is categorised.

5.2

Disabling Events There are three (3) categories of event that may result in a Disabling Event: Tier 1 Participating Member is unable to electronically send and/or receive data file(s) using primary exchange arrangement; Tier 1 Participating Member is unable to process data file(s); and Tier 1 Participating Member is unable to provide settlement data to the Collator.
Last amended effective 5/12/07

Each of these categories only results in a Disabling Event if it affects, or may affect, the ability of a Participating Member to participate to the normal and usual extent in exchanges of Items (including Record Type 1 Items issued by any User, Returned Items, Refusal Items and Reversing Items).

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E036, issued as CS2/r&p/006.07

I5.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 5 Disabling Events

Disabling Events & Actions 5.2.1 Disabling Event Category No. 1


Last amended effective 5/12/07

Disabling Event Description: Tier 1 Participating Member(s) unable to send or receive Direct Entry (DE) files to other Tier 1 Participating Members using primary exchange arrangements.

EXTENT OF THE DISABLING EVENT


Reported by a Tier 1 Participating Member where Primary Exchange Arrangement has failed. Reported by a Tier 1 Participating Member that they have failed to exchange DE files with another Tier 1 Participating Member using Contingency Exchange Arrangements, assuming that the Primary Exchange Arrangement failure has already been reported.
1 2

POSSIBLE ACTIONS1 BY IMPACTED TIER 1 PARTICIPATING MEMBER(S)


Invoke Contingency Procedures which may include: arrange a later transmission after the problem is fixed agreed bilaterally with other Tier 1 Participating Members; complete a Contingency File Exchange Form (as set out in Appendix M1) and forward to the receiving Tier 1 Participating Member; exchange files using Contingency Exchange arrangements as tabled in Appendix L Contingency Exchange Arrangements Matrix; send initial PDN to the Company; and broadcast regular PDN advice to the Company, during business hours2, until Disabling Event resolved.

POSSIBLE ACTIONS BY THE COMPANY TO ASSIST


To assist Disabled Tier 1 Participating Member: broadcast PDN to all Participating Members (in consultation with Disabled Tier 1 Participating Member); broadcast updates to all Participating Members until Disabling Event resolved; provide advisory support and coordination to impacted Participating Member(s); and monitor progress during business hours2.

Invoke Contingency Procedures which may include: arrange a later transmission after the problem is fixed agreed bilaterally with other Tier 1 Participating Members; complete a Contingency File Exchange Form (as set out in Appendix M1) and forward to the receiving Tier 1 Participating Member; exchange files using other bilaterally agreed Contingency Exchange arrangements as tabled in Appendix L Contingency Exchange Arrangements Matrix; identify problems and invoke resolutions with Contingency Exchange arrangements; send PDN to the Company, during business hours ; and broadcast regular PDN advice to the Company, during business hours2, until Disabling Event resolved.
2

To assist Disabled Tier 1 Participating Member: broadcast PDN to all Participating Members (in consultation with Disabled Tier 1 Participating Member); broadcast updates to all Participating Members until Disabling Event resolved; monitor progress during business hours2; and provide advisory support and coordination to impacted Participating Members.

Agreed bilaterally Monday to Friday, 8.30am to 5.30pm

Australian Payments Clearing Association Limited I5.2

[ABN 12 055 136 519] Version E036, issued as CS2/r&p/006.07

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 5 Disabling Events

5.2.2 Disabling Event Category No. 2


Disabling Situation/Event Description: Participating Member(s) unable to process Direct Entry (DE) data internally and/or unable to process data received from their Tier 1 Participating Member representative (if applicable).

EXTENT OF THE DISABLING EVENT


Reported by any Participating Member that they are unable to process DE data internally

POSSIBLE ACTIONS1 BY IMPACTED TIER 1 PARTICIPATING MEMBER(S)


Invoke Contingency Procedures which may include: delay exchange pending resolution of the problem if problem relates to electronic files received - agreed bilaterally with other Tier 1 Participating Members; send initial PDN to the Company during business hours; and broadcast regular PDN to the Company, during business hours2 until Disabling Event resolved.

POSSIBLE ACTIONS BY THE COMPANY TO ASSIST


To assist Disabled Participating Member: broadcast Members; PDN to all Participating

broadcast updates to all Participating Members until Disabling Event resolved; provide advisory support and coordination to impacted Participating Member(s); and monitor progress during business hours2.

Agreed bilaterally Monday to Friday, 8.30am to 5.30pm

Australian Payments Clearing Association Limited I5.3

[ABN 12 055 136 519] Version E036, issued as CS2/r&p/006.07

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix I Contingency Procedures For Disabling Events Section 5 Disabling Events

5.2.3

Disabling Event Category No. 3

Disabling Situation/Event Description: Tier 1 Participating Member unable to provide settlement data to Collator

EXTENT OF THE DISABLING EVENT


Reported by a Tier 1 Participating Member that they are unable to provide part or all settlement figures to the Collator with respect to Direct Entry files sent and received for the business day.

POSSIBLE ACTIONS1 BY IMPACTED TIER 1 PARTICIPATING MEMBER(S)


Refer to Part 9 of the BECS Procedures.

POSSIBLE ACTIONS BY THE COMPANY TO ASSIST

Agreed bilaterally

The next page is J1.1

Australian Payments Clearing Association Limited I5.4

[ABN 12 055 136 519] Version E036, issued as CS2/r&p/006.07

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix J Processing Difficulty Notification Forms

LAST AMENDED EFFECTIVE 11/6/08

APPENDIX J1 APCS AND BECS PROCESSING DIFFICULTY NOTIFICATION

APCS and BECS Processing Difficulty Notification


Disclaimer: This document has been compiled in good faith from information provided by third parties. No representation or warranty is made by APCA as to the truth or accuracy of the information and APCA, its officers, employees and agents expressly disclaim all and any liability in respect of the information.

DETAILS
Date of Advice: DD MMM YYYY

Notifying Institution: Institution Experiencing Difficulty:

CONTACT POINT
`
Name: Phone Number: Fax Number: Email Address:

PAYMENT STREAMS AFFECTED


APCS Australian Paper Clearing System BECS - Bulk Electronic Clearing System

PROCESSES AFFECTED APCS


Delivery of Not-for-Value Items Dishonours - Paper Dishonours - Electronic Refusals - Electronic Voucher Required - Electronic
Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E038, issued as CS2/r&p/004.08

J1.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix J Processing Difficulty Notification Forms

Special Answers - Paper Special Answers - Electronic Urgent Trace Requests - Paper Urgent Trace Requests Electronic

PROCESSES AFFECTED - BECS


Detail Records Returned Items Refusals

EXPECTED DURATION OF PROCESSING DIFFICULTY


Date Difficulty Occurred: DD Expected Availability Time: MMM YYYY (Approximate)

Date of Availability: DD MMM YYYY

COMMENTS

ATTACHMENTS

There are No Attachments to this PDN

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E038, issued as CS2/r&p/004.08

J1.2

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix J Processing Difficulty Notification Forms

LAST AMENDED EFFECTIVE 25/5/07

APPENDIX J2 BECS PROCESSING DIFFICULTY NOTIFICATION

BECS Processing Difficulty Notification


Disclaimer: This document has been compiled in good faith from information provided by third parties. No representation or warranty is made by APCA as to the truth or accuracy of the information and APCA, its officers, employees and agents expressly disclaim all and any liability in respect of the information.

DETAILS
Date of Advice: DD MMM YYYY

Notifying Institution: Institution Experiencing Difficulty:

CONTACT POINT
Name: Phone Number: Fax Number: Email Address:

PAYMENT STREAMS AFFECTED


BECS - Bulk Electronic Clearing System

PROCESSES AFFECTED
Detail Records Returned Items Refusals

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E034, issued as CS2/r&p/003.07

J2.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix J Processing Difficulty Notification Forms

EXPECTED DURATION OF PROCESSING DIFFICULTY


Date Difficulty Occurred: DD Time of Availability: MMM YYYY (Approximate)

Date of Availability: DD MMM YYYY

COMMENTS

ATTACHMENTS

There are No Attachments to this PDN


The next page is K1.1

Australian Payments Clearing Association Limited [ABN 12 055 136 519] Version E034, issued as CS2/r&p/003.07

J2.2

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix K Primary Exchange Arrangements Matrix Confidential

APPENDIX K - PRIMARY EXCHANGE ARRANGEMENTS MATRIX PRIMARY EXCHANGE ARRANGEMENTS MATRIX

APPENDIX K IS LOCATED SEPARATELY

The next page is L1.1

Australian Payments Clearing Association Limited [ABN 12 055 136 519]

Version E018, issued as CS2/r&p/003.04

K1.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix L Contingency Exchange Arrangements Matrix Confidential

APPENDIX L - CONTINGENCY EXCHANGE ARRANGEMENTS MATRIX

APPENDIX L IS LOCATED SEPARATELY

The next page is M1.1

Australian Payments Clearing Association Limited [ABN 12 055 136 519]

Version E018, issued as CS2/r&p/003.04

L1.1

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M1 Contingency File Exchange Form (Part 1.1, Clause 10.2)
Inserted effective 30/06/03

Sending/Disabled Participating Members Logo (Optional)

BECS Contingency File Exchange Form


Date sent: / /
CONFIDENTIAL COMMUNICATION: This communication is confidential and intended only for the use of the addressee. If you have received this communication in error, please notify the financial institution from which you have received it, at the telephone number given, to arrange disposal. Unauthorised use of the information in this message may result in legal proceedings against the user. Thank you.

To: Fax number: Email:

[Full Name of Receiving Participating Member]

Please refer to the email file exchange contacts database for details of Receiving Members facsimile number / email address.

From: Fax number: Authorised Contact: (Name & position) Email: Signature:

[Full Name & ACN/ARBN/ABN of Sending Participating Member]

We advise that due to a Disabling Event we are experiencing a partial/total loss of our ability to send/receive DE files using our primary exchange arrangements. We seek your assistance in sending/receiving our files as detailed below. Sending Filename: File size : Number of Items in file: Type of items in file: Total Value of file: Debits Credits Expected Transmission (Date/Time): Sending Files: File will be sent using the following Contingency Exchange Arrangement Receiving Files: Please forward our files using the following arrangement.
Email File Exchange Alternate electronic link Pass through Courier using ________2 Physical Medium using ____________3 Other please specify ______________ Email File Exchange Alternate electronic link Pass through Courier using ________1 Physical Medium using ____________ Other please specify _______________ Standard (non-Government) Direct Entry items Government Direct Entry items

$ $

Please acknowledge successful receipt of our file(s) by contacting : Contact (Name & position) Please acknowledge acceptance of our file(s) by contacting : Contact (Name & position) Contact Phone: Contact Phone:

2 3

Include full name or mnemonic of pass through courier. Provide details of the type of physical medium to be used (eg: CD, tape cartridge)

Australian Payments Clearing Association Limited M1.1

[A.B.N. 12 055 136 519] Amendment No. E014, issued as CS2/r&p/002.03

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M2 Email File Exchange Forms (Part 1.1, Clause 10.2)

CONTACTS LODGEMENT FORM

Australian Payments Clearing Association Limited M2.1

[A.B.N. 12 055 136 519] Amendment No. E037, issued as CS2/r&p/002.08

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M2 Email File Exchange Forms (Part 1.1, Clause 10.2)

PUBLIC KEY LODGEMENT FORM

Australian Payments Clearing Association Limited M2.2

[A.B.N. 12 055 136 519] Amendment No. E037, issued as CS2/r&p/002.08

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M3 Contingency Procedures Testing Certificate (Clause 10.11)
Last amended effective 23/12/09

BECS CONTINGENCY PROCEDURES TESTING


Each Tier 1 Participating Member in the Bulk Electronic Clearing System (BECS/CS2) is required to have in place contingency exchange arrangements and to test such arrangements regularly. These requirements are set out in: Part 10, clauses 10.10 to 10.13 of the BECS Procedures.

Specifically, the Procedures documents require each Tier 1 Participating Member to test its contingency exchange arrangement: with a minimum of one other Tier 1 Participating Member, at least once each calendar half year, over a period of time that is no more than four calendar years apart, using live data, and data received must be used to process actual live transactions.

Tests to be done each calendar half year should be with partners, to be arranged bilaterally. Participating Members choosing to use physical medium for contingency exchange must test each bilateral arrangement at least once every calendar half year, until such physical medium is replaced with alternate electronic communication. After every test of contingency exchange arrangements, each Tier 1 Participating Member is required to: provide APCA with a signed Contingency Procedures Testing Certificate; and confirm or amend the contact details held on APCA's Email File Exchange Contacts Database.

Details of person providing the Contingency Procedures Testing Certificate


From: (Name of person) __________________________________________________________________

Institution _____________________________________________________________________________ (Tier 1 Participating Member) ABN/ARBN/ACN: __________________________________________________________________ Please complete and return before [ Insert date ] to APCA Operations Australian Payments Clearing Association Limited Fax: (02) 9221 8057 Email: <operations@apca.com.au>

Australian Payments Clearing Association Limited M3.1

[A.B.N. 12 055 136 519] Amendment No. E042, issued as CS2/r&p/003.09

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M3 Contingency Procedures Testing Certificate (Clause 10.11)
Last amended effective 23/12/09

CONTINGENCY PROCEDURES TESTING CERTIFICATE


WE CONFIRM AND CERTIFY THAT
Tier 1 Participating Member:

Has completed its bilateral testing of contingency exchange arrangement(s) in the clearing system(s) specified below, with at least one Tier 1 Participating Members (test partner) as indicated.

Bulk Electronic Clearing System


Name of test partner 1 Date test conducted

Name of test partner 2 Date test conducted

Our contingency exchange arrangements for the clearing system(s) (indicated above) have been successfully tested and comply with the industry standards outlined (as appropriate) in: BECS Procedures, Part 10, clauses 10.10 to 10.13.

Email File Exchange Contact Details


We also confirm that our details held on APCAs Email File Exchange Contacts Database are correct for: BECS Please tick box to confirm

OR
We advise that our details held on APCAs Email File Exchange Contacts Database are not up-to-date. The correct details are shown below. We also confirm that we have posted the correct details directly to the relevant Email File Exchange Contacts Database on the APCA Extranet.

Australian Payments Clearing Association Limited M3.2

[A.B.N. 12 055 136 519] Amendment No. E042, issued as CS2/r&p/003.09

Bulk Electronic Clearing System (CS2) PROCEDURES Appendix M3 Contingency Procedures Testing Certificate (Clause 10.11)
Last amended effective 23/12/09

Bulk Electronic Clearing System


Name of Contact Position Telephone number Fax number Contingency File email address

( (

) )

AUTHORISED SIGNATORY
Name of person signing Certificate Position Signature Date

- END -

Australian Payments Clearing Association Limited M3.3

[A.B.N. 12 055 136 519] Amendment No. E042, issued as CS2/r&p/003.09

Potrebbero piacerti anche