KriyaGo's MRI products work with MRI Platform X only. The post doesn't mention Property Tree or other MRI products.
The short answer
MRI Agora Orchestrator brings governed AI agents into MRI's ecosystem, and Agora Intelligence surfaces risks and opportunities across a portfolio every day. For MRI Platform X finance teams, that means fewer surprises and faster month-end investigation. Bank reconciliation, though, depends on data outside MRI: bank statements, lockbox files, card settlements, and payment returns. Matching that data to the ledger at volume, every day, is still a specialist job. The strongest month-end for PMX teams in 2026 uses Agora for portfolio-wide insight and orchestration, and purpose-built automation for the bank-to-book match.
Key takeaways
• Agora Intelligence
monitors leasing, finance, and operations workflows and delivers ranked signals: risks, trends, watches, and opportunities.
• Agora Orchestrator
runs real-estate-specific agentic workflows from a catalog of pre-built agents, with audit trails and role-level permissions.
• Bank reconciliation is different.
It starts with bank-side data in formats such as BAI2, MT940, and CAMT.053, and needs high-volume, rules-plus-learning matching across many entities and accounts.
• The two approaches work together.
Agora can flag a cash risk. Automated reconciliation makes sure the cash figures behind that signal are already matched and trustworthy.
• Start with the close.
Map your month-end tasks, decide which belong to Agora, which to bank automation, and which stay with people.
What MRI launched: Agora Intelligence and Agora Orchestrator
On June 25, 2026, MRI Software launched two new products on its MRI Agora platform. Both are available to MRI clients globally across commercial, multifamily, residential, social housing, local authority, and occupier sectors.
MRI Agora Intelligence
Agora Intelligence is a monitoring layer. It tracks workflows across leasing, finance, and operations every day. It then delivers role-specific briefings that classify each finding as a risk, trend, watch, or opportunity, ranked by business impact.
Three features stand out for finance teams:
• Explainable findings.
Each signal says what changed, why it matters, and what to do next.
• Traceability.
Signals link back to the underlying data and include confidence levels.
• Ask Agora.
A natural-language query feature lets users investigate a signal without leaving the platform.
According to Commercial Observer, Agora Intelligence uses a semantic layer that lets large language models interpret real estate data. That matters because real estate data is full of domain-specific structures, such as entities, leases, recoveries, and property hierarchies, that generic AI tools often misread.
MRI Agora Orchestrator
Agora Orchestrator is the action layer. It runs real-estate-specific agentic workflows using a catalog of pre-built agents that MRI has refined across its client base. Teams configure agents for their own operations. The Orchestrator handles routine execution automatically and routes complex cases to people.
Governance is built in. MRI highlights full audit trails, searchable and exportable logs, and role-level permission controls. As MRI CEO Patrick Ghilani put it: "Connecting AI agents to systems is becoming easier. The bigger challenge is ensuring those agents operate in ways organizations can trust."
That focus on trust is the right one for finance. Any automation that touches the books needs a clear record of what it did, when, and on whose authority.
A. The "Spam Folder & Attachment" Trap:
Manual email distribution reliance creates significant deliverability risks. Large PDF attachments, unverified sending domains, and bulk distribution lists routinely trigger enterprise spam filters. When an investor or property owner fails to receive a monthly financial statement, the resulting friction strains business relationships and creates redundant work.
B. Portal Fatigue and Low Engagement:
The industry's default response to email deliverability issues has been forcing stakeholders onto client portals. While portals are essential for static document archives, relying on them for time-sensitive notifications creates friction. Expecting stakeholders to proactively log into separate portals leads to low engagement and delayed approvals.
C. Static Data vs. Dynamic Operational Signals:
A standard 50-page monthly owner report provides historical context, but it rarely highlights immediate operational priorities. When a major commercial lease renewal hits a critical milestone or a capital expenditure threatens a budget, leadership needs an immediate, contextual signal rather than a retrospective month-end summary.
What Agora could change in the MRI Platform X month-end close
MRI's announcement covers leasing, finance, and operations broadly. It doesn't list specific month-end or accounting workflows, so PMX teams should confirm the agent catalog with their MRI account team. Based on what Agora is designed to do, here is where finance teams are likely to feel it first.
Earlier warning, fewer surprises.
Today, many problems surface during close: an arrears spike at one property, a recovery that didn't bill, a lease event nobody actioned. A daily signal layer can surface those weeks earlier, so the close becomes confirmation rather than discovery.
Faster variance investigation.
Controllers spend a large share of close week answering "why did this move?" A natural-language query that traces a signal back to its source data can shorten that loop, especially for portfolio-level reviews.
Orchestrated routine steps.
Repetitive, rules-based workflows with clear inputs and outputs are natural candidates for pre-built agents, with exceptions routed to people.
Better governance evidence.
Audit trails and exportable logs help when auditors ask how an automated step was performed and who approved it.
Month-end task | Where Agora is likely to help | What still needs attention |
Portfolio review and variance analysis | Daily signals, ranked findings, Ask Agora investigation | Final sign-off by the controller |
Lease and operational exceptions | Early flags on risks and trends | Source data quality in PMX |
Routine workflow steps | Pre-built agents with human hand-off | Agent configuration and testing |
Bank reconciliation | Signals on cash-related risks | Matching bank-side data to the ledger at volume |
Audit evidence | Logs and audit trails for agent actions | Evidence for steps outside Agora |
The last two rows are where finance teams should look closely. Bank reconciliation is the one month-end task that depends mainly
on data that doesn't originate in MRI.
Why bank reconciliation is a different kind of problem
Most month-end tasks start and finish inside the property management system. Bank reconciliation doesn't. It's a comparison between two independent records, the bank's and the ledger's, and the bank's record comes from outside. That changes what good automation looks like in four ways.
1. The data starts at the bank
Bank activity arrives as statement files and feeds in formats such as BAI2, MT940, and CAMT.053, through bank portals, host-to-host connections, or APIs. Each bank has its own quirks: description fields that truncate, batched deposits, delayed returns. Before any matching can happen, someone or something has to collect, normalize, and load that data every day. A signal layer that reads the ledger can't fix a missing or late bank file.
2. Matching is many-to-many, not one-to-one
In real estate, one bank deposit can contain dozens of tenant payments. One lockbox file can cover several properties. A card processor settles net of fees, days after the charge. A single owner distribution can split across entities. Good matching needs rules for the predictable cases, learning for the messy ones, and confidence scores so people review only what's uncertain.
3. Volume and entity count multiply the work
A portfolio with hundreds of properties can have hundreds of bank accounts, often one or more per legal entity. Reconciliation effort grows with every account, not with every property manager. That's why manual reconciliation so often becomes the long pole of the close.
4. Controls and evidence are non-negotiable
Bank reconciliation is a core financial control. Auditors, lenders, and investors expect it to be complete, timely, and evidenced: who matched what, which items were cleared manually, and why an outstanding item is still open. Trust-account and client-money rules in some jurisdictions add stricter requirements.
This isn't a criticism of Agora. It's a reminder that a general-purpose orchestration layer and a purpose-built reconciliation engine solve different problems. Finance teams need both.
Where specialist automation fits alongside Agora
The simplest way to picture the modern PMX close is as two layers. One layer keeps the ledger's cash data correct. The other reads the ledger and tells the team what needs attention.
MRI Platform X month-end · bank automation and MRI Agora
Bank data enters from outside MRI and is matched daily before it lands in the Platform X ledger. Agora then reads that reconciled ledger and sends signals to the finance team, which also reviews the few exceptions the matching engine couldn't resolve.
How KriyaBalance and Treasury 360 work with MRI Platform X
KriyaGo is an MRI Software solution partner. Its bank reconciliation engine, KriyaBalance, was built specifically for real estate and connects directly to MRI Platform X. It covers the bank-to-book match that Agora isn't built to do.
KriyaBalance: automated bank reconciliation for MRI Platform X
• Bank data every day.
KriyaBalance takes bank activity from statement files such as BAI2 and MT940, plus direct bank connections (including Wells Fargo, TD, and RBC) and aggregators in North America, Europe, and Australia.
• Real estate matching logic.
Machine-learning matching handles complex, many-to-many transactions. When the engine isn't sure, it shows confidence scores and suggested matches, so people review only the exceptions.
• Bi-directional with PMX.
KriyaBalance reads from and writes to MRI Platform X, so it can create the required transactions directly in the MRI environment instead of leaving staff to key them.
• Controls built in.
Role-based access, multi-factor authentication, and full audit trails record every match and every manual decision.
• Built on Microsoft Azure
for security and scale across large, multi-entity portfolios.
The goal is simple: turn reconciliation from a 40-to-60-hour monthly task into a short daily review of exceptions.
Treasury 360: from reconciliation to cash control
Treasury 360 brings KriyaBalance together with KriyaVision (AI invoice processing) and KriyaCash (payments and cash management). For MRI Platform X teams, that adds:
• Three-way matchingbetween the bank, the ledger, and invoices.
• Cash flow forecastingwith fund-transfer recommendations across entities.
• Electronic payments with approval workflows, so cash leaves only after the right sign-offs.
How it complements Agora
Agora Intelligence is only as good as the data it reads. When bank activity is reconciled daily, the cash balances, receipts, and outstanding items inside PMX are current. Any cash-related signal that Agora raises then rests on matched, trustworthy numbers. In the other direction, exceptions that KriyaBalance can't resolve become clear, evidenced items for people to investigate, which is exactly what a governed month-end needs.
A practical checklist for MRI Platform X finance teams
Use these steps to plan an AI-ready month-end without disrupting the close you run today.
1. Map the close.
List every month-end task, its owner, its system, and how long it takes. Mark which tasks start inside PMX and which depend on outside data, such as bank files, lockbox, card settlements, and invoices.
2. Ask MRI about the Agora catalog.
Confirm which pre-built agents and Intelligence signals are relevant to finance on your PMX deployment, and what licensing applies.
3. Count your bank accounts.
Record the number of accounts, banks, entities, and monthly transactions. This is the clearest measure of your reconciliation workload.
4. Measure the baseline.
Track hours spent on reconciliation, the number of unreconciled items at close, and how many days after month-end each account is signed off.
5. Fix the bank data path first.
Move from manual statement downloads to daily automated files or API feeds. Matching can't be faster than the data arriving.
6. Move from monthly to daily reconciliation.
Daily matching shrinks the close to a review of a few exceptions, rather than a month of backlog.
7. Define the human hand-off.
Set confidence thresholds, approval roles, and escalation paths for both Agora agents and reconciliation exceptions.
8. Keep one evidence trail.
Make sure auditors can see agent actions, automated matches, and manual decisions, with who did what and when.
9. Pilot on a slice.
Start with one region, one bank, or a group of entities. Compare hours and days-to-close against the baseline before scaling.
10. Review quarterly.
Agent catalogs and bank formats both change. Revisit thresholds, rules, and ownership every quarter.
Frequently asked questions
MRI Agora Intelligence and Agora Orchestrator are a meaningful step for the MRI ecosystem. They bring governed, explainable AI into the daily work of real estate teams, and finance leaders should explore them. The fastest close, though, comes from pairing that intelligence layer with clean, reconciled cash data. For MRI Platform X teams, that means purpose-built bank reconciliation running every day,
so Agora's signals rest on numbers the controller already trusts.
To see how KriyaBalance and Treasury 360 work alongside MRI Platform X, book a demo with KriyaGo.
