Cross-Document Verification: Checks That Catch Bad Files

Cross-document verification means taking one fact (a name, an address, an income figure, a BSB and account number, an ABN, a date) and checking that every document in the file, and every public record you can reach, says the same thing about it. Most incomplete or inconsistent files are not forged. They hold a payslip from one employer, a bank statement under a slightly different name and a utility bill that is five months old. Each document looks fine alone. The file does not.

This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of October 2026 and cover Australia at the Commonwealth level unless stated otherwise; state and territory rules vary. Consult a qualified professional for your situation.

What does cross-document verification compare?

It compares a field on one document with the same field on another document or a public record, then routes any difference to a person with a defined next step. It is a consistency control, not an authenticity test: two documents can agree with each other and both be wrong.

The Anti-Money Laundering and Counter-Terrorism Financing Act 2006 requires reporting entities to carry out customer identification procedures, and AUSTRAC's guidance describes verifying identity from reliable and independent documents or electronic data, so a second independent source is part of the framework (AUSTRAC). The regime is being reformed in phases; check AUSTRAC for the dates that apply to your sector. Landlords, recruiters and lenders that are not reporting entities sit outside the Act, but the logic carries over: an error or a lie has to survive two documents from independent issuers.

For the wider method, see our document verification guide. For why extracting text is not enough, read cross-document validation beyond OCR.

The seven cross-checks, field by field

Seven comparisons cover most of what goes wrong in an applicant file. Each has a source field, a comparison field, a typical mismatch and a reviewer action.

Dates run through all seven. A document issued after the application date, a payslip from before the employment contract, or an ID that expires before the decision date are cross-checks in their own right.

How does the income triangle work in practice?

The income triangle compares a payslip, a bank statement and a tax document, because each comes from a different party: the employer, the bank and the Australian Taxation Office (ATO).

Take an illustrative case. A payslip shows net pay of $2,314.60 for the fortnight ending 26 September, paid on 30 September. The bank statement shows a credit of $2,314.60 on 30 September from "NORTHWAY LOGISTICS PTY LTD". The payslip reads "Northway Logistics Pty Ltd". Amount, date and payer line up, and the capitalisation is harmless. Now change one thing: the statement shows $2,980.00 from the same payer. That gap is a bonus the payslip does not show, a second job, or an edited document. The reviewer does not decide which. The reviewer asks for the next pay cycle and an employment contract, and records the reason.

Three rules keep this check useful:

• Compare net pay to the credit, not gross pay.
• Match amount first, then date (allow a few days either side), then payer name.
• Compare at least two pay cycles. One match proves little; a pattern proves a lot.

The third corner is a tax document the applicant did not prepare. Employers report income to the ATO, and the applicant can retrieve an income statement and a notice of assessment through their ATO online services (ATO). A figure that conflicts with year-to-date pay is a reason to ask a question, not to reject. For rental files, our guide to income verification on rental applications applies the same logic.

Where do name, address and bank-detail mismatches hide?

They hide in formatting differences that look like fraud but usually are not, and in real differences that look like formatting.

Names: variants versus different people

A name mismatch is benign when surname and date of birth agree and the difference is a preferred name, a dropped middle name or a hyphen. It needs a question when the surname differs, which happens after marriage, divorce or a registered name change. It needs escalation when first name and surname both differ and no change document exists. Write these three tiers down so every reviewer applies them the same way.

Addresses: one-line differences

Addresses fail more often on form than substance: "Unit 3/14 Smith St" against "3/14 Smith Street" or "14 Smith Street, Unit 3". Normalise abbreviations and the unit-slash convention, then compare postcode and street number. A different postcode on a document dated after a move is expected; the same postcode with a different street number is not.

Bank details: the account holder is the real field

Australian accounts are identified by a six-digit BSB and an account number rather than an IBAN, so there is no standard international checksum to lean on. The field that matters is the account holder name. A valid BSB and account in a third party's name is a valid number and a failed check.

Can an identity document be checked against the issuer?

Yes, for some documents. The Document Verification Service (DVS), run by the Attorney-General's Department, compares biographic details on an identity document with the issuing agency's record and returns a match result to the requesting organisation (Identity Matching Services, DVS). Access is granted to approved organisations under agreements, so a small landlord or recruiter will usually reach it through an identity service provider.

The DVS confirms that the details you submitted match the issuer's record; it does not compare the face on the document with the person in front of you, and it does not tell you whether the address or income in the rest of the file is correct. Use it as one corner of the comparison, then carry on with the other checks.

How do you cross-check a company file against the registers?

You compare legal name, ACN or ABN, status, registered office and directors on the contract or invoice with the public record. ASIC holds the company register and company extracts, and ABN Lookup shows the ABN, entity name and status.

Four comparisons do the work:

1. ABN or ACN on the contract against the registry entry for that name.
2. Status: registered, deregistered or in liquidation on the date of signature.
3. Registered office against the address on the letterhead.
4. Signer against the listed directors and officeholders in the ASIC extract.

A registry lookup proves that an entity exists with that status on that day; it does not prove that the document in front of you is genuine or that the signer has authority.

What does a mismatch look like, and what does the reviewer do?

A mismatch falls into one of three classes, and each has a fixed response. Without that, the same discrepancy is accepted by one reviewer and rejected by another.

A file is complete when each of the seven checks has a result, not when each document is present. A missing statement and a failed comparison are different states and should be reported as different states.

Questions people ask about mismatched files

People who handle applicant files in professional communities tend to ask the same things. These two come up most.

"The name on the payslip is slightly different from the driver licence. Do I have to reject it?" No. Check surname and date of birth first. If both match, treat it as a variant and record the rule you applied. Escalate only when surname or date of birth differ without a supporting document.

"The bank credits are lower than the payslip shows. Is it fake?" Not necessarily. Pay can be split across two accounts, reduced by an advance or paid late. Ask for the next pay cycle and a second payslip. It becomes unexplained only if the gap persists with no explanation.

Automating the comparisons

A validation tool should extract the same fields from each document, normalise them and show a field-by-field comparison with a reason for each difference. Whether a mismatch is acceptable stays a policy decision for your team. The comparison should only use information reasonably necessary for your purpose, in line with the Australian Privacy Principles under the Privacy Act 1988 (OAIC). A Tax File Number in particular has restricted uses and should not be collected unless the law allows it. CheckFile compares fields, dates and register data across a file and flags differences for review; it does not certify that any document is authentic. To see how this works on a financing file, read about our solution for financing and leasing, check pricing or review our approach to security and data handling.

Frequently Asked Questions

What is cross-document verification?

It is the comparison of the same field (such as name, address or income) across several documents and public records in one file. Differences are classified and sent to a reviewer with a defined next step.

Which documents should be compared first?

Start with the photo ID, the proof of address and the income documents. Name, date of birth and address on these three catch the largest share of inconsistent files, and they are the cheapest to compare.

Does cross-document verification detect forged documents?

Not by itself. It finds inconsistencies between documents. A well-made forgery that agrees with the rest of the file would pass, which is why an issuer check such as the DVS or a registry lookup is added where one exists.

How many months of bank statements should be matched to payslips?

At least two pay cycles. One can match by coincidence or fail for an innocent reason; two show whether the pattern holds.

What should the reviewer record?

The check, the fields compared, the result, the rule applied and any document requested. That record is what you show an auditor or AUSTRAC if the decision is questioned.