Two spurious lines were added to the accounts receivable summary and detail invoices and displayed if the show banking details on invoice was ticked. This issue has been resolved.
Business activity statements.
When preparing a BAS and choosing the "Output account reconciliation reports to document management" option, if a bank account has been reconciled, but had never had any transactions processed through the account, the reconciliation report would not be output. This issue has been resolved.
When choosing the create receivable/payable option at the end of the BAS wizard, under certain circumstances an out of balance error would be reported. This error was previously reported as having been fixed in 2020.12, however, the circumstances giving rise to the error in that version were different to the error that has now been resolved.
Under certain circumstances, "error 70 - permission denied" would occur when importing creditors. This issue has now been resolved.
After linking a document to a creditor or a transaction, if the same document was linked to a task, the original entity reference would be lost. This issue has been resolved.
Editing email after initial creation of email.
If an email containing personalised attachments was subsequently edited after initial creation, any personalised attachments would appear in the email as Word document files, not pdf files. This issue has been resolved.
Creditors with unknown or RTS addresses.
If an email containing personalised attachments was created, attachments relating to creditors that had unknown or RTS address types set as their mailing address would not be generated. This would result in a file not found error appearing when sending the email. This issue has been resolved.
File not found error.
In version 2012.12 any attempt to send an email using the send in background process would fail with a file not found error. Emails could still be sent by opening the email and clicking the send button. This issue has been resolved.
If no creditors lodged votes at a meeting, the Meeting Chairperson's Report would run with a divide by zero error. This issue has been resolved.
For online meetings all meeting attendance reports have been updated with the online meeting's URL.
On the meeting attendance register, if a POD and admitted to vote amount was entered by a user directly into the grid, if the user double clicked to enter the creditor attendance record and the creditor already has a formal POD entered, the amounts entered in the grid would be overwritten by the formal POD and admitted amounts. This issue has been resolved.
Running the Fee resolution detail report from the practice without entering a to date resulted in a syntax error. This issue has been resolved.
When printing the debtor receivable contribution report directly from the contribution screen, error 91 would be thrown if bank account details had not been entered into the default bank account. This issue has been resolved.
The account transaction detailed listing report has been reporting an incorrect GST value for the realisation of pre-appointment debtors where the original value of the debt had been adjusted. This was a reporting issue for this report only, had no effect on the BAS and is now resolved.
The receipts and payments summary by account (ungrouped) reported GST with the incorrect description of VAT. This issue has been resolved.
Running any reports from a FEG direct payment batch would result in an error. The error did not affect the running of the reports and has been removed.
Receipts and Payments
Changing the bank account on a saved receipt or payment previously resulted in the reference to the counterparty record being lost (if set). This issue has been resolved.
Single Touch Payroll
If any single payroll line item in a payroll transaction had custom PAYG details entered, any additional transaction coding lines are also required to have custom PAYG details entered to report in STP.