The financial links in RetailVista currently provide a link for cash transactions and a link for invoicing. Cash transactions refer to cash sales through the cash register. Inventory transactions and purchase invoices, for example, are not yet part of a financial link. Please indicate below which of the available links need to be activated.

How is the cash register setup done, is it per user (cashier) or per POS terminal/workstation. In case of setup per user, each user has their own cash drawer.

Which financial application is being used. We support the following standard applications, but some exports are also suitable for other financial administrations.

RetailVista exports sales journals with revenue excluding VAT per cash group and the VAT component totaled per VAT rate. Some financial products want to receive revenue per cash group including VAT and then split the VAT themselves. How should the revenue per cash group be provided in a journal, including or excluding VAT?

If the revenue per cash group is provided excluding VAT, can the VAT be provided in one general ledger per VAT rate, or must the VAT be provided in a VAT general ledger per cash group. The latter requires considerably more time in setting up the cash accountability export.

Not all financial administrations and not all imports work with a general ledger for VAT. Sometimes VAT must be imported using a code. Specify below the codes used for VAT as they occur in the financial package (as far as applicable VAT rate).

When using Exact, turnover per branch must be booked on a relationship number. What is the relationship number on which the turnover of this branch should be booked (only in case of Exact integration)

Cash differences are the differences that arise between the counted amount in a cash drawer and the amount that should be in the drawer.

Safe differences are the differences that arise between the counted amount in the (sometimes fictitious) safe and the amount that should be in the safe.

Cash transactions are the increases or decreases in outstanding cash. If a cash drawer starts with 100 euros in the morning and contains, for example, 500 euros at the end of the day (without being skimmed), a cash transaction of 400 euros occurs.

Safe transactions are the increases or decreases in outstanding safe money. If there is an amount of 1000 euros in the safe in the morning and due to skimming the safe contains an amount of 1800 euros at the end of the day, a safe transaction of 800 euros occurs.

If customers pay invoices in cash, it is a balance entry. These payments are offered by RetailVista on the specified general ledger account.

If customers make down payments in cash, it is a balance entry. These payments are offered by RetailVista on the specified general ledger account. When items are later picked up, a corresponding negative entry is made on this general ledger.

The money that is deposited from the safe to the bank, or vice versa, the deposit of, for example, change in the safe, is recorded in the ledger below.

If money is taken out of the cash register during the day, for example, for payment of lunch, it is recorded as a payment from the cash register. This payment is recorded in the ledger below.

RetailVista can create a journal file per day, week, month, or on request. For example, if a journal is requested on March 25th while the month is not yet over, no journal is created. Only when a specified period is over, the journal is created. By choosing 'On request', a journal can be created at any time.

The turnover and VAT rules can be compressed to the end journal date of the period. The individual daily sales are effectively eliminated.

The sum of all journal lines in the journal file results in the cash mutation. Some financial applications calculate this journal mutation themselves, while others want to receive this cash mutation as an additional line in the journal file. In the first situation, the journal will not be balanced by itself, while in the latter situation, a journal is always balanced.

Non-cash payments (EFT payments) can be compressed per POS terminal. Different card types such as Maestro, Visa, etc. can then be combined into 1 EFT payment line per POS terminal.

Some financial applications determine the + or - sign for a general ledger mutation themselves, depending on the debit or credit setting of the general ledger. In that case, RetailVista must provide the mutations without a sign.

Financial software sometimes looks at + or - amounts differently. It depends on the perspective, whether it's from the bank or the entrepreneur. Revenue from RetailVista is offered as positive by default, while payments are offered as negative. However, RetailVista can provide the opposite indication.

RetailVista links cash and credit sales solely based on the combination of VAT rate and cash register group revenue/no revenue. If further breakdown is desired, it is possible. Further breakdowns work on revenue types. For example, all landscaping work can be separately provided to the financial administration. We do not prefer such breakdowns, as detailed reports can also be requested from RetailVista itself. Moreover, the integration becomes significantly more complex and expensive because linking by revenue type is labor-intensive.

Sold gift cards are registered by default per type of gift card on a separate ledger code. It is possible to create multiple variants of the same type of gift card, for example, the 'Fleurop' gift card in a 10 and 25 euro product variant. In RetailVista, there are then 2 products. Is it desired to register the sale of gift cards per individual product instead of per type of gift card?

Revenue and VAT ledgers per cash register group, VAT rate. If 'Yes' was chosen for the previous question 'Can set VAT ledger per cash register group', print the following report:

If 'No' was chosen for the previous question 'Can set VAT ledger per cash register group', print the following report: