|
|
| (11 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == Ledger Cardline - Bulk Import Feature == | + | =This Content Has Moved House= |
| | + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | The Emersion system has a feature which permits you to bulk import cardlines into the system.
| + | We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to out new home. |
| | | | |
| − | This is an add-on feature - if you do not have access to it and would like to use it, please contact Emersion Sales.
| + | [https://resources.emersion.com/display/EKB/Cardlines Take me to the Emersion Knowledge Base article] |
| − | | |
| − | The format (in CSV) for a ledger cardline file is as follows;
| |
| − | | |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ! TRANSACTION_DATE !! ACTUAL_VALUE !! TAX_AMOUNT !! DESCRIPTION !! LEDGER_CODE !! ACCOUNT_ID !! SERVICE_ID !! BILLING_TYPE_ID !! COVERS_FROM !! COVERS_TO
| |
| − | |-
| |
| − | | 2010-12-30 || 10 || 1 || "Test Transaction, Blah" || LEDGER_CODE || 111377 || 171519 || 1 || 2010-12-30 || 2010-12-30
| |
| − | |-
| |
| − | | 2010-02-01 || 33 || 3 || "Blah Transaction, Blah" || || 111377 || || 1 || 2010-12-30 || 2010-12-30
| |
| − | |-
| |
| − | | 2010-12-30 || 22 || 2.2 || Test Transaction || MY_TRANSACTION || 111683 || 173038 || 2 || 2010-12-30 || 2010-12-30
| |
| − | |}
| |
| − | | |
| − | [[File:Sample Cardline Import.csv|thumbnail|Cardline Sample Import File]]
| |
| − | | |
| − | The fields are described below;
| |
| − | * TRANSACTION_DATE - This field is mandatory and must be in the format of YYYY-MM-DD
| |
| − | | |
| − | * ACTUAL_VALUE - This field represents the EX TAX portion of your charge. It is mandatory and
| |
| − | must be rounded to two decimal places.
| |
| − | | |
| − | * TAX_AMOUNT - This represents the tax portion of your charge. Can be zero. Is mandatory and
| |
| − | must be rounded to two decimal places.
| |
| − | | |
| − | * DESCRIPTION - This is the description for the charge that will appear on the customers invoice
| |
| − | or service information record. It is mandatory and must be less than 255 characters.
| |
| − | | |
| − | * LEDGER_CODE - This is the a ledger code from the Emersion system. You can find a list of the
| |
| − | available ledger codes in the ledger code (mapping) report -
| |
| − | https://cumulus.emersion.com.au/report/generic/view/1001 - Please ensure you use the ledger code NAME,
| |
| − | not the MAPPING_NAME or SIMPLE_CODE.
| |
| − | | |
| − | * ACCOUNT_ID - The account you wish to have the cardline assigned against. This is a mandatory field.
| |
| − | | |
| − | * SERVICE_ID - The service ID you want this charge to be assigned against. This is not mandatory and has no default.
| |
| − | | |
| − | * BILLING_TYPE_ID - Whether the charge (or credit) you are creating is representative of an advance
| |
| − | charge (1) or an arrears charge (2). It is not mandatory and defaults to 1 (advance).
| |
| − | | |
| − | * COVERS_FROM - The start date for the period of which the charge (or credit) covers. This is mandatory
| |
| − | and must be in the format of YYYY-MM-DD
| |
| − | | |
| − | * COVERS_TO - The end date for the period of which the charge (or credit) covers. This is not mandatory,
| |
| − | will default to the covers from and must be in the format of YYYY-MM-DD
| |
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to out new home.
