Corporate invoicing, automated straight out of Mews
SwiftInvoicePro reads closed folios from the Mews Connector API, groups every corporate charge by the company that owes it, and issues one consolidated, VAT-correct invoice per company per period — instead of a finance team rebuilding them by hand from folio exports.
What it does
- Corporate folio aggregation. Room, restaurant, bar and incidental lines from every stay belonging to the same corporate account are collected across properties and periods, not invoice-by-invoice.
- One invoice per company. Negotiated rate codes and discounts are applied, VAT is calculated on the net, and the result is a single PDF plus a prepared accounts-payable email.
- Exceptions surfaced, not hidden. Folio lines that cannot be attributed to a company — missing PO, unknown account, split payer — land in an exception queue for a human, rather than being silently dropped.
- Reconciliation view. Per-property and per-company totals reconcile back to the Mews figures they came from, so finance can tie the invoice to the folio.
- Mobile checkout capture — sending a corporate guest their invoice at departure — is available on the same connection, but it is a side effect of the ingest, not the product.
How the connection works
You issue a Client Token and Access Token from your own Mews environment. They are encrypted at rest, scoped to your organisation only, and never shared between tenants.
Each organisation gets a dedicated webhook URL and its own signing secret. Mews posts BillClosed and AccountingItemCreated events there; nothing else is consumed.
Every event is SHA-256 HMAC verified before it is read, then written once against a unique event ID. Mews retries and duplicate deliveries cannot double-invoice.
Disconnecting purges both tokens, clears the enterprise and service IDs, and rotates the webhook secret so any event still in flight at Mews fails verification.
Configuration is validated live: a connection test calls configuration/get and services/getAll and reports the enterprise and stay service it resolved, so you know the credentials work before any folio moves.
See it work
Which numbers are measured, and which are not
Webhook acknowledgement latency, duplicate-event rejection and burst throughput are taken from real runs of our load and idempotency harnesses against the live endpoint. They are reproducible, and the method is documented in the trust pack.
Every savings, recovery and payback figure on our decks is modelled from public estate size and standard finance-team labour rates. None of it is a measured result until a shadow pilot measures it on your own estate — which is exactly what the 60-day pilot is for.
Security and review
The integration is read-only, per-tenant isolated, and covered by row-level security on every table it touches. Architecture, controls, incident response and a CAIQ Lite response are published rather than sent on request.
Run it alongside your current process
A 60-day shadow pilot connects read-only to one cluster of Mews properties. We produce the corporate invoices in parallel; your team keeps issuing theirs. At the end you have a measured comparison — value recovered, exceptions caught, hours returned — on your own data, with nothing written back to Mews at any point.