I can definitely assist and help correct this period, @erika26.

The most common reason why users encounter performance issues, such as incorrect date periods, is due to data damage and an outdated program. You can run the Verify and Rebuild Utility to troubleshoot potential data issues.

Here’s how:

1. Open your QuickBooks account and go to the File menu.
2. Select Utilities and click on Verify Data.
   
3. Tap OK when you see this message "QuickBooks detected no problem with your data." Otherwise, you’ll be prompted to Rebuild Now or View Errors if you receive an error message.
4. Select Rebuild Now.
5. On the popup window, click OK.
6. Choose the desired location where you want to save the backup of the company file, and then select OK. The process of data rebuilding will get started automatically.
7. Click OK when complete.
8. Run the Verify Data once more to make sure your company is repaired.

Since you’re using QuickBooks Pro 2019, please know that last May 31 this year, access to add-on services and certain features are discontinued for all QuickBooks Desktop 2019 versions. The program will no longer receive any latest security patches and updates. Based on our service discontinuation policy, unsupported QuickBooks will continue to work only for basic accounting functions.

If you want to continue having an up-to-date system and product improvements, you can upgrade to a higher version.

Once everything is good, you can create any transaction and prepare for the reconciliation. See our complete reconciliation guide if you need fixes and steps to make changes after the process.

I’ll be here if you need further assistance with managing your books. Just add them to your reply below. Have a good one!

Thank you for the reply,

The bank recon is not really the problem, I can not do any transactions.

As you can see from attached file the automatic date on the system is correct, as is the calendar setting in the system

The only place I can find the difference date of 2034 is on the bank recon, 

I did the verify data, and rebuilt you suggested

The attached report was the result of that, it unfortunately also did not fix the problem