Question regarding tax periods in legacy tax. Is there any workable solution in order choose the tax point date without affecting the aging reports? Since the tax period is always sourced by the transaction date, I thought it could be a workable solution to set up another date field and reuse the transaction date field in order to declare this as the tax date, and the other date field to be the invoice date. However, since the Aging reports can only do the aging according to transaction or due date, my aging report would suffer in that case. I know I could just set up a different period field, where the accountants could plug in the accounting period and declare this as tax period, but then I would not see this reflected in the VAT reporting out of NetSuite. Thanks for the help!

Does this apply to most of the transactions or few around month end where date for tax and aging will be different.

Quick example: Let's say we want to report VAT for January - that would mean we need to report by the 10th of March - therefore it could be any vendor bill or vendor credit that we receive from first of February until 10th of March, wich could affect my VAT reporting for January, as long as the service period for the invoice was within January. So, this could mean a few transactions, and not just around the edges of the month

You can override the due date. You may need a workflow though to autopopulate it based on the custom date field which is the real transaction date.

Yeah true that - but my issue is that I have to report my AP aging by transaction date age, so unfortunately the due date cannot help me then