About 30 minutes of your team's time, end to end

How to connect your hotel to SwiftInvoicePro

Five steps from first email to live corporate invoicing on a Mews or Oracle OPERA property. No migration, no developer time, and nothing changes at the front desk.

Start a 60-day pilot Download the hotel guide (PDF)

The five steps

  1. Step 1

    Tell us about the property

    5 minYou

    Hotel name, PMS (Mews or Oracle OPERA Cloud), room count and the finance contact who should receive corporate invoices. Submitted through the pilot form — no call required.

  2. Step 2

    Issue a read access token in your PMS

    10 minYour PMS admin

    In Mews: Marketplace → SwiftInvoicePro → enable the connector and copy the access token. In OPERA: an OHIP client credential scoped to reservations and folio transactions. Read access only — we never write to your PMS.

  3. Step 3

    We register the webhook

    5 minUs

    We provision your tenant and register a per-property webhook endpoint. Reservation, folio and check-out events start streaming to us. Nothing changes in your front desk workflow.

  4. Step 4

    Run one test folio

    10 minTogether

    Check out a single test reservation. You see the corporate invoice generated, taxed and matched to the ledger inside a couple of seconds. If the mapping is wrong, we fix it before anything real flows.

  5. Step 5

    Go live in shadow mode

    Day 1Us

    Real bookings flow in, invoices generate alongside your existing process so you can compare line by line. Switch off shadow mode whenever you're satisfied — typically inside week one.

What we need from you

  • Mews access token, or OPERA OHIP client credentials (read scope)
  • Property / enterprise IDs for each site in the pilot
  • The email addresses corporate invoices should be sent from and to
  • Your VAT / tax registration details for compliant invoice output
  • One nominated finance contact to sign off the first week of output

What you don't need

  • No PMS migration or version upgrade
  • No developer time on your side
  • No changes to front desk procedure
  • No card data — we never touch PAN or cardholder data
  • No credit card for the 60-day pilot

What happens after go-live

Day 1

Connected, test folio verified, shadow mode running.

Week 1

Side-by-side comparison against your manual output. Mapping tuned to your chart of accounts.

Week 2–8

Live corporate invoicing. Weekly reconciliation report showing time saved and discrepancies caught.

Day 60

Pilot review with the measured numbers. Continue, extend, or walk away — no commitment.

Single property vs. multi-property chain

The five steps are identical for a group rollout. Three things change at chain scale.

One credential, many properties

Mews issues the access token at the enterprise level, and OPERA OHIP credentials are scoped to a chain code. You authorise once, then we enable properties in batches — no per-hotel setup call.

Tenant isolation per property

Every property gets its own isolated ledger enforced at the database layer, rolling up to a group view. No site can read another's data, and group finance still sees one consolidated report.

Central mapping, local tax

Your chart of accounts and invoice template are mapped once centrally. Regional VAT and tax rules are applied per property, so a UK and a German site invoice correctly from the same configuration.

Recommended chain pattern: 2–3 pilot properties first, then bulk-enable the rest of the estate from the same credentials — no repeat of steps 1, 4 or 5.

Security and data handling

Read-only PMS access, HMAC-SHA256 signed webhooks, TLS 1.3 in transit, and database-enforced tenant isolation so no property can ever read another's ledger. We never receive or store cardholder data. Full detail on the security and compliance pages.

Questions before you start? Email Richard at natromrich@googlemail.com

Start a 60-day pilot

SwiftInvoicePro is operated by Apex Flow Technology Ltd.