You manage 40 units across two LLCs. One holds a group of long-term rental properties in MXN. The other holds a smaller set of furnished apartments priced in USD. Each entity has its own owner, its own bank account, and its own expectation of a clean monthly statement. Your accountant has one more opinion: the books must never mix.
For most property management tools, this structure is a workaround waiting to happen — one account per entity, multiple logins, reconciling across exports. For some operators, that works until it doesn't. For others, it never really works.
Here is how BasePro handles it.
The Portfolios layer
A Portfolio in BasePro is an entity-level grouping — a named container that holds a set of properties, its own bank accounts, and its own financial record. It is designed around the investor, not the property type: the question it answers is "who owns this group of assets and what do they need to see?"
You can run multiple portfolios under one organisation. PORTFOLIO_A might hold your MXN residential assets; PORTFOLIO_B might hold your USD furnished units. Each portfolio has its own:
- Bank accounts — multiple accounts per portfolio, each in the currency of that entity's operations. MXN and USD accounts live in the same platform; the ledger keeps them separate.
- Financial records — transactions, income, and expenses are attributed at the portfolio level. No bleed between entities.
- Owner statements — monthly statements are generated per portfolio, not per property. If PORTFOLIO_A belongs to a single investor, you send one statement covering all their properties together.
Multi-currency: what ships today
Multi-currency bank accounts are available at the Professional tier. You can hold MXN and USD accounts in separate portfolios and reconcile each in its native currency. Consolidated reporting across currencies — for operators who want a single view of net performance across both portfolios — follows IAS 21 exchange-rate principles and is available at Enterprise.
The practical implication: if your two LLCs operate in different currencies, you can run them as separate portfolios with full financial isolation, and you can generate per-portfolio statements in each currency. Cross-portfolio consolidation (one report showing both, converted) is an Enterprise capability.
One organisation, one country
One constraint worth knowing before you configure: each BasePro organisation operates within a single country. This is intentional — compliance obligations (SAT, CFDI, ARCO), tax treatment, and bank-account structures are country-specific. If your entities are all Mexican, this is a non-issue. If you are an operator in Mexico who also manages assets in a second country, that second country would require a separate organisation.
Most LATAM operators with multi-entity structures — two or three LLCs under a single management company, all operating in the same country — will not hit this limit.
What the operator sees day-to-day
From your daily view, switching between portfolios is a context switch, not a login switch. The maintenance kanban, vendor queue, and financial dashboard filter to the active portfolio. If you have admin rights across portfolios, you can move between them in the same session.
Owner statements generate at the portfolio level. You send one statement per portfolio per month — not one per property. If an investor holds 12 units across PORTFOLIO_A, they receive one statement summarising all 12. If you need to share a subset of those properties with a second stakeholder, that is a portfolio configuration conversation.
Before you configure
The multi-entity question is usually one of the first structure decisions to get right, because moving properties between portfolios after the fact requires adjusting opening balances and historical attribution. The team can walk you through your specific structure — how many LLCs, whether they share vendors or operate independently, which currency or currencies are involved — and confirm the right portfolio setup before you start loading data.
If your operation involves multiple entities and you want to make sure the configuration fits your structure, talk to the team before your first setup.