Extract PEXA Settlement Statements to Excel

To extract a PEXA settlement statement into Excel, build the spreadsheet as one row per source fund, destination fund, fee, withholding, or adjustment line. At minimum, capture the matter reference, property, settlement date, party side, line category, authority or payee, description, period covered, debit or credit amount, source file, page number, and a review flag.

That structure matters because a completed Australian settlement file is not one simple total. A PEXA workspace output can include source funds, destination funds, revenue office and land registry payments, mortgage discharge or redemption figures, agent commission, conveyancer fees, PEXA fees, Foreign Resident Capital Gains Withholding (FRCGW), and a separate statement of adjustments for rates, water, strata or owners corporation levies, land tax, rent, and other periodic amounts adjusted to the settlement date.

A 2025 Australian Senate committee report on e-conveyancing states that PEXA's platform supports over 90 per cent of Australian property settlements. For conveyancers, property lawyers, WA settlement agents, accountants, SMSF advisers, and portfolio bookkeepers, that means PEXA settlement output is no longer an edge-case document. It is a recurring financial record that often needs to survive matter close, tax workpapers, SMSF audit evidence, portfolio reporting, and later CGT review.

The extraction job is not to explain what PEXA is or to recalculate the settlement. It is to convert the settlement statement, statement of adjustments, and workspace financial summary into reviewable rows. The spreadsheet should let a reviewer see which side the line belongs to, what the line represents, where it came from, whether it needs judgement, and whether the amount agrees back to the source document.

Keep the boundary clear. A spreadsheet can preserve evidence for vendor net proceeds, purchaser cost-base support, CGT working papers, trust or matter ledger reconciliation, and post-settlement archiving. It should not decide legal treatment, recalculate duty, determine deductibility, or replace the conveyancer's settlement review. The best extraction output gives the professional enough structure to review the file properly.

The spreadsheet schema that survives review

A one-row-per-document export is too blunt for settlement work. The useful unit is the line item, because the same pack can contain payment directions, funds movements, settlement fees, outgoings adjustments, tax withholding, and evidence that later belongs in different workpapers.

Use a schema that keeps each row traceable:

• Matter or file reference
• Property address and title reference, where available
• Settlement date
• Party side: vendor, purchaser, incoming mortgagee, discharging mortgagee, agent, conveyancer, revenue office, registry, or other
• Document type: settlement statement, workspace financial summary, statement of adjustments, trust ledger, invoice, authority notice, lodgement or registration evidence, or EFT/payment confirmation
• Line category: source funds, destination funds, fee, withholding, duty or lodgement, mortgage payout, commission, adjustment, reimbursement, or rent
• Authority or payee
• Description exactly as shown, with a normalised description only in a separate column
• Period covered, where the line is an apportionment
• Paid, unpaid, or adjusted-as-paid status, where visible
• Debit amount and credit amount in separate columns
• GST or tax treatment note where the source document states one
• Source file name
• Page number
• Review flag and reviewer notes

The review flag is not a failure field. It is how the extraction stays honest. FRCGW, land tax, owners corporation levies, rent adjustments, unclear payee names, duplicate descriptions, and amounts that appear in both the statement of adjustments and the final settlement statement should be visible to a person before import or archive.

Some supporting documents should be preserved even when they are not adjustment rows. Lodgement summaries, registration evidence, EFT confirmations, and cleared-payment records can explain why a settlement-statement amount was paid and whether the matter file has enough source evidence for close, audit, or later accounting review.

Manual entry is fine for one settlement; batch extraction becomes useful when a firm or accountant needs the same columns across many matters. In that setting, financial document extraction to Excel is useful because the workflow is repeatable: upload the completed PEXA settlement packs, describe the required columns, export XLSX, CSV, or JSON, then review flagged rows against source file and page references.

Before import, check completeness, reconcile source funds and destination funds to the settlement statement, reconcile adjustment subtotals to the statement of adjustments, and verify debit and credit signs by party side. Keep ambiguous FRCGW, land tax, rent, mortgage payout, commission, reimbursement, and repeated-description rows flagged rather than silently classifying them.

Separate the settlement statement from the adjustments

A PEXA settlement statement or workspace financial summary is mainly about money moving at settlement. It records the source funds needed to complete the transaction and the destination funds paid out to the parties or authorities. Depending on the matter, those rows may involve the purchaser, vendor, incoming mortgagee, discharging mortgagee, agent, conveyancers, the state revenue office, the land registry, and PEXA itself.

Extract those rows as funds or payment-direction evidence. Common categories include purchaser source funds, incoming lender funds, vendor destination funds, mortgage discharge or redemption, agent commission, conveyancer fees, PEXA fees, duty or transfer duty, lodgement or registration fees, and FRCGW withholding where it appears. The spreadsheet should preserve whether the line is a source or destination, who the payee or payer is, and which side of the transaction the amount belongs to.

The statement of adjustments is a different document. It explains how outgoings and incomings are apportioned to the settlement date. Council rates, water rates, strata levies, owners corporation fees, body corporate contributions, land tax, rent, and similar periodic amounts should be extracted with their period covered, paid status, apportionment basis if visible, and the amount allocated to each side.

The danger is double-counting. An adjustment may help calculate the final settlement amount and then flow through to the PEXA workspace as part of the final funds movement. If the spreadsheet treats both appearances as separate costs, the accountant or reviewer may overstate the transaction. Use document type, line category, and review flags to show whether a row is an underlying adjustment, a final payment direction, or a repeated amount that needs reconciliation.

For adjustment review, the practical checks are the rating or levy period, settlement date, paid or unpaid status, purchaser allocation, vendor allocation, and whether the final amount reconciles to the side of the matter being reviewed. Vendor net proceeds, purchaser source funds, and purchaser cost-base support are related outputs, but they are not the same reconciliation. Keep each row tied to the side and purpose it supports.

This is where Australian settlement records differ from overseas analogues. The closest sibling workflow is Australian statement of adjustments and PEXA FSS extraction; global property-settlement documents such as UK completion statement extraction may share traceability principles, but the vocabulary, parties, tax fields, and adjustment mechanics in an Australian PEXA matter should be kept Australian. Do not translate PEXA source and destination funds into UK completion language in the export.

Capture vendor and purchaser records differently

The same settlement pack is read differently depending on which side of the matter the reviewer represents. A vendor-side extraction is usually concerned with net proceeds, selling costs, mortgage payout, agent commission, conveyancer costs, and any withholding that affects the cash received at settlement. Those rows help the conveyancer close the matter and give the accountant a clearer trail for capital proceeds and CGT support records.

A purchaser-side extraction has a different centre of gravity. The important rows are source funds, incoming loan funds, duty and lodgement payments, acquisition costs, settlement adjustments, and evidence that may support future cost-base work. A purchaser spreadsheet should keep settlement adjustments visible even when they are netted into a final figure, because the accountant may need to understand the period, paid status, and authority behind the amount years later.

SMSF and audit contexts need stricter traceability. The spreadsheet should preserve the source file, page number, party side, payee, description, period covered, and review flag. An auditor should be able to move from a row in the spreadsheet back to the settlement file without relying on memory or a manually renamed PDF. For trustees holding the asset through a fund, the settlement export usually feeds into a wider per-property audit evidence ledger covering rates, levies, agent statements, trades invoices, and LRBA records that supports the annual SAR.

Portfolio accounting adds another practical requirement: consistency across properties. If one transaction uses "water rates", another uses "water usage", and a third uses a local authority description, the export should preserve the original wording while also giving the reviewer a normalised category. That lets a family office, SMSF practice, or property accountant compare transactions without losing the evidence trail.

Some errors are easy to create when the spreadsheet does not carry party side. Agent commission is usually a vendor-side selling cost, not a purchaser acquisition cost. A settlement adjustment is not automatically an immediate expense. FRCGW should not disappear simply because it is only one line in the settlement statement. The extraction should capture the evidence and flag the issue; the responsible adviser decides tax treatment, deductibility, cost-base inclusion, and any further workpaper classification.

Extract adjustment lines for rates, water, strata, land tax, and rent

When extracting a statement of adjustments, preserve the evidence behind the apportionment, not just the final amount. For each adjustment row, capture the authority or payee, assessment or account reference where visible, period covered, paid or unpaid status, apportionment basis if shown, purchaser amount, vendor amount, source page, and review flag.

Council rates and water rates are common because they are periodic outgoings that may have been paid by one party for a period that straddles settlement. The useful spreadsheet row does not merely say "rates adjustment". It should show the council or water authority, the period, whether the amount was paid before settlement, and which side bears the adjustment. If the file includes the original notice, Australian council rates notice extraction can provide the upstream assessment details that support the settlement adjustment.

Strata, owners corporation, and body corporate levies need the same discipline, with local terminology preserved. A Victorian owners corporation fee, a Queensland body corporate contribution, and a NSW strata levy may function similarly as periodic property outgoings, but the spreadsheet should not normalise away the wording a reviewer needs to recognise.

Add state or territory, revenue office, land registry, duty or transfer duty reference, registration or lodgement reference, and the exact wording used on the source document. New South Wales, Victoria, Queensland, Western Australia, South Australia, Tasmania, the ACT, and the Northern Territory can differ in revenue office names, registry references, duty wording, land tax language, and strata, owners corporation, or body corporate terminology. Preserve that source wording in one column and use a separate category column for reporting.

Land tax is especially sensitive because treatment and recoverability can depend on state law, contract terms, property use, and timing. The extraction file should capture the line exactly as shown, the state or revenue authority where visible, the period, the amount, and a review flag. It should not decide whether the amount is recoverable, deductible, capital, or otherwise. Where the source pack includes land tax assessments across multiple jurisdictions, Australian land tax assessment extraction is the better place to capture the authority-level notice data before it feeds the settlement file.

Rent and other income adjustments deserve their own category when an investment property has tenants in place. Capture the payer or recipient, period covered, amount allocated to each side, and whether the line is income, outgoings recovery, bond-related, or simply a settlement adjustment requiring review.

Do not turn the extraction spreadsheet into a duty calculator or apportionment engine unless the firm has deliberately built that process with the right authority and source data. For most post-settlement records, the safer job is to preserve the evidence layer clearly enough that the conveyancer, accountant, or auditor can review the calculation already made in the settlement file.

When to automate and what to hand to the reviewer

Manual entry is still reasonable for a single residential settlement where the buyer or vendor only needs a simple record. In that case, the priority is accuracy, not speed: copy the key settlement and adjustment lines, keep the source PDF, and make sure the accountant or conveyancer can trace each figure back to the file.

Batch extraction becomes worthwhile when the same task repeats. A conveyancing firm closing a steady monthly settlement load can use a consistent export to check source and destination funds, close matter files, and identify exceptions. A property accountant can extract settlement lines across several client transactions before preparing cost-base records. A portfolio office can keep acquisition and disposal records in one structure instead of rebuilding the spreadsheet for every property.

The reviewer should receive more than a spreadsheet of amounts. A useful handoff package includes the XLSX, CSV, or JSON export; the source PDFs or images; source file and page references; review flags; and notes for tax, audit, trust ledger, or matter-close follow-up.

Invoice Data Extraction fits the batch and portfolio route: upload the completed settlement packs, specify the row-level schema in the prompt, export XLSX, CSV, or JSON, then review flagged rows before import or archive. Use it as the extraction layer, with legal, settlement, and tax treatment left to the responsible professional.

The standard is simple: a conveyancer, accountant, SMSF auditor, or portfolio reviewer should be able to open the spreadsheet years later, understand each settlement line, find the source document, and see which items needed judgement before the record was filed.