Visma eAccounting Pro
Importing or exporting customer records
You can in an efficient and easy way update your customer records by using the export and import functionality in Visma eAccounting Pro. To import the customer records, you first have to use a comma separated file, called a CSV file. Read more about how to get a correctly formatted CSV file in the general topic Import or export records (CSV file).
In this topic, we have put together a list of field explanations for importing and exporting customer records, which explains how to enter the data in the CSV file so that the import of your customer record is problem-free. When you have a correctly formatted CSV file for your import, use the field explanations below as a guide when you enter the customer data into the CSV file.
For the import to be successful to Visma eAccounting Pro, it is important that each column has the correct header, is in the correct order, uses correct coding, and has a value in the mandatory fields. The column header represents the fields you find when you create a new customer in Visma eAccounting Pro.
Add or update customer register
In order to update your customer register, you export a CSV (Excel) file, update the customer register and then import the register again. Please note that if a value is unique (for example a customer number), the value will not change even if it has changed in the CSV file. If you make changes to a unique value such as the customer number, a new customer will be added instead when you import the file, and leave the original customer unchanged.
Delete customers
It is not possible to delete customers from a register by exporting and importing. Rows that are deleted from an exported file and that later is imported into Visma eAccounting Pro again will still be shown in Visma eAccounting Pro. If you want to delete a customer you do this in Visma eAccounting Pro.
Default value
There are fields that are not mandatory but still have a value by default. If you add rows to a CSV file but do not add values before you import the file into Visma eAccounting Pro, the program will add the default value for you.
The field explanations below provide more information on which fields need to be included for the import to work, as well as how to code them. It is important that you read through these to ensure correct coding.
Certain fields in the list are mandatory. These must be included to be able to import to Visma eAccounting Pro.
| Field name in file | Field name in Visma eAccounting Pro | Value in file | Comment |
|---|---|---|---|
| IsActive | Active or not |
False for inactive |
|
| CustomerNumber | Customer no | Mandatory | |
| Name | Customer name | Mandatory | |
| IsPrivatePerson | Customer type | True for private individual False for company |
Requires code |
| Corp.ID no. | Corporate identity no | ||
| InvoiceAddress1 | Address | ||
| InvoiceAddress2 | |||
| InvoicePostalCode | Postcode | Mandatory | |
| InvoiceCity | City | Mandatory | |
| InvoiceCountryCode | Country | Mandatory and requires code | |
| VatNumber | VAT no | ||
| Telephone | Phone no | ||
| MobilePhone | Mobile no | ||
| EmailAddress | |||
| CcEmailAddresses | E-mail cc address | ||
| WwwAddress | Website | ||
| Note | Notes | ||
| ReverseChargeOnConstructionServices |
Construction sector, VAT reverse charge (Only shown if activated) |
True for active False for inactive |
|
| SalesDocumentLanguage | Sales document language | nl or en |
nl for Dutch en for English |
| ContactPersonName | Name | ||
| ContactPersonEmail | |||
| ContactPersonPhone | Phone no | ||
| ContactPersonMobile | Mobile no | ||
| TermOfDeliveryName | Terms of delivery | ||
| DeliveryMethodName | Delivery method | ||
| DeliveryCustomerName | Delivery address when different from postal address | ||
| DeliveryAddress1 | Delivery address | ||
| DeliveryAddress2 | |||
| DeliveryPostalCode | Delivery postcode | ||
| DeliveryCity | Delivery city | ||
| DeliveryCountryCode | Delivery country | Requires code | |
| TermsofPaymentCode | Terms of payment | Requires code | |
| CurrencyCode | Currency | Requires code | |
| PayToAccount | Pay to account | Requires code | |
| DiscountPercentage | Customer discount | Value between 1-100 | |
| CustomerLabels | Customer labels | If several per customer, separate by semicolon, example: gold; silver | |
| Category | Member or not | customer or member |
customer for customers member for members Only for non-profit organisations and economic associations |
| Iban | IBAN | Mandatory when direct debit extension is active. | |
| IsDirectDebitEnabled | Direct debit |
False for inactive |
Only applies to direct debit extension. |
| MandateId | Mandate ID | Only applies to direct debit extension. Mandatory, max. 35 characters. | |
| MandateType | Mandate type | B2B or CORE | Only applies to direct debit extension. Mandatory. |
| SequenceType | Sequence type | RCUR for Recurring FNAL for Recurring, final OOFF for One-off |
Only applies to direct debit extension. Mandatory. |
| Bic | BIC | Only applies to direct debit extension. Only mandatory when customer country is in non-EEA SEPA area. | |
| SigningDate | Signing date | Use date format d-m-yyyy | Only applies to direct debit extension. Mandatory. |
| EndDate | End date | Use date format d-m-yyyy | Only applies to direct debit extension. Optional. |
| LatestDirectDebit | Latest direct debit | Only applies to direct debit extension. Only for export purposes, updates through import are being ignored. |
To be able to import different payment terms, they must be coded as specified in the table below.
| Payment terms in program | Code in CSV file |
|---|---|
| Invoice date +0 days | 0 |
| Invoice date +7 days | 170 |
| Invoice date +10 days | 140 |
| Invoice date +14 days | 70 |
| Invoice date +15 days | 130 |
| Invoice date +20 days | 80 |
| Invoice date +21 days | 60 |
| Invoice date +30 days | 110 |
| Invoice date +45 days | 180 |
| Invoice date +60 days | 160 |
| End of month from invoice date +10 days | 20 |
| End of month from invoice date +14 days | 120 |
| End of month from invoice date +15 days | 150 |
| End of month from invoice date +20 days | 10 |
| End of month from invoice date +21 days | 30 |
| End of month from invoice date +30 days | 100 |
| End of month from invoice date +45 days | 190 |
| End of month from invoice date +60 days | 40 |
| Cash payment | 90 |
To load country codes, they must be entered according to the ISO standard. You can find the codes to be used at countrycode.org in the ISO Country Codes column. The codes must be specified with two letters.
Example: Brunei = BN
To load currency codes, they must be entered according to the international standard. The codes which must be used can be found at nationsonline.org. The codes must be specified with three letters.
Example: Euro = EUR
Related topics
|
Import or export records (CSV file) |
|
Importing or exporting article records |
|
Importing or exporting supplier records |
|
Importing or exporting chart of accounts |
Searchword: Bulk update