Before you start
The overview must offer Import CSV / Excel and you must be allowed to add data. If the button is missing, the owner can ask their assistant to add it. The app takes an Excel XLSX file (up to 10 MB) as well as a spreadsheet saved as CSV.
Prepare the file
Choose one sheet
In Excel or another spreadsheet app, prepare a header row with column names and one record per row below it. Remove totals, empty helper rows and merged cells.
Save the file
An ordinary Excel workbook (XLSX) is enough: the app reads the first visible sheet and takes the value Excel last showed for cells with formulas. From another app, save CSV with UTF-8 encoding; Vibee recognises commas and semicolons as separators. Dates such as 1. 10. 2026 are converted for you. A plain import can contain up to 5,000 rows. Import with record matching, described below, has a limit of 1,000 rows.
Start with a small sample
Try a few rows and check numbers, dates and status names. Do not send the same file repeatedly: ordinary import adds new records and can create duplicates.
Import and check the result
Open Import CSV / Excel
Choose the file in the destination overview. The dialog shows column matching and a preview of values.
Check column matching
Choose the correct app field for each file column. Skip unnecessary columns. Always check automatic matching by name.
Confirm the import
Check the row count and preview, then confirm. If a row contains invalid data, the app rejects the whole import. Correct the file and try again.
Import with record matching
Review columns and matches
Choose the file and map its columns to app fields. Then choose Review matches. Nothing is saved yet; each row shows its result and suggested assignment.
Review uncertain results
Ready to assign means there is one eligible match. For Multiple possible matches, choose the correct record from the list or choose Leave unassigned. The list respects your permissions.
Confirm import and assignments
Check all results and choose Confirm import and assignments. New rows are saved, unassigned rows keep no link and duplicates are skipped. Then check the number of new rows and their assignments in the overview.
If the owner has configured matching, the app can link new rows to existing records. For example, it can assign bank statement payments to invoices by payment reference and check the amount and currency. The owner defines the rules; matching does not guess from similar names.
Understand other matching results
Unassigned or additional details do not match
There is no match under the configured rules, or details such as the amount or currency differ. You can save the row unassigned for later review. Do the same if the record is already assigned. To assign it later, use record editing if your app offers it, or ask the owner.
Already imported
Matching import uses the configured identifier to recognise a row that already exists or repeats within the file. It skips the row and leaves the original record unchanged. Importing it again will not correct an earlier assignment. Plain import without matching does not automatically provide this protection.
Matching details missing
Add the imported row’s missing identifier in the file and check column mapping. You cannot confirm the import without an identifier. A missing value used to find a match, such as a payment reference, can instead leave the row unassigned.
Matching has changed
The data changed while you were reviewing it. Choose Review matches again and check the current results before confirming.
Prepare a file for matching
One import with matching can contain up to 1,000 rows. Keep each transaction’s unique identifier and any leading zeroes in payment references, such as 00123. A payment reference alone may not uniquely identify a bank transaction.
Matching does not automatically split a payment across several invoices or handle partial payments and overpayments. Arrange those workflows separately with the owner.
In my app [name or address], configure bank statement import with a matching review before saving. Assign payments to invoices by exact payment reference, amount and currency. Detect duplicates by the bank transaction’s unique identifier, not the payment reference. Leave uncertain rows unassigned and only offer invoices the user is allowed to see. Show me the flow with a small sample.
If import is not configured yet
You can also attach a file to your assistant while building the app, if it can read the contents. That is separate from repeated imports directly in the app.
Add CSV import to the client overview with name, e-mail and phone columns. Validate required values before saving and suggest how to prevent adding the same client twice.