Automating client document collection cut one Sydney mortgage brokerage's average loan cycle by nearly two weeks — not because the clients suddenly became more organised, but because the chase stopped being a manual job.
The problem: why document gaps stall every loan application
Most mortgage brokers do not lose deals because of bad credit assessments or poor lender relationships. They lose momentum — and sometimes deals — because the gap between "documents requested" and "documents received" is wide and unpredictable.
A typical loan application needs ten to twenty supporting documents: bank statements, payslips, tax returns, a letter of employment, rates notices, rental ledgers. Each lender has its own freshness rules. Many require payslips no older than 30 days at the time of assessment — not at the time they were requested. A payslip collected in week one might be stale by the time the application reaches credit in week four.
That creates a second round of chasing that most brokers absorb quietly. The client receives a request for a fresh payslip. They do not respond immediately. The broker sends a follow-up. The loan processor follows up again. Meanwhile the application sits in a queue it cannot leave until the document arrives.
For small broking practices running on Mercury Nexus, BrokerEngine or FinanceVault, the document chase is often owned by one person — the broker or a part-time loan processor. When that person is the bottleneck, every loan in the pipeline moves at the speed of the slowest client. The document automation and workflow services FluxWork builds for mortgage brokers are designed to remove exactly this layer.
What a document collection gap actually costs a broker
An unconditional approval typically takes 20–35 business days for an owner-occupier refinance and longer for investment purchases. A significant share of that elapsed time is waiting for documents — or waiting for expired ones to be replaced.
Every week a loan sits incomplete is a week of pipeline uncertainty. In a market where clients compare broker speed, a practice that moves faster through the document stage creates a real competitive advantage. Because the chase is repetitive — the same SMS, the same email, the same "just checking in" — it is exactly the kind of work that automation handles without degrading the client relationship.
What FluxWork built for a Sydney brokerage
A small owner-operated brokerage in Sydney was processing eight to twelve loans per month with one loan processor. Document collection was managed through a combination of email threads and BrokerEngine notes, with the processor manually following up every few days.
FluxWork mapped the document intake process and built an automated collection workflow around the brokerage's existing stack.
Single intake link. When the broker opens a new loan file, the workflow generates a client-specific intake link. The client sees a checklist of exactly what is needed — payslips, bank statements, tax returns — with upload instructions matched to their application type (owner-occupier, investor, SMSF).
Staged automated reminders. If a document is not uploaded within 24 hours, the workflow sends an SMS reminder. A second reminder goes at 48 hours and a third at 72 hours for any outstanding items. The tone is friendly and clear: "We still need your most recent payslip to keep your application moving." No more manual follow-up emails from the processor.
AI document classification and freshness check. Each uploaded file is classified by type and checked against the issue date. Payslips more than 28 days old, bank statements older than 60 days, or tax returns from the wrong financial year are flagged automatically. The workflow alerts the broker before the application goes to lender — not after credit assessment returns a gap.
Structured CRM update. Once all required documents are uploaded and pass the freshness check, the workflow updates BrokerEngine with a status flag and notes the completion date. The broker opens a ready-to-submit file instead of an inbox thread.
For a broader view of how document automation fits into the mortgage onboarding process, see document automation for mortgage brokers.
How does automated document expiry checking work?
Document expiry in mortgage applications is distinct from the initial collection problem. A broker might collect a payslip successfully in week one, only to find it rejected at lender credit because it is now 35 days old and the lender requires documents dated within 30 days of submission.
The automated freshness check reads the issue date from each uploaded document — payslip date, statement end date, valuation date — and compares it against the expected submission date for the application. If a document is likely to be stale by the time the lender sees it, the workflow flags it in the queue and prompts the client to upload a fresh copy before the application progresses.
ASIC's responsible lending obligations require brokers to verify the accuracy of the financial information they rely on. An automated freshness check is not a compliance shortcut — the broker still reviews every file — but it removes the risk of a stale document slipping through because the issue date was not checked during a busy week.
The results
For the Sydney brokerage, the outcomes were measurable within the first month of the workflow going live.
The average time between a new loan opening and a complete document set dropped from around fourteen days to five. Most of that reduction came from the first stage: clients who received the intake link and automated reminder sequence uploaded their documents faster than they responded to ad hoc email requests.
The loan processor's time on document follow-up dropped from roughly three hours per loan file to under thirty minutes — mostly reviewing the completed checklist rather than chasing it. Document rejections at lender due to stale files dropped to near zero in the first quarter, because expired documents were flagged and replaced before the application left the brokerage.
These are scenario-based figures, not a guaranteed result. But the pattern is consistent: structured intake plus expiry checking together remove the two biggest sources of delay in the pre-submission stage.
Why document collection is the first workflow worth automating
Most mortgage brokers who explore automation look at back-of-house tasks first — compliance note generation, client update emails, invoicing. Document collection is often underestimated because it looks like a communication problem rather than a workflow problem. But the document chase has all the characteristics of a workflow problem: it is triggered by a predictable event, it follows a fixed sequence, it involves retrievable data, and it repeats at the same frequency for every loan.
Fixing the document stage first has a compounding effect. When applications move through pre-submission faster, credit queue time becomes visible rather than hidden behind incomplete files. Broker capacity increases because the time recovered from chasing is time that can go into new loan assessment or client relationships.
If document collection is your slowest stage, book a free workflow review and we will map where the hours are going and what an automated intake sequence would look like for your practice.
Frequently asked questions
How can a mortgage broker automate collecting client documents?
The most effective approach is a client-facing intake link that lists exactly what is needed, followed by automated SMS and email reminders at set intervals until all documents are uploaded. FluxWork builds this around the tools your practice already uses — BrokerEngine, Mercury Nexus, or a simple intake form — so there is no new portal for clients to navigate.
What is the 30-day document freshness rule for mortgage brokers?
Most Australian lenders require payslips to be dated within 30 days of the loan submission date, not the application open date. Bank statements are typically required within 60–90 days. The gap between when documents are collected and when they are submitted creates a window in which documents can expire, requiring a second round of client requests. Automated expiry checking flags these before the application leaves the brokerage.
Does automating document collection create compliance risks?
No — it reduces them. Automated intake creates a timestamped record of when each document was received and whether it passed the freshness check. The broker still reviews every file before submission. Automation removes the chance that a stale document slips through because the processor did not notice the issue date during a heavy week.
Can this automation work with BrokerEngine or Mercury Nexus?
Yes. FluxWork builds workflows that connect to the aggregator CRMs brokers already use. The automation sits above your existing stack — it does not replace BrokerEngine or Mercury Nexus, it feeds them clean, classified, dated document records so the broker's file is ready to submit rather than ready to chase.
How long does it take to build a document collection workflow?
For a mortgage broking practice, a focused document collection and freshness-check workflow is typically live within two to three weeks from the scoping call. The fastest part is the intake link and reminder sequence. The longest part is agreeing exactly which document types, freshness windows, and CRM status updates apply to your lender mix.