Freelance project event ledger

Applicant playbook

Explain freelance work, invoices and payments

Work completed, an invoice issued and a payment received are three different entries.

Market: AU
Jurisdiction: Australia
Updated: 2026-10-11T19:49:45.792Z

Short answer

Give each relevant project a neutral key and record its completed work dates, invoice date and received-payment date separately. Point each entry to its source. Label an unpaid invoice or future project with its actual status; do not include it as money already received. Explain a timing gap briefly, using the period the recipient actually asked about.

Continue in RentFiles

Turn this guide into a clear application pack

Fill your application before you choose whether to pay for a PDF export.

Continue with the Tenant resume guide.

Build my personal rental profile Use the free Rental Readiness Score

Create a personal rental profile, delivered as a shareable PDF, to complement the process required by the agent or landlord.
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

Filled example: three clients, three different stages

This example is entirely fictional. Elise, the clients, records and dates are invented. She checks the ledger on 11 October 2026 and uses neutral project keys.

Project A | Completed work: 3 to 7 September, completion email | Invoice: A101 issued 9 September | Received payment: 18 September, matching A101 reference in the payment record | Status: received; keep the later payment date distinct from the work dates.
Project B | Completed work: 15 to 19 September, completion note | Invoice: B202 issued 22 September | Received payment: not shown in the records checked on 11 October | Status: invoice issued, payment pending; no received-payment entry is invented.
Project C | Proposal dated 8 October for possible work on 20 to 23 October | Work: not completed | Invoice: none issued | Payment: none received | Status: future proposed work, separate from the completed entries.
Elise’s note | "Project A was paid after the work period. Project B is invoiced but not shown as received. Project C remains proposed future work. The ledger does not present all three as a monthly income total."

Working checklist

Use a project, event and source ledger

Keep client identities and confidential work details out of your private summary where a neutral locator is enough. Check the recipient’s actual document instructions before preparing sharing copies.

Project key: one consistent neutral label, with the original source kept privately traceable.
Work event: completed dates and the record supporting them, or not completed.
Invoice event: actual issue date and reference, or no invoice issued.
Payment event: actual received date and matching reference, or payment not shown as received.
Open point: a combined payment, missing period or unclear reference stays unresolved rather than being allocated by guess.

Action plan

Copy and adapt: explain one payment timing gap

Replace the keys, dates and record titles below with facts from your own ledger. Remove any sentence that does not apply.

Subject: Freelance project records for [property reference] Hello [name], For the requested period [dates], my ledger separates completed work, invoice dates and received payments. Project [A] was completed on [dates], invoiced on [date] and paid on [date], as shown by [source references]. Project [B] has an invoice dated [date], but my checked records do not yet show the payment as received. Project [C] is future work and is not included as a completed receipt. Please confirm whether the selected records answer your requested period or identify the specific event you need clarified. Thank you, [name]

A short explanation of the actual gap is enough. Do not promise when an unpaid invoice will be paid or use the ledger as a forecast.

Useful context

Keep the project events separate

Start with the requested period, then find the projects whose records answer it. A project can have completed work without a received payment. Another may still be a proposal rather than completed work.

This ledger tracks events across several clients. It does not turn business receipts into personal income, calculate affordability or predict a regular monthly amount. Use the separate contractor guide when the main question is one agreement’s parties and confirmed term.

Keep in view

Check the source behind each outgoing entry

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

Reopen the source for each work, invoice and payment date. Preserve the originals and ask whether a changed sharing copy is suitable before altering a requested record. Keep the project key consistent without adding unnecessary client contacts or commercial detail.

Create a personal rental profile, delivered as a shareable PDF, to complement the process required by the agent or landlord. 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 building

Browse all resources

Questions

Common questions

Clear answers for the decisions people usually pause on.

Does an issued invoice show a payment has been received?

Keep those events separate. Record the invoice date from the invoice and the received-payment date only when your checked payment record supports it.

What if one payment covers several projects?

Mark the payment as combined and keep its source reference visible. Do not invent a project allocation; ask which period or breakdown the recipient needs clarified.

Your next step

Put your application documents in one clear pack