Daily journal¶
PMS Dashboard → Daily journal shows the hotel's revenue transactions as they arrive from the hotel system. From here they are coded and moved to posting.
The tabs¶
| Tab | Contents |
|---|---|
| In progress | New transactions not yet handled. |
| Follow up | Transactions needing a decision before they can be posted. |
| Posted | Transactions sent for posting. |
| Rejected | Transactions that were refused. |
The columns¶
Each line shows the date, confirmation no., room no., market code, PMS code, hotel code, description, currency, cheque no., payment method, debit, credit and status.
The PMS code is the code the hotel system put on the transaction. It is what the coding is looked up by.
Coding with mappings¶
A mapping ties a PMS code to the account that transactions with that code post to.
| Action | What it does |
|---|---|
| Normal mapping | Creates a mapping that applies from now on to all transactions with that code. |
| One time mapping | Codes only the current transaction. The code is not remembered. |
Choose Normal mapping where the code should always post the same way, and One time mapping for a one-off entry.
Where no mapping exists for the code, the page says No mappings found, and the transaction cannot be posted until a decision is made.
New and changed mappings need approval
A mapping does not take effect immediately. It has to be approved under Changes for approval.
Posting¶
- Tick the transactions.
- Choose Move to posted.
Reset all the selected transactions clears the selection again.
Transactions with opposite sign swap debit and credit — used where the hotel system's sign does not match the posting.