OSCRE International has formally launched its Universal Chart of Accounts (UCoA) initiative, a common data model that acts as a translation layer between firm-specific general ledger structures, rather than a standard everyone is forced to adopt. The goal is to make chart-of-accounts mappings machine-readable, cut manual mapping effort by up to 80%, and unlock AI-driven financial reporting across portfolios. A pilot is underway now, with first publication expected in three to nine months. This article explains what the UCoA is, the four use case patterns behind it, why it matters for real estate finance teams,
and how to get ready, including where a multi-platform PropTech consultancy like Assetsoft fits into the work.
If you have ever watched a finance team spend weeks manually reconciling general ledger data from Yardi, MRI, and a homegrown system before they could produce a single consolidated report, you already understand the problem OSCRE is trying to solve. Every owner, operator, and fund has built its chart of accounts a little differently. That bespoke structure is fine inside one system and a serious bottleneck the moment data has to move between systems, partners, or portfolios.
OSCRE International the Open Standards Consortium for Real Estate has now formally kicked off its Universal Chart of Accounts initiative to address exactly this. And the design choice at the heart of it is the part worth paying attention to.
What is the OSCRE Universal Chart of Accounts?
The OSCRE Universal Chart of Accounts is a common data model that translates between existing, firm-specific chart-of-accounts structures so that financial data can be exchanged and aggregated automatically. It is the first initiative under OSCRE's broader "Smart Data Highway" strategy, announced in February 2026, which builds on the organization's open-source Industry Data Model (IDM) — a free, use-case-driven data model already underpinning 150+ real estate use cases. OSCRE describes the UCoA as a "financial dictionary" within those standards, ensuring accounting and cost data align across systems.
The critical distinction: OSCRE is not asking the industry to rip out its charts of accounts and adopt a single universal one. That would be an unrealistic ask, and OSCRE knows it. Instead, the UCoA functions as a translation layer — a Rosetta Stone for real estate accounting data — that maps each organization's existing structure to a shared reference model. Firms keep operating exactly as they do today. The mapping happens in the data layer, machine-readable and automated, without disrupting core chart structures.
That reframing matters. Industry standards historically fail not because the standard is wrong, but because adoption demands that everyone change at once. By treating the chart of accounts as something to be interpreted rather than replaced, OSCRE sidesteps the adoption problem that has stalled similar efforts for two decades.
Why does chart-of-accounts mapping matter so much in real estate?
Because almost every meaningful financial activity in real estate crosses a system boundary.
A fund consolidating returns across a multi-manager portfolio has to normalize ledgers from operators who each built their own account hierarchy. An owner migrating from one property management platform to another has to remap thousands of GL accounts by hand. A firm reporting to NCREIF, lenders, or LPs has to translate its internal structure into someone else's expected format. A company integrating a newly acquired portfolio inherits a chart of accounts that looks nothing like its own.
Each of those is a manual mapping exercise today. It is slow, it is expensive, it is error-prone, and it produces no lasting asset — the next migration or consolidation starts from scratch. The UCoA aims to turn that recurring manual cost into a reusable, machine-readable mapping that compounds in value over time.
The four use case patterns behind the UCoA
According to OSCRE's initiative announcement, the project scope took shape during a planning session in New York, where contributors aligned the framework around four real-world use case patterns. These patterns describe the situations a translation layer actually has to handle:
Composition
How individual accounts roll up into groups, subtotals, and statements. The same line item may aggregate differently depending on the report.
Resolution
How an account in one firm's structure resolves to the equivalent concept in another's, even when names, codes, and granularity differ.
Change
How mappings stay valid as charts of accounts evolve. Accounts get added, retired, split, and merged over time.
Perspective
How the same underlying financial data can be presented through different lenses without re-keying the data.
Sitting underneath these is a metadata standards layer that defines the minimum descriptors needed to make dynamic reporting possible. In plain terms: the smallest set of tags each account needs so that software can interpret it correctly — without anyone having to alter the core chart structure to add them.
This is a pragmatic, engineering-minded design. It acknowledges that real charts of accounts are messy, that they change, and that the same number means different things to different readers — and it builds the model to absorb that reality instead of pretending it away.
Adual-track roadmap: usable standards now, AI automation over time
OSCRE has structured the work on a dual track. The near-term track delivers practical, usable standards that finance and systems teams can put to work in the short run. The longer-term track builds toward AI-driven automation, where mappings are suggested, validated, and maintained by machine intelligence rather than spreadsheets and tribal knowledge.
OSCRE's stated long-term target: reducing manual mapping effort by up to 80%.
That number is worth sitting with. If you have ever costed a system migration or a portfolio consolidation, you know how much of the budget and timeline is consumed by account mapping and reconciliation. Cutting the bulk of that effort doesn't just save money — it changes which projects are feasible at all.
A pilot program kicks off immediately, with first publication expected within three to nine months. The work is live, not theoretical.
Why this matters now
Three forces are converging to make this initiative land at the right moment.
First, consolidation and reporting pressure is rising. Investors and lenders increasingly expect timely, granular, comparable financial data across portfolios. Manual reconciliation simply cannot keep pace.
Second, platform diversity is the norm, not the exception. Most real estate organizations run more than one accounting or property management system — through acquisition, through legacy, or by design. A translation layer is the only realistic way to make heterogeneous systems speak to each other.
Third, and most importantly, AI is only as good as the data structure beneath it. Generative and analytical AI can transform real estate reporting — but only if the financial data feeding it is consistently interpretable. A machine-readable UCoA is precisely the substrate that makes reliable AI-driven financial analysis possible. Without it, every AI initiative starts by re-solving the mapping problem. With it, the mapping becomes infrastructure.
How should firms prepare for the UCoA?
Whether or not your organization joins the pilot, there are concrete steps that pay off regardless:
Inventory your charts of accounts
Document the structures in use across every entity and system. Most firms are surprised by how much variation has accumulated.
Capture mapping logic
Get the tribal knowledge of what each account really means written down and formalized.
Standardize your metadata
Begin attaching consistent descriptors to accounts so they can be interpreted programmatically later.
Clean up before you automate
Resolve duplicate, dormant, or inconsistently-coded accounts before automation amplifies the problem.
Treat mapping as reusable asset
Stop solving it project by project. Build it once, maintain it, and let it compound.
This is unglamorous work, and it is precisely the work that determines whether the UCoA delivers an 80% reduction in your environment or a 20% one.
Where Assetsoft fits
This is the kind of problem Assetsoft works on every day. Founded in 2012 and headquartered in Markham, Ontario, Assetsoft is a multi-platform PropTech consultancy with 50+ specialists across Canada, India, Sri Lanka, and the United States. The firm's whole reason for existing is to make real estate systems and data work together — which is to say, the translation problem the UCoA addresses is its native terrain.
Assetsoft's platform credentials span the systems where chart-of-accounts complexity actually lives: it is a Yardi ICN Member and Virtuoso Qualified, MRI Certified, a Procore Partner, UiPath Certified and a UiPath Fast Track Agent, and a SAP Concur Partner. The firm's founder brings more than 25 years of PropTech experience dating back to 2000, across owners, operators, and funds on five continents.
Concretely, the consultancy already does the work the UCoA is designed to standardize:
Cross-platform GL Mapping
Remapping accounts between Yardi, MRI, and other platforms during system migrations and consolidations.
CAM & Financial Reconciliation
Normalizing account structures across portfolios before numbers can be trusted.
Multi-currency & GAAP Analysis
Supporting revaluation analysis across entities with divergent ledger structures.
Data Quality Remediation
Cleaning duplicate, dormant, and inconsistently-coded accounts that sabotage automation.
For a firm trying to prepare for the UCoA, that practitioner experience is the difference between a tidy theoretical framework and a mapping that survives contact with a real portfolio.
The Automation layer: KriyaGo
Preparation is one thing; sustained automation is another. That is where KriyaGo comes in.
KriyaGo is an integration and automation platform — "The Operating System for Real Estate" — with 100+ integrations across the real estate technology stack. It is an iPaaS and automation layer, in the same category as Workato, Boomi, and MuleSoft, purpose-built for the realities of property and investment data.
100+ Integrations
Connect real estate platforms, accounting systems, and business applications seamlessly.
Automation Engine
Automate repetitive finance and operational processes across systems.
Continuous Mapping
Move, map, and reconcile financial data continuously rather than as one-time projects.
Data Synchronization
Keep financial and operational information aligned across your technology ecosystem.
Where the UCoA defines how accounts should translate, a platform like KriyaGo is what executes that translation continuously — moving, mapping, and reconciling financial data between systems on an ongoing basis rather than as a one-time project.
The combination is the point. A machine-readable mapping standard plus an automation platform to run it is exactly the architecture that turns the UCoA's 80% reduction goal from an aspiration into operational reality. Translation defines the rules; automation enforces them at scale.
How to get involved with the OSCRE UCoA
OSCRE has room for organizations that want to participate. That can mean contributing real-world chart-of-accounts examples, joining mapping exercises, or participating in the working group. Real charts of accounts — with all their messiness — are exactly what the project needs to pressure-test the model, so contributing examples is genuinely valuable, not just a formality.
To get involved, reach out to OSCRE International's Chief Innovation Officer, Ian Cameron, at [email protected].
If your organization wants help getting its chart-of-accounts data into shape — to participate in the pilot, to prepare for the standard, or simply to stop losing weeks to manual reconciliation — Assetsoft can help you inventory, clean, map, and automate. That is the work the firm does, and the UCoA initiative makes it more valuable, not less.
Frequently asked questions
About Assetsoft
Assetsoft is a multi-platform PropTech consultancy founded in 2012 and headquartered in Markham, Ontario, with 50+ specialists across Canada, India, Sri Lanka, and the United States. The firm helps real estate owners, operators, and investment managers implement, integrate, and automate their technology, including Yardi (ICN Member, Virtuoso Qualified), MRI (Certified), Procore (Partner), UiPath (Certified, Fast Track Agent), and SAP Concur (Partner). Its sister platform, KriyaGo, is an integration and automation platform with 100+ integrations positioned as "The Operating System for Real Estate."
Learn more at assetsoft.biz and kriyago.com.
