One invoice,
across every property.
When a company account, a contractor crew or a long-stay project team uses six of your hotels in a month, it receives six invoices. SwiftInvoicePro reads the folio data and compiles one finished, tax-compliant invoice per account per billing period — each property’s own tax lines and currency preserved, settled amounts excluded, every line traceable back to the originating charge.
Certified Mews Connector API partner (read scopes only). Oracle Opera / OHIP ingestion is built and tested end to end, and is now open to a small number of early-adopter properties through a free, read-only 60-day shadow pilot. Prefer not to share data? See a pre-compiled sample invoice — no upload needed.
Send us one folio set — we send the finished invoice back
One corporate account, one month, across however many properties it touched. Paste the lines below or just leave your email and send them by reply. We compile them into a single tax-compliant corporate invoice and send it back within two working days. No system access, no credentials, no contract and nothing to sign — remove guest names before you send; we only need property, date, description, amount and currency.
Compliance & Privacy Tip: If internal data sharing policies are causing any hesitation, feel free to use a dummy corporate account name and completely randomize the financial figures. As long as the raw property countries, item descriptions, and currencies are left intact, the compiler engine will still demonstrate the exact consolidated tax layout your estate receives.
Compliance & Evaluation Risk Shield
Bypass corporate procurement delays. Access our standard, read-only evaluation Mutual Non-Disclosure Agreement. Our details are pre-filled under Apex Flow Technology Ltd; your finance or systems director can execute locally in about 3 minutes, so real folio exports can be shared under a signed confidentiality agreement. Return the signed copy and we countersign the same day.
Stateless Integrity
Compilation runs in short-lived, isolated server processes with no state kept between requests. Once your finished invoice is returned, your folio is deleted from our systems — nothing is kept on our side. For testing under this Mutual NDA, your operations teams are fully authorised to cross out, mask or black out guest names, room numbers and corporate client identity strings before uploading. Our engine reads tax rows, service charges and incidentals, and multi-currency lines to map systemic leakage profiles.
- 92,110
- completed business events in five minutes
- 0.00%
- failures across 276,330 requests
- 39 / 170 ms
- ledger write, median and p99
- 319 ms
- webhook to finished invoice, p99
Sustained production load test. Replay is idempotent — a retried event is a no-op, never a second invoice against a corporate account. Any recovery or time-saving figures elsewhere on this site are modelled and stay labelled that way until a live property measures them.
Extended-Stay & Infrastructure Crew Reconciliation
“Corporate” covers more than business travellers. These are the four billing problems we compile into one finished invoice.
Extended Stay & Crew Bookings
Multi-week crews, contractors and project relocations. Stays cross month-end, and in many US states occupancy tax stops after 30 consecutive nights — the invoice reflects both.
Multi-Property Project Teams
One invoice for a client whose teams are spread across separate franchised properties, with each property's own tax lines kept intact.
Global Corporate Accounts
Multi-currency, split-night folios brought into one statement for central accounts receivable, with the exchange rate shown.
Post-Departure Incidentals
Late charges posted after checkout are picked up and added to the right invoice instead of being missed or chased by hand.
What it actually is
An overlay above the PMS, not a replacement for it. The shape of the integration matters more than the pitch.
Read-only
No write-back to the PMS, no posting to a guest or company bill, no card data requested at any point.
Nothing on property
No agent, no middleware box, no schema change. Connection is by token issued from within the PMS.
Revocable in one click
A property revokes its token and all access ends immediately and permanently. Nothing is left behind.
Multi-jurisdiction
Each property's own tax lines and currency are preserved in the single invoice rather than flattened.
Traceable line by line
Every compiled line maps back to the originating order items, bills and payments. Verification is reconciliation, not trust.
PMS-neutral
Mews Connector API certified; Opera / OHIP built and open to early-adopter pilots; a mixed estate works.
Today, and with us
- Six property invoices for one company account, one month.
- Charges pulled per property by hand, at period end.
- Each jurisdiction’s tax worked out again in a spreadsheet.
- Settled amounts chased out manually; queries land on finance.
- One finished invoice per company account per period.
- Per-property tax lines preserved and labelled, not flattened.
- Currencies squared, with the rate shown.
- Settled amounts excluded; every line traceable to source.
A fair question, and the honest answer is that we do not replace it. Mews Accounts Receivable, and the equivalent in Opera and other systems, does the money side well: issuing an invoice, chasing it, collecting the payment and reconciling it against the open balance. If a hotel is not doing that today, they should be.
The difference is scope. PMS accounts receivable is per property. We are per company.
- A corporate account that stayed at six of your hotels in a month receives six invoices from a PMS ledger — one per property, each with its own numbering and its own ledger. We compile one invoice for that company account covering all six.
- Where those properties sit in different tax regimes or trade in different currencies, each property’s own tax lines are preserved and labelled on the single invoice rather than flattened into one total.
- An estate rarely runs one PMS end to end. We are PMS-neutral, so a mixed Mews, Opera and legacy estate still produces one consolidated corporate invoice.
- We are read-only. Nothing is written back, no bill is posted, no ledger is altered, and revoking the token ends access immediately and permanently. Whatever the PMS already does keeps doing it.
- Every compiled line traces back to the originating order items, bills and payments, so checking our output against the PMS is reconciliation rather than trust.
Put simply: if a hotel operates one property, the PMS ledger is probably enough. The moment one negotiated company account spans several properties, brands, tax regimes or systems, the consolidated invoice is still being assembled by hand — and that is the only job we do.
Check it yourself
Nothing here needs an account, a token or a conversation with us first.
Live compiler
Paste or type folio lines and watch the invoice build.
OpenFinished invoice
A compiled corporate invoice with tax lines applied.
OpenLive status
Real-time system checks and measured response times.
OpenTrust pack
Security architecture, CAIQ, DPA and the pentest scope.
OpenSimple, per room, per month
£1.70 to £2.00 per room per month, billed monthly in arrears on live rooms. No setup fee, no per-invoice charge, no minimum and no exclusivity. Evaluations are free: 60 days, read-only, one property or cluster, and you can end it at any time by revoking the token.
Send one folio set
One corporate account, one month, guest names removed. We compile it and send the finished invoice back within two working days. No contract, no IT time, no token.
Send a folio setApex Flow Technology Ltd · Company No. 17347345 · Registered in England & Wales