Adelaide Bank Broker Portal: Legacy Access and Support

For Adelaide Bank broker portal enquiries, use Bendigo Bank Broker for new business and identify the servicing route separately for an existing Adelaide Bank file. Adelaide Bank’s broker brand has retired for new lending. An old loan reference or partner login still needs to be matched to the team responsible for that file.

For another lender’s workspace, use the broker portal directory.

Adelaide Bank Broker Brand Retirement

Bendigo Bank’s 20 August 2024 announcement identifies Bendigo Bank Broker as its flagship mortgage-broker offering following Adelaide Bank’s brand retirement. The bank’s 26 August 2024 results announcement also confirms the retirement of the Adelaide Bank brand for new lending.

Start by separating a new application from work on an existing loan. A fresh purchase or refinance enquiry belongs with the current Bendigo Bank Broker offering. A status request, servicing change or document request for an existing Adelaide Bank loan starts with that file’s reference and current lender correspondence.

The retirement announcement establishes the new-business destination. It doesn’t establish which workspace holds an individual legacy file or make an old login suitable for a new application.

Find Support for an Existing File

Use the file’s current lender instructions to identify its servicing team before attempting legacy access. As at October 2026, Adelaide Bank Connect describes itself as the bank’s mortgage-manager information portal for authorised business partners. Its public page lists secure document upload, loan tracking and reporting.

That description applies to mortgage-manager partners. Use Adelaide Bank Connect when your authorised partner access and the instructions for the file identify it as the right workspace. It isn’t a general instruction for every Adelaide Bank broker to sign in there.

For a broker file whose current workspace is unclear, call Bendigo Bank Broker Partner Assist on 1300 791 679. As at October 2026, the team publishes support for applications through settlement and post-settlement enquiries. Its email is partnerassist@bendigoadelaide.com.au.

Prepare the details before contacting support, then follow this sequence.

1. Find the loan or application reference. Keep the latest lender letter and the brand or mortgage-manager name shown on it available.
2. Confirm borrower authority. Have the authority allowing you to discuss the file ready, along with your broker or partner identifier.
3. Describe the stage and required action. For example, explain whether you’re following up an application or requesting a change to a settled loan.
4. Ask support to identify the responsible team and authorised workspace for that reference. Confirm the document destination before sending client records.
5. Record the answer in your file notes. Keep the support reference, responsible team and agreed next action so follow-up stays with the same file.

If authorised Adelaide Bank Connect access fails, its mortgage-manager help desk lists 1300 733 119, option 3, as at October 2026. Keep the error message and time of the attempt for technical support. Apply this help-desk route to Adelaide Bank Connect, rather than assuming it governs Bendigo’s broker portal.

For customer lending enquiries, Bendigo Bank’s current contact page lists 1300 236 344, option 3, as at October 2026. A borrower can use that route when they need the bank to identify the servicing contact for their existing loan.

Move a New Enquiry to the Current Route

Start a new broker enquiry at the official Bendigo Bank Broker website, which has a Portal Login link as at October 2026. Use the Bendigo Bank broker portal guide for its accreditation, access recovery and new-application steps.

If the client already has a file underway, establish whether the request continues that file before creating another application. Give Partner Assist the existing reference and ask whether the requested action belongs to that application, loan or a separate new submission. This keeps a login problem from becoming a duplicate application.

Proceed when you have a named team, a confirmed file reference and the correct destination for the requested action. Send documents through the channel that team identifies and retain the confirmation with the file.