Document guide · Income evidence
Document workspaceTurn requested income material into a readable evidence summary
Income material is easier to review when the reader can see what was selected, where each item sits and what question remains open. The summary should navigate evidence, not argue that it meets a financial test.
- Market
- AU
- Jurisdiction
- Australia
- Updated
Short answer
For an Australian rental application, build an income evidence map from the recipient's current request. Label each selected item by its real source and period, separate applicant notes from attachments and leave an unresolved point visible. The summary helps a reader locate material. It does not assess affordability, certify documents or predict a recipient decision.
Continue in RentFiles
Turn this guide into a clear application pack
Keep the request, selected sources and open questions clear before export.
- 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.
Working checklist
Build a request-to-source evidence map
Before assembly, create three short working lists: what the recipient currently asks for, the source pages the applicant has selected and any point that needs confirmation. This prevents a missing item from being hidden inside a broad label and prevents an unrelated page from entering the file merely because it contains financial information.
For every selected item, check the real source, document type and visible period. The list is descriptive only. It should not calculate a ratio, claim that the material is sufficient or call an applicant-supplied document verified.
- Recipient request recorded
- Source label and owner are accurate
- Shown period is visible
- Open question remains visible when unresolved
Action plan
Assemble a reader route, not an affordability case
Use the request as the section heading, then place each selected source beneath a short accurate label. Where context is needed, add a factual applicant note and keep it visibly separate from the attachment. A reader should be able to move from the request to the item without guessing why it is there.
Finish by comparing the map with the exported PDF. Check every page reference, remove duplicates and make sure an open question has not been rewritten as a conclusion.
- Request heading
- Accurate source label
- Separate applicant note when needed
- Export checked against the map
Key points
Finish with an unresolved-question check
Read the final section once as a reader who only has the request and the selected file. If a label is vague, a period is missing or an applicant note makes a conclusion the source does not support, revise it or leave the question visible.
RentFiles organises applicant-selected material. It does not validate financial records, give financial advice, assess affordability or decide whether the evidence meets a landlord or agent's criteria.
Useful context
Define the summary's job before adding files
The summary should help a reader navigate the supplied material. It can name the document type, owner and period, but it should not declare that income is sufficient, stable or acceptable. Those conclusions belong to the recipient's process, not the document-preparation layer.
Write the recipient's request at the top of your working notes. That line keeps the section focused and makes it easier to exclude files gathered for another purpose.
Keep in view
Run a deliberate privacy review
Review what the recipient asked for and whether each visible detail is necessary for that purpose. Do not assume that every field on a source document must be shared. When redaction or an alternative format may be appropriate, confirm the recipient's requirements before changing the document.
Keep original files outside the assembled pack and inspect the exported copy. This helps catch a hidden extra page, an exposed identifier or a scan that became unreadable during conversion.
Provide information relevant to the recipient's application process and handle identity or financial material carefully.
Questions
Common questions
Clear answers for the decisions people usually pause on.
How does a request-to-source income map work?
It starts with the recipient's current request, then lists the selected source material under accurate labels and keeps any unresolved point separate. The map helps navigation without making an affordability conclusion.
What should happen when the requested income item is not available?
Keep the item as an open question in the working list and confirm what the recipient needs. Do not hide the gap with a different document or an unsupported applicant statement.
Does RentFiles verify the income evidence in the PDF?
No. RentFiles organises information and documents selected by the renter. It does not certify records, assess affordability or decide whether the recipient will accept them.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Keep the request, selected sources and open questions clear before export.
Map your income evidence