Error messages are few and generally weak in SQL-ledger. This writer notes a few error situations:
when data is incorrectly entered (such as a date eg. 31 June or a non-existent stock code), one will received a complex database error explanation. – Response: take note of the top line.
when there is an ‘encoding’ issue in the copy-pasting of notes in a transaction, there appears a dialogue box to download a .pl file. - Response: Ignore the download request and possibly type in the required notes.
There are a number of community lists that can assist in resolving errors. Here's a few:
Create a ‘template’ database for the company where customer data, stock parts – all info updated but with no transactions. To be used as a ‘starter’ file each year (or two).
In starting the year, one can create reversed ‘Credit Note’ for the total outstanding of a customer as a negative figure linked to ‘Retained Earnings’ and put the list of unpaid invoices and interest changes in the notes.