Reckon One BAS statement problem

alister_7824269

Hi all,  I have just changed over to Reckon One from a old QB desktop.  I have been through and entered invoices and bills from 1/7/15 till yesterday and run a P&L and BAS statement is not showing any income for the qtr as well as wrong expenses.  Help please.

Qwerty

Hi Alister,

In the two report examples you have provided, they both state Cash basis in the report header section.

Reporting on cash basis won't show any amounts relating to open invoices or open bills.
Reporting on accrual basis will show amounts relating to open invoices & open bills.


To configure tax reports (includes the GST Summary report)...

Administration menu (i.e. the cogs icon in the top right of the screen) > Tax settings > General > Set "Reporting basis" to Accrual


To configure non-tax reports (includes the P&L report)...

Administration menu (i.e. the cogs icon in the top right of the screen) > General settings > Report settings > Set "Report basis" to Accrual


Also the GST Summary report will only detect transaction data that is associated with tax codes.


Hope this helps.

alister_7824269

Thanks have done that.. however my BAS is still showing no sales and G10 & G11 seam to be a double up.

Qwerty

I'd suggest having a look at the Tax code transactions report for the same period as it will show you what transactions are linked to each tax code.

Reporting > Tax > Tax code transactions

alister_7824269

Qwerty

In the above example, I notice that you are using the GST tax code for both sales transactions (invoices) & purchase transactions (bills). In Reckon One, GST is a sales tax code for sales transactions. Purchase transactions generally shouldn't be using the GST tax code.

Refer to the tax code list report below. The tax codes above the blue line are sales tax codes & the tax codes below the blue line are purchase tax codes. 

alister_7824269

Think you may be on to the problem..  Now how to change the codes...  Hopefully not 1 at a time...  ARRRRRR

Qwerty

When looking at the tax code transactions report you generally don't want to see purchase tax codes under the SALES section of the report or sales tax codes under PURCHASE section of the report.

You may need to review you tax code allocations for those transactions where this occurs.

Qwerty

Seeing that the transactions have already been entered then yes you'd need to review them individually.

You should also review any items, income accounts & expense accounts that you have setup in your book to ensure that they have the correct default tax codes assigned. This way moving forward any new transactions should be using the correct tax codes.

gazza73

Alistair.

You and I had a long chat about this yesterday - not sure if the Community info in this forum article was before or after.  But I would point out one othe aspect.

You mentioned on the phone that you run "CASH" basis.    Did you mention that in terms of what you are obliged to do on your returns,  or in therms of what Reckon ONE just happens to be setup for.  If the ATO has been arranged to work on a particular basis, then you need Reckon ONE to work on such a basis.   Our talks yesterday all revolved around 'CASH'.   

You were using a 25/8/15 example of 10526 sale that was paid three days later on 28/8/2015.  That single transaction would qualify for CASH basis reporting.    Stick with that example for the GST sales problem.

As for the expenses,  QWERTY has echoed the same comments as we went through,  being that you need to use NCG,  NCF   for gst/fre when dealing with non-capital purchases.

So get all that sorted first.



Then....   to the BAS Settings.

ADMIN -->  Tax Settings  -->  BAS Settings...
-  make sure you are on option 1  (calc and pay quartery)
-  you can decide if displaying with.without tax on the BAS forms

ADMIN -->  Tax Settings -->  Tax Groups...
- make sure you haven't marked any critical ones as inactive
   (GST FRE NCG NCF CAG CAF   and EXP)


TIP:  Alistair...  compare the DEMO company settings which has DATA relating to the quarter  1/7/2014 thru 30/9/2014 to see the settings.



Gary Pope
m: 0408994799 
An Accredited Partner- Consultant (VIC. Aust)
http://www.alchester.com.au/reckon-ac...
"Working with Accountants/Bookkeepers PPs/APs, as an
independent IT Professional and retired FCPA Accountant"

alister_7824269

Well i would like to see that things are getting better..  Until i just struck a little problem..  This is not happening on every bill, I have changed 40-50 but this has come up 8 - 10 times..  All different dates and suppliers..





h

Scott_6428906

Hi Alister,

This particular issue regarding unlinking transactions from within bills or invoices is a known issue. It has been reported to the Reckon One development team.

For now the suggested work around is:

Bills
Instead of using the unlink option within the bill, open the linked transaction/s (i.e. payment/s) & you can unlink the payment from the bill by viewing the Allocate tab within the payment & removing the amount shown in the How much to allocate field for the relevant bill.

Invoices
Instead of using the unlink option within the invoice, open the linked transaction/s (i.e. receipt/s) & you can unlink the receipt from the invoice by viewing the Allocate tab within the receipt & removing the amount shown in the How much to allocate field for the relevant invoice.

Please note: When you unlink a transaction, the transaction remains in the system (as a credit) so it's not the same a deleting a transaction. So if you are unlinking transactions in order to edit the original transaction, you can relink these transactions again after making your edits to the original transaction.

Refer to the threads below for more clarification on the above paragraph & how to reapply the credits.

https://community.reckon.com/reckon/topics/how-do-i-unpay-a-bill-once-its-been-marked-payed

https://community.reckon.com/reckon/topics/wrong-date-paid-invoice?topic-reply-list[settings][filter_by]=all


Regards,
Scott.

Scott_6428906

Hi Alister,

Just an update in regards to the error that occurred when unlinking transactions.

This issue is now fixed.

Regards,
Scott.