When an invoice is issued to a guest with the wrong amount, billing name or payment information, simply issuing another document is not enough. The PMS folio, fiscal e-document, collection, room status and accounting record are separate but connected layers. Correcting one while leaving another open can create duplicate revenue, an incorrect balance or an untraceable refund. This guide explains how to stop the error, choose the correct cancellation or correction path, reinstate check-out only when necessary and close every action with an auditable record.

What you will learn in this article
  • Voiding a PMS folio does not automatically cancel the e-Invoice or e-Archive Invoice at the Turkish Revenue Administration; verify both statuses separately.
  • Refunding money and correcting the revenue document are different actions; record the payment movement separately with the correct method and reference.
  • Do not erase the incorrect transaction; preserve the document number, reason, approving user and offsetting entry to create an audit trail.

Stop the process and identify the scope of the error

As soon as the error is noticed, prevent new collections, another invoice or a second check-out on the same folio. The agent should bring the reservation number, folio number, fiscal document number, document type, issue time, buyer details, currency, total amount, tax breakdown and payment movement together on one screen. Do not press cancel before determining whether the problem concerns only the billing name, one posting line, the entire invoice or the payment method.

The same error can have different outcomes in different systems. For example, an incorrect room charge may still be editable in the PMS folio while the fiscal document has already reached the private integrator or GİB. Mark the case as pending correction, assign an owner and query the fiscal document's actual status before promising a final outcome to the guest. A screenshot alone is not enough; link transaction IDs and timestamps to the case as well.

  • Reservation, folio and fiscal document numbers were matched.
  • The document's draft, sent, accepted, cancellation-pending or cancelled status was verified.
  • The incorrect field and the correct value were recorded clearly.
  • New transaction entry was temporarily restricted and an owner was assigned.

Separate the folio, fiscal document and payment movement

The folio is the operational record of room, food and beverage, tax, discount and payment movements in the guest's stay account. The fiscal document is an e-Invoice, e-Archive Invoice or another document type used by the property, produced with a legally compliant number and status. Collection is the movement of money through cash, card, bank transfer or an accounts-receivable account. Their amounts often match, but none is technically identical to the others.

Oracle OPERA Cloud's billing documentation treats posting adjustments, payment reversals, folio generation and credit bills as separate functions. A hotel system should likewise show users which layer they are changing. If 'Cancel invoice' only voids the PMS output, the system must warn that the e-document service requires a separate action. Similarly, a cash refund should not be treated as automatically correcting the incorrect invoice from a fiscal perspective.

  • Folio status and e-document status were shown in separate fields.
  • Collection and refund movements were separated from revenue lines.
  • Each system's transaction ID was linked to the shared case record.
  • The scope of the action was shown to the user before confirmation.

Control same-business-day folio voids

If the error is found on the same business day while the folio is still eligible, the PMS may allow it to be voided. Oracle's Void Folio documentation states that a folio can only be voided on the business date on which it was created, that some folios transferred to direct bill or accounts receivable cannot be voided, and that the document is retained with a Void status. This behaviour is not identical in every PMS; also check the property's end-of-day, accounts-receivable and fiscal-integration rules.

A void should not behave like an irreversible deletion. The user should first see the document, amount and reason, and an authorised role should provide a second approval. The system should preserve the original folio number, void time and user. If the incorrect posting is then corrected and a new document issued, cross-reference the old and new numbers. After end of day, or once the document is in folio history, a credit or correction workflow may be required instead of a same-day void.

  • Business date and end-of-day status were checked.
  • Accounts-receivable transfer and closed-period restrictions were checked.
  • A void reason and authorised approval were required.
  • The original document was retained with a void status rather than deleted.

Verify the fiscal e-document status with GİB or the integrator

Even when the folio is voided in the PMS, the submitted e-document must be tracked separately at GİB or the private integrator. GİB's e-Invoice Cancellation/Objection Portal explains that a cancellation or objection request is created with the invoice number and amount and, where applicable, the recipient approves the request. The e-Archive technical guide also defines reporting fields for cancelled invoices, including invoice number, cancellation date and total amount excluding tax.

The correct path can vary by document type, the buyer's taxpayer status, whether the invoice uses a commercial or basic scenario, and the time elapsed. This guide does not prescribe a fixed cancellation window; verify the current rule with the accounting owner, the private integrator and GİB's official channel. The system must not display a failed integrator response as cancelled; distinguish request created, awaiting counterparty approval and completed statuses.

  • Document type and scenario were verified.
  • The GİB or integrator response code was added to the record.
  • Cancellation requests and completed cancellations were tracked as separate statuses.
  • Regulatory and deadline verification was assigned to the authorised accounting owner.

Create a credit or correction document when cancellation is unavailable

If the document can no longer be cancelled directly, a linked credit or correction document may be required instead of removing the original record. Oracle's historical folio screen retains generated folios and, when configured, can generate a Credit Bill from that record. The credit can be linked to selected lines or all transactions on the original folio, with explanation and reference fields used for negative postings.

A correction may be partial rather than total. If only one minibar line is wrong, reversing the correct room charge is unnecessary. The system should check the remaining eligible amount, previously issued credit documents and the original document number. Before issuing a new document, recalculate the tax base, VAT, accommodation tax, discounts and exchange rate and show the user an old-versus-new comparison. Confirm the final document type and accounting entry with the property's financial adviser.

  • The correction was linked to the original folio and document number.
  • The full or partial correction scope was selected line by line.
  • Tax, discount, currency and exchange rate were rechecked.
  • Previously credited and remaining correctable amounts were verified.

Record the refund separately from the document correction

When money is returned to the guest, process the refund as a separate payment movement using the original collection method and the property's procedure. A cash refund creates a cashier outflow, while a card refund requires the reference and status returned by the payment provider. Oracle's billing documentation shows a payment reversal as a new offsetting transaction for the same amount and can require a reference or explanation for negative payments. This preserves the original collection and links the refund to it.

A cash refund should not appear as a new revenue line on the sales invoice. Conversely, taking money out of the cashier alone does not correct the incorrect fiscal document. Record the refund amount, method, recipient, approving user and receipt, and complete the folio balance and fiscal-document correction separately. Method changes, such as returning a card payment in cash, should require authorisation and a reason because they create fraud and reconciliation risk.

  • The refund was referenced to the original collection.
  • The cash, card or bank-transfer method was posted to the correct cashier account.
  • The refund was not added to the invoice as sales revenue or a new charge.
  • The folio balance, cashier/POS total and bank result were verified separately.

Reinstate check-out only when necessary

Correcting an invoice error is not always a reason to show the guest as in house again. Reinstate check-out only for defined cases such as reposting a room charge, correcting an erroneous departure or completing a required action on an open folio. Oracle explains that a checked-out reservation can be reinstated on the same departure date before end of day, that this affects room inventory and that the system warns when the room has been assigned to another guest.

Before reinstatement, check the room status, new reservation, housekeeping task and key access. If the purpose is only a financial correction, do not return the room to inventory as though it were genuinely occupied. Where the PMS supports historical-folio or post-stay processing, it is safer to correct the record without changing the operational stay status. If reinstatement is required, check the guest out again after the correction and keep both status changes in the same case record.

  • The operational reason and authorised approval for reinstatement were recorded.
  • It was confirmed whether the room had been assigned to a new guest.
  • The effect on housekeeping, inventory and key access was verified.
  • Check-out and room status were completed again after the correction.

Create an audit trail and shift checklist

The answer to who did what on an invoice-correction screen cannot be reconstructed later; capture it during the action. Oracle's adjustment-reason-code approach supports predefined reasons such as duplicate charge, error, overcharge or manager discretion. In addition to free text, keep the standard reason code, explanation, approving role, before-and-after values, document links and integrator response in an immutable log.

Before closing the shift, list open corrections and hand over e-documents awaiting cancellation, incomplete refunds, reservations requiring a new check-out and documents awaiting accounting approval. The daily report can track reason distribution as well as the gross void amount. Repeated errors in billing name, tax number or price should not be dismissed as staff mistakes; reduce them at source with required fields, preview, second approval and customer-profile verification.

  • Standard void and correction reasons were defined.
  • Before-and-after values and the user's timestamp were logged.
  • Open e-document, payment and check-out tasks were handed to the next shift.
  • Validation and authorisation rules were updated for recurring errors.
Short answers

FAQ

Does voiding the folio in the PMS also cancel the e-Invoice?

Not always. The PMS folio and the fiscal document at GİB or the private integrator can have separate statuses. Query the e-document response after voiding the folio, and do not confuse request created with cancellation completed.

Must the guest's check-out always be reinstated after an incorrect invoice?

No. If the correction can be made through the fiscal document or historical folio, there is no need to change room inventory. When reinstatement is required, check end of day, room assignment and housekeeping impact, then complete check-out again after the correction.

Should a cash refund appear as a separate line on the invoice?

A cash refund is a payment or cashier outflow, not new sales revenue. Record it separately with a reference to the original collection, and complete the fiscal document's cancellation or correction in its own workflow. Confirm the document type with the accounting owner.

Sources and updates

Operational recommendations should be adapted to the property's own conditions. Information about PMS and e-document workflows was checked against the official documents below on 21 September 2026.