Prove the invoicing layer before you change anything.
SwiftInvoicePro runs alongside Oracle OPERA and Mews in read-only shadow mode. It replaces nothing in your PMS estate — it observes folio events, compiles corporate invoices, and lets your finance and technical teams compare the output against what your teams produce today.
It cannot change, delay or break anything in your estate.
A shadow pilot runs beside your live systems, not inside them. There is no cut-over, no parallel go-live, and no dependency on us for any guest-facing or finance-facing process.
We subscribe to folio and check-out events. We never write, post, void, adjust or reverse anything in your PMS. There is no write scope on the credentials we are issued.
During the shadow pilot no invoice we produce is sent to a guest, a corporate client, or your finance system. Output is compared side-by-side against what your team already produces.
Only the fields needed to build an invoice line. No PANs, no payment credentials, no marketing use. Processing is stateless — payloads are not retained beyond the run.
Your estate runs in an isolated pipeline with row-level access controls. You can revoke the integration key at any moment and every connection stops immediately.
Because nothing was written and nothing was replaced, ending the pilot is a key revocation — no migration, no rollback, no change control on your side.
Worst case at the end of 60 days: you have measured evidence and you revoke a key. Your PMS, your ledger and your guest experience are exactly as they were on day one.
The questions reviewers ask before they say yes
What a 60-day corporate invoicing pilot actually involves
The pilot is free, lasts 60 days and runs on a single property. We take a read-only feed from your property management system — Mews through the official Marketplace API, or Oracle Opera through a folio transaction-line export — and build the corporate invoices your billing team would have built by hand. Your existing process keeps running untouched throughout, so there is nothing to roll back if you decide not to continue.
Week by week
Week 0 agrees scope, owners and the read-only credentials. Weeks 1 to 8 run the pipeline in shadow, with a weekly report showing consolidated corporate invoices produced, folio lines matched, exceptions raised and where the two processes disagreed. Week 9 is the review: your finance and security teams look at the same evidence and decide whether it is worth taking further.
What we never do
No writes to the PMS, no schema changes, no software on property, no automatic credentials and no production go-live without a manual review on both sides. Pilot data stays isolated per tenant and is never used to train anything.
Who should own it
In practice the useful sponsor is whoever owns corporate billing reconciliation — usually within group finance, with IT reviewing the integration rather than leading it. Because the pilot is read-only and single-property, it rarely needs a procurement cycle to start.
Load characteristics under a peak check-out window
Provision a sandbox property and replay a peak-hour webhook burst against our ingestion edge.
Slide to simulate burst size; metrics update live below.
Performance Metrics
Measured on deployed Cloudflare Worker: 24 ms p50, 79 ms p99, ~1,929 req/sec sustained, zero 5xx errors.
Apply without a demo call
Size your estate, see today versus SwiftInvoicePro line by line, and submit the pilot application in the same page. Free, 60 days, read-only, single property.
Compare and applyBook a stay & watch it flow into the folio engine
Create a test reservation, advance it through the lifecycle, and the same edge pipeline that powers check-out automation generates the folio on the final step.
Sandbox mode: reservations live in your browser only. Check-out triggers a simulated folio generation using the same pipeline the production engine uses for live OHIP & Mews properties.