Why does a deleted booking reappear in the system every morning?
This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com.
Observation
In a ledger there is an entry which can be deleted, but which is present again every morning.
Background
timeSensor LEGAL has a nightly check mechanism that detects inconsistencies in the accounting data and automatically cleans them up. If an entry reappears overnight, it has probably been restored by the checking mechanism.
Example
You mistakenly enter a cross entry (i.e. a transfer from one bank account to another bank account) with a VAT code. Now timeSensor LEGAL will automatically create a second entry (shadow entry) with VAT for this transaction. You see this VAT entry, consider it to be incorrect and delete it.
The next morning, the VAT entry is there again because the check mechanism detects a data inconsistency during the night, namely an entry with a VAT code for which the VAT entry is missing. Now the check mechanism will automatically restore the VAT entry. The solution is to remove the VAT code from the cross entry, because no VAT is due on a transfer between accounts.
Solution: Remove the VAT code!