Post charges to Opera PMS
Day-to-day workflows for posting services, packages, memberships, gift cards, and retail charges from Zenoti to a hotel guest's Opera folio. Covers the standard charge flow, walk-in guests, cross-center posting, editing, refunds, and end-of-day reconciliation.
On this page
- Before you begin
- Post a charge to an Opera folio
- Post a charge for a walk-in guest
- Cross-center posting
- Single-line vs multi-line posting
- Edit a posted charge
- Refund a posted charge
- Handle a failed posting
- Reconciliation
- Tips
Before you begin
Permission: You need front-desk billing permissions to post charges to Opera.
- Oracle Opera PMS must be configured and connected to Zenoti. See Connect Oracle Opera PMS.
- For guest postings: the guest must have an active reservation and in-house status in Opera.
- For walk-in postings: the center must have Post Non Room Charge to PMS enabled with PM rooms configured.
- For cross-center postings: participating centers must share the same GroupCode.
Post a charge to an Opera folio
- Open the POS (Point of Sale) window for the appointment or invoice.
- Review the invoice items and totals.
- In the Collect Payment section, select the custom Opera payment method (for example, Charge Room).
- Enter the guest's Room Number, or search by guest name to find the folio.
- Zenoti queries Opera and displays the guest's name, room, and folio balance for confirmation. If your integration is Opera Cloud and the reservation has accompanying guests, select the correct guest from the list.
- Confirm the charge details.
- Select Post Charge.
- Zenoti sends the charge to Opera via the configured integration (HTNG SOAP or Opera Cloud REST).
- The invoice closes in Zenoti, and the charge appears on the guest's folio in Opera with the Zenoti invoice number as the posting reference.
Post a charge for a walk-in guest
Walk-in guests (not checked in at a hotel room) can still be billed to Opera when your center has Post Non Room Charge to PMS enabled.
- In the POS, collect payment from the guest using a standard method (Cash, Card, or Cheque).
- Select the custom Opera payment method (for example, Charge Room).
- Zenoti routes the posting to the Payment Method (PM) room configured for that payment type β for example, Cash β PM room 9000, Card β PM room 9001.
- The charge appears on the PM room's folio in Opera. The hotel's auto-balancing reconciles the PM-room postings against end-of-day payment totals.
See Configure payment mapping for walk-in guests for PM-room setup.
Cross-center posting
When centers share a GroupCode, a guest staying at one hotel property can have charges posted to her folio from any participating center.
Example. Alice stays at Property A (a hotel with a connected spa). She receives a spa service at Property B (a sister spa center that shares Property A's GroupCode). The front desk at Property B posts the charge β it lands on Alice's folio at Property A. At checkout, Alice settles the folio at Property A with her chosen payment method.
Revenue attribution
This is a frequent source of confusion. Cross-center posting separates where the charge is posted from where the revenue is recognised:
| Dimension | Attributed to | How it flows |
|---|---|---|
| Opera posting (charge) | Host property (Property A) | Opera folio reflects the charge against Alice's room. |
| Zenoti invoice / service revenue | Serving center (Property B) | The Zenoti invoice is created at Property B and shows in Property B's revenue reports. |
| Guest payment at checkout | Host property (Property A) | Settled inside Opera. Does not flow back to Property B as a payment against the Zenoti invoice β the invoice is already closed in Zenoti at post time. |
If your finance reporting combines properties, confirm with your accounting team whether they want to reconcile at the Opera level (folio settlements per property) or the Zenoti level (service revenue per center).
Single-line vs multi-line posting
Two center-level settings change how Zenoti packages line items for Opera. They are independent β neither overrides the other.
| Single-line posting | Post non-room charges | Result |
|---|---|---|
| Off | Off | Room charges post per line item (service cost and tax on separate lines). Walk-in charges are not posted to Opera. |
| On | Off | Room charges post with cost and tax aggregated per charge (one Opera line per charge). Walk-in charges are not posted. |
| Off | On | Room charges per line. Walk-in charges post to the configured PM rooms. |
| On | On | Room charges aggregated per charge. Walk-in charges post to PM rooms. |
Change these settings only in coordination with your hotel finance team β they affect how revenue appears in Opera's reporting and how taxes are grouped. In most deployments, leave single-line posting off unless your Opera property is configured to aggregate tax at the transcode level rather than the line level.
Edit a posted charge
Whether you can edit a posted charge depends on the invoice state.
Open invoice
If the invoice is still open (not yet closed in Zenoti):
- Open the invoice in the POS.
- Edit the amount, change the room number, or remove the charge.
- Save.
Zenoti sends the updated posting to Opera. The original posting on the folio is replaced.
Closed invoice
Closed invoices cannot be edited directly β this is a system-wide rule enforced by Zenoti to preserve audit integrity. To correct a closed invoice:
- Void the original invoice. Voiding posts a reverse transaction to Opera, removing the charge from the guest's folio.
- Create a new invoice with the corrected amount, provider, or room.
- Post the new invoice to Opera.
The guest's folio now shows the reverse (negative) posting from the void, plus the new correct posting.
Refund a posted charge
- Open the invoice in Zenoti.
- Select Refund.
- Choose the refund mode and confirm the amount.
- Zenoti posts a reverse transaction to Opera through the same posting flow with the void flag set. The refund appears on the Opera folio as a negative posting with the same transcode as the original charge.
- The Zenoti invoice now shows the refund entry.
What you will see in Opera
- Opera folio: a negative line with the same transcode as the original charge.
- Opera reporting: the net charge for the period drops by the refund amount on the next report run. No separate reconciliation step is required on the Opera side.
- Zenoti: the invoice shows the refund with an icon indicating the reversal.
Opera does not push a separate refund event back to Zenoti β the Zenoti invoice is the record of the refund.
Handle a failed posting
Zenoti surfaces the failure reason in the POS. Common failure modes:
| Symptom | Cause | Resolution |
|---|---|---|
| Room not found. | Wrong room number, or Opera has not sent the reservation to Zenoti yet. | Verify the room number with the front desk. If it is correct and still missing, the reservation may not have synced β ask the hotel to re-send or wait a minute and retry. |
| Guest is checked out. | The guest's reservation has been closed in Opera. | The charge can no longer post to that folio. Collect payment from the guest directly and use a non-Opera payment method. |
| Opera is unreachable. | Network issue between Zenoti and Opera, or Opera is down. | Retry after a few minutes. If the issue persists, contact the hotel's Opera administrator to confirm Opera is online. Cached charges do not automatically retry β you must re-post once Opera is reachable. |
| Credit limit exceeded. | The guest's folio has hit a credit limit in Opera. | Front desk at the host property must raise the limit or collect a deposit. Retry after the limit is adjusted. |
| Folio closed. | The guest's folio has been settled and closed in Opera even though the guest is still in-house. | The hotel needs to reopen the folio or create a new one. Post again after Opera confirms. |
| Authentication error. | Opera service account or OAuth token has expired. | Check integration health. If the credentials are rejected, re-enter them on the PMS Integration setup page (see Connect Oracle Opera PMS). |
If a posting fails during a cross-center flow, the charge still lives in Zenoti as an unposted invoice β no data is lost. Retry from the invoice once the underlying issue is resolved.
Reconciliation
Reconciling Zenoti postings against Opera end-of-day reports catches discrepancies early.
Zenoti-side source of truth
Run the Collections by Invoices report, filtered to the Opera custom payment method, for the period you want to reconcile. The report lists every invoice that was posted to Opera with:
- Invoice number (used as the posting reference in Opera)
- Amount and tax breakdown
- Posted timestamp
- Status (Posted, Failed, Voided)
Opera-side source of truth
The hotel's Opera administrator pulls the corresponding Opera transaction or posting report. Exact name varies by Opera deployment β ask your hotel's Opera consultant for the specific report used for PMS reconciliation.
Match on posting reference
Match rows on the Zenoti invoice number. Every Zenoti posting carries the invoice number in Opera's posting reference field. Investigate any Zenoti posting that does not appear in Opera or that appears with a different amount.
Recommended cadence
Reconcile daily at close. Any Zenoti posting that does not match the Opera report within 24 hours should be investigated using the PMS posting audit log in Zenoti.
Tips
- Always confirm the guest's room number before posting to avoid charges landing on the wrong folio.
- For cross-center postings, warn your front-desk staff that the guest will settle at the host property, not at the serving center.
- Keep a test reservation on your Opera property for training and troubleshooting. Use it after any Opera update to verify posting still works.
- Review the PMS posting audit log at least weekly β failed postings that went unnoticed at POS time will surface there.