Import and export PMS codes¶
An integration's PMS codes can be exported to a file and imported from one. Use it to create many codes at once, and to move or copy the codes from one hotel or company to another.
Both are under PMS Dashboard → Settings: open the integration and choose the PMS Codes tab. The Export and Upload buttons are at the top of the page.
Move PMS codes to another company¶
- Select the company the codes come from and open the integration under PMS Dashboard → Settings.
- Choose the PMS Codes tab, click Export, choose All PMS codes and click Export.
- Select the company the codes go to and open its integration.
- Choose the PMS Codes tab, click Upload and choose the exported file.
- Choose whether the codes are added to the existing ones or replace them, and whether they are imported as Active. Click Import.
The file holds neither hotel code nor company. Both are taken from the integration the file is imported into.
Check that the accounts, VAT groups and dimension values in the file also exist in the new company's ERP system. The import checks the file's format, not whether the accounts exist.
Copy PMS codes from another hotel in the same company¶
Within one company the codes can be copied directly, without going through a file.
- Open the integration the codes go to and choose the PMS Codes tab.
- Click Upload and turn on Copy from another integration.
- Choose the integration the codes come from.
- Optionally tick further integrations to import the codes into as well.
- Under Overwrite dimension values with the integration's own, tick the dimensions the codes should take from the integration they are copied into, such as the hotel's department. The ticked dimensions get the value set on each target integration, or none where it has none; the other dimensions keep the copied code's values.
- Choose whether the codes are added to the existing ones or replace them, and whether they are imported as Active. Click Import.
Only the active codes are copied. Codes awaiting approval and one-time mappings stay in the integration they come from. Where a code is being changed, its active version is copied.
Codes can only be copied between integrations with the same PMS type, and the lists show only those.
Export¶
Export offers two choices:
| Choice | The file holds |
|---|---|
| All PMS codes | The integration's codes as the tab lists them, without one-time mappings. |
| An empty file | The header row alone, for filling in new codes. |
The file is a semicolon-separated CSV file, which Excel opens directly.
The file format¶
The first row is the header row. Each column is read by its name, so the columns may stand in any order and an optional one may be left out. The export writes them in this order:
| Column | Required | Content |
|---|---|---|
| PMS CODE | Yes | The code from the hotel system. |
| MARKET CODE | Yes | The market code, or * for all market codes. |
| ACCOUNT TYPE | Yes | G/L Account, Customer or Vendor. |
| ACCOUNT NO | Yes | The account posted to. |
| BALANCE ACCOUNT TYPE | Yes | G/L Account, Customer or Vendor. |
| BALANCE ACCOUNT NO | Yes | The balancing account. |
| VAT BUS POSTING GROUP | No | VAT business posting group. |
| VAT PROD POSTING GROUP | No | VAT product posting group. |
| OPPOSITE SIGN | No | 1 for opposite sign, otherwise 0. |
| PAYMENT ACCOUNT | No | 1 or 0. |
| CALCULATE GROSS AMOUNT | No | 1 or 0. |
| IGNORE TRANSACTION | No | 1 or 0. |
| POST AGGREGATED | No | 1 or 0. |
| USE VAT ACCRUALS | No | 1 or 0. |
| VAT ACCRUALS ACCOUNT | No | VAT accruals account. Required when VAT accruals are used. |
| POSTING G/L ACCOUNT | No | The G/L account of a customer or vendor on the account side. |
| BALANCE G/L ACCOUNT | No | The G/L account of a customer or vendor on the balancing side. |
| one column per dimension | No | The dimension's value, headed by the dimension's code. |
After the fixed columns comes one column per PMS dimension of the company, in the order of its dimension setup, each headed by the dimension's code, such as Department or CostCenter. On import a dimension column is matched by that code or the dimension's name, so a file moves to a company that orders its dimensions otherwise and each value still lands on its own dimension. A column that names a dimension the company does not have is refused.
A code marked as a payment account is one a card payment is posted on, and card settlement reports are matched against its postings. When you save or import such a code, the hotel's earlier postings of it are added to the matching too, so a code mapped after its journals were read is still matched.
A card taken on a separate terminal reaches 2Click Accounting without its card type. The card is then read from the description the payment's code has in Opera, such as "American Express Card Manual" or "Visa Card Manual", so an Amex settlement line is only matched with Amex payments. A code that several cards share in Opera, such as "Visa/Mastercard", is matched without a card type.
An empty yes/no column means no. Each combination of PMS code and market code may appear only once.
The import reads CSV files separated by semicolons, commas or tabs, and Excel workbooks (.xlsx and .xls). An older file with numbered dimension columns (DIMENSION 1, DIM1 and so on) can still be imported: its dimensions are read by their number in the company's dimension setup.
Leading zeros
Excel removes leading zeros from a number, so the account 0010 becomes 10. Format the account
number columns as text before typing in them, or open the CSV file through Data → From
Text/CSV and choose text as the data type.
Import¶
- Click Upload on the PMS Codes tab.
- Click Choose file and choose the file.
- If the company has other integrations with the same PMS type, you can tick those the codes should be imported into as well.
- Choose what happens to the codes the integration already has with the Replace the existing codes switch:
- Off: the existing codes are kept and the imported ones are added. A PMS code and market code that already exist are refused.
- On: all of the integration's codes are deleted and replaced by the imported ones. One-time mappings are kept.
- Tick Import as Active if the codes should take effect at once.
- Click Import.
When you replace, you are asked to confirm that the existing codes are deleted. They cannot be restored, so export them first if you may need them again.
When importing into several integrations, the codes are imported into all of them or none. If, when adding, a code already exists in just one of them, nothing is imported, and the problem names that integration's hotel code.
Pending approval or Active¶
Without Import as Active, the codes are imported as Pending creation. They are used only once they are approved under Changes for approval.
With it, the codes are used at once, and the approval log shows them as approved by you. Transactions that were waiting for a mapping are posted again.
When the file is refused¶
The import checks the whole file before anything is saved. If anything is wrong, nothing is imported, and the window lists every problem with its row and column, for example:
- The columns are in the wrong order, or a column is missing.
- A required field is empty.
- An account type is not
G/L Account,CustomerorVendor. - A yes/no column holds something other than
1or0. - A PMS code and market code appear twice in the file, or already exist in the integration.
Correct the file, choose it again and click Import. The row numbers match the rows in Excel.