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.
Blocked accounts are not listed. A receivables or payables account is chosen as the G/L account of a customer or vendor, as described below. The information mark beside the field says the same.
A mapping that posts to a customer books the customer's own receivables account. Where the customer has none in your ERP, Receivables account for customers without their own from the hotel's PMS settings is used. The field appears only where your ERP needs a receivables account on a customer line. It lists the ERP's receivables accounts first, then every other account a journal line can book.
Where your ERP needs a G/L account on a customer or vendor line, as Exact Online does, a mapping whose account or balancing account is a customer or vendor also shows a G/L account for that side. Choosing the customer or vendor fills it with their own account from the ERP, and you can pick another of the ERP's receivables accounts for a customer, or payables accounts for a vendor, or any other account a journal line can book. A receivables or payables account leaves an open item on the customer or vendor; any other account only names them on the line. Left empty, the line books as described above.
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.
In your ERP, each posted line's description reads
when;PSP reference;authorisation code;booking reference;check no.;card;room;currency;text. when is the
payment time as yyyyMMddHHmmss, or the day as yyyyMMdd where only the date is known. These are the values
the card payment matching uses, so the line can be found again from a payment report or a bank statement.
An empty value leaves its place empty (;;), and a long text is shortened at the end.
With Dynamics 365 Finance and Operations, posting writes the transactions to a general journal and stops there: post the journal in Finance and Operations. The transaction's status names the journal and its number. The journal is the one chosen as Transactions journal on the ERP journals tab of the hotel's PMS settings, or the company's first daily journal when none is chosen. The same tab holds a Statistics journal and a Folios journal for the hotel.
A rejected transaction always shows why it was rejected in its status.