Visma eEkonomi Smart
Import transaction file
In Cash and bank, if you click the arrow next to the green button in the top right of the window, you will see the option Import transaction file. This option is useful if you want to import a file with giro transactions from your bank and unpack these, but also if you are working with ROT and RUT and have downloaded a decision file with transactions from . The transactions in the decision file are then unpacked and can be matched against your sales invoices. Read more about these two file imports below.
Please note that this topic is not relevant if you have a bank integration with Nordea, Danske Bank, Handelsbanken, Sparbanken, Swedbank or SEB (when using two-step verification). The transactions will automatically be specified to the same level of detail as when importing a giro transaction file, when Visma eEkonomi Smart synchronises the bank transactions between the program and the bank.
On the bank statement the giro payments are shown as a lump sum for each day. By importing a transaction file from the bank you can get all transactions included in the lump sum specified. You import the file with specified giro transactions regardless of whether you have added the bank transactions manually or pasted the bank statement from the bank. You can also use the file if you have bank integration with Swedbank or Sparbanken.
The transaction files you download from the bank to import into Visma eEkonomi Smart should be in the LB or BgMax (20, 21 or 70) formats. When the files have been downloaded they will have the file extension .txt.
- Choose Cash and bank.
Please note that before importing the file you should add the bank transactions from your bank statement in Visma eEkonomi Smart. The file only specifies already registered transactions.
- Click the arrow next to New bank transaction and select Import file from bank.
- Upload one or several transaction files. You can also drag and drop the file anywhere in the Cash and bank window.
When the upload has finished, the bank transactions that match accounting transactions are automatically posted and listed in the view Bank transactions this period. Transactions that need to be manually matched or posted to the ledger are found in the view All unreconciled bank transactions.
Please note that payments made from your bank giro account will be specified in the transaction file only when you have sent the payments using a so-called LB file. Read more in the topic Send purchase invoices via payment file.
If you do not have a bank integration, please note that before importing the decision file from the Visma eEkonomi Smart. The file only specifies already registered transactions.
, you should add the bank transactions from your bank statement inIn order to import a ROT/RUT decision file with transactions, you first need to log in to the Visma eEkonomi Smart. When the file is imported, transactions that are included in the lump sum become specified. You can import the file regardless of whether you have added the bank transactions manually or pasted the bank statement from the bank. You can also use the file if you have bank integration.
and download the file. When you have downloaded your decision file, it is time to import the file intoIf you want to register the payments manually instead, follow the steps under "Sales invoice - fully paid" in the topic Match incoming payments manually.
The transaction files you download from the Visma eEkonomi Smart should be in the .json format.
and import into- Choose Cash and bank.
- Click the arrow next to New bank transaction and select Import file from bank.
- Upload the decision file. You can also drag and drop the file anywhere in the Cash and bank window.
When the upload has finished, you will get suggestions of which bank transactions that match accounting transactions in the view All unreconciled bank transactions.
- Select Post to ledger.
Related topics
Work with ROT/RUT deduction | |
Match incoming payments manually | |
Match outgoing payments manually |
Work smarter
This is how you can work most effectively