Accounts and their tickets can appear to be duplicated - or, in some cases, show no ticket lines at all - in the pre-invoicing report if the account's details (such as its primary address, or its account/short name) have been changed partway through the period.
The pre-invoicing report looks at all tickets against an account that have not yet been invoiced. If the account's details have been altered between transactions being generated, the system will see multiple sets of details against the same account number, and the only way it can reconcile that is to display the tickets separately for each set of details it sees.
Example
You create 5 transaction against account A001 on Monday which has the primary address of "12 The Street".
On Tuesday the accounts primary address is changed to "13 The Street". On Wednesday you create 5 more tickets, which will now display the account address of "13 The Street".
If you then go to the pre-invoicing report you will see 2 entries for account A001, each with 10 tickets against them. One set will show "12 The Street" and the other will display "13 The Street".
The same account number appears more than once in the report, each entry showing a different version of the account's address or name.
In some cases, one of the split entries shows an account summary or gross total, but no ticket lines appear when you expand it - even though the tickets exist and everything on the account looks correctly set up.
Symptoms
Note: This issue is purely display-related and if you do the invoice run the system will not produce multiple invoices for the same tickets. If you require the tickets to all show the same address details please raise a case with support and it can be looked at.
In the meantime, exporting the Pre-Invoicing Report to PDF or CSV will include the missing transactions, even if they aren't visible when expanding the entry on screen.
One specific variant of this - where the account name has a leading or trailing space - was fixed in Weighsoft version 5.544.9. If you're on an earlier version and this matches what you're seeing, upgrading resolves it. For other cases (e.g. an account name changed mid-period), use the workaround below and raise a case with support so it can be looked at.