Statement of Adjustments Data Extraction (Canada)

Statement of adjustments data extraction Canada converts the closing-day PDF set — the Statement of Adjustments, the law firm's Trust Ledger, and the provincial Land Transfer Tax, Property Transfer Tax, or Welcome Tax notice — into structured rows that map cleanly to Adjusted Cost Base additions and current-period expenses on the property's books. The extraction returns one or more rows per closing, with the closing-cost detail preserved at the line-item level: provincial tax separated from municipal tax, Foreign Buyer Additional separated from base PTT, HST separated from the underlying service fee, and a source-file reference on every row.

Three provincial differences shape the schema. Ontario charges a graduated provincial Land Transfer Tax on every transfer, and the City of Toronto layers a Municipal Land Transfer Tax on top — two distinct fields the extraction has to keep apart. British Columbia charges a bracketed Property Transfer Tax with a Foreign Buyer Additional of 20% layered on residential transfers to foreign buyers in specified regional districts. Quebec charges municipal mutation duties (the taxe de bienvenue, or Welcome Tax) under a single provincial framework, and unlike LTT or PTT the duties arrive as a separate municipal invoice payable within 30 days of the billing date rather than on closing day.

That last point is the angle the rest of this guide is built on. The closing in Canada is a connected document set, not a single closing-day PDF. Treating it that way — Statement of Adjustments and Trust Ledger together at closing, plus the provincial tax notice, plus the post-closing tail of Welcome Tax invoices and municipal property-tax true-ups as they arrive — is what turns extraction output into a usable property ledger across provinces. A bookkeeper recording a stack of acquisitions into an Adjusted Cost Base schedule, a CPA processing closing packages on behalf of investor clients, or a developer rolling several closings into a project ledger needs the schema to hold up across all of those documents and across all of those provinces.

The Closing-Day Document Set: Statement of Adjustments and Trust Ledger

The Statement of Adjustments is the lawyer-prepared closing-day document that records every dollar moving on closing day from the buyer-and-seller perspective. The line items it carries are the purchase price; the deposit credit; the prorated property-tax adjustment as of the closing date; prorated utility, fuel-oil, and (for condominiums) common-expense adjustments; and any prepayments the seller made that the buyer is reimbursing on closing. It nets to a single balance the buyer pays or receives at closing. By itself it does not reconcile to a property-ledger row. The closing costs that determine the Adjusted Cost Base — provincial Land Transfer Tax, municipal Land Transfer Tax in Toronto, BC Property Transfer Tax, legal fees, title insurance, registration — are not on it.

Those costs live on the Trust Ledger. The Trust Ledger is the law firm's record of money in and out of the lawyer's trust account on the file: the buyer's mortgage advance and deposit going in, and the disbursements going out — provincial LTT or PTT, Toronto MLTT where it applies, legal fees, title insurance, registration fees, courier and search disbursements, and any other charge the law firm paid from trust on the buyer's behalf. The Trust Ledger is what bookkeepers read to allocate closing costs between capital additions to the property and current-period expenses on the rental P&L.

The two documents are complementary, and extracting one without the other leaves the property ledger row incomplete. Pulling the SOA alone gives the proration adjustments and the deposit handling but no closing-cost detail. Pulling the Trust Ledger alone gives the closing costs but no proration story. Both have to come through the extraction layer to reconcile a single acquisition row.

The harder reality for any extraction workflow is that there is no Canadian-standard form for either document. SOAs and Trust Ledgers come from many different law firms in many different layouts: column orderings differ, line-item descriptions differ, some firms put HST as a separate column and some bury it in the line total, some firms label the Trust Ledger as a "trust statement" or "lawyer's reporting letter" entirely. An extraction layer has to read the layout each firm uses rather than pattern-match against a canonical template. This is structurally different from the US side, where readers handling cross-border closings can rely on a standardised form; for that audience, extracting ALTA and HUD-1 settlement statements into Excel is the comparable workflow, but the Canadian set carries the Trust Ledger as a separate document and the provincial tax fragmentation that the next sections work through.

---

Ontario: Provincial LTT and Toronto MLTT as Separate Fields

Ontario charges a provincial Land Transfer Tax on every property transfer registered in the province. The residential brackets run 0.5% on the first $55,000 of value, 1% on the portion from $55,000 to $250,000, 1.5% on the portion from $250,000 to $400,000, 2% on the portion from $400,000 to $2,000,000, and 2.5% on the portion above $2,000,000. For properties inside the City of Toronto, the city layers a Municipal Land Transfer Tax on top of the provincial one — at the same closing, on the same value, into the same Trust Ledger — and the two amounts have to come out of extraction as separate fields. Collapsing them into one "land transfer tax" total destroys the audit trail back to either taxing authority and makes the resulting ledger row impossible to reconcile against either the Ontario LTT receipt or the Toronto MLTT receipt the closing package contains.

Toronto's MLTT bracket structure changed in 2024, and the change matters for any extraction touching high-value residential closings. The standard residential brackets rose to mirror the provincial ones at the lower end, and the city added luxury brackets above $3,000,000 that step up to 3.5% on the portion of consideration above $20,000,000. Extracting Toronto MLTT as a single number without preserving the bracket-allocation detail is no longer enough for the high-value end of the market, and any bookkeeper or CPA serving developers, foreign-purchaser entities, or family trusts on luxury Toronto closings has to confirm which bracket structure applied at the closing date. A 2023 closing and a 2025 closing on a $25,000,000 Toronto property produce materially different MLTT, and the extraction output should make that visible at the bracket level rather than burying it in a top-line total.

The first-time home buyer refund is a separate flag the extraction has to carry through. The Ontario refund is up to $4,000 of provincial LTT for qualifying first-time buyers, and the Toronto refund is up to $4,475 of municipal LTT. Both are claimed on closing and appear on the Trust Ledger as a credit against the gross tax. The extraction has to carry the gross provincial LTT, the gross MLTT, and the refund as three separate fields rather than a single net amount, so the bookkeeper or CPA recording the closing can decide where each component lands in the property's books and on the eventual capital-gain calculation.

The extraction prompt has to look in the right document for these fields. Provincial LTT and Toronto MLTT typically land on the Trust Ledger as disbursements, not on the Statement of Adjustments. A separate Land Transfer Tax statement (the Teraview prescribed-statement output) often accompanies the closing package as well, with the bracket allocation set out explicitly. Pointing the extraction at the SOA alone for Ontario LTT receipt extraction or for Toronto MLTT closing document extraction will return blanks; the prompt has to identify the Trust Ledger and the LTT statement as the source documents for the tax fields, with the SOA reserved for the proration adjustments.

Ontario property investors who close on a condominium have a connected extraction concern that begins on closing day and continues monthly: the Ontario condominium corporation accounts payable workflow is the recurring AP flow that follows from the same property ledger row this article is building.

British Columbia: PTT, Foreign Buyer Additional, and Exemption Flags

British Columbia's Property Transfer Tax sits at the field level on the same logic as Ontario but with different brackets and an extra layer for foreign buyers. The base PTT brackets are 1% on the first $200,000 of fair market value, 2% on the portion between $200,000 and $2,000,000, and 3% on the portion above $2,000,000. On residential property, a further 2% applies to the portion above $3,000,000, taking the effective top rate to 5% on the residential portion above that threshold. These brackets are the rate-allocation fields BC PTT closing cost extraction should preserve at line-item level. A single gross PTT number is sufficient for cash-flow accounting on closing day and useless for anything after that.

The Foreign Buyer Additional is a discrete second tax, not an adjustment to the base PTT. It applies an additional 20% PTT to residential transfers to foreign nationals, foreign entities, or taxable trustees in the specified regional districts — Greater Vancouver, Capital, Fraser Valley, Nanaimo, and Central Okanagan. In the extraction output it has to be a separate column. Folding it into a single PTT total destroys both the audit trail back to the underlying foreign-buyer determination and the foreign-buyer flag itself, which is information the property ledger needs for its own reasons even when the gross tax has already been paid.

BC's exemption regime is the third dimension the extraction has to carry. The first-time home buyer exemption gives a full PTT exemption on qualifying purchases up to $835,000 of fair market value, with proportional reduction up to $860,000 in the current schedule. The newly-built home exemption gives a full exemption on qualifying purchases up to $1,100,000, with proportional reduction up to $1,150,000. Other exemptions exist for related-party transfers, separation agreements, and certain trust transactions. None of these are amounts the extraction calculates; they are flags it carries through. Each is a discrete output column the bookkeeper later reconciles against the Adjusted Cost Base — the gross PTT that would have been due, the exemption claimed, and the resulting cash PTT paid all matter for different downstream uses, and an extraction that only returns the cash number can't support any of them.

BC PTT typically appears on the Trust Ledger as a single disbursement line, with the Property Transfer Tax Return (Form 17 series) carrying the rate-bracket detail and the exemption flag. Both can land in the closing package as separate documents, and the extraction prompt should be ready to draw the bracket allocation and the exemption flag from whichever document carries them — sometimes both, sometimes only the return form. For the foreign-buyer determination, the return form is the source of record; the Trust Ledger will show the additional 20% as a separate disbursement but the buyer-classification flag itself sits on the return.

The practical consequence is that a BC PTT extraction returning only the gross tax number is insufficient for any property ledger that has to survive past closing day. The property ledger needs the bracket allocation for the eventual capital-gain calculation, the Foreign Buyer Additional as a separate field for residency-status records, and each exemption flag as a column the ACB schedule can carry forward. The schema is wider than a single tax line.

Quebec: Welcome Tax, Montreal Brackets, and the Post-Closing Arrival

Quebec's transfer tax is structured differently from Ontario LTT or BC PTT in three ways that matter for extraction: it is a municipal tax, not a provincial one; it is calculated on the highest of three values rather than just the price; and it does not arrive with the closing-day documents. The tax is the taxe de bienvenue — Welcome Tax — formally the duties on transfers of immovables. It is levied by every municipality in Quebec under the provincial Act Respecting Duties on Transfers of Immovables, which sets the framework while leaving each municipality to set its own bracket structure within the limits the act allows. The tax applies to every immovable transfer registered in the Quebec land register.

The calculation basis is the highest of three inputs: the sale price agreed between the parties, the price stated in the deed of sale, and the municipal assessment-roll value of the property multiplied by the comparative factor for the year. The comparative factor adjusts the assessment-roll value for the lag between the assessment date and the transaction date — the assessment is set on a multi-year roll, the comparative factor brings it forward to the current year. For most arm's-length residential transactions the sale price is the highest of the three and the duties are calculated on that. For transactions at below-market consideration (related-party transfers, partial gifts, succession-driven sales), the assessment-times-comparative-factor figure is often higher, and the duties end up calculated on it instead. This three-input basis is what extraction has to record from the eventual Welcome Tax invoice. Collapsing to a single "purchase price" field misses how the duties were actually calculated and breaks the audit trail back to the municipality's calculation.

For Montreal closings, the bracket structure carries luxury rates that move the duties materially above the provincial baseline. Per Ville de Montréal's property transfer duties calculation rules, Montreal calculates property transfer duties on the highest of the selling price, the price stated in the deed of sale, or the municipal assessment roll value times the comparative factor, with bracketed rates rising to 4% above $3,113,000 for 2026, and the resulting duties are payable within 30 days of the billing date rather than on the closing day itself. That last clause is the differentiator the rest of the article is built around. The Statement of Adjustments closes the deal with no Welcome Tax line item on it. Weeks later — typically 30 to 60 days after the registration of the deed of sale — the municipality issues a separate invoice with its own due date, payable within 30 days of the billing date.

Treat the timing pattern as an extraction-and-bookkeeping consequence, not just a fact about Quebec. The Welcome Tax invoice has to be matched back to the property when it arrives, routed through the same extraction layer that handled the closing-day documents, and posted to the same property ledger row. The extraction output for the closing has to carry a property identifier — the lot number, the registration number, the property address — that survives into the post-closing documents so the Welcome Tax invoice can be matched against it later. A schema that doesn't carry that identifier turns the post-closing matching into a manual exercise the bookkeeper has to do by hand against a stack of invoices.

Other Quebec municipalities operate under the same framework with their own bracket structures. Quebec City, Laval, Gatineau, Longueuil, and the smaller municipalities each set rates within the bounds the provincial act allows. The general extraction model — separate post-closing invoice, highest-of calculation basis, 30-day post-billing payment window — applies across Quebec; only the brackets shift. A multi-property investor with closings in more than one Quebec municipality needs the bracket allocation as a per-municipality field rather than a single Quebec-wide rate.

---

HST on Closing Services as a Separate Extracted Field

Legal fees, title insurance, and (on the seller side) real estate commission are taxable services for HST purposes, and the HST charged on them has to come out of extraction as its own column rather than buried inside the line total. Bookkeepers reconciling input tax credits, accountants recording self-supply on a newly-acquired rental property, and CPAs filing rebate claims need the HST broken out per service line. A Trust Ledger that shows "Legal Fees - $2,825" with HST silently included is unworkable for any of those downstream uses; the same line shown as "Legal Fees - $2,500 / HST - $325" is what the extraction output should produce, and a robust prompt should pull the HST amount per service rather than a single closing-total HST.

Rate fragmentation across Canadian provinces is the other reason the HST field has to be discrete. Ontario charges HST at 13%, the Maritime provinces (New Brunswick, Newfoundland and Labrador, Nova Scotia, Prince Edward Island) at 15%. British Columbia and Alberta operate outside the harmonised system: BC charges 5% GST plus 7% PST on most services (with PST sometimes not applying to legal services depending on the nature of the matter), and Alberta charges 5% GST alone. Quebec collects QST alongside GST through Revenu Québec. A bookkeeper consolidating closings across provinces has to see the right tax type for each closing — collapsing all of them into a single "HST" column for an investor with Ontario and BC properties produces a worksheet that doesn't reconcile to either provincial filing. The extraction output should accommodate the rate column or carry the tax type explicitly so the breakdown survives consolidation.

The Trust Ledger typically itemises legal fees and the HST charged on them as separate disbursement lines. Title-insurance providers vary: some invoice HST as a separate line on the closing disbursement and some bundle it into the premium quoted, requiring the extraction to back-calculate the tax-included portion. Real estate commission on the seller side carries HST on the gross commission; on the Trust Ledger of a seller closing it appears as a substantial HST disbursement, often the largest single HST line in the closing package. Each of these has its own cleanest extraction shape, and the prompt should reflect that the documents inside the closing package don't all describe HST the same way.

For a rental-property investor, the HST on closing services is the start of an ongoing GST/HST workflow. New residential rental properties carry their own rebate regime — the New Residential Rental Property Rebate and the Public Service Bodies' Rebate where applicable — and the same investor faces ongoing extraction needs for operating invoices through the year. The closing-day HST data feeds that downstream workflow: GST/HST rental property invoice extraction for NRRP and PBRH rebates is the natural continuation for investors whose extraction needs run past closing day into ongoing rental operations.

For investors and bookkeepers whose extraction workflow reaches into operating invoices beyond closing — supplier invoices, contractor invoices, utility bills — the broader pattern of calculating GST/HST on Canadian invoices sits behind the same fragmentation question this section raised. The closing PDF set is one entry point into the same field-extraction problem; the closing services are taxable services for HST purposes, and treating them with a discrete HST column on every relevant line is what makes the closing data consolidate cleanly with the rest of the year's invoice extraction.

---

Output Schema: ACB Additions, Current-Period Expenses, and Information-Only Fields

Extraction produces a row, or a group of rows, per closing. Each output column has a typical destination in the property's books: the capital cost of the property (an Adjusted Cost Base addition that becomes part of the eventual capital-gain calculation), a deductible current-period expense (typically only on rental property, and often only when input tax credits are not available against the same line), or an information-only field that documents the closing without posting to a ledger account. Which destination applies to a given column depends on the property's facts — rental versus principal residence, HST registration status, mixed-use considerations — so the schema below sets out the typical pattern rather than ruling on any specific allocation. Treating the closing as ACB cost base extraction Canadian property means preserving every closing-cost field rather than collapsing to a single "closing costs" total, so the bookkeeper or CPA can apply the right allocation against the property's facts.

The columns below reflect the most common allocation pattern across Canadian residential real-estate closings. Borderline calls (mixed-use property, partial business use, rental conversion, properties that toggle between principal residence and rental within a calendar year, HST-registered owners with input tax credit posture) belong with a CPA who can review the specific facts. CRA Folio S3-F4-C1 is the authoritative Canada Revenue Agency framework on the cost of depreciable property and the related capital cost rules, and is the right reference for the unusual cases this guide does not rule on.

Field	Source Document	Typical Destination
Purchase price	Statement of Adjustments	ACB addition
Provincial LTT (Ontario) / PTT (BC) / Welcome Tax (Quebec)	Trust Ledger / LTT or PTT statement / Welcome Tax invoice	ACB addition
Toronto Municipal LTT	Trust Ledger / LTT statement	ACB addition
BC Foreign Buyer Additional	Trust Ledger / PTT return	ACB addition
Land registration and title-registration fees	Trust Ledger	ACB addition
Title insurance premium (excluding tax)	Trust Ledger / title insurance disbursement	ACB addition
Survey costs commissioned for the closing	Trust Ledger	ACB addition
Legal fees (acquisition portion, net of tax)	Trust Ledger	ACB addition (typical)
HST/QST/GST on legal fees	Trust Ledger	Current-period expense (rental, no ITC) or ACB addition (typical)
HST/QST/GST on title insurance and other closing services	Trust Ledger / title insurance disbursement	Current-period expense (rental, no ITC) or ACB addition (typical)
Interim mortgage interest, insurance binder fees	Trust Ledger / lender disbursement	Current-period expense (rental)
Deposit credit	Statement of Adjustments	Information-only (already in purchase price)
Prorated property-tax adjustment as of closing	Statement of Adjustments	Information-only (cash settlement)
Prorated utility / fuel oil / common-expense adjustments	Statement of Adjustments	Information-only (cash settlements)
First-time buyer refund / exemption flags	LTT statement / PTT return	Information-only flags
Foreign-buyer flag and resident-status determination	PTT return	Information-only flag
Property identifier (lot, registration number, address)	Statement of Adjustments / Trust Ledger / deed of sale	Information-only (post-closing matching key)
Source PDF reference and page reference	Every output row	Information-only (audit trail)

Two notes on the schema. First, the current-period expense destination applies only when the property is held for rental use and the owner is not entitled to claim input tax credits on the relevant tax — for a principal residence, the closing costs are a personal expense and the residence is not on a property ledger that tracks ACB for capital-gain purposes (the principal residence exemption usually applies); for an HST-registered owner with full ITC entitlement, the HST is recoverable rather than a current-period expense. Second, the schema is the spine of the extraction prompt. Every column above corresponds to a named field the prompt asks the AI to produce, and the prompt examples that follow in the next section are the operational expression of this column structure given to the extraction layer.

Prompt Examples for Canadian Closing-Document Batches

A batch of closing-day PDFs — Statements of Adjustments, Trust Ledgers, LTT or PTT receipts, and Welcome Tax invoices arriving later — goes into the extraction tool with a single prompt that describes the output schema. The prompt is the configuration. There is no template to set up, no rules engine to wire, no per-firm mapping to maintain. The same prompt applies whether the batch is ten closings from one law firm or a thousand closings spread across firms and provinces, and the schema column structure from the previous section is what the prompt asks the AI to produce.

A single-province Ontario batch is the clearest place to start. The prompt below extracts an Ontario closing package — Statement of Adjustments plus Trust Ledger plus the Land Transfer Tax statement — into a single normalised row per closing:

I'm processing Ontario residential real-estate closings. The PDFs in this batch are Statements of Adjustments, Trust Ledgers, and Land Transfer Tax statements from multiple law firms.

Group all documents for the same closing together by file name, address, or registration number, and produce one row per closing with these columns:

Closing Date, Property Address, Vendor, Purchaser, Purchase Price, Deposit Credit, Prorated Property Tax Adjustment, Prorated Utilities Adjustment, Provincial LTT, Toronto MLTT (zero if outside Toronto), First-Time Buyer Refund Flag (Yes/No), First-Time Buyer Refund Amount, Legal Fees Net, HST on Legal Fees, Title Insurance Net, HST on Title Insurance, Registration Fees, Other Disbursements, Source File Reference.

If a field is absent from the documents, set the value to 0 rather than blank. Format all amounts as numbers to 2 decimal places. Format dates as YYYY-MM-DD. For the Source File Reference, include the file name and page numbers for the SOA, the Trust Ledger, and the LTT statement.

The prompt names the document types it should expect, names the columns from the schema, instructs the AI to look in the right document for each field (the LTT statement and Trust Ledger for the tax fields, the SOA for the proration adjustments), specifies how to handle absent fields, and asks for the source-file reference on every row. This is the workflow that turns a folder of mixed Ontario closings into a usable property ledger across the year. To automate Canadian closing-document extraction for a recurring book of investor or developer clients, this is the prompt structure that scales — saved once, applied to every new batch as it arrives.

For a multi-province batch where Ontario, BC, and Quebec closings sit in the same folder, the prompt has to detect the province from the document and apply the right schema variations rather than producing a wrong-shape row for any province:

I'm processing Canadian residential real-estate closings across Ontario, British Columbia, and Quebec. The PDFs in this batch are Statements of Adjustments, Trust Ledgers, provincial LTT/PTT/Welcome Tax statements, and law firm reporting letters from multiple firms.

Identify the province for each closing from the document content (lawyer's address, provincial tax type, registration system, currency formatting). Group all documents for the same closing together and produce one row per closing.

For all rows, include: Closing Date, Province, Property Address, Vendor, Purchaser, Purchase Price, Deposit Credit, Prorated Property Tax Adjustment, Prorated Utilities Adjustment, Legal Fees Net, HST or QST on Legal Fees, Tax Type on Legal Fees (HST/GST+PST/GST+QST/GST), Title Insurance Net, Tax on Title Insurance, Registration Fees, Source File Reference.

For Ontario rows, also include: Provincial LTT, Toronto MLTT (zero if outside Toronto), First-Time Buyer Refund Amount.

For BC rows, also include: BC PTT (Base), Foreign Buyer Additional (zero if not applicable), Foreign Buyer Flag (Yes/No), First-Time Home Buyer Exemption Flag (Yes/No), Newly-Built Home Exemption Flag (Yes/No).

For Quebec rows, also include: Welcome Tax Invoice Received Flag (Yes/No - usually No on closing day), Municipality, Municipal Assessment Roll Value, Comparative Factor (if shown), Welcome Tax Calculation Basis (Sale Price / Deed Price / Assessment x Comparative Factor).

Set absent fields to 0 for amounts, blank for flags. Format amounts to 2 decimal places. Format dates as YYYY-MM-DD.

This prompt is doing more work — province detection, conditional column population, the province-specific flags — and the AI follows the structure rather than the specific phrasing. The point is that one prompt covers the multi-province workflow rather than three separate jobs that have to be reconciled later.

The post-closing tail is where the third prompt comes in. Welcome Tax invoices arrive weeks after closing, municipal property-tax true-up invoices arrive at year end, and supplementary assessment notices can arrive months later. The extraction has to match each new document to the property the closing established:

I'm processing post-closing tax notices for Canadian properties already in my ledger. The PDFs in this batch are Quebec municipal Welcome Tax invoices, Ontario and BC municipal property-tax bills, and supplementary or omitted assessment notices.

For each document, extract: Document Type (Welcome Tax / Property Tax Bill / Supplementary Assessment), Municipality, Property Address, Roll Number or Registration Number, Tax Year or Period, Amount Due, Due Date, Payment Window (in days from billing date if stated), and a Property Identifier field that captures the address, lot, or registration number cleanly enough to match against my closing ledger.

For Welcome Tax invoices specifically, also extract: Calculation Basis (Sale Price / Deed Price / Assessment x Comparative Factor), and the Bracket Allocation showing how much of the duties came from each rate bracket if the municipality discloses that on the invoice.

Format amounts to 2 decimal places, dates as YYYY-MM-DD, and include the source-file reference and page number on each row.

These three prompt shapes — single-province batch, multi-province batch, post-closing tail — cover the working life of a property ledger. Each prompt can be saved and reapplied; each can be adjusted for the specific firms or municipalities a particular bookkeeping book sees most often; each produces Canadian closing documents to Excel in the format the property ledger consumes. Invoice Data Extraction handles closing-document batches as PDF, JPG, or PNG inputs and returns Excel, CSV, or JSON output with a source-file-and-page reference on every row, so the ledger stays auditable against the original closing PDFs months or years after the closing date.

---

Post-Closing Reconciliation: The Tail After Closing Day

The Statement of Adjustments and Trust Ledger record what was known on closing day. The post-closing tail records what becomes known afterward, and a property ledger that stops at the closing-day documents will be wrong by the end of the year for any Quebec property and for many Ontario or BC properties where the prorated property-tax adjustment doesn't match the eventual municipal levy. Closing day is the start of the data set for a Canadian acquisition, not the end of it.

The Quebec Welcome Tax invoice is the most consequential case because it is the largest single post-closing line and the timing is predictable. Thirty to sixty days after the registration of the deed of sale, the municipality issues a separate mutation-duties invoice payable within 30 days of the billing date. The extraction workflow has to ingest that invoice when it arrives, match it to the property the closing established (by registration number, lot, or address), and post the duties to the same property ledger row. There is no Welcome Tax line on the closing-day SOA to reconcile against; the entire amount is new information arriving at the property ledger weeks after closing day. Bookkeepers waiting for the closing package to be "complete" before recording the acquisition will end up booking a partial entry first and amending it later — a reasonable workflow only if the post-closing invoice is treated as a continuation of the same extraction job rather than a separate manual exercise.

Municipal property-tax true-ups are the second post-closing case, and they apply across provinces. The SOA prorates the property tax based on the seller's provisional payment to the municipality as of the closing date — usually a payment-on-account or interim-bill amount rather than the full annual levy. When the municipality later issues the actual annual levy, the buyer's bookkeeper has to compare the proration-as-of-closing against the actual full-year amount and recognise any over- or under-credit at year end. For Ontario closings, this typically falls out as a small variance against the prorated adjustment on the SOA. For municipalities where the interim bill was materially different from the final levy, the variance is large enough to matter for the rental P&L. The extraction layer that read the SOA on closing day is the same one that should read the eventual annual property-tax bill, with the two records reconciling against each other on the same property identifier.

Supplementary and omitted assessment notices are the third case and the most variable in timing. Provincial assessment authorities (MPAC in Ontario, BC Assessment, Quebec municipal assessment rolls) periodically reassess properties — typically after construction, additions, or use changes — and can issue supplementary or omitted assessment notices that retroactively adjust the property's assessed value. The municipality then issues retroactive municipal property-tax invoices on the new assessed value, sometimes for a closing-day period that has already been booked. These invoices can arrive months or years post-closing. The extraction workflow should match each supplementary or omitted notice against the property identifier from the closing and route the resulting tax adjustment to the right tax year on the property ledger.

The post-closing tail is not a separate document set or a separate process. It is the same connected document set the article has built around, extended in time. The Statement of Adjustments and the Trust Ledger establish the property identifier, the closing date, and the closing-day allocation between ACB and current-period expense. The post-closing documents — Welcome Tax invoices, annual property-tax bills, supplementary or omitted assessment notices, and the operating-period invoices that follow — flow into the same property ledger row when the extraction layer carries the property identifier through. Treating the closing as the start of the property ledger rather than the end of an isolated transaction is what produces a ledger that still holds up at year end, at the eventual sale, and on the resulting capital-gain calculation.