Mortgage Broker Loan Origination Software 2026

Mortgage broker loan origination software turns your client’s fact find into a lender-ready application, checks it against each lender’s field rules and sends it, usually through ApplyOnline. Choose the platform that reaches your main lenders by a documented route and stops missing or invalid data before it leaves your office.

Rekeying happens wherever data leaves your customer relationship management (CRM) system and has to be typed again. Preventable rejections happen where a lender’s own field rules meet that data. Test those two points before you compare screens or feature lists.

Your aggregator shapes the shortlist, because NextGen connects third-party platforms to ApplyOnline only where they’re contracted to a broker group or aggregator. AFG brokers can lodge from BrokerEngine Plus, Connective members get Mercury Nexus at no extra cost, and Salestrekker lists gateways and direct lodgement for 50+ lenders. Simpology’s Loanapp is mortgage loan origination software for lenders and brokers, built on a data model that follows LIXI standards.

Trace a Submission

Trace one application from the first entry to the lender gateway and mark every point where someone types or picks a value. Each of those points is where rekeying and submission errors start.

Where Borrower Data Enters

A typical file picks up data in several places before it reaches a lender:

1. The CRM client record that feeds each application, with contact details, household and employment history. Removing duplicate entry starts here.
2. A client portal or fact find, such as BrokerEngine’s FinanceVault, which collects fact finds, documents and bank statements through one link.
3. Open banking and verification services, such as Simpology’s Connect gateway, which auto-populates fields from services like identity checks and automated valuations.
4. The lodgement gateway itself, where you select the product, loan purpose and lender-specific codes.

Fields completed in the gateway are typed by hand unless the platform fills them. Ask each vendor which fields reach the gateway already filled and which ones your staff complete there.

Lender-Specific Field Mappings

Loan origination software maps its own fields to a shared format before the lender sees them. In Australia, electronic lodgement is frequently built on LIXI’s Credit Applications for Australia (CAL) standard. It carries applicant details, assets, liabilities, employment and needs analysis data from CRM systems through aggregator systems to lender gateways (LIXI’s CAL page, last updated 7 September 2026).

The shared format doesn’t remove lender rules. Macquarie’s broker help centre, as at October 2026, asks for a primary purpose in ApplyOnline: Owner Occupied, Residential Investment or Non-Residential Investment. You then add an Australian Bureau of Statistics (ABS) loan purpose code that must suit that purpose.

When the platform maps a CRM loan purpose to these two fields, check the mapping for every purpose you write. A wrong mapping repeats on every file until someone fixes it.

What Pre-Submission Validation Catches

Pre-submission validation compares the application with the receiving system’s rules before delivery. Macquarie’s ApplyOnline checks show two levels.

A red validation message blocks an invalid combination, such as Owner Occupied with ABS code 237 for household and personal goods. A yellow message suggests other codes, and you can dismiss it.

Macquarie also marks mandatory documents with a red dot and keeps a submission checklist that updates as you complete the application. Validation in the gateway is useful, but it catches errors late, after your team has entered the data.

Check whether the platform validates before the gateway. LIXI publishes a library of over 1,600 business rules written in Schematron, a format software can run as automated tests (last updated 7 October 2025). Ask whether the platform runs these rules, or its own lender rules, before it hands the file over.

Validation checks whether the data is complete and compatible. It doesn’t check whether the lender accepts the client’s circumstances.

• Wrong reading: the file passed validation, so the lender will accept a client with 14 months of self-employed income.
• Right reading: the fields are complete and valid. Whether the lender accepts 14 months of self-employed income is a policy question.

Pick a lender whose policy fits before anyone builds the application. Bulma’s Scenario Planner checks the client’s scenario against 52+ lenders’ policies and quotes the policy wording behind each result. Bulma loads the scenario from your CRM, and it doesn’t lodge applications or connect to lodgement platforms.

Confirm Lender Connectivity

Confirm that each lender you use receives applications by a documented route that your brokerage can reach under its current access arrangements. A vendor’s lender count doesn’t tell you how each lender is reached.

Four Delivery Routes

Each lender receives applications by one or more of these routes:

1. Native delivery: the application goes straight into the lender’s own channel, such as a lender portal or a lender-hosted application site.
2. Aggregator route: your aggregator’s platform sends the application through a contracted gateway, usually ApplyOnline.
3. Connector: a third-party CRM pushes the deal into the gateway, where your team completes and submits it. BrokerEngine Plus’s direct lodgement to ApplyOnline for AFG brokers is an example, documented by both BrokerEngine and AFG.
4. Manual export: you produce the application or documents from your CRM and upload them in the lender’s portal. Salestrekker creates Word and PDF documents from CRM data, which suits this route.

ApplyOnline’s own page lists 60+ lenders, as at October 2026. NextGen supports a third-party platform’s integration only where that platform is contracted to a specific broker group or aggregator. A CRM’s connector therefore depends on your aggregator’s contract as well as the vendor’s software.

Routes for Named Lenders

The table ties each lender to its documented route and the access it needs. Lender details are as at October 2026, from each lender’s broker pages.

Lender	Documented route	Route type	Access needed	Step that stays manual
Macquarie	Applications submitted in ApplyOnline; later documents and status in Macquarie’s Broker Portal	Aggregator route for lodgement; native channel after submission	Accreditation form from your aggregator; support staff registered in Broker Portal	Documents needed after submission are uploaded in Broker Portal
Pepper Money	Pepper’s broker site links to its own ApplyOnline site and to App Tracker	Native delivery through a lender-hosted ApplyOnline site	Accreditation with Pepper Money	Progress is read in App Tracker, outside your CRM, unless your platform imports it
St.George	BrokerHub, to lodge deals, track applications and request pricing. NextGen also names St.George among ApplyOnline lenders	Native delivery through BrokerHub; aggregator route through ApplyOnline	St.George accreditation at Accredited, Gold or Flame level	Pricing requests sit in BrokerHub
ANZ, CBA, NAB and Westpac	Named by NextGen among ApplyOnline’s lenders	Aggregator route	Accreditation with each lender and a platform contracted to your aggregator	Any post-submission step the lender runs in its own portal

Use the lender pages for your own panel, such as Macquarie’s broker portal or Pepper Money’s broker portal. A platform that lists a lender but sends it through a different route from the one your team uses still leaves rekeying.

Platform Connections

For the platforms on the shortlist, the documented connections are these, as at October 2026:

• BrokerEngine Plus is the AFG version of BrokerEngine and lodges directly to ApplyOnline. BrokerEngine’s pricing page lists that lodgement for AFG brokers only, and AFG’s page lists over 80 lenders on its panel.
• Mercury Nexus lists application lodgement for Connective members. Connective’s page doesn’t publish a lender-by-lender route list.
• Salestrekker says it has multiple lender gateways and direct lodgement options covering 50+ lenders, and lists ApplyOnline among its integration partners.
• Simpology runs Loanapp, an e-lodgement platform for lenders and brokers. Its homepage says 70+ companies use Simpology but doesn’t list which lenders receive Loanapp applications.

Match each platform’s routes against your top lenders by volume. A missing route for a lender you use every week costs more than a missing route for one you use twice a year.

Observe Status and Documents

After lodgement, the platform must return each lender message to the broker who owns the file, with a status your team can act on. If messages land in a shared inbox or a lender portal only, requests for information wait until someone looks.

Requests for Information

Macquarie’s broker help centre, as at October 2026, describes the messages a platform has to handle. Macquarie sends back channel messages (BCMs) with status, outstanding items and queries until settlement. Brokers and their registered support staff receive them.

When documents are missing, Macquarie sends a BCM that itemises them. Its Broker Portal also shows each application’s status, outstanding documents and queries. Pepper Money, as at October 2026, offers App Tracker for application progress.

Check three things in the platform:

1. Each lender message attaches to the right deal, not just to the brokerage.
2. The message goes to the responsible broker and their assistant, with a status such as outstanding documents or query.
3. Your team can answer from the deal, or the platform shows which lender portal holds the reply.

Attachments and Application Versions

Attachments and versions drift apart when an application is changed after submission. Macquarie lets you edit and resubmit before formal approval, but editing doesn’t extend the expiry date. After formal approval, you can’t edit the application in ApplyOnline.

Cloning restarts Macquarie’s expiry periods. A cloned application doesn’t include supporting documents from the earlier one, including identity documents. Your platform’s history must show which version went to the lender with which attachments, so nothing is lost when you clone.

Macquarie asks for documents needed after submission through its Broker Portal, where you or your registered support staff upload them and select Send for assessment. For documents lodged with the application, it says to allow up to 2 hours for them to attach. Record the Broker Portal uploads in the deal’s history, even when they happen outside the platform.

For the earlier step, see collecting the documents needed at lodgement.

These records support your compliance file too. ASIC’s Regulatory Guide 273 on the best interests duty expects records of information given to the lender and the outcomes of applications. It says the retention period depends on factors such as the loan term, any interest-only period and refinancing.

Compare Workflow Fit and Cost

Compare mortgage broker origination software on the same criteria for every platform: lender reach, validation, permissions, support, implementation, annual cost and the handoffs each leaves manual. The table uses each vendor’s public pages as at October 2026, and it states price structure only, because prices change often.

Criterion	BrokerEngine	Mercury Nexus	Salestrekker	Simpology
Who can use it	BrokerEngine: brokers from any aggregator. BrokerEngine Plus: AFG brokers only	Connective members	Brokerages, including members of listed partner groups such as Astute, Compass and Specialist Finance Group	Brokers, aggregators and lenders
Lender reach	Direct lodgement to ApplyOnline in BrokerEngine Plus (AFG brokers only)	Application lodgement; no route list on Connective’s Mercury Nexus page	Multiple gateways and direct lodgement covering 50+ lenders	Loanapp e-lodgement and 100+ integrations through its SSI gateway; 70+ companies use Simpology
Validation before lodgement	Deal-specific checklists matched to each deal	Compliance checks and credit checks inside the workflow	Compliance documents are prepared before lodgement; field validation not described on its features page	Connect gateway auto-populates and validates data on a LIXI-based data model
User permissions	Staff permissions management, with broker and support user types	Not described on Connective’s Mercury Nexus page	Role settings for what each user can see, plus multi-factor authentication	Not described on Simpology’s homepage
Implementation and support	Optional one-time Kickstart program per broker group for workflow setup, data migration and training	Onboarding and support for brokers moving from other aggregators and CRMs	Live chat support six days a week and a knowledge base; no onboarding program listed on its features page	Lenders configure their own data schema, policy rules and document checklists without a code release; no broker onboarding program listed on its homepage
Annual cost structure	Per user, monthly or annual, with a discount for annual billing and volume discounts from 10 users; no lock-in contract; free demo instead of a trial	Included at no extra cost for Connective members	Set out on Salestrekker’s separate pricing page	No prices on Simpology’s homepage
Handoffs left manual	All lodgement for non-AFG brokers; lenders outside ApplyOnline; post-submission uploads a lender takes in its own portal	Lenders without a published route	Lenders outside its gateways	Depends on the lenders and aggregator connected

Work out annual cost from the billing unit. For per-user software, count broker users and support users separately, then add any one-time onboarding. For bundled aggregator software, the cost sits inside your aggregator arrangement, so compare it with the full research, CRM and lodgement stack you already pay for.

Choose on the handoffs that hit your volume. A brokerage with AFG and a high share of ApplyOnline lenders gets the most from BrokerEngine Plus.

A Connective brokerage starts with Mercury Nexus because it’s already included. A brokerage that also writes asset finance or commercial deals can weigh Salestrekker, which includes asset finance and commercial lending tools alongside home loans.

Run a Lodgement Trial

Before you sign, test each platform with a synthetic application and record what it accepts, rejects and keeps. A synthetic application is a fictional file built for testing, so no real client’s data leaves your office.

Build the Synthetic File

Use a fictional applicant with clearly fake details. For example, “Test Applicant” buys a $650,000 owner-occupied home with a $520,000 loan, a loan-to-value ratio (LVR) of 80%. The applicant earns a pay as you go (PAYG) salary and has one credit card.

Then seed known errors so the trial has something to catch:

1. Map the loan purpose to Owner Occupied with ABS code 237, the combination Macquarie’s ApplyOnline blocks, as at October 2026.
2. Leave out a mandatory document, such as a payslip.
3. Attach an Excel file and a password-protected PDF, which Macquarie’s document guidance says it doesn’t accept.
4. Leave the employment start date blank.

Test Validation, Delivery, Permissions and the Audit Trail

1. Run the platform’s validation and note whether each seeded error is caught in the CRM, caught at the gateway or missed.
2. Ask the vendor to send the file to a test endpoint in its demonstration environment and show the delivery receipt. If it can’t, stop at the final submit screen and treat delivery as unproven. Never send the synthetic file to a live lender.
3. Log in as a support user. Confirm what that user can see, edit and submit, then remove the user and confirm the access ends.
4. Export the file history. Check that it shows who changed each field, which version reached the submit step and which attachments went with it.

Record the Results

Record each test in the same table for every platform so the results compare directly.

Test	Result to record	Accepted, rejected or retained
Owner Occupied with ABS code 237	Where the error appeared and the exact message	Rejected before submission, or missed
Missing payslip	Whether the checklist flagged it before the gateway	Rejected before submission, or missed
Excel file and password-protected PDF	Whether the platform warned before upload or only the gateway rejected them	Rejected, or retained in error
Blank employment start date	Whether validation named the field	Rejected before submission, or missed
Delivery to a test endpoint	Receipt message and time, or “unproven”	Accepted by the test endpoint, or not tested
Support user removed	Whether access ended at once	Retained access or removed
File history export	Fields, versions and attachments the export shows	Retained in the export, or missing

Choose the platform that caught the seeded errors before the gateway, reached your top lenders by a documented route and kept a history you could hand to your licensee. If two platforms tie, choose the one your aggregator already supports, so its gateway connection doesn’t depend on a new contract.