Step 1
Read-only access, same week
You open a restricted profile in your PMS. Your team keeps working exactly as today. Guest data stays untouched.
Statement integrity check
Parallel to your PMS, read-only. Sample variances below.
For 50 to 200 door operators. Parallel to Hostaway and Guesty.
Month-end should be boring.
At 120 doors, your bookkeeper is drowning and your PMS is telling three different stories. We stand beside your team with read-only access and zero guest data: every payout, platform fee, and field cost reconciled to the bank before your owner packets ship.
Month-end turns boring. In STR finance, boring is the ultimate luxury.
Read-only access. Revocable in one click.
No software migration
No new logins to babysit
No retraining your team
REF_ID: 40288-OTA
OTA payout mismatch
variance($1,240.00)
Reservation #40288 altered mid-stay. Logged payout settles below the reservation and lands short of the cleared bank deposit.
REF_ID: 40301-FIELD
Unreconciled field expense
variance($385.00)
Field job #40301. Hot-tub maintenance logged in the field app, never anchored to the reservation folio or the owner statement.
REF_ID: PKT-40317
Clean packet reconciliation
variance0.00
All remaining line items reconcile to the bank. Variance notes ship attached, audit trail intact, so the packet needs no follow-up call.
Net variance identified($1,625.00)
Owner questions after verification0
Zero-PII by design: names, phones, emails, and message histories are blocked. See the protocol.
Prepared by STR Financial Controller. Figures shown are illustrative samples.
Page 1 of 1
Run by operators who have closed the books at scale.
A decade of ERP architecture behind the checks, live controller work in front of you. Not software to learn. Oversight you feel in the first packet.
Live case study
The 100+ door close, running now
This is not framework talk. I am the active fractional financial controller for a premier, rapidly scaling 100+ door vacation rental brand. Multi-million dollar cash flows, pipelines shielded from operational drops, owner trust bulletproofed every close. Enterprise battle-testing, applied to your ledger.
Enterprise foundation
10 years of ERP architecture
A decade designing corporate ERP systems and protecting institutional data integrity. Structural compliance no generic tool can prompt into existence.
Why software fails
Reports do not stop leaks
Your PMS reports. Your bookkeeper reconciles weeks later. Neither intercepts leakage while it happens. This is the executive layer that does.
You stopped being able to eyeball the ledger at 40 doors.
You are at 50 to 200 now. Every month without a parallel check is a donation to the channels, the field vendors you never billed back, and the owners who are quietly shopping managers.
Top line
OTA payouts move without telling you
Adjusted payouts, altered cancellation terms, mid-stay guest refunds. Your PMS shows the reservation. The bank shows less. Nobody flags the gap until the owner does.
Caught where: reservation intent vs actual payout, before the packet ships. Full method on the audit page.
Field cost
The job gets done, the charge never lands
Hot-tub repair, deep clean after guest damage, emergency callout. Logged in the field app, never anchored to the folio or the owner. You eat it.
Caught where: every field job tied to a folio or owner before the close.
Retention
One shaky statement and the owner is gone
Upscale investors do not complain twice. One late or inaccurate packet and your contract is on someone else's desk. Verification before shipping is retention insurance.
Caught where: packets verified line by line, every cycle, before they ship.
We do not replace your PMS. We stand beside it.
Read-only access, zero guest data, and a clean exception list for your bookkeeper instead of a month of detective work. See the Zero-PII protocol.
Step 2
Independent check, before the packet ships
Reservation vs payout vs bank, matched on our side. Channel overrides, mid-stay edits, and missed fees surface while there is still time to recover them.
Step 3
Your bookkeeper gets answers, not homework
We clear the discrepancies, disputes, and trust-accounting exceptions with your back office. Owners receive packets that need no explanatory call. The 90-day audit proves it before you commit.
A one-time cleanup rots in 30 days. A standing close does not.
Rates shift, reservations get edited mid-stay, vendors charge back. The audit finds what already leaked. The retainer makes sure next month's packet is boring too, and keeps your books diligence-ready for a raise, a sale, or an acquisition.
- Statements verified before they ship, every cycle
- Trust accounting watched every cycle, not at year-end
- Owner questions answered with a line-item trace, not a meeting
We find the leaks first. You keep the report either way.
Give us 45 minutes to connect read-only. We review your last 90 days: uncollected guest fees, OTA underpayments, field costs nobody billed back. You get the findings in your own numbers. If there is nothing worth fixing, we part ways and the report is yours.
- 45-minute connection call. Restricted profile, read-only, zero guest data.
- 90-day findings report with line-item traces you can check yourself.
- Straight answer on retainer fit. No pressure, no demo theater.
Operators, not just advisors.
I started with the books: ERP systems, reconciliations, accounting standards. Twelve years learning where money moves and where systems break. What I build is reporting infrastructure that runs without being triggered. Systems that outlast the engagement.
Controller-led operators running closes across multi-market portfolios. ERP consulting background from 2021 to present, now fractional controller for a 100+ door brand.
BSc Hons, Oxford BrookesACCA AdvancedCAT10 years ERP architecture
What changes when we run it.
Leaks intercepted. OTA and fee leakage caught before statements go out.
Field costs anchored. Every job tied to the right folio or owner.
Owners retained. Packets ship verified and forwardable.
Built for the 50 to 200 door stretch.
The exact band where eyeballing breaks and owners get nervous. PMS-agnostic across the stack you already run.
Short-term rentals, 50 to 200 doors
Hostaway portfolios
Guesty portfolios
Owner-direct and co-host mixes
Multi-market operators
Read-only across PMS, OTA payouts, field apps, and bank. Guest data blocked by design. Details on the security page.
Managers stopped dreading the owner call.
Operator feedback from reporting and reconciliation work. Names withheld, outcomes shared.
"Month-end used to take a week of rebuilding. Now the packet arrives verified and the owners stopped asking questions."
Reporting automation engagement, multi-year.
"Exceptions arrive cleared instead of as homework. The close stopped being detective work."
Back-office reconciliation work.
"One reply with a line-item trace ends the question. No meeting needed."
Owner statement verification work.
If month-end costs you owners, make it boring instead.
One 45-minute connection call. We connect read-only, review your last 90 days, and show you the leaks in your own numbers. Start on the audit page or write directly.