it seems to be date format mm/dd/yyyy
change it to dd/mm/yyyy
try this
in control panel check the short date format

It's not date format issue because all other dates for all other periods in the fiscal calendar are correct. Period 8 start date has always been June 1/16 until last week when it changed from June 1/16 to Jan 6/16. However, the start date is not even a field that can be edited. So we are trying to figure out how the date could have been changed. What I'm looking for is a report/audit log that shows changes to the fiscal period calendar so we can see who changed this field and when.

Thank you though.

Unfortunately, I don't believ any such an audit log exists for these records. The tables that hold fiscal year (tglFiscalYear) and fiscal periods (tglFiscalPeriods) do not contain UpdateDate nor UpdateUserID fields. Additionally, neither the System Activity Log, Maintenance Audit Log nor GL Fiscal Calendar List capture changes to the Fiscal Year. The beginning date of the period in a Fiscal Year is not editable because the system starts the period one day following the end of the prior period. Does the prior period now end on 05/31/2016? If not, you should be able to force the system to recalculate the periods by manually changing the period end dates within the fiscal year, even if you have to change them to 'bad' dates, save the year, and then enter the correct ending date for each period.

No, the prior period end date did not change. The dates for the periods in question looked like this:

Period Start Date End Date
03 01/01/2016 31/01/2016
04 01/02/2016 29/02/2016
05 01/03/2016 31/03/2016
06 01/04/2016 30/04/2016
07 01/05/2016 31/05/2016
08 06/01/2016 30/06/2016

So period 8 overlapped periods 3-7. Strange. It created duplicate transactions for period 8 from Jan 6-May 31. Thankfully, they were all $0 so we were able to delete them.

We were able to get the date fixed simply by tabbing through the fiscal period calendar fields, and it auto-corrected the date. We saved the changes and all is well now. We were just looking to understand how it occurred, and prevent it from reoccurring. We may just chalk this one up to a "once in a lifetime unanswered phenomenon" and leave it at that.

Thanks for your input on the report and the fields in the tables.