EvidenceSheet

CPS 230 para 53 Formal legally binding agreement for each material arrangement and its minimum terms

For every material arrangement the entity must hold a formal, legally binding agreement that at least: (a) defines the services and their service levels; (b) sets each party's rights, duties and expectations, including asset ownership, data ownership and control, dispute resolution, audit access, indemnity and liability; (c) lets the entity satisfy its legal and compliance obligations; (d) obliges the provider to notify the entity when it materially relies on other material service providers through subcontracting or similar to deliver the service; (e) makes the provider responsible for any subcontractor's failure; (f) contains a force majeure clause stating which parts survive a force majeure event; and (g) gives termination rights over the whole arrangement or parts of it, and for an RSE licensee a right to terminate where continuing would breach the best financial interests duty (SIS Act s 52(2)(c)). Para 57 can exempt the arrangement (Attachment category provider on standardised terms or no formal agreement), and APRA can exempt it in writing under para 58.

Source: APRA CPS 230, CPS 230 para 53. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open APRA CPS 230 in the compliance library.

Applies to APRA-regulated entities.

3
artefacts
0
held by a system
0
at each review
hard
to go live
Vendor register / contract repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Executed agreement for each material arrangement · Vendor register / contract repository
  • Contract clause checklist mapping each agreement to items (a) to (g) · Vendor register / contract repository
  • Exemption record under para 57 or APRA notice under para 58 for any material arrangement without a compliant formal agreement · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CPS 230 para 52 Due diligence and risk assessment before entering or materially modifying a material arrangement · CPS 230 para 54 APRA access, on-site visit and non-impediment clauses