Factual name comparison

Situation playbook

Check name consistency for a rental application

A difference between documents is not solved by quietly choosing one version. First identify exactly where the difference appears and which source is current.

Market: AU
Jurisdiction: Australia
Updated: 2026-08-05

Short answer

Make a small comparison table with the application field, the version shown in each source, the source date and the reason it differs if you know it. Use the version supported by your current document, preserve a genuine difference and ask the recipient whether a short factual note or a specified record is required. Do not add sensitive documents simply to make the names look uniform.

Continue in RentFiles

Turn this guide into a clear application pack

Fill your application before you choose whether to pay for a PDF export. RentFiles does not guarantee an outcome.

Organise your confirmed application details Use the free Cover Letter Builder

Prepare a structured rental application PDF with RentFiles.
Fill your application before you choose whether to pay for a PDF export.
RentFiles helps organise the file; the agent or landlord decides the application outcome.

Keep in view

Do not solve a name difference with excess data

Where the Privacy Act covers a real estate agent, it may collect only personal information reasonably necessary for its functions or activities.

This is not legal advice and it does not determine whether a particular agent is covered, what evidence it may request or whether a name record is sufficient. Ask the recipient a property-specific question when you need clarification, and seek appropriate independent advice for a legal question.

RentFiles helps organise the information you choose to enter into a structured application PDF. It does not verify identity, amend source documents, contact a recipient or promise that an application will be accepted.

Useful context

Separate a spelling difference from a record change

Start by copying the name exactly as it appears in the application and in each relevant record. Look for a spelling variation, a different order, a missing middle name, a previous name or a data-entry error. These are different situations and they need different descriptions. A single label such as 'name mismatch' hides the detail a recipient may need to see.

Keep the comparison limited to fields that the recipient has asked for. The purpose is to avoid a confusing application record, not to build a complete identity history. If an old document has no role in the application, keep it out of the package rather than using it to explain a difference it does not resolve.

Action plan

Build a four-column consistency check

Use four columns: application field, current source, other source and action. In the action column, write 'matches', 'correct application', 'ask recipient' or 'not used'. Include source dates where they are shown. This keeps a correction separate from an explanation and stops an unsupported guess becoming part of the file.

If the application itself has an error, correct it before sending. If two relevant documents genuinely differ, use a short neutral description of the difference and ask the recipient what it needs. Do not claim that a recipient will accept a particular record or that an explanation proves identity.

Current document used for the application field.
Other relevant document and its date.
Exact difference, without a conclusion beyond the source.
Next action owned by the applicant or recipient.

Working checklist

Keep an explanation narrow and traceable

A useful note identifies the field, says which version appears in the application and names the supporting document. It should not include a broad personal story, unrelated account details or claims about why a recipient should overlook a difference. If a change is not documented in the material you hold, state that the supporting record is not available and ask what the recipient accepts.

Do not combine another person's record with yours to create a fuller narrative. The recipient may need its own process for joint applicants or references. Your job is to preserve what each document says and to make a missing connection visible.

Practical example

Example: an abbreviated middle name

A fictional applicant's current identity record shows a middle name in full, while an income record uses only an initial. The application includes the full version. The comparison table records both forms, their document dates and the fact that the income record uses an initial. The applicant asks whether the recipient needs anything beyond that concise note.

The applicant does not crop a document to conceal the initial or attach an unrelated historic record. The purpose is a readable trail. Any further identity check remains the recipient's decision and process.

Questions

Common questions

Clear answers for the decisions people usually pause on.

Should I silently correct a different name in a document?

Correct an application entry that is wrong, but preserve a genuine document difference and ask the recipient what concise supporting record it needs.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack