The BAS report does not always include transactions on the 29th February.

Legacy KB ID: 1577

Question

Why doesn't the BAS report always include transactions from the 29th February?

Answer

During a leap year if I have transactions on the 29th of February they are not always included in the BAS report. If I am doing the BAS on a monthly basis, and selecting February as the month, then the date range at the top of the BAS appears as 01/02/04 - 28/02/04, and the transactions from the 29th february are not included.

The same occurs if performing the BAS quarterly where the ending month is February.

This will also occur in the situation where you do the BAS Annually, and the ending month is February.

If you do the BAS quarterly or annually, and February is not the ending month, but it is covered by the period, then the transactions from the 29th February will be included.
The issue occurs on both Cash and Accrual basis.
The other tax reports pick up the transactions correctly in all cases.

The only way to have these transactions showing on the BAS report is to change the date of the transactions. For example if you change the date of these transactions to the 28th February then the BAS will be fine in all cases.

If you do not wish to alter the transaction dates, then do not use the BAS report. As the other Tax reports always show these amounts, you can use the Tax Summary report to gather the information required for your BAS.

How did we do?

BAS is still incorrect after confirming Tax Reports are correct

Including Pays information in BAS when not using the Accounts Business Payroll function.

Related Articles

Retrieving a Held Transactions does not update the status of the transaction
Why does the G15 field in the BAS report always show a zero value?
Transaction rule does not pick up the transaction
Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)