Kuala Lumpur · application file audit
QueryEngine Hub Advisory sits with the credit application — income exhibits, commitments, related-party notes, override memos — and tests whether those papers can support the score, the exception, or the limit that was placed on them.
Work is scoped from our rooms on Jalan Tun H. S. Lee. We do not approve applicants, call scorecards, or sell software.
Primary engagement
Lenders in Malaysia put enormous weight on a small set of fields that feed a credit scoring engine. Those fields are extracted from a thicker object: the application file. When income cannot be rebuilt from payslips, when a purpose code does not match the story in the statements, or when an override memo never returns to capacity, the problem is already in the pack.
Our primary service is a pre-score file audit — a sample of packs read line by line against your product programme and against ordinary financial arithmetic. You receive an exception log, a written report, and a discussion with the named lead. You do not receive a dashboard, a model opinion, or a recommend-to-approve.
We work from copies you transfer under an engagement letter. We do not collect papers from applicants.
Related readings
Pre-score work is the usual starting point. These engagements use the same method on a different cut of the book.
A line-by-line reading of the credit application pack before it is submitted to the scoring engine, focused on financial evidence, completeness, and internal consistency.
An audit of files that left the engine path — manual overrides, policy exceptions, and committee referrals — to test whether the written reason matches the financial evidence.
A retrospective reading of applications that already received a score, to see whether the inputs the engine used were faithful to the underlying financial file.
A concentrated audit of how income, existing commitments, and repayment capacity are evidenced in the application, including variable pay, self-employed accounts, and household support claims.
A reading of SME and commercial application files for related parties, common directors, and group commitments that should have been visible before a score or a limit was assigned.
A structured comparison of application files against the written product programme — eligibility, documentation, tenor, purpose, and stated exceptions — before or after scoring.
How an engagement starts
Write to us with the product, the question you actually have (income construction, overrides, group disclosure, policy drift), and a sense of file volume. We reply with a scope note: sample size, documents we need, timeline, and a fee. Work begins when the letter is signed and the first batch of files is received.
Fees are quoted per engagement. There is no online checkout and no subscription. Indicative bands sit on each service page.
From credit rooms we have sat in
“They did not bring us a dashboard. They brought us twelve files where the income on the form could not be rebuilt from the payslips we already had. That is what we took to operations.”Head of credit operations · Consumer lender, Kuala Lumpur
“The override sample was uncomfortable reading. Most of our memos restated the score. After the report we shortened the template and required a financial sentence that points at an exhibit.”Credit committee secretary · Regional banking group
“We asked for a policy-alignment reading before a product refresh. The useful part was not the drift count. It was the places where the programme and the originator checklist already disagreed.”Product owner, personal financing · Klang Valley credit provider
Notes from the reading table
13 May 2026 · Income evidence
A scored file can look complete while the income figure on the form cannot be reproduced from the payslips, statements, or accounts attached to it.
1 April 2026 · Exceptions
An override paper that mainly restates the engine outcome has not yet explained the exception. The financial reason still has to be written.
17 February 2026 · Group exposure
SME application files often attach company documents that name common directors, while the application itself still presents a standalone borrower.