Australian Strata AP: Admin vs Capital Works Fund Coding

Every supplier invoice that lands in an Australian strata manager's inbox carries two questions before it can post: which scheme does it belong to, and which fund within that scheme pays for it. Australian strata supplier invoice admin vs capital works fund coding is the harder half of that pair, and miscoding remains one of the most common findings strata auditors raise at the annual audit.

The split is consistent in shape across the country and inconsistent in name. Recurring operating costs — strata or body corporate manager fees, building insurance premiums, common-area utilities, recurring fire compliance, recurring cleaning and gardening — sit in the administrative fund in NSW and QLD, or the general fund in VIC. Planned long-cycle capital expenditure — roof replacement, lift overhaul, façade restoration, structural repairs — sits in the capital works fund in NSW under the Strata Schemes Management Act 2015 sections 74 to 76, the sinking fund in QLD under the Body Corporate and Community Management Act 1997, and the maintenance plan fund in VIC under the Owners Corporations Act 2006. WA, SA, TAS, ACT and NT each carry their own act and their own nomenclature; the spine of this guide stays on NSW, QLD and VIC where the bulk of Australian strata stock sits.

The reason both questions matter on every invoice is the operating reality of the work. A single fire-compliance contractor services dozens of schemes managed by the same firm. The insurance broker places cover on hundreds. The lift-service company runs quarterly tests across half the portfolio. Every invoice that arrives has to land in the correct scheme's ledger under the correct fund before it can be paid, approved, or audited — and most invoices reference the building in free text rather than the canonical scheme number the manager keeps the books under.

What follows walks the practitioner workflow inside the strata manager's office: scheme-reference resolution from free-text supplier references to canonical scheme numbers; the state-specific fund-coding decision under SSMA 2015, BCCM 1997, and the OC Act 2006; the chart-of-accounts coding that sits inside the chosen fund; the tax-invoice and ABN validity gate that protects the input tax credit; the scheme-specific committee approval threshold flag; and the structured row each invoice needs to produce to load cleanly into StrataMax, MRI StrataMaster, MYBOS, or BCMax. This is not a generic AP automation piece, and it is not an owner- or committee-side fund-rule explainer; it is the per-invoice routing decision the AP queue runs hundreds of times a day. Readers operating across jurisdictions may also want the cross-Pacific sibling on BC strata corporation supplier invoice processing under BCFSA, which walks the same workflow under different statute and a different platform stack.

Mapping invoice to scheme: the reference-resolution problem

Before a single fund-coding decision can run, the inbound invoice has to be tied to a scheme. This is the part of the workflow most software glosses over and most strata managers spend the most manual time on, because the supplier-side reference is almost never the one the manager's books are kept under.

What suppliers actually print on the invoice is a mix of whatever they were given when the work was booked and whatever fits in their accounting system's address line. Street addresses ("Apt 12 / 45 Smith St"). Strata plan numbers (SP 12345) for NSW. Community titles scheme numbers (BCS 67890 or CTS 67890) for QLD. Plan of subdivision references for VIC. The trading name of the body corporate or owners corporation, sometimes abbreviated, sometimes mistyped. None of these reliably match the canonical scheme identifier the manager keeps the books under, and the AP system has to normalise before posting.

The canonical identifier shifts by state. NSW strata schemes are keyed on the strata plan number, conventionally written as SP followed by the registered plan number. QLD bodies corporate are keyed on the community titles scheme number, usually with a BCS or CTS prefix in the management software depending on platform vintage. VIC owners corporations are keyed on the plan of subdivision under the Owners Corporations Act 2006. The reference-resolution step turns whatever the supplier printed into the canonical identifier and posts against that.

The case that breaks naive matching is the consolidated invoice. A fire-compliance contractor running quarterly tests across thirty buildings produces one invoice with thirty line groups, each line group referencing a different building. An insurance broker placing a multi-scheme cover produces one invoice covering twenty schemes. A lift-service company running scheduled servicing across the portfolio bills the lot together. The AP system has to split that one invoice into per-scheme rows so each scheme's ledger sees only the lines that belong to it — and each split row goes through its own fund-coding decision downstream. A consolidated invoice that is not split is a consolidated audit problem at year-end.

Resolution accuracy is bounded by the manager's own scheme master. The lookup runs against the master record in StrataMax, MRI StrataMaster, MYBOS or BCMax, which carries the canonical scheme number, the registered trading name, the registered address, and any aliases the manager has captured over time. A scheme that the supplier consistently writes as "The Quay Apartments" but that the master holds as "SP 54321 — Quay Residences" needs the alias added to resolve cleanly; a scheme keyed only on plan number cannot be matched from a supplier reference that uses only the trading name. Master-data hygiene is the upstream lever on resolution accuracy — invest there once and the AP queue runs cleaner indefinitely.

When confidence is low, the right answer is not a guess. An unresolved or low-confidence reference goes to a manual review queue rather than auto-posting to a default scheme; the manager either updates the scheme master to add the missing alias (so the next invoice from this supplier resolves automatically) or queries the supplier for the correct identifier. The cost of routing one invoice to the wrong scheme is far higher than the cost of a manual review touch, because the audit trail follows the original posting.

There is one related-document touchpoint that pays back into this stage. When a unit changes hands, the disclosure certificate at sale carries the canonical scheme reference, the registered scheme name, and the strata plan or plan of subdivision number — all the fields the AP scheme-master needs to maintain. Firms already running Australian strata disclosure certificates across NSW s184, VIC s151 and QLD Form 33 through a structured extraction pipeline have the master-data side of resolution running on the same rails, which keeps both workflows pointed at the same canonical identifiers.

NSW: administrative fund vs capital works fund under SSMA 2015

For a scheme registered under the Strata Schemes Management Act 2015, section 74 establishes that the owners corporation must keep an administrative fund and a capital works fund. The only carve-out is the two-lot scheme exception, which allows a scheme of just two lots to resolve unanimously to operate without a capital works fund — for the rest of the NSW portfolio, the two-fund split is mandatory and every invoice has to land on one side of it. Sections 75 and 76 set out the purposes for which each fund may be applied.

The administrative fund pays for the recurring operating expenses of running the scheme. In practice, that includes the strata manager's fee, accountant and audit fees, building insurance premiums, common-area utilities (electricity, gas, water), recurring fire compliance — fire-detection-system testing, exit-light maintenance, fire-door inspection, sprinkler servicing — recurring cleaning and gardening, recurring lift maintenance, security monitoring, and the minor and recurring repairs that fall short of capital works. ASIC fees attached to the administrative function and the GST liability tied to admin-side activity sit here too. The defining property is recurrence: these are the costs the scheme incurs to operate the common property month after month, regardless of capital condition.

The capital works fund pays for planned medium- to long-term capital expenditure on the common property. Roof replacement. Lift overhaul or replacement. Façade restoration. Structural repairs. Plant replacement (HVAC, generators, pumps). Large painting cycles when scheduled in the long-horizon plan. Building-defect rectification works funded outside any defects bond. The test on each invoice is whether the work is recurring operating maintenance — admin fund — or planned long-cycle replacement, restoration, or upgrade of common-property components — capital works fund.

The 10-year capital works fund plan is the planning artefact every capital-side coding decision has to reconcile back into. Under SSMA 2015 the owners corporation is required to prepare a 10-year plan that anticipates the major capital works the scheme will fund through the capital works fund and the contributions required to support it. In day-to-day AP terms, every invoice coded to the capital works fund should map to a planned line in the current 10-year plan; an unplanned capital works invoice is a signal that the plan needs revision, not a signal that the invoice should be coded silently and the plan ignored. From 1 April 2026, NSW strata schemes must use a mandatory standard form issued by NSW Fair Trading when preparing or revising the 10-year capital works fund plan, per the NSW Government's guide to strata law changes for committees and owners. For managers, the practical effect is that capital-side coding from that date forward feeds a plan in a uniform format across every NSW scheme they manage, which makes the cross-scheme reconciliation cleaner but also makes any drift between actual capital spend and planned capital spend more visible at audit.

The contribution side of the same machine is the levy run that funds both the administrative and capital works funds — owners pay separate levies into each fund, and the administrative-fund and capital-works-fund balances on the scheme's books reconcile to the levies received less the AP postings on each side. Firms already extracting NSW strata levy notices into a working spreadsheet on the contribution side benefit from the same fund-tagging discipline running on the AP side; the two halves close cleanly when both posting streams use the same fund vocabulary.

One miscoding source worth flagging explicitly: SSMA 2015 allows a scheme to establish a special-purpose fund by special resolution for a specific project — typically a major works programme funded outside the regular capital works fund cycle, often through a special levy. Invoices for that project code to the special-purpose fund, not the capital works fund and not the administrative fund. Letting them slide into capital works because the work looks capital in nature is a frequent audit-finding source; the AP system has to recognise the special-purpose fund as a third destination for the schemes that have one.

QLD: administrative fund vs sinking fund under BCCM 1997

Queensland community titles schemes operate under the Body Corporate and Community Management Act 1997. The legal entity is the body corporate, not the owners corporation, and the fund structure differs from NSW in name and in the planning artefact behind it. Each body corporate must keep an administrative fund and a sinking fund. The detailed rules sit in the relevant module regulation — the Standard Module, Accommodation Module, Commercial Module, Small Schemes Module, or Specified Two-lot Schemes Module — with most invoice-volume schemes operating under the Standard Module or the Accommodation Module. QLD body corporate sinking fund vs admin fund invoice coding is therefore a module-aware decision; the two-fund shape is universal but the surrounding obligations vary by which module the scheme sits under.

The administrative fund covers the recurring operating expenses of running the body corporate. That includes the manager's fees, accountant and audit fees, common-area utilities, recurring fire compliance, recurring cleaning and gardening, security, recurring lift maintenance, minor recurring repairs, and the body corporate's mandatory insurance premiums. Insurance is worth singling out in the QLD context: BCCM imposes mandatory insurance obligations on bodies corporate (building insurance for the common property, public risk insurance, and certain other covers depending on the scheme type), and those premiums always sit in the administrative fund. There is no construction under which a sinking-fund coding for an insurance premium reads correctly under BCCM.

The sinking fund pays for planned long-cycle capital expenditure on the common property — major repairs, replacement of common-property assets such as lifts, roofs, and major plant items, planned painting cycles, and façade and structural works. The category test is the same in shape as the NSW test: recurring operating maintenance to admin, planned long-cycle replacement and major repair to sinking. The difference is the planning artefact behind the sinking fund.

Under the Standard Module (and analogous provisions in the other modules), the body corporate is required to maintain a 9- to 10-year sinking fund forecast that anticipates the major capital expenditure expected over that horizon and the contributions required to fund it. Sinking-side coding feeds that forecast directly. Every invoice coded to the sinking fund should reconcile back to a planned line in the current forecast; unplanned sinking-fund expenditure means the forecast is out of date and needs revision, not that the invoice should be coded silently and the forecast left alone. The sinking fund forecast is a budget-rule artefact, and miscoded sinking-side expenditure breaches the forecast assumption that sat behind the levy contributions the body corporate set for the year.

The audit consequence in QLD is concrete enough to motivate the discipline. Strata auditors check fund-allocation accuracy as part of the annual audit, and admin-versus-sinking miscoding is one of the more common findings raised — in particular, recurring maintenance items inadvertently coded to sinking (because the work touched a major asset) and capital replacement items coded to admin (because the invoice fitted into a recurring service contract). The cleanest way to keep audit findings off the schedule is to make the fund decision deliberately at posting rather than at year-end clean-up.

The contribution side of the same flow is the body corporate's contribution notice, which carries the levy split across the administrative and sinking funds. Firms running QLD body corporate contribution notice extraction to Excel on the contribution side and the same fund-tagging on the AP side close the loop neatly: administrative-fund contributions in, administrative-fund AP postings out, balance reconciles; sinking-fund contributions in, sinking-fund AP postings out, balance reconciles back into the 9- to 10-year forecast.

VIC: general fund vs maintenance plan fund under the OC Act 2006

Victorian owners corporations sit under the Owners Corporations Act 2006 and the Owners Corporations Regulations 2018. The OC Act framework introduces a distinction NSW and QLD readers do not have to think about: not every VIC owners corporation has a maintenance plan fund, and the AP workflow has to branch on tier classification before it branches on category. Getting VIC owners corporation general fund vs maintenance plan fund coding right starts with knowing which tier the scheme falls into.

Every owners corporation maintains a general fund — colloquially called the maintenance fund in everyday strata conversation — which covers the recurring administrative and maintenance expenses of the common property. This is the OC Act analogue of the NSW administrative fund and the QLD administrative fund, and it carries the same recurring-operating-cost set: manager fees, accountant and audit fees, building insurance, common-area utilities, recurring fire compliance, recurring cleaning and gardening, recurring lift maintenance, security, and minor recurring repairs.

Under the OC Act and the OC Regulations 2018, tier 1 and tier 2 owners corporations are also required to prepare a maintenance plan covering anticipated major maintenance and replacement works on the common property, and to maintain a maintenance plan fund to implement that plan. The tier classification is set by the regulations on the basis of lot count and other prescribed factors: tier 1 covers owners corporations with more than 100 occupiable lots and carries the most stringent obligations; tier 2 covers 51 to 100 occupiable lots; tier 3, 10 to 50; tier 4, fewer than 10; and tier 5 covers services-only owners corporations and other small or limited-purpose schemes. The maintenance plan and maintenance plan fund obligation falls on tier 1 and tier 2 owners corporations only. Tier 3, 4, and 5 owners corporations may adopt a maintenance plan voluntarily but are not required to, and many do not. The practical AP-workflow consequence is direct: for tier 1 and tier 2 owners corporations the fund-coding decision runs the same two-fund branch as NSW and QLD, with the maintenance plan acting as the long-horizon planning artefact equivalent to the NSW 10-year plan or the QLD sinking fund forecast. For owners corporations in the lower tiers without a maintenance plan fund, every invoice codes to the general fund, and the manager records the capital nature of any major-works invoice in the chart-of-accounts coding inside the general fund rather than in fund tagging.

The maintenance plan fund pays for planned long-cycle capital and major-maintenance expenditure that the maintenance plan itself anticipates: planned painting cycles, plant replacement, major lift works, façade and roof works, and structural and waterproofing replacements. As with the NSW capital works fund and the QLD sinking fund, the discipline is that maintenance-plan-fund-coded invoices reconcile back to planned lines in the current maintenance plan; unplanned major-maintenance expenditure means the plan is due for revision.

The terminology trap to watch in VIC is that "maintenance fund" in everyday strata-manager conversation almost always means the general fund, because maintenance is the largest category of general-fund spend. It very rarely means the maintenance plan fund. When the AP system is configured (and when the manager is briefing offshore or junior staff), this needs explicit disambiguation — coding an invoice to "maintenance fund" without specifying whether that means general fund or maintenance plan fund is a slow-burning miscoding that does not surface until the year-end audit.

The contribution side of the VIC machine is the owners corporation fee notice, which carries the contributions to both the general fund and (for tier 1 and tier 2 schemes) the maintenance plan fund. Firms already running Victorian owners corporation fee notices to a spreadsheet on the contribution side and the same fund-tagging on the AP side reconcile each fund's balance cleanly across both flows.

The category test and the chart-of-accounts code inside the fund

The three preceding sections each instantiate the same underlying test under a different statute. The test on each invoice is whether the expenditure is for the day-to-day administration and recurring maintenance of common property — admin or general fund — or for medium- to long-term planned capital replacement, restoration, or structural work — capital works in NSW, sinking in QLD, maintenance plan in VIC. Once the fund is fixed, the second decision is the chart-of-accounts code inside that fund.

Some categories sit unambiguously on the admin or general side regardless of state. Building insurance premiums always code to the admin or general fund — capital works funds, sinking funds, and maintenance plan funds in every state are restricted to capital and major-maintenance use and cannot pay insurance, regardless of whether the policy is for the building structure or for liability. Strata or body corporate manager fees, accountant and audit fees, tax-agent fees, recurring fire-compliance contracts (annual fire-detection-system testing, monthly exit-light testing, fire-door inspection, sprinkler servicing), recurring cleaning, recurring gardening, security monitoring, common-area utilities (electricity, gas, water), minor recurring repairs and call-outs, recurring lift maintenance, and legal fees attached to administration of the common property all sit on the same side. The shared property is recurrence at relatively low unit cost.

Other categories sit unambiguously on the capital side. Roof replacement. Façade restoration. Painting cycles when scheduled in the long-horizon plan. Lift overhaul or replacement. Plant replacement — HVAC, generators, pumps, hot-water systems at end of life. Structural and waterproofing repairs. Building-defect rectification works that fall outside any defects bond. Other works specifically planned in the NSW 10-year plan, the QLD sinking fund forecast, or the VIC maintenance plan. The shared property is planned, long-cycle, and material in unit cost.

The borderline cases are where the AP system has to escalate rather than guess.

• Large planned painting cycles — often capital, because the work is long-cycle and costed into the long-horizon plan, but sometimes coded to admin or general where the scheme's by-laws treat painting as recurring maintenance. The decision rests on the scheme's by-laws and the current plan, not on a universal rule.
• Mid-cycle plant overhauls that extend asset life rather than replace the asset — capital where they materially extend life beyond the next replacement cycle, admin where they are routine servicing of a degrading but operational asset.
• Hybrid maintenance-plus-replacement projects where one invoice covers some recurring service work and some component replacement — typically split across the two funds at line level, not coded as a single fund decision.
• Remediation works funded partly through a special levy — the special-levy portion codes to the special-purpose fund or to the capital works / sinking / maintenance plan fund per the levy resolution, while any non-special-levy-funded remediation portion follows the standard test.

When the fund and category are not unambiguous on the face of the invoice, the AP system flags the invoice for manager review with the candidate options surfaced, rather than picking a default. A five-minute review touch at posting is far cheaper than a clean-up at year-end.

Inside the fund, the chart-of-accounts code lands on a specific category line. The categories the AP system generally has to recognise are:

• Cleaning — common-area cleaning contracts, plus ad-hoc cleans.
• Gardening — landscaping and grounds maintenance.
• Fire Compliance — usually broken into Fire Detection, Exit Lights, Fire Doors, and Sprinklers as separate sub-codes for the annual compliance trail.
• Security — monitoring, patrol, and access-control servicing.
• Plumbing and Electrical — recurring repairs and call-outs.
• Lift Maintenance — scheduled servicing and inspection contracts.
• Common Area Electricity, Common Area Gas, Common Area Water — the three utility splits.
• Building Insurance and Insurance Excess — both to admin or general fund.
• Audit Fees, Tax Agent Fees, and Legal Fees — the professional-services lines.
• Special-Levy Capital Project — the project-specific code that sits inside the capital works, sinking, maintenance plan, or special-purpose fund as appropriate.

The strata or body corporate manager's own fee is typically not invoiced through the supplier-invoice AP run at all — it is the manager's own charge to the scheme, posted through a separate journal. AP-side processing applies to third-party suppliers; the manager fee belongs to a different posting stream.

One scheme-class footnote: NSW two-lot schemes that have unanimously resolved out of the capital works fund under SSMA 2015 section 74 collapse the entire workflow to admin-only coding. For those schemes the borderline rules around capital allocation simply do not apply, because there is no capital works fund to code into. None of this guidance, and none of the workflow that follows, constitutes tax or legal advice — schemes facing unusual configurations (special-purpose funds, building-defect levy interactions, mixed-use schemes, layered schemes) should consult a registered strata auditor or strata lawyer.

Pre-payment validation: tax invoice, ABN, and the committee-approval threshold

Two further gates have to clear before any invoice posts to payment. Both are fast, both are mechanical, and both have a real cost when they fail unnoticed.

Most non-trivial Australian strata schemes are GST-registered. Levy or contribution income for any scheme of meaningful size exceeds the registration threshold, and once a body corporate or owners corporation is registered for GST it can claim the input tax credit on supplier invoices that fund the common property. The catch is that the input tax credit only applies to a valid tax invoice under ATO rules, which is what the first gate enforces. That makes tax invoice ABN validation a strata AP gate with real money attached: every invalid tax invoice paid through is, in practice, a forgone input tax credit, and the cost compounds across thousands of invoices a year.

The validity check covers a defined set of fields:

• The supplier's name.
• The supplier's ABN.
• The words "tax invoice" stated on the document.
• The date of issue.
• The buyer's identity (the body corporate or owners corporation), required where the invoice is over the ATO's threshold for buyer details.
• A brief description of the goods or services supplied.
• The GST amount payable, or a statement that the total includes GST where the GST amount is calculable from the total.
• A clear total.

An invoice missing any of those fields is not a valid tax invoice; the GST line cannot be claimed as an input tax credit until the supplier issues a corrected document. The AP system flags the failure and queues the invoice for a supplier query, rather than paying through and reconciling later — once the payment has gone out the door, the simplest path to recovering an over-claimed credit is a BAS amendment, which is a far heavier remediation than a same-week supplier email.

The ABN side runs alongside. The supplier's ABN is checked against ABN Lookup or an automated equivalent for current registration and current GST status. An ABN that is invalid, cancelled, or registered without GST status when the invoice is charging GST changes the AP outcome — either the invoice is queried back to the supplier for a corrected document, or the line is treated as not eligible for input tax credit and the coding adjusted accordingly. ABN validation is also the moment to catch the rarer but more consequential case where a small contractor is operating without an ABN and the no-ABN withholding rules apply; the AP system has to surface that condition explicitly rather than assume registration.

The second gate is the scheme-specific committee approval threshold. Every scheme has a by-law or module-default spending threshold above which expenditure requires committee approval, and a higher general-meeting threshold above which it requires the body corporate or owners corporation as a whole. The thresholds vary scheme by scheme — a tightly-managed inner-city scheme may set a five-figure committee threshold, while a smaller suburban scheme may default to the standard module's lower figure. Where the scheme's by-laws are silent, the relevant state's standard module or default rule applies. The committee spending threshold is a strata invoice approval flag that has to be evaluated on every invoice before it posts to payment.

Mechanically, the AP system pulls the scheme-specific threshold from the scheme master and compares it against the invoice's net or gross amount (depending on how the scheme's by-law is written). Invoices below the threshold post and pay on the manager's standard delegation; invoices above the threshold are flagged for committee routing and held in an approval queue rather than auto-paid. The approval pathway varies by scheme — circular resolution by email, formal committee meeting, or general meeting depending on which threshold is breached and what the by-laws prescribe — and the AP system records the approval reference against the invoice when it does post.

There is one common interaction the threshold gate has to handle correctly. A capital-works-coded invoice funded out of a special levy has, in effect, already been approved at the general meeting that struck the levy. Routing every line of that project through a fresh committee approval cycle wastes everyone's time and clogs the queue. The system routes those invoices against the special-levy resolution rather than against the routine-expenditure threshold — same gate, different reference. Schemes facing genuinely unusual configurations on either side of these gates (mixed-use schemes, layered schemes, building-defect levy interactions, special-purpose funds) sit outside the standard workflow and warrant a registered strata auditor or strata lawyer's input rather than an automation rule.

Multi-scheme portfolio consolidation: the vendor-management view

The per-scheme ledger is the view that goes to each scheme's committee at the annual general meeting. It is not the view that helps the strata manager renegotiate the cleaning contract that runs across forty buildings. Multi-scheme supplier invoice portfolio consolidation is the second cut of the same data, aimed at the firm's own procurement, finance, and vendor-management functions rather than at the schemes the firm acts for.

The dual-cut requirement is structural. Each scheme's committee is interested only in the spend on its own scheme — the line items, the vendors, the budget variance. The manager's procurement function is interested in the total spend with each vendor across the whole portfolio, because that is where rate negotiation, vendor consolidation, and supplier-performance review actually happen. Both views have to come out of the same posted data; the difference is how it is filtered and aggregated.

The portfolio cuts that pay back across a sizeable book are concrete:

• Total spend with each cleaner across the portfolio. Useful for vendor consolidation conversations and for rate negotiation when one cleaner services thirty schemes at thirty separate contracts.
• Total fire-compliance spend by supplier across the portfolio. Useful for the annual procurement review — fire compliance is a category where one or two suppliers often dominate firm-wide volume.
• Total insurance premium spend by broker, by underwriter, and by scheme. Useful for broker review and for insurance-tender preparation.
• Total lift-maintenance spend by contractor. Useful when the firm is reviewing whether to consolidate lift servicing across a regionally clustered subset of schemes.
• Total recurring electrical and plumbing spend by trade. Useful for the smaller-trades vendor list, where consolidation often saves more in administrative cost than in headline rate.

These cuts only work if the supplier master is clean. The same trading entity coded under three different supplier records across three schemes — once with the trading name, once with the legal name, once with a typo — produces a fragmented portfolio view that systematically understates spend with that supplier. The structured row carrying the supplier's ABN as a stable key alongside the supplier name is what bridges the gap. Two records with different name strings but the same ABN merge cleanly at the portfolio level; two records with the same name string but different ABNs are flagged as a master-data hygiene issue that needs cleaning.

There is a second portfolio cut on the fund side that is less obvious but useful at scale. Capital-works spend across the portfolio — the total of capital works fund, sinking fund, and maintenance plan fund coding across every scheme the firm manages — is itself a meaningful aggregate. It supports benchmarking long-cycle replacement programmes across structurally similar buildings (two thirty-year-old high-rises in the same suburb should not be running radically different roof-replacement budgets without a reason) and it forecasts the firm's own workload around major capital projects, where two or three large lift overhauls landing in the same quarter changes the manager's resourcing for that quarter.

This article stops at the per-invoice fund-coding decision and the structured row that carries it. The wider apparatus around it — committee approval mechanics, trust-account discipline, the per-scheme close at year-end, the manager-level reporting cadence — is the territory of the multi-scheme supplier invoice AP workflow for strata and body corporate firms, which sits alongside this guide as the workflow companion.

The structured row that loads into StrataMax, StrataMaster, MYBOS or BCMax

The output of every preceding decision is a single structured row per billable line, ready to import into the manager's chosen platform. The row carries a defined field set:

• Scheme reference — the canonical scheme number from the manager's scheme master.
• Supplier name and supplier ABN — both required; ABN is the stable key for portfolio consolidation.
• Invoice number and invoice date.
• Due date where present on the document.
• Line description — verbatim from the invoice, not a normalised category.
• Line net amount, GST amount, and line gross amount.
• Fund-type tag — one of Administrative, Capital Works, Sinking, Maintenance Plan, General, or Special Purpose.
• Suggested chart-of-accounts code — the category line inside the fund.
• Approval-threshold flag — Below or Above the scheme-specific committee threshold.
• Source-file reference and page number — for audit traceability back to the original PDF.

Each row corresponds to one billable line on one invoice for one scheme. Multi-scheme consolidated invoices produce multiple rows from one source file. Multi-line invoices produce multiple rows from one invoice. Each row is independently coded and independently auditable.

The four dominant strata-management platforms each consume a structured import to load supplier invoices into their creditor and ledger modules. The row above is shaped to load cleanly across all four:

• StrataMax, the QLD-strong platform that runs across roughly 650,000 lots managed nationally, takes CSV imports into its creditor and invoice modules. A fund-tagged supplier invoice import row in this shape posts directly against the scheme reference, with the fund tag driving which fund the entry hits and the chart-of-accounts code driving the category line inside the fund.
• MRI StrataMaster (formerly Rockend), the enterprise-scale platform at the largest firms, takes structured imports into its supplier and ledger modules. The fund-coding workflow runs cleaner when the supplier-invoice row arrives already fund-tagged — the platform-side load becomes a routing operation rather than a coding decision.
• MYBOS, the cloud-first platform for multi-occupancy building management, takes per-scheme supplier-invoice records. The same row shape supports per-scheme extraction at MYBOS-scale firms: the scheme reference resolves against the MYBOS scheme master, and the fund tag and code drive the ledger posting.
• BCMax, the QLD-focused platform with a smaller-firm focus and a StrataMax-linked stack, takes a structured import in much the same form. The supplier invoice import file shape required is essentially a constrained variant of the StrataMax shape; the row above loads against either with minimal field-mapping work.

The integration boundary matters and deserves stating directly. This guide describes the structured row that loads cleanly into the four platforms. It does not claim that the extraction layer integrates directly with StrataMax, MRI StrataMaster, MYBOS, or BCMax. The manager runs the platform-side import as they do today — what changes is what they import. Instead of a CSV they coded by hand from a stack of PDFs, they import a CSV that arrives already coded.

Producing the row from the inbound supplier-PDF inflow is the practical job. Invoice Data Extraction is the layer that runs that job: the manager forwards or uploads the daily inflow of supplier-invoice PDFs and email attachments, describes the row shape and the scheme/fund/category logic in a natural-language prompt, and downloads a structured Excel, CSV, or JSON file with one row per billable line. The product is built to handle this at strata-portfolio scale — single batches up to 6,000 mixed-format files (PDF, JPG, PNG), single PDFs up to 5,000 pages — and to deliver consistent output across every document in the batch, which is the point of difference from running a portfolio's worth of invoices through a general-purpose AI tool that handles each document as a fresh conversation. Every row carries a reference back to the source file and page number, so each posting in the platform retains a click-through path back to the original PDF for audit. Firms wanting to see the shape end-to-end can start at structured invoice extraction for Australian strata managers and then build the prompt around their own scheme, fund, category, and threshold logic.