Integrations · Real estate

Connect Yardi Virtuoso to Well

Read Yardi Virtuoso property billing into Well through its MCP server: the invoices a property bills, the transactions that settle them, and the bank and ledger accounts they post to. Rent collected lines up against the books without re-keying.

What Well pulls from Yardi Virtuoso

Yardi Virtuoso feeds tenant ledger, lease, property into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Yardi Virtuoso’s access.

From Yardi VirtuosoIn Well
Tenant ledger
Receivable
Lease
Revenue stream
Property
Asset
Yardi Virtuoso logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Yardi Virtuoso → Well

What Well does with your Yardi Virtuoso connection

Connect

Connect Yardi Virtuoso over OAuth (MCP DCR): Well registers a client through Yardi Virtuoso's OAuth Dynamic Client Registration and you approve on Yardi Virtuoso's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings tenant ledger, lease, and property in from Yardi Virtuoso on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Yardi Virtuoso entity into receivable, revenue stream, and asset, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Yardi Virtuoso lands in the workspace as receivable, revenue stream, and asset you can search, chart, and automate.

Questions Yardi Virtuoso unlocks

Ask in plain language. Well answers from your connected Yardi Virtuoso connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Yardi Virtuoso connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Yardi Virtuoso connection…

Connect Yardi Virtuoso in three steps

  1. 01

    Authorise Yardi Virtuoso over its MCP server

    Find Yardi Virtuoso in Well's Connections panel and begin. Well reads the OAuth metadata at the Yardi MCP server on mcp.virtuoso.ai, registers a client through Dynamic Client Registration, and hands you to Yardi to approve the read scopes, so there is no key to copy across.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.virtuoso.ai/mcp
  2. 02

    Map your entities

    Well reads the companies and people on a lease, the invoices a property bills, and the transactions that settle them, resolving each one onto its bank account, ledger account, and payment instrument through Well's data-views layer.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Then ask which properties are behind on billing, table collected rent by ledger account, or let an agent reconcile a settled payment against the books. Yardi stays the operating system of record; Well holds the read-only financial reading of it.

    • First syncstarts as soon as connect completes

Connecting takes about a minute. Current billing is read on connect and the longer lease and transaction history backfills in the background.

How Yardi Virtuoso stays secure with Well

Well reaches Yardi Virtuoso through its MCP server at mcp.virtuoso.ai over the Model Context Protocol, and OAuth Dynamic Client Registration keeps the Yardi credential with Yardi rather than with Well. The grant is scoped to the property, lease, billing, and account data Yardi exposes, and it refreshes server-side. Every call is a read; Well cannot create a charge, post a payment, or change a lease in Yardi.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.virtuoso.ai/mcp
  • Read Yardi Virtuoso records

    Resources the Yardi Virtuoso MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve tenant ledger, lease, and property across your stack

    Match identifiers in Yardi Virtuoso against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Yardi Virtuoso records

    Not granted; Yardi Virtuoso is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Yardi Virtuoso passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or Yardi Virtuoso’s admin panel.

Frequently asked questions about Yardi Virtuoso and Well

Pick Yardi Virtuoso in Well's Connections panel to begin. Well reads the OAuth metadata published at the Yardi Virtuoso MCP server on mcp.virtuoso.ai, registers itself through Dynamic Client Registration, and routes you to approve the read scopes on Yardi's own screen. No API key changes hands, and the consent step keeps the choice of what Well may read with you.

More than most property tools surface to a finance layer. Well reads the companies and people behind a lease, the invoices a property bills, the transactions that settle them, and the bank accounts, ledger accounts, and payment instruments those movements run through. A tenant resolves to a company, a billed charge to an invoice, and the rent that clears to a transaction posted against the right ledger account.

You can, because Well reads the ledger account and the payment instrument alongside each transaction. A rent payment that settles in Yardi arrives carrying the account it cleared in and the ledger line it belongs to, so collected rent reconciles against the books without re-keying. Ask which properties are behind on billing this period and the answer joins the invoice, the transaction, and the account in one place.

Every company, invoice, and transaction Well builds from Yardi keeps its Yardi identifier and a link to the original. You reach the Yardi record in one click from a workspace page, and the same identifier travels back so a search resolves from either side. Yardi stays the operating system of record for the property; Well holds the financial reading of it next to your other accounts.

Well reads properties, leases, invoices, and the transactions behind them through the Yardi MCP connection and folds new activity in as it is read, with the first connect pulling existing billing history in the background. The connection is read-only, so your team keeps working leases and charges in Yardi while Well mirrors the financial side for reporting and agents.

Disconnecting Yardi Virtuoso in Well revokes the token and stops further reads at once, and since Well only ever read, nothing needs reversing on Yardi's side. The companies, invoices, transactions, and account records already brought across stay in your workspace, so a question about collected rent last quarter keeps answering after the connection is gone.

Yardi Virtuoso logo

Ready to connect Yardi Virtuoso?

Connect once. Every tenant ledger, lease, property from Yardi Virtuoso becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.