BWA report

This report is similar to the DATEV report in large parts, but it uses the validity date with priority over the opening day or /TTA.

Priority of the validity date

If a validity date is specified for a sale, for example of a ticket, the turnover is exported to accounting (BWA) with the validity date instead of the sale date. The structure of the export is exactly the same as for the DATEV report. If a transaction with more than one validity date has been sold for different items, the payment amount is split according to the ratio between the journal entries.

Allocation algorithm...

If a ticket is booked at 80,- with validity date = 01.04.2023 and one at 50,- with validity date 01.05.2023 and then paid with 10,- voucher and 120,- cash, it will be booked as follows:

On 01.04.2023 -> 6.15 euros on voucher, 73.85 euros on cash. Sum 80,-

On 01.05.2023 -> 3.85 euros on voucher, 46.15 euros on cash. Sum 50,-

Checking and indication of no validity dates....

If no validity date has been used in the selected period, the BWA report does not differ from a DATEV report and this is also displayed as a note:

Option switch during export...

For the BWA report, there is the option switch Do not apply validity date in the export for DATEV. This has the effect that the payments are not posted on the validity date, but on the posting date (like DATEV Standard).

---

Back to the parent page: S Interface Reports