Import Viseca statements into bexio with importly
importly recognizes Viseca statements automatically – from the One app or the customer portal. Viseca is one of only two sources whose file importly also reads as Excel.
Which files importly reads from Viseca
| File | Description |
|---|---|
| Transaction export XLSX | The transaction export as an Excel file |
| Transaction export CSV | The same columns as CSV, three variants |
Step 1: Download the statement from Viseca
- Log in to the One app or the Viseca customer portal.
- Open the card whose transactions you want to post.
- Choose the export function and Excel or CSV as the format.
- Set the desired period and download the file.
If the Excel file contains several sheets, importly asks you during the import which sheet should be used.
Step 2: Import the file into importly
- Open the entries table in importly.
- Drag the file anywhere onto the page. The import opens automatically.
- importly shows you the detected format – for a Viseca statement, Viseca (One) is at the top. If something doesn’t match, pick a different format in the Detected format field or create a new template via Create / edit template.
- Select your bank account from the chart of accounts, for example 1020.
- Check the preview and click Import.
If your table already contains rows, importly asks whether the new entries should be appended or the existing ones replaced.
What importly does with each column
| Column in the statement | Field in importly |
|---|---|
| TRANSAKTIONSDATUM / Date | Date |
| ValutaDate | not imported |
| HÄNDLERNAME / MerchantName | Description |
| MerchantPlace und MerchantCountry | Place and country, can be inserted via the pattern fields |
| BRUTTOBETRAG RECHNUNG / Amount | Amount with sign |
| Currency | Currency |
| TransactionId | can be used as document number |
| VORNAME und NACHNAME | Cardholder, not imported |
The sign is resolved into debit and credit: when money comes in, your bank account is in Debit; when money goes out, in Credit. importly leaves the contra account empty – you set it in the table or through your rules.
The statement lists incoming and outgoing payments in one amount column with a sign. importly converts that into debit and credit.
For a card statement, the contra account is usually the credit card account from your chart of accounts, not the bank account. Select it accordingly during the import.
Because the export delivers merchant name, place and country separately, a pattern that combines the three is worthwhile.
Adjusting document number and description
The two pattern fields in the import window let you decide what ends up in the description and document number. When you click into the field, importly suggests the available values as placeholders. importly remembers your setting for your next Viseca import.
If something doesn’t work
importly doesn’t recognize the format Check that you downloaded the Excel or CSV file and not the PDF. importly cannot read PDF statements. If the file is correct and still nothing is recognized, you can send it to us directly from the import window – we’ll add the format.
Umlauts are displayed incorrectly Don’t open the file in Excel and don’t re-save it – import it exactly as you downloaded it. Viseca delivers the file in an older character encoding that importly reads correctly – Excel often rewrites it when saving.
Rows are missing The export is limited to the selected period. An import can contain at most 5,000 rows.
Amounts end up on the wrong side This happens when the wrong bank account was selected. The debit-credit decision depends solely on the sign in the statement and the selected bank account.