Read enough broker files cold and you stop being surprised. The same handful of gaps turn up again and again, across brokers and across businesses, and almost none of them are dramatic. They are not fraud and they are not incompetence. They are the ordinary things that do not get written down when a busy broker is already onto the next deal, and they sit in the file unnoticed because the loan settled and everyone moved on.
The reason a principal is usually the last to see them is structural. The broker who wrote the file saw the loan settle, so to them the file is fine. The principal is not reading every file, and often not any of them. The question is not whether your files would pass. It is whether anyone has actually read them.
Why the file looks fine to the people closest to it
A file that produced a clean settlement feels like a finished job. The loan was approved, the client is happy and the commission got paid. Nothing about that outcome tells you whether the file shows the work behind it, and the two are not the same thing.
An independent audit reads the file the way nobody in the transaction did: cold, after settlement, against what should be on it. The audit is not testing whether the loan settled, but whether the file would answer someone who picked it up in two years wanting to know what was done and why. That is the read that surfaces the pattern, and it is one the person who wrote the file cannot easily do on their own work.
What the same files keep showing
A few categories come up so often they are almost predictable.
The reasons for the recommendation are thin. This is the one I see most often. The file shows why the chosen loan suited the client, but not what else was considered and why it was set aside. Under the best interests duty the reasoning is what counts, and it has to be specific to the person in front of you. ASIC has been blunt about this: reasons generic enough to apply to any borrower do not show the recommendation was in that particular client's best interests. Where the recommended product is not the cheapest, the file has to carry the reasoning for that, and often it does not.
Living expenses rest on a benchmark, not the client. The file justifies expenses by reference to a benchmark like the HEM, with nothing showing it was checked against the client's actual figures. The obligation is to assess the real situation, and a benchmark alone has never met it. An audit sees the gap at once, because the verification that would close it is not on the file.
Inconsistencies on the face of the file go unaddressed. The application says one thing; the supporting documents say another; nothing in the file resolves it. Bank statement spending that does not match the declared living expenses is the classic. What an audit flags is not the discrepancy itself, but that nothing in the file shows it was ever questioned.
The file notes are not there. No date-stamped record of the conversations, the inquiries, the client's changing circumstances, the advice given. When a question is asked later, the business is leaning on the broker's memory. The working standard across ASIC and AFCA is plain and unforgiving: if it is not documented, it is treated as not done.
The preliminary assessment is thin or missing. The record of the assessment that the loan was not unsuitable, and the needs analysis behind it, is either absent or does not connect to what was recommended. The requirements and objectives were gathered and then never tied to the recommendation that followed.
The disclosure documents have gaps. The Credit Guide, the Credit Quote and the Statement of Credit Assistance turn up not given, given late or incomplete. Mundane, entirely avoidable and a recurring finding all the same.
None of these are exotic, and that is what makes them easy to miss. They are the quiet, ordinary gaps that a settled loan hides and that only show up when the file is read after the fact.
Why a clean settlement is not the test
The exposure in a file does not sit at settlement; it comes later, when someone else reads it: a client dispute, a complaint at AFCA, a review by the licensee, a question years after the broker who wrote it has moved on. At that point the file is the only witness. If the inquiries, the reasoning and the disclosures are not on it, the business cannot show they happened, whatever the broker remembers.
These files did not cause harm at the time. The point is subtler: the business is carrying a record it has never read, and that record is what will speak for it when it matters. That is also why ASIC has been reading broker files itself, in its own review of how the sector is meeting the best interests duty, and why the weaknesses it has pointed to are the same ones a file audit turns up.
What an independent audit does
An independent hindsight file audit service reads the files, documents what it finds, notifies the broker and keeps the record. It does not fix anything, and it does not certify that a business is compliant. That line matters and we hold it deliberately: we identify issues, you fix them, you verify completion. The value is not a stamp. It is that someone independent has finally read the files, the findings are written down, and the business can see the pattern it could not see from the inside.
I run these audits on real files, as an ACL holder myself. The findings above are what a cold read keeps surfacing, not what I imagine might be there. There is nothing glamorous about it. The work is reading files properly, which is the one thing a busy business never gets to.
Better you read it first
You cannot fix what you cannot see, and you cannot see it by asking the people who wrote the files, because to them the files look fine. The gaps are consistent enough to be worth looking for, and the file is the record that stands for the business long after the loan has settled. Better you have read it first.