For FIBRAs
Committee-grade property operations, built for Mexican FIBRAs.
Hash-chain audit log, CFDI 4.0 Path B, ARCO workflow with regulatory SLA tracking, and multi-entity consolidation foundations. The institutional infrastructure your committee expects, shipped in weeks, with no consulting SOW.
The FIBRA reality
Four friction points your committee already knows.
6–18
months to go live on SAP Real Estate or Oracle NetSuite
Source: Published enterprise-ERP implementations, 2022–2025
The only ERPs that claim institutional scale were designed for manufacturing and adapted to real estate by consultants. Your team spends a year configuring LATAM modules that still ignore the CFDI. The system integrator who signs the invoice does not pay the SAT penalty when a CFDI rejects. Your finance director does. BasePro ships the foundations on day one, configured in weeks. Country registry, CFDI emitter, banking schema, and ARCO workflow are live at trial signup, not at SOW milestone six.
Cryptographically chained audit log, per organization
Every write to your portfolio anchors to a SHA-256 hash chain. Monthly partitions, nightly verification cron, 10-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.
Trustee · Class B
Capital call issued
Investment Committee
Quarterly close approved
Trustee · Class A
Distribution paid
DPO · Compliance
ARCO response · 20-day SLA met
Finance Office
CFDI batch issued
Trustee · Class B
LFPIORPI filing submitted
Investment Committee
Committee vote recorded
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.
Dual-dimension row-level security
Every org-scoped table enforces organization_id. Every property-scoped table additionally enforces property_id. Cross-org queries return 404 rather than 403, so portfolio enumeration is impossible, not merely forbidden. Your DBA, your pen-tester, and your compliance auditor can verify this at the PostgreSQL layer. No middleware to trust, no code-review promise to take on faith. Dual-dimension RLS is not a configuration option. It is the database schema.
Multi-entity 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 multi-entity 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 Clerk 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. A SIEM webhook forwards each elevation event to your own security platform. Alert rules catch impossible-travel logins, new-SSO configurations, and ten-plus failed-login patterns.
Enterprise SSO, SAML, and SCIM
Clerk Professional+ surfaces production-verified SAML SSO, OIDC identity providers, and SCIM inbound provisioning. SCIM events emit to your security audit log. When an investor-admin team member is deprovisioned from your IdP, BasePro removes their access inside the provisioning cycle, not at the next support ticket. Your team's joiner-mover-leaver lifecycle runs through one control plane.
Cross-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, KMS envelope encryption, ten-year retention
Your org creation dialog lets you pick the Supabase region that holds your data. Sensitive PII sits behind KMS envelope encryption with org-specific keys. The audit log retention window extends to ten years, which aligns with NOM-151 expectations. When your committee asks where the data lives, who holds the keys, and for 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: