A Mortgage Broker's Guide to Connective Mercury Nexus

If your brokerage aggregates through Connective, Mercury Nexus is where your loans live. It is your system of record for clients, applications, compliance, and commissions, and most brokers spend a good part of every day inside it.

This guide covers what Mercury Nexus does well, the one area brokers most often wish it did more, and how to extend it with a client-facing onboarding experience that feeds straight back in, so you get a better front end without giving up the platform your business runs on.

What is Connective Mercury Nexus?

Connective is one of Australia's largest mortgage aggregators, and Mercury Nexus is its proprietary software platform for members. It brings the core of a broking business into one place: a CRM for managing clients and referrers, application and lodgement tools, compliance and document storage, and commission tracking.

For a broker aggregating under Connective, that makes Mercury Nexus the hub. It is where a deal is recorded, progressed, submitted, and reconciled, and it holds the compliance trail that sits behind every loan you write.

What Mercury Nexus does well

The reason Mercury Nexus is the system of record is that it is built for exactly that job.

• Deal and pipeline management. A structured place to track every loan from enquiry through to settlement.
• Lodgement and application handling. Tools to prepare and submit applications to lenders as part of the broking workflow.
• Compliance and record keeping. Document storage and a compliance trail that supports your obligations, including Best Interests Duty.
• Commissions. Tracking and reconciliation so you can see what you have earned and what is outstanding.

If you aggregate through Connective, none of that should move. Mercury Nexus staying as your system of record is a feature, not a limitation.

Where brokers often want more: the client-facing experience

The gap most Connective brokers describe is not in the back office. It is in the front end, the part your client actually sees and touches.

Collecting a client's information still tends to mean a mix of emails, PDF fact finds, and chasing documents one at a time. For the client it can feel clunky and impersonal, and for you it means manual data entry, missing pages, and follow-up that eats into your week. That first impression matters, because it sets the tone for the whole relationship, and it is the part of the journey that a lodgement-focused platform is not primarily designed to own.

This is the natural place to extend Mercury Nexus rather than replace it: keep it as the engine, and put a better experience in front of it.

How to extend Mercury Nexus without leaving it

The trap to avoid is bolting on a separate tool that creates a second place to enter data. If your onboarding tool and Mercury Nexus do not talk to each other, you have not saved time, you have doubled it.

The test for any tool you add on top of Mercury Nexus is simple:

1. Does it sync? Client details, deal data, and approved documents should flow into Mercury Nexus automatically, so nothing is entered twice.
2. Does it respect Mercury as the system of record? The add-on should handle the client-facing work and hand off cleanly, not try to become a competing source of truth.
3. Does it map to your existing workflow? If its pipeline stages line up with how you already work in Mercury, adoption is easy. If they do not, you will fight it.
4. Does it carry your brand, not the tool's? The client should feel like they are dealing with your brokerage, not a piece of third-party software.

A tool that passes all four extends Mercury Nexus. A tool that fails any of them adds work.

How Lend1 works alongside Mercury Nexus

Lend1 is built to sit in front of Mercury Nexus, not to replace it. It handles the client-facing experience while Mercury remains your system of record.

In practice, that means client details, documents, and deal data collected through your branded Lend1 portal sync across to Mercury Nexus, and Lend1's default pipeline stages map to Mercury out of the box, so your workflow stays familiar from day one. Approved documents sync to your aggregator automatically once they pass your review, which keeps your compliance file complete without a single manual upload.

The division of labour is clean. Lend1 owns onboarding, document collection, and client communication, the parts your client experiences directly. Mercury Nexus stays where it belongs, as the platform for submission, compliance, and commissions. You get a premium front end and keep the back office your business already runs on. You can see the detail on the Connective integration page.

Getting more out of Mercury Nexus

A few practical habits help brokers get more from the platform, whether or not you add anything on top of it.

• Standardise your pipeline stages. Consistent stages across your team make reporting meaningful and handovers painless.
• Keep the compliance trail current as you go. Capturing notes and documents at each step is far easier than reconstructing a file later, and it strengthens your Best Interests Duty position.
• Reduce re-keying wherever you can. Every manual copy-paste between systems is a chance for an error to creep into your compliance file. Favour tools that sync.
• Make the client's first step effortless. The smoother onboarding is, the more complete your data is by the time a deal reaches Mercury Nexus, and the fewer reworks you face at assessment.

Frequently asked questions

Do I have to replace Mercury Nexus to improve my client experience? No. The better approach is to keep Mercury Nexus as your system of record and add a client-facing layer in front of it that syncs back automatically. You improve the front end without disrupting the platform your business runs on.

Will a client onboarding portal create double entry with Mercury Nexus? It will if the two tools do not integrate. The point of a syncing portal like Lend1 is that data captured once in the client-facing flow lands in Mercury Nexus without being re-keyed.

Can my branding be on the client experience instead of the software's? Yes. A white-label portal lets clients complete onboarding under your brokerage's brand, while the resulting data still flows into Mercury Nexus behind the scenes.

Does this change how I lodge or manage compliance? No. Lodgement, compliance, and commissions stay in Mercury Nexus. A front-end tool should hand off cleanly to it, not try to replace those functions.

The takeaway

Mercury Nexus is a strong system of record, and for Connective brokers it should stay exactly that. The opportunity is at the front end: a branded, low-friction onboarding experience that collects clean data once and syncs it straight into Mercury, so you get a better client journey without double entry or a second source of truth.

If you want to see how that works with your own onboarding flow, explore the Connective integration or request a demo.