On Fri, Jan 8, 2016 at 10:24 PM, Cédric Krier <[email protected]> wrote:
> On 2016-01-08 04:00, Vincent Bastos wrote: > > For my part ( Australia ), the sequence is not important. As you can see > in > > the links below, the ATO ( Australian Taxation Office ) does not require > an > > invoice to have a number :)... we are pretty easy going down under. > > > > https://www.ato.gov.au/Business/GST/Issuing-tax-invoices/ > > > > > http://www.business.vic.gov.au/money-profit-and-accounting/getting-paid-on-time/invoicing > > > > However, if we are going to make invoice_date = accounting_date why the 2 > > fields? > > Because for supplier invoice, you will mostly change it. > > > To be honest I don't understand what the purpose of the > > accounting_date field is for? > > accounting date is used to fill the move date. > > I think Korbinian correctly summarize it: > > invoice_date -> for payment term > accounting_date -> for accounting/taxation ok, so in Australia it is possible to report your income on a cash basis, but your GST on an accrual basis. Quote below is from [1]: There are two methods of accounting for GST: a cash basis and a non-cash basis (accruals). The method you use will affect when you must report GST. Businesses with an aggregated turnover (your businesses' turnover and the turnover of closely associated entities) of less than $2 million, or who use cash accounting for income tax, can use either method. Most larger businesses must use the non-cash method. It is allowed and possible to create an invoice in one period, but only have it paid in another period. How would one create both the income and GST ( VAT ) report accurately? Or rather which fields to use? [1] https://www.ato.gov.au/Business/GST/Accounting-for-GST-in-your-business/Choosing-an-accounting-method/ -- *Vincent Bastos* *Lava Lab Software* -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/CACLX58DCCLL2x7Av1NLi2%3Djo_EH8cqUL0Co-ydbXE19YjdKHMQ%40mail.gmail.com.
