Xero
Invoices and payments, per legal entity
Your accountant keeps their ledger, your bank keeps its gateway, your doors keep their controller and your ads keep running. DeskOS sits in the middle and makes them agree with each other.
Somebody keys the month into Tally. Somebody exports leads out of the ad account. Somebody adds the new member to the door app, and somebody forgets to remove the old one. None of that work shows up in the accounts, and all of it is where the errors come from.
Invoices and payments, per legal entity
One way push into QuickBooks Online
Sales invoices and receipts, tax intact
Vouchers in the format your CA opens
IRN and signed QR on the invoice
Pay from the invoice link or the app
Cards in your own currency, reconciled

Phone access that follows the membership

Cloud doors, with the events pulled back
Face, finger and card readers
Captive portal WiFi, per location
Network login tied to the membership
Room bookings on the member calendar
Outlook calendars, the same one way sync
Subscribe from Apple Calendar or anything else

Marketplace demand, billed to the partner
Lead form leads with the campaign attached
Meta instant forms straight into the pipeline
Official Cloud API on your own number
Keep HubSpot at the front of the funnel
Metered printing on the printers you own

Quotas pushed to your PaperCut server
Cloud printing with no print server
Agreements out for signature, back stamped
Thousands of apps, no code in between
Workflows we host and run for you
Your numbers, read only, inside Claude
The same MCP server and permission fence
Accounting connections and payment gateways hang off the billing centre, not the campus. Two companies under one roof keep two sets of books and two settlement accounts, without running two systems.
Invoices leave DeskOS for your accounting system and do not come back changed. Leads and door events come in. Nothing is bidirectional merely because it could be, because that is how two systems end up quietly disagreeing.
You keep your own Xero subscription, your own Razorpay account, your own ad accounts. We connect to them, and we do not put a margin on another vendor invoice.
28 named integrations is a list, not a limit. Most of what operators ask us for turns out to be a webhook, a field mapping and an afternoon.
Read and write against your own workspace, scoped to the campuses that key is allowed to see.
New leads, paid invoices and bookings fire outward the moment they happen, to any endpoint you own.
For the systems that will never justify an adapter of their own. No code, and no ticket with us to wait on.
Your live numbers inside Claude, ChatGPT or Cursor, read only, fenced to what that person is allowed to see.
Yes. There is a REST API, outbound webhooks that fire on leads, invoices and bookings, and a Zapier connection for the things in between. There is also an MCP server, which puts your own data inside Claude, ChatGPT or Cursor as a read only assistant.
Connecting one is part of setting you up rather than a separate product to buy. You pay the other vendor directly for their own service, at their own price, and we take no cut of it.
Whichever one your accountant already opens on a Monday morning. The push is one way and the mapping is per legal entity, so the honest answer is that this choice belongs to your finance team rather than to us.
Yes, and it is the case the design is built around. The accounting connection, the payment gateway, the invoice numbering and the tax configuration all belong to the billing centre, so an invoice raised by one entity settles into that entity and files in its own books.
Tell us what it is. Most requests turn out to be a webhook and a field mapping, and the API plus Zapier covers a lot of ground on day one. Where a proper adapter is warranted we build it, and we will tell you plainly which of the two you are looking at.
A connection that stops working raises an alert on our side rather than failing silently on yours. Failed pushes are retried and stay visible as unsynced, so the gap is something you can see and clear instead of discovering it at year end.
Send us your accounting package, your gateway and your door controller. We will tell you what connects on day one, what needs a mapping and what does not exist yet.