Import cash statement

You can import cash transactions in CSV format. To create such a format, it is best to use a spreadsheet and save it as 'Windows text separated by list separators (.csv)'. The separator should be set to ';'.

This file will be recognised and the cash statement (read transactions) will be processed.

Only a user with a 'Back office' role in the domain or the 'External accountant' role can import a cash statement. 

If you use your own software for the cash register(s) but part of the revenue is also paid by debit card, credit card or on account, a combination of cash import and the 'Sales web service' can be used in Yuki. 

The first line of the spreadsheet must have the same column titles as prescribed in the table below:

The 'Project code' and 'Project number' columns can optionally be added to the spreadsheet. This automatically assigns cash transactions to the corresponding project.

In the attachment you can find an example of a cash statement in CSV format!

The import file is recognised as a cash statement if the first line with headers contains the column names in the following order:

• Grootboekrekening kas: Determines into which petty cash the cash statement is imported.
• Kas omschrijving: Can be entered optionally, serves as a check with the cash general ledger account, if the description is not the same as that of the cash general ledger account, the import will not be accepted.
• Transactie code: A code arbitrarily invented by the user for the transaction that is used in the match rules. The restriction is that this field may contain a maximum of 10 characters. If the code is longer, only the first 10 characters are processed.
• Tegenrekening: The offset account for the specified transaction. Not required. Maximum 34 characters. This can be used for, for example, a contact code or general ledger account. This code can also be used to create match rules.
• Naam tegenrekening: Name of the contact associated with the offset account. Not required. Maximum 34 characters. This code can also be used to create match rules.
• Datum transactie: The date of the transaction should be in the following format: dd-mm-yyyy.
• Omschrijving: Description of the transaction. The transaction text is truncated at 1024 characters.
• Bedrag: The transaction amount, + in front of transactions that increase the cash balance, - in front of transactions that decrease the cash balance.
  
  If the separator between fields is a ',' (comma) the following applies:
  The number format for decimals must include a period (.) and cannot contain a comma (,).
  Thousands separators may not be used.
  
  If the separator between fields is a ';' (full stop comma) the following applies:
  The number format for decimals may contain a (,).

• Saldo kas: This is the actual value on the relevant date of the petty cash  (total petty cash balance) after the transaction of that line has been processed. This value is not required under the following conditions:
  • If a balance has been entered, the transactions must be in chronological order with the oldest transaction at the top and the youngest at the bottom.
  • If no balance has been entered, the transaction order is not important.
  • If the balance value is not entered consistently i.e. in some lines it is and in other lines it is not, then empty values are considered as having an amount of 0.00.
• Projectcode (optioneel): Code stored with a project (this code must match exactly)
• Projectnaam (optioneel): Volledige naam van een project (deze naam moet exact overeenkomen).

Determination of opening and closing cash balance

Yuki assumes that all transactions are in order in the file, with the first transaction line being the oldest and the last being the most recent transaction.

The opening balance is determined by subtracting the transaction value of the first transaction line from the balance value.

The closing balance is the balance value in the last transaction line.