Operations + Finance

The intelligence layer where reconciled data becomes decisions.

Other tools stop at operations, so you export and reconcile by hand. In BasePro, operations and finance are one dataset: a booking is a receivable, a maintenance order a payable, an inspection finding the evidence on the claim.

app.basepro.io · boutique
live
Try toggling· click any scale · same architecture, different magnitude
Scale
AnchorUnit 14B · Polanco Tower1 of 18Boutique operator
Layer 1Operations· field reality
What's happening?
in flight08:14 · MX

Quarterly inspection logged

Field team

Marcos

on mobile

Photos

12

Follow-ups

2

open

Layer
operations · 1 of 3 · 3s per layer

One data stream, three connected layers

Operational data enters once and flows into financial action and portfolio intelligence automatically.

Financial Pipeline

// MONTHLY CLOSE — Portfolio A Portfolio · March 2026

→finance.receivable.aggregate(portfolio: PORTFOLIO_A, period: MAR_2026)✓8ms
→tax.withholding.calculate(iva: 16%, isr: 1.25%, retenciones: applied)✓3ms
→banking.reconcile(accounts: [USD_4821, MXN_7293], tolerance: $0.01)✓34ms
→reports.generate(type: PL, format: PDF, branding: SURFSIDE_PM)✓120ms
→finance.disbursement.calculate(owners: 3, net_after_fees: true)✓89ms

// 23 bookings reconciled · $47,200 gross · $0.00 variance · report sent to 3 investors

How the layers connect

Operations and finance share the same data layer — not through integrations, not through exports, natively.

Layer interconnection — operations → financial → intelligence
L1Operations · the work happens10K+ events/day
L2Financial · reconciled, not retypedauto-reconciled
L3Intelligence · forecasts on real data30d forecast

Data Interconnection

The Foundation

Connected workflows generating operational data. Every booking, inspection, maintenance order, and compliance record is linked. This connected data is the raw material that makes everything else possible.

Reconciliation-driven actions

Next

When operational events land in the financial layer directly, the actions that follow are reconciliation-driven, not manual: receivables track from bookings, vendor costs link to maintenance orders, owner shares calculate from reconciled transactions. The financial layer runs itself on the data the operations layer already produces.

MX · Operations · CLABE$2.41M MXN
Trend: 1.82, 1.94, 2.01 … current $2.41M MXN, delta +32%+32%
US · Distributions · ABA$432K USD
Trend: 0.32, 0.34, 0.34 … current $432K USD, delta +34%+34%
EU · Holding · IBAN€870K EUR
Trend: 0.85, 0.87, 0.86 … current €870K EUR, delta +0.2%+0.2%
MX · Trust escrow · CLABE$520K MXN
Trend: 0.42, 0.41, 0.43 … current $520K MXN, delta +24%+24%
Global · Reserve · SWIFT$4.0M USD
Trend: 4.02, 4, 4 … current $4.0M USD, delta 0.0%0.0%

Financial data capture — live now

Every transaction is captured, categorized, and connected to the property, booking, or maintenance order that generated it. This data layer is live in every BasePro account.

Live capabilities — proof-stat strip
100%of bookings auto-flow into AR/APshipped
4+currencies tracked natively per fundshipped
CFDI4.0 Path B emission native to Mexicoshipped
<2sto generate quarterly LP roll-upshipped

AR/AP Tracking

Every transaction linked to the property, booking, or maintenance order that generated it. AR/AP aging at a glance. Receivables and payables tracked from the moment they're created.

Multi-Currency Tracking

Bank account tracking in USD, MXN, COP, EUR. Per-investor portfolio grouping. Cross-currency consolidated reporting. Running balances tracked per account. The data foundation for reconciliation-driven financial actions.

Tax Configuration

Three-level hierarchy: organization defaults, property overrides, booking-source exceptions. Automatic tax calculation on every transaction. The configuration layer for future automated compliance.

Push-Button Reports

Branded PDF composed on demand from live data. P&L, AR/AP aging, occupancy, owner statements, maintenance costs. One-click investor reporting.

What we're building next

Connected operational data is already flowing. Everything below is a natural extension.

FINTECH-RAIL ROADMAP · 2026–2027Insurance · Building
INSURANCE
Building
COLLECTIONS
In design
TAX AUTO
In design
DISBURSE
In design

Reconciliation-driven receivables

In design

Bookings already become receivables. The next step: rent reminders, late payment escalation, and collection tracking — all triggered from booking data already in the system.

Reconciled disbursements

In design

Owner shares already calculate from reconciled data. The next step: automated payout queuing and vendor payment reconciliation — matched from completed maintenance orders and validated before anything posts.

Claim evidence compilation

Building

Inspections already capture photos, asset history, and compliance records. The next step: connecting that evidence directly to insurance claims. One click, not one binder.

Compliance automation

In design

Tax configuration already applies to every transaction. The next step: compliant invoice generation and automated filing preparation across jurisdictions.

Day-1operational data already powers Day-1 financial intelligence

Operational events (bookings, work orders, inspections) reconcile through the financial layer at the moment they happen. Quarter-close becomes a button, not a project. The financial layer runs itself on the data the operations layer already produces.

Why architecture matters

Financial intelligence requires connected operational data. BasePro's workflows share a single data layer — every booking, inspection, maintenance order, and compliance record is linked. Financial intelligence isn't bolted on. It's the natural result of building operations on a connected foundation.

Property operations. Financial intelligence. One system.

See the full platform roadmap →

Operations and finance. One platform.

Operations and finance in one connected system.

Start Free TrialBook a Demo