Folios¶
PMS Dashboard → Folios shows guest folios from the hotel system and their route to being posted as a sales invoice.
The page is split into tabs by status, opening on Failed, so what needs action comes first.
The statuses¶
A folio cannot be posted until everything the posting needs is in place. The status says what is missing:
| Status | What to do |
|---|---|
| Awaiting | The folio has arrived and is waiting to be handled. Nothing to do. |
| Missing payment method | The folio's payment method is not set up. Create a mapping for it. |
| Not fully paid | The folio is not fully settled in the hotel system. Close it there. |
| Missing customer | There is no customer to invoice. Create or link the customer. |
| Missing AR ledger | The receivables setup is missing in the ERP. |
| Missing transactions | The folio holds no lines to post. |
| Missing mapping | A PMS code on the folio is not coded. See Daily journal. |
| Missing details | A required field is empty. |
| Missing configuration | The PMS integration is not fully set up. Contact support. |
| Posting | On its way to the ERP. |
| Posting error | The posting failed. You can try again. |
| Posted | Posted as a sales invoice. |
| Skipped | Deliberately left out. |
| Failed | Stopped by an error. |
Most statuses point at something to fix elsewhere — in the hotel system, in the ERP, or in the coding. Once that is in place, the folio moves on by itself.
Italian customers without a post code¶
For Opera, Cloud and Apaleo on a company in Italy, an Italian customer needs a post code before the folio can be posted — the ERP uses it to find the customer's region code. Without one, the folio shows Missing customer with a message naming the customer. Add the post code to the customer in the ERP, and the folio moves on by itself.
Post again¶
Where a folio shows Posting error, you can send it for posting again from the list once the cause has been corrected.
Detailed sales invoice¶
For Opera, Cloud and PEP, the PMS integration can be set to Generate detailed sales invoice PDF in the PMS settings. The invoice PDF then shows the folio's lines from the hotel system — charges and VAT lines, with their description and VAT rate — instead of the invoice's own line. That is the PDF kept in the sales archive and attached to the invoice in the ERP.
Posting is the same with or without the setting: the invoice still posts as a single line, and the total on the PDF is the posted total.
PEP invoices to companies¶
For PEP, invoices to companies (bill to company, LDB) are created from the Closed invoice
transactions report. Each line of the report becomes its own sales invoice:
- It is dated on the day the hotel issued the invoice.
- It goes to the customer with the line's account number. That is the account from the Direct bill company details report.
Have the hotel mail this report every day alongside All Transactions. Sending a report again does not create invoices twice.
The PMS settings have the option Use All Transactions for folio generation. Turn it on to create the invoices from All Transactions instead, at the moment the folio is closed. The Closed invoice transactions report is then ignored.
External document number¶
The invoice carries the hotel's own invoice number as its external document number in the ERP when the hotel system provides one: the fiscal bill number from Opera and Cloud, and the tax invoice number from OnQ. Otherwise the folio's number is used, as before.
Search¶
The search box finds folios across the tab, and you can switch between 20 and 50 rows per page.