For Mexican FIBRAs
The operating system Mexican FIBRAs run on. Committee-grade out of the box.
Hash-chain audit log, CFDI 4.0 Path B, ARCO workflow with regulatory SLA tracking, Cross-LLC consolidation. Configured in weeks, not SOW milestones.
The FIBRA reality
Four friction points your committee already knows.
Foundation frictions
Implementation roadmap · enterprise ERP
6 phases · 14 mo to go-liveSix to eighteen months is the go-live arc on enterprise ERPs adapted to Mexican real estate by consultants who learned the vocabulary last fiscal year. The integrator who signs the SOW does not pay the SAT penalty when a CFDI rejects. Your finance director does. BasePro ships the foundations live at trial signup: country registry, CFDI emitter, banking schema, ARCO workflow. Configured in weeks, not at milestone six of an SOW you are already paying for.
Source: Published enterprise-ERP implementations, 2022–2025
One canonical view, every specialist on the team.
Twelve trusts × four asset classes roll up into a single audit-grade cockpit. Occupancy, NOI delta, cap-rate, distribution-cycle status, and audit-chain integrity on one canvas — the same canvas your DPO opens before the CNBV filing deadline, your investment committee reads at month-end, and your auditor reconstructs from. No reconciliation between formats. No consolidation tooling. No version-of-truth ambiguity. The cockpit IS the canonical view; specialists project per-domain where their depth lives.
FIBRA Admin · 12 trusts · Q3 2026
CNBV filing · 14d remainingTrusts
12
Total AUM
$2.4B
Weighted occ.
89.4%
+2.1% QoQ
Reviews due
3
Distribution cycle: 8 of 12 disbursed · Audit chain: intact · 0xa3f2…ec47 · Last specialist review: today · 09:42
Cryptographically chained audit log, per organization
Every write to your portfolio anchors to a tamper-evident audit chain. Multi-year retention available; sensitive fields redact cleanly for external review without breaking the chain. When your audit committee asks whether a specific inspection, booking, or disbursement was altered after the fact, you answer in seconds, with cryptographic certainty, not institutional memory. That is the difference between an audit opinion that passes with modifications and one that does not.
Capital Call Ledger
LIVE · #2,847,193Capital call · MXN 12.4M
Quarterly close · Q1 2026
Distribution · MXN 8.2M
ARCO · 20-day SLA met
CFDI batch · 1,247 docs
LFPIORPI filing
Committee vote · 7–0
today: 12 events · this quarter: 847 · flagged: 0
Native Mexican tax and regulatory infrastructure
CFDI 4.0 Path B lives in the platform, not in a consulting SOW. Monthly ARCO requests trigger a 20-business-day countdown that notifies the DPO, tracks SLA status, and routes the response through your legal review. LFPIORPI Option Y detection runs against every transaction. SPEI identifiers, CLABE, and multi-currency reconciliation sit in the same banking schema as IBAN, SWIFT, and ABA. Your compliance workload becomes a workflow, not a project. The ARCO deadline tracker means your DPO never walks into a meeting discovering that a 20-business-day clock started 18 business days ago.
Two-dimension tenant isolation, structural
Tenant isolation is enforced below the application layer — at every table that holds your data, in two dimensions: organization-scope and property-scope. Cross-tenant boundaries cannot be probed. Your auditor, your external security review, and your privacy counsel can verify the posture against documentation we provide. The isolation is structural, not configurable — part of the data architecture, not a setting your team toggles.
Two-dimension tenant isolation — org × property check
Structurally enforcedCross-tenant cells cannot be probed. Isolation is structural, not configurable.
Cross-LLC consolidation foundations
Your structure is typically a Mexican CKD or FIBRA with multiple underlying SAPIs and fideicomisos, plus cross-border holding entities. BasePro's portfolio layer models that: one-country-per-org for regulatory clarity, portfolio-layer config for shared settings, per-property overrides where operations differ. Consolidated reporting for the committee, isolation for the auditor, flexibility for operations. A boutique operator with 12 units runs on the same BasePro as a Cross-LLC institutional portfolio. The permission boundary is the same; only the scale shifts.
Step-up auth on every critical operation
Role promotion, session revocation, SSO configuration changes, offboarding, and approval of high-value disbursements each require step-up reverification at the moment of action. Your team's day-to-day runs smoothly. The decisions that matter to your committee trigger an explicit second factor. Elevation events stream to your own security platform — your SIEM picks them up alongside the rest of your access telemetry. Alert rules catch impossible-travel logins, new-SSO configurations, and ten-plus failed-login patterns.
Step-up auth — critical operations
MFA-anchoredAdmin elevates a teammate to Manager. Re-verification at moment of action; the elevation is auditable, not blanket.
IT revokes an active session after device loss. Re-verification confirms identity before the revoke executes.
Admin updates the SAML attribute mapping. Step-up MFA gates the change so a compromised admin token cannot rewire access alone.
Finance approves a high-value disbursement. Re-verification of the approver attaches a fresh MFA timestamp to the audit chain.
HR offboards a departing operator. Re-verification confirms the action; SCIM event closes the access loop.
Enterprise SSO, SAML, and SCIM
Production-verified SAML SSO, OIDC identity providers, and SCIM inbound provisioning. Your investor-admin team authenticates through your existing IdP — Okta, Azure AD, Google Workspace. Provisioning events land in the security audit log. When a team member is deprovisioned in your IdP, BasePro revokes their access inside the same cycle — not at the next support ticket. Joiner-mover-leaver runs through one control plane.
SCIM lifecycle — joiner / mover / leaver
IdP-drivenCross-border banking in one schema
Your funds move across Mexican, US, and European rails. The banking schema carries CLABE for MX, ABA for US, SWIFT and IBAN for international, all in one normalized table mapped to currency and country. Bank feed reconciliation, SPEI identifier matching, and multi-currency P&L roll-ups sit on the same substrate. Your consolidated statements stop depending on Excel macros that nobody wants to own.
Data residency, envelope encryption, ten-year retention
Choose the region that holds your data at signup — EU, US, or APAC. Sensitive personal data sits behind envelope encryption with per-organisation keys. The audit log retention window extends to ten years, aligned with NOM-151 expectations. When your committee asks where the data lives, who holds the keys, and how long the record is preserved, the answers are documented policy — not a best-effort claim.
Enterprise tier, priced against what you actually operate.
Custom pricing anchored to portfolio size, entity count, and compliance surface. No consulting SOW. No minimum seat-count lockout.
How BasePro reads against your current options.
Walk us through your committee's reporting cadence.
We show you BasePro against your specific audit, consolidation, and tax-calendar requirements. We open the call in the platform, not in slides.
Not ready? Explore by role: