PropertyMe, PropertyTree and Console Statements to Excel

PropertyMe, PropertyTree and Console Cloud owner statements can be converted to Excel by capturing the statement period, payment date, agency, property, gross rent, management and letting fees, creditor deductions, GST shown on fees, withheld amounts and net disbursed into one spreadsheet. Manual entry or portal downloads can work for a single property. Batch extraction becomes more useful when the statements span several properties, agencies, months or PDF formats.

That is the practical job behind searches for PropertyMe PropertyTree Console owner statements to Excel. The reader usually is not choosing a property management platform. They already receive owner statements from a managing agent using PropertyMe, MRI Property Tree, Console Cloud or Reapit PM, and they need the data in a workbook that a landlord, bookkeeper, SMSF accountant or tax agent can actually use.

The hard part is not one statement. It is the recurring pattern: a mid-month payment, an end-of-month disbursement, an EOFY summary, an attached creditor invoice, a council rates charge, a water recovery, an agency fee with GST, then the same thing again from another agency using a different layout. A PDF archive proves the documents exist, but it does not give you a portfolio view of gross rent, deductions, fees and net cash received.

A useful spreadsheet keeps each statement traceable back to its source. At minimum, it should store the agency, PM system, property, owner or folio reference, statement number, statement period, payment date, income lines, fee lines, deduction categories, GST shown on agent fees, withheld amounts, net to owner and the source file. Once those fields are consistent, PropertyMe, PropertyTree and Console statements can sit in the same workbook without pretending they are identical documents.

Know what the owner statement is, and what it is not

An owner statement, sometimes called a landlord disbursement statement, summarises what the managing agent received, deducted, withheld and paid to the owner for a defined period. It normally sits between the agency's trust accounting records and the owner's tax or bookkeeping file. For spreadsheet extraction, that makes it a summary document, not the whole evidence pack.

It is different from a rent ledger. A rent ledger tracks tenant charges, receipts and arrears over time. It may help explain why a rent receipt appears on the owner statement, but it is not the same as the owner's disbursement record.

It is also different from a creditor invoice. A plumber's invoice, council rates notice or body corporate contribution notice supports a deduction line. The owner statement may show the deduction, but the source document explains the supplier, tax invoice details and charge description.

Nor is it a settlement statement. A property settlement statement belongs to a purchase or sale transaction, while an owner disbursement statement is the recurring rental-management record after the property is being managed.

An EOFY statement is a related annual summary. It is useful for tax-time consolidation, but monthly and mid-month owner statements still matter when an accountant needs timing, payment dates, statement numbers, attachments or exception notes. If a June repair is paid in July, a yearly summary alone may not tell the whole story.

Finally, owner-statement extraction is not the same as Australian real estate trust account reconciliation. Trust account reconciliation is the agency-side control process for matching trust bank, ledger and trial balance records. The landlord's job is narrower: turn the statements they receive into a reliable rental-property spreadsheet.

Map the fields each platform gives you

PropertyMe owner statements are useful extraction sources because they expose identifiers and totals that help keep a workbook auditable. The statement number, folio code, total income, expenses, total disbursed and generated date can all become control fields. Owner portal access lets owners download statements, although mobile financial activity export is limited, so some owners still need to request a financial summary from the agent.

PropertyTree, or MRI Property Tree, tends to surface a broader document pack through the owner portal context: reports, owner statements, ownership ledgers, creditor invoices and invoice attachments. For an SMSF accountant working through PropertyTree disbursement records, those attachments matter because they connect the statement deduction back to the supporting evidence. The EOFY statement can help consolidate the year, but the monthly statement still carries useful period and payment detail.

Console Cloud and Reapit PM statement material points to consolidated owner statements, income and expense breakdowns, owner percentage splits, payment summaries and property identifiers. Console statement examples also show fields that are easy to lose in manual entry: payment date, paid-to-owner amount, rent receipts, GST columns, letting fee, rent commission fee, withheld amounts and per-property summaries.

The spreadsheet should not preserve every platform's wording as separate columns. Normalise the meaning. A PropertyMe folio code, a PropertyTree ownership reference and a Console property identifier can all sit in an owner or property reference column. A letting fee, rent commission fee and management fee should remain separate where the statement separates them, but they still belong in one fee group for review.

Build the accountant-ready spreadsheet schema

For an accountant-ready landlord statement workbook, start with control fields before money fields. Use columns for property, agency, PM system, owner or folio reference, statement number, statement period, payment date, source file and notes. Those fields are what let a reviewer trace a row back to the exact statement rather than trusting a copied total.

Then split the financial fields by accounting use: gross rent received, tenant or reference where shown, management fee, letting fee, lease renewal fee, inspection fee, other agent fees, creditor deductions, council rates, water, strata or body corporate charges, repairs, insurance, smoke alarm compliance, land tax where shown, GST on agent fees, withheld amounts and net disbursed.

Statement period and payment date need separate columns. The statement period explains which rental activity the statement covers. The payment date explains when the owner received money in the bank account. In a twice-monthly disbursement cycle, those dates can answer different questions. Collapsing them into one "month" field is how June income, July bank deposits and EOFY summaries become difficult to reconcile.

Gross rent, fees, deductions, withheld amounts and net disbursed should also remain separate. Net to owner is useful for bank reconciliation, but it hides the components an accountant or landlord usually wants to inspect: rent collected, agent fees charged, supplier invoices paid and amounts retained for future costs.

The spreadsheet should organise source records for review, not decide tax treatment on its own. A line appearing on an owner statement does not automatically make it deductible, correctly categorised or complete. It gives the accountant structured evidence to question, reconcile and supplement.

Handle mid-month, end-of-month and multi-agency statements

Australian owner-statement workflows often have a cadence problem. A landlord may receive a mid-month disbursement and an end-of-month disbursement for the same property, each with its own payment date, rent receipts, fees and deductions. New Payments Platform transfers can make the bank movement fast, but the accounting question remains: which statement period did that payment represent?

PropertyMe commonly exposes the mid-month and end-of-month rhythm, PropertyTree can follow a similar statement and payment pattern, and Console Cloud depends more on agency configuration. That variation is exactly why the spreadsheet should store period, payment date, agency and PM system as separate fields.

The spreadsheet needs both dates because they serve different checks. The payment date ties the statement to the bank deposit. The statement period ties the statement to the rental activity. If the workbook stores only one month label, two statements can be merged accidentally, or one month's activity can be split across the wrong reporting period.

The problem compounds when the landlord uses more than one managing agent. A Sydney property may arrive as a PropertyMe statement, a Brisbane property as a PropertyTree owner statement and a Melbourne property as a Console Cloud disbursement. Each file may use different names for similar concepts: paid to owner, total disbursed, net disbursement, rent commission, management fee, ownership split or folio reference.

That is why the Australian workflow should be designed around the local document pattern, not copied from a US owner statement extraction workflow. US owner-statement guides often assume different tax forms, software ecosystems and statement conventions. For Australian landlords, the workbook needs to respect mid-month and EOM disbursements, EOFY summaries, council rates, water charges, body corporate or strata costs and local GST treatment.

For multi-agency portfolios, add a PM system column and an agency column even if the property address seems unique. They make filtering and exception review much easier when one agent changes platform, one property changes manager, or a later EOFY summary needs to be checked back against monthly statements.

Preserve deduction categories, GST and source documents

The ATO lists council rates, water charges, land tax, property agent's fees and commission, and repairs and maintenance among rental property expenses that can be claimed as immediate deductions when the property is rented or genuinely available for rent, according to its guidance on ATO common rental property expenses. That is the reason to preserve categories, not flatten every deduction into "expenses".

Council rates, water, strata or body corporate charges, repairs, insurance, smoke alarm compliance, sundry fees and withheld amounts should remain separate where the statement gives them separately. A landlord with several properties may need to review one council area, one water recovery or one supplier charge without unpicking a combined deduction total later.

Keep jurisdiction or exception notes where local treatment can change the review question. Water recovery, smoke alarm compliance, council rates and strata or body corporate charges do not always behave the same way across NSW, Victoria, Queensland and other states, so the workbook should preserve what the statement says rather than turning local detail into a generic deduction label.

GST deserves its own field when it appears. Residential rent is generally treated differently from commercial rent, and agent fees may show GST even where the rental income itself is not being handled as a taxable supply by the landlord. The spreadsheet should capture GST as shown on the statement or supplier document rather than infer it from the total amount.

Some deduction lines need a second source document. A council rates deduction on the owner statement may have a rates notice behind it, which is why a sibling workflow such as multi-property Australian council rates notice extraction can sit alongside owner-statement extraction. The same applies to strata and body corporate charges, where QLD body corporate contribution notice extraction is the supporting-document problem rather than the statement-summary problem.

Add a source document reference column for the statement file and, where available, the attached creditor invoice or notice. That column is especially useful when a deduction needs to be queried, recoded, split between properties or checked for SMSF audit support, and it slots directly into a wider SMSF property audit evidence pack that pulls rates, levies, agent statements, trades invoices, tax depreciation schedule workpapers and LRBA records into a per-property ledger.

Choose the right extraction route

Manual entry is reasonable when the file count is small. A landlord with one property, one agency and a handful of monthly statements may spend less time keying the figures than setting up a repeatable process. The important discipline is to enter the control fields, not just the net payment.

Portal downloads and exports are the next option. Owner portals can provide statements, EOFY summaries, ledgers, reports and attachments, depending on the platform and the agency's configuration. PropertyMe, PropertyTree and Console Cloud do not behave identically, and export availability does not guarantee the spreadsheet will contain every field the accountant wants. Check whether the export preserves property identifiers, payment dates, statement periods, fee categories, GST fields and source-document links.

Batch extraction fits a different workload: historical PDF stacks, multiple agencies, mixed PropertyMe and PropertyTree layouts, Console Cloud statements with consolidated properties, or an accountant processing several client portfolios before EOFY. In that case, the value is not just speed. It is consistency across statement formats.

Invoice Data Extraction is relevant in that batch context because it converts invoices and financial documents into Excel, CSV or JSON from a natural-language prompt. For this workflow, the prompt should ask for the owner statement fields explicitly: agency, PM system, property, owner or folio reference, statement number, statement period, payment date, rent income, management fee, letting fee, creditor deductions, GST shown, withheld amounts, net disbursed and source file. That is the point where financial document extraction into structured spreadsheets is a better fit than re-keying each PDF into a landlord cashflow tracker.

For line-level analysis, ask for one row per statement line or deduction line. For portfolio summaries, ask for one row per property and statement period, with separate columns for income, fees, deductions and net disbursed. The right row grain depends on the accountant's review process, so decide that before processing a large statement batch.

Check the spreadsheet before EOFY review

Before sending the workbook to an accountant, reconcile the net disbursed amounts to bank deposits. This is where the payment date field earns its place. If two statements share a month but only one bank deposit appears, or one payment covers several properties, flag it rather than forcing the numbers to balance silently.

Check that each statement period is represented once for each property and agency. Missing statements, duplicated payment dates, overlapping periods and EOFY summaries mixed into monthly data are common sources of double-counting. Keep annual summaries in the workbook if they help review, but label them clearly so they are not added to the same totals as monthly statements.

Review the fee and deduction categories before relying on the totals. Management fees, letting fees, lease renewal fees, sundry fees, repairs, water, council rates, insurance, strata or body corporate charges and withheld amounts should not all sit in one undifferentiated expense column. If the statement shows an owner percentage split or a multi-property allocation, keep that split visible.

Treat GST as captured data, not a formula guessed after extraction. If a statement shows GST on an agent fee, preserve it. If it does not show GST for a line, leave the field blank or mark it for review rather than inventing a tax component.

Finally, retain the source files. A useful EOFY rental statement consolidation workbook is not a prettier PDF archive. It is a structured Australian rental record with enough source references for an accountant, bookkeeper or SMSF auditor to interrogate the numbers.