Contract term and payer map

Applicant playbook

How to prepare a contractor rental application in Australia

Contractor can describe different working arrangements, so the application should use the wording and dates in the applicant's own records rather than infer a status.

Market: AU
Jurisdiction: Australia
Updated: 2026-07-20

Short answer

Start with the recipient's request, then record how the applicant's agreement describes the relationship, the named counterparty, confirmed term, payer, payment basis and completed pay periods. Keep invoices or pay records separate from contract facts, mark renewal discussions pending, and do not forecast income. Ask which period and format the recipient wants when the request is broad.

Continue in RentFiles

Turn this guide into a clear application pack

Fill your application before you choose whether to pay for a structured application PDF export. RentFiles does not assess evidence, submit the application or influence the agent or landlord's decision.

Build your structured application PDF

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.

Practical example

Trace a fixed term with a pending extension

Imagine an agreement showing a confirmed three month term and four completed payment records. The map points each payment to its covered period and keeps the counterparty separate from the payer. A message discussing a possible extension appears only in the pending row because it is not an amended agreement or completed period.

A new reader should be able to locate every sentence in the selected sources. If the note says the arrangement is ongoing, but the only term has ended and no new source confirms continuation, the wording must stop. The clean result is a visible term boundary and an open question, not a smoother unsupported story.

Term trace
Payer trace
Completed period trace
Pending extension
Unsupported continuity removed

Working checklist

Inventory the term and completed payment records

Create one row for the agreement and one row for every selected payment record. For the agreement, capture the source title, issue date, confirmed term, payment basis as displayed and any notice or renewal field that actually appears. For a payment record, capture its source, covered work or invoice period, payment date and payer.

Do not convert an invoice date into a payment date or extend a term because work may continue. If several counterparties or payers appear, give each its own row. Mark records current, completed, superseded or pending, and place an unresolved discrepancy in a question log before the application note is written.

Agreement row
Payment row
Date meaning
Record state
Discrepancy flag

Action plan

Write the contractor context in source order

Open with the exact relationship wording and confirmed term. Next identify the counterparty and payer without assuming they are the same organisation. Then describe the completed payment periods selected for the recipient's request. Finish with any renewal, new assignment or missing period as pending or unavailable rather than blending it into the confirmed record.

A short note can explain why agreement dates and payment dates differ, provided the applicant knows the reason and can trace it. Avoid projecting a monthly average, claiming continuous future work or interpreting a commercial clause. Route broad income summaries to the income evidence page and keep the contractor profile focused on relationship and term boundaries.

Relationship first
Counterparty and payer second
Completed periods third
Pending item last
No forecast

Useful context

Do not use contractor as a status shortcut

Copy the relationship wording from the applicant's agreement or current record. Record the organisation named as counterparty, the service or role description, the payer and the confirmed start and end information. If different records use different labels, keep those labels attached to their sources instead of choosing one that sounds more favourable.

The profile solves a navigation problem: a reader needs to see contract facts, completed payment facts and future questions as separate groups. It does not decide employment status, tax treatment, affordability or whether the records satisfy an agent. Those questions remain outside this clean room method unless an appropriate source and reviewer later support them.

Relationship wording
Counterparty
Payer
Confirmed term
Unresolved label

Keep in view

Protect client and commercial information

Contracts and invoices can expose client contacts, service detail, account information and commercial terms unrelated to a rental request. Compare each selected field with the recorded purpose, ask before altering a requested source file and keep the unchanged original secure. Use neutral filenames that do not expose a client or account number.

The OAIC tenancy source supplies the privacy boundary used here. It does not define contractor evidence requirements or decide what a recipient will accept. Once the applicant has checked the term map and selected facts, RentFiles can structure entered details into an application PDF before payment; it does not verify the arrangement or decide the result.

Provide information relevant to the recipient's application process and handle identity or financial material carefully.

Purpose matched
Client data checked
Commercial detail checked
Original retained
Recipient question recorded

Keep building

Browse all resources

Questions

Common questions

Clear answers for the decisions people usually pause on.

Does the word contractor prove a particular work status?

No. Use the wording in the applicant's actual agreement and keep any conflicting labels attached to their sources. This page does not determine legal or tax status.

Can I include a likely contract renewal?

Include it only as pending, with the source and date of the discussion. Do not add it to the confirmed term until a current record supports the change.

Should invoices and payments be treated as the same date?

No. Keep invoice, work period and payment dates distinct. The map should show what each source actually records without converting one event into another.

Do I need to identify every contractor client?

Follow the recipient's request and share only relevant applicant controlled information. Ask whether a neutral source label is acceptable when client detail has no stated purpose.

Does RentFiles verify contractor agreements or income?

No. RentFiles organises details entered by the applicant into a structured application PDF. It does not verify contracts, calculate income or decide the outcome.

Your next step

Put your application documents in one clear pack