Australian Competition and Consumer Commission (ACCC) and OAIC
Timing
Set the timetable with the sponsor or assurance provider and the portal team. Allow separate time for evaluation, any follow-up questions, conformance testing and activation where applicable.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Organisations intending to collect, receive or use Australian CDR data, including applicants for unrestricted or sponsored accreditation and businesses considering a representative arrangement.
What you’ll produce
An agreed participation route, a current record of accreditation or arrangement as applicable, approved information security and privacy controls, and a documented start decision.
Sponsored accreditation involves an unrestricted sponsor and limits how the affiliate collects CDR data. A representative works through its principal under a representative arrangement. Verify the route and limits before building the data flow.
Which path and official decision does the business need?
Confirm intended market or customer, covered product or service, and the required approval route. Fund evidence, test or assessment work, and time to respond to reviewers.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor outstanding evidence, external dependencies and authority responses due. Bring changes to the assessed product or service to the decision owner.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Australia Consumer Data Right accreditation kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Choose a participation route and map the data · Product + legal + executive sponsor [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Write down the proposed route, what eligibility depends on and who can verify it. Pull a representative test, evidence record or service use case to check the boundary.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which entity obtains consent and collects the data, and from whom?
Can the team prove that collection stops after withdrawal and the applicable deletion or de-identification workflow runs?
Worked scenario
An Australian budgeting service wants customers to share bank data. It evaluates unrestricted and sponsored accreditation and a representative arrangement, decides where data can enter its service, and exercises withdrawal and data disposal before enabling collection.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Choose a participation route and map the data
Who Product + legal + executive sponsorWhen Before vendor agreements or technical design
Identify the sector, use, organisations and data to be collected. Compare unrestricted and sponsored accreditation and a representative arrangement. Document who can collect from whom, which organisation contracts with the consumer and the proposed sponsor or principal.
What to produce
CDR route and responsibility recordMemo
Gather first
Proposed use and service architecture
Legal entities and consumer flow
ACCC accreditation guidelines
Proposed sponsor or principal agreement
How to prepare it
List each collection, use and disclosure, the legal entity responsible, and where the data comes from. Limit the first release to the data needed for the requested service.
Compare the routes for direct collection, sponsored collection and acting through a representative principal. Record the current registration or accreditation required for each entity.
Confirm who operates the dashboard, handles complaints and issues directions to outsourced providers. Have Legal and the executive sponsor approve the route and outstanding dependencies.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional service
Wattle Budget Pty Ltd wants read access to consumer bank data. It compares a sponsored route through an unrestricted sponsor with a representative arrangement.
Data-flow decision
The planned sponsored route collects through the appointed sponsor. Product documents which service retrieves the data, which information Wattle uses and what each party records.
Check before handing it over
The approved route matches the actual collection and use, agreements and each organisation’s responsibilities.
Give the approved record to Engineering and the provider who will sponsor or act as principal.
Who Compliance + Security + FinanceWhen Before completing the participant portal application
Map the CDR data environment and its suppliers. Collect the required fit and proper information, insurance, dispute resolution and security evidence. Use the current guidance for the applicable independent assurance or sponsored self-assessment and attestation route.
What to produce
CDR accreditation evidence packSpreadsheet
Gather first
Participation route
Current ACCC application and Schedule 2 guidance
Insurance and dispute resolution evidence
Security control and supplier records
How to prepare it
Create a checklist of eligibility, fit and proper, insurance, dispute resolution and applicable information security items. Assign each document an owner, source and review date.
Map the agreed CDR environment and suppliers to Schedule 2. Match control statements to evidence and check whether the current route requires independent assurance or sponsored self-assessment and attestation.
Have an independent reviewer check the evidence and dates and give the primary business contact a signed version and list of gaps before submission.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional security evidence
Wattle supplies an approved data-flow diagram, the inventory of systems holding CDR data and dated evidence of a production access review.
Fictional sponsored application
Compliance records the sponsor and attaches the current sponsored self-assessment and attestation where applicable. Finance supplies the current insurance evidence.
Check before handing it over
The reviewer can locate evidence for each application response and verify the proposed environment and assurance route.
Hand the reviewed application pack to the primary business contact.
Submit, complete onboarding and confirm activation
Who Primary business contact + engineering + onboarding teamWhen Before starting live data collection
Use the Participant Portal and track information requests and the written decision. Reconcile conditions and accreditation level. Complete applicable onboarding and conformance checks, or verify the representative arrangement entry when using that route.
What to produce
CDR application and activation logChecklist
Gather first
Final application
Participant Portal access
Accreditation decision
Onboarding instructions
Conformance and register evidence
How to prepare it
Record the entity and application route, portal reference, submission date and requests for clarification. Archive the exact submitted versions.
Check the written decision and applicable conditions. Complete and document the onboarding and conformance checks for the agreed route.
Verify the required register entry and activation status before permitting live use. Give Product the permitted uses and any hold points.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional release gate
Accreditation decision received. Live data stays disabled while Wattle completes the applicable onboarding and verifies the approved status and sponsor arrangement.
Sign-off
Primary business contact records the decision. Engineering links conformance evidence. Regulatory Compliance checks the register and signs the start decision.
Check before handing it over
The log connects the agreed route, written outcome, onboarding and real start conditions.
Give Operations the approved go-live scope and current register details.
Operate consent, privacy safeguards and change controls
Who Privacy + Operations + RiskWhen During participation
Test consent and dashboard functions, withdrawal, redundant-data handling and complaints. Track privacy obligations, outsourced services, insurance and required reports. Review route and scope changes before changing production collection or use.
What to produce
CDR consent and data lifecycle workbookSpreadsheet
Gather first
Consumer consent and dashboard designs
Data inventory and flow
CDR privacy policy
Relevant retention and disposal rules
Supplier agreements
How to prepare it
Record each consent type, associated purpose, data scope, dates and how the customer can withdraw. Check that the dashboard and evidence reflect what actually happens.
Exercise withdrawal and expiry in a test account. Verify relevant collection or use stops, applicable downstream instructions run and redundant data is handled under the rules and consumer election.
Record the responsible operator, outcome and retained proof. Test how staff handle complaints, backup recovery and changes to suppliers or data use.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional test
A Wattle user withdraws collection consent. Support checks the dashboard, Engineering verifies scheduled collection stops, and Privacy records the applicable disposal actions and evidence.
Change review
Product proposes a new data category for reports. Legal checks consent, necessity and the approved route before Engineering enables it.
Check before handing it over
The organisation can prove what was collected, for which uses, and what happened after expiry or withdrawal.
Give control owners the test evidence, follow-up actions and the review date.