These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect the PMS and operating evidence your hotel already uses.
- Property management system
- Reservations and staysin and out
- Room status and preferencesin and out
- Guest financial activityPayments · in
- Property operations
- Purchasing and receivingin and out
- Kitchen and stock observationsLots · in and out
- Operational evidencein
- Finance and migration
- Bank and payment evidencein
- Accounting mappingsAccounts · in and out
- Opening dataStockEvents · in and out
- Agents
- Your agentWorks within the permissions you assign
Property management system
- Reservations and stays. Configure reviewed mappings for property, room type, reservation, room assignment and actual stay state. Local requests remain pending until a verified PMS outcome establishes what happened.
- Room status and preferences. Exchange supported cleaning or readiness information while preserving occupancy, access instructions and unresolved discrepancies. Vendor-specific room restriction meanings need an explicit mapping.
- Guest financial activity. Bring actual source charges, deposits, credits and payments into a controlled accounting review. Keep external event and component identities so an imported summary cannot repeat its underlying detail.
Property operations
- Purchasing and receiving. Use reviewed imports or interfaces for supplier and delivery evidence. A supplier document does not establish an actual accepted receipt or authorize payment by itself.
- Kitchen and stock observations. Capture real quantities, source lots and applicable date or condition evidence. A planned recipe or room charge does not prove ingredient consumption. No connected sensor or kitchen device is included merely by naming this workflow.
- Operational evidence. Retain approved documents and actual observations with the work they support. Configure access to guest and staff details according to the task rather than copying unrestricted source payloads into every view.
Finance and migration
- Bank and payment evidence. Reconcile actual settlement to the selected clearing sources. A PMS payment report and a bank import must not both create the same bank movement.
- Accounting mappings. Review source transaction classification, company accounts and currency treatment before a financial packet can post. Unsupported or incomplete mappings remain visible for finance review.
- Opening data. Reconcile source identities and remaining balances at an agreed cutoff. Historical stays, charges and stock events provide nonposting context for the approved opening balances; importing them cannot execute them again.
How connections are governed
service accounts, audit, pausingEach operational connection must be configured and verified during implementation. Supported commands and outcomes depend on the chosen PMS and the customer’s reviewed mapping; no named connector is installed by this website.
Connections retain source identity, content revision and actual occurrence time separately from receipt time. Duplicate content returns the established result, while conflicting or out-of-order updates require reconciliation. An uncertain response remains unresolved until authoritative evidence is available. Approval and successful transport do not stand in for an actual booking, stock movement or payment.
The API is one more client of the same interface. Your AI assistant →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Show my property's arrivals with unresolved PMS changes.
› Prepare the room-turnover inspection queue from completed work.
› Explain the difference between PMS tender activity and bank settlement.