An electronic statement can be a CSV file or coda file with bank transactions. In first instance we recommend to use as much as possible coda files (link with Codabox, link with ING, download and deliver codas). If there are no coda files, you can use a Yuki CSV file for bank transactions. You can create this file yourself in Excel or you can use a template (see attachment at the bottom of the page).
The Yuki format has the following columns:
- IBAN: Bankaccount number
- Currency: The currency of the account. EUR for euro, USD for US dollars etc.
- Statement: Statement number (optional)
- Date: Date of the transactions
- Value date: In case the value date is not known, you can also enter the transaction date.
- Suspense account: Bankaccount of the counterpart. This can be blank but we recommend to fill it in for automatisation purposes (match rules).
- Name suspense account: Name of the counterpart. This can be blank but we recommend to fill it in for automatisation purposes (match rules).
- Description: Description of transaction. In case it is known, the invoice number, structured payment ID or name of counterpart can be specified. This will improve the automatic matching with an invoice.
- Amount: Amount of transaction using the same currency as the one in the account. A positive amount is seen as a debit and negative amount is seen as a credit. Decimals should be separated by a comma and thousand separators can not be used.
Once the file is completed, you should save it as a CSV file (use list separators)
The columns need the correct column titles as well as follow the exact same order as listed above. If this is not the case, Yuki will not recognise the file and it will be send to the workflow with an error message.
In case the file meets the conditions, Yuki will automatically recognise it as an electronic statement and archive it accordingly.
Below you can find a brief explanation of the buttons:
- Folder: File the electronic statement in another folder
- Reimport: Can be used if the file was not completely screened through the IDR. Technically, this should not be applicable.
- Replace: The electronic statement can be replaced by another electronic statement (bank file) and automatically be imported once again.
- Standard: The electronic statement will be converted to a standard document by which all bank transactions will be deleted out of the workflow and bookkeeping.
- Delete: Delete the electronic statement with all of its bank transactions
- Details booking: The underlying entries linked to the transactions
All transactions will be directed to the bank transactions workflow, unless match rules were already created. In that case, the transactions that comply with the values of the match rules will be automatically processed.
A green box means that the transaction is already processed (manually or automatically). A yellow box means that it is not processed yet.