Aggregator consent should be treated as a documented condition to a trail-book purchase, not as an administrative task left until settlement. The buyer needs to know which entity must approve the transfer, what it is approving, which conditions remain outstanding and when commission payments and servicing access will move.

There is no universal Australian transfer process that makes every aggregator accept every buyer. Examine the governing aggregator agreement, commission arrangements, lender requirements and licensing structure together. A sale agreement alone does not prove the aggregator will recognise the buyer, redirect trail or provide system access.

Separate the approvals that are often bundled together

Ask the aggregator to describe the proposed pathway in writing. “Consent” can conceal several different decisions:

  • acceptance of the buyer as a member, licensee or credit representative within the aggregator’s structure;
  • approval to assign, novate or otherwise redirect contractual commission rights;
  • migration of loan records to a new broker or account code;
  • access to the aggregator’s customer relationship management, commission and compliance systems;
  • confirmation of any lender-level accreditation, panel or operational requirements; and
  • agreement about responsibility for existing complaints, clawbacks, adjustments and client servicing.

These steps may be linked, but are not interchangeable. A buyer may be acceptable as a broker yet still lack approval for a particular transfer. An economic entitlement in the sale agreement does not necessarily establish authority to provide credit assistance or contact clients. Record each approval, issuing entity and effective date separately.

Establish the buyer’s regulatory pathway early

The National Consumer Credit Protection Act 2009 generally prohibits a person from engaging in a credit activity without an Australian credit licence authorising that activity, subject to applicable exceptions such as acting within a licensed principal’s authority as a credit representative (Federal Register of Legislation). Section 64 provides for a licensee to authorise a person by written notice to engage in specified credit activities on its behalf.

ASIC explains that a credit representative’s authority covers only specified activities and may be ineffective in circumstances identified by the Act. Its guidance also addresses written authorisation, AFCA membership, training and the consent needed where a person represents multiple unrelated licensees (ASIC). AFCA separately identifies membership arrangements for authorised credit representatives appointed by a licensee or aggregator (AFCA).

Do not ask only whether the buyer has a credit representative number. Confirm the acquiring entity, its ACL or representative structure, authorised activities, responsible individuals, AFCA position and intended aggregator. Check relevant parties on ASIC’s Professional Registers Search, while recognising that a public register result does not replace contractual approval (ASIC).

Request the transfer pack, not an informal assurance

Before signing an unconditional agreement, request:

  • the seller’s current aggregator agreement and all amendments relevant to assignment, termination, trail, records and post-termination payments;
  • the aggregator’s current transfer or sale policy, application form and buyer onboarding criteria;
  • written identification of required seller, buyer, lender or licensee consents;
  • application fees, transfer charges, ongoing fees, minimum volumes or other commercial conditions;
  • the proposed treatment of commission splits, aggregator deductions, reserves, clawbacks and disputed amounts;
  • the cut-off date, first expected payment date and reconciliation method;
  • the data-migration specification, system-access date and responsibility for rejected or unmatched records;
  • required client communications and evidence that their timing and content have been approved; and
  • a named decision-maker, target timetable and list of documents still outstanding.

Check each document’s source and date. If the aggregator will not provide documents directly, ask the seller to authorise confirmation or arrange a three-party discussion.

Protect privacy while seeking approval

Aggregator review does not justify unrestricted disclosure of borrower files. The OAIC says that Privacy Act obligations can apply to personal information used or disclosed during a business sale and recommends de-identified or aggregated customer information where possible, controlled access and privacy terms in confidentiality arrangements (OAIC).

Use staged disclosure: aggregated book data first, de-identified loan-level information for assessment, and identifiable records only when there is a lawful basis, genuine need and appropriate controls. Record who can access a data room, prevent unnecessary downloads, and specify return or destruction if the transaction does not proceed. Obtain privacy advice for the actual structure rather than assuming aggregator participation resolves the buyer’s and seller’s obligations.

The sale agreement should define the required approval objectively. With legal advice, consider stating:

  1. the exact aggregator entity and approval required;
  2. whether approval must be unconditional or may contain agreed acceptable conditions;
  3. which party must submit documents, pay fees and answer follow-up requests;
  4. a deadline, extension mechanism and evidence of satisfaction;
  5. what happens if only part of the book is accepted;
  6. whether lender exclusions or delayed records change the price or settlement population;
  7. who bears income, deductions and servicing responsibility between cut-off and migration; and
  8. termination, refund or alternative-transfer consequences if approval fails.

Avoid treating consent as satisfied because it is “expected”. Seek written approval naming the parties, book or account codes, effective date and outstanding conditions. Your lawyer should align that evidence with payment and any holdback.

Hypothetical example: an aggregator approves a buyer subject to completed onboarding, AFCA confirmation and migration testing by a specified date. The sale agreement settles as soon as “consent” is issued. If testing fails after settlement, the buyer may own contractual rights against the seller while trail continues to be reported under the old account. This example does not describe a standard aggregator process; it shows why approval, operational readiness and payment redirection should have separate completion tests.

Test operational readiness before funds move

Run a pre-settlement rehearsal using a small de-identified sample. Confirm identifiers map correctly, commission rates and splits are represented, historical statements remain accessible, and the buyer can reconcile the first payment. Nominate contacts for rejected loans, missing records and post-cut-off adjustments.

Also confirm who will respond to existing clients and complaints from the effective date. ASIC’s mortgage-broker guidance explains that brokers must act in consumers’ best interests when providing credit assistance and prioritise consumers where conflicts arise (ASIC). Buying the book does not turn future refinancing into automatic revenue or remove those obligations.

Warning signs that justify a pause

  • The seller will not allow direct confirmation with the aggregator.
  • “Approval” names a different entity from the proposed buyer.
  • Material conditions are described verbally but not in the approval letter.
  • The aggregator can reject loans, yet the contract assumes the whole book transfers at one price.
  • No party owns migration errors or the first-payment reconciliation.
  • The buyer’s authorisation, AFCA or onboarding status will not be effective by the transfer date.
  • Identifiable borrower data is being circulated before the privacy basis and controls are settled.
  • The timetable depends on lender or platform actions that nobody has confirmed.

Frequently asked questions

Can the sale agreement be signed before aggregator approval?

It can be made conditional, but the drafting should be transaction-specific. Buyers should not assume a general “consent” condition deals with partial approval, adverse conditions, delays, data migration or payment redirection.

Does ASIC registration mean the aggregator must accept the buyer?

No. Registration or licensing evidence helps test regulatory status. It does not compel an aggregator to admit a buyer or approve a transfer under its commercial arrangements.

Should settlement wait until the first trail payment reaches the buyer?

That is a commercial and legal structuring question. Alternatives may include evidence-based completion tests, deferred consideration or a holdback, but advisers should match the mechanism to the actual aggregator timetable and risks.

Sources

Disclaimer

This article provides general information only. It does not constitute legal, tax, accounting, financial, credit, valuation or other professional advice. Circumstances differ. Obtain advice from appropriately qualified advisers before acting or entering a transaction.