Object Reference Error on an Import

Learn how to troubleshoot and resolve object reference errors that occur when importing data in your code.

May 19, 2026
Article

Title

Content

The "Object reference not set to an instance of an object." error can occur when doing an Import of a record type that references Financial Periods if the Custom Financial Period is being used, but no valid Custom Financial Periods are available.

To check if this error is caused by missing a valid Custom Financial Period, do the following:

Select the Module for which you are trying to Import (Accounting or Assets) (from the side menu bar).
Select the specific module section (Equipment, Locations, Accounts, Cost Centers, etc).
Select any record.
Select the Financial tab (if on Assets, or move to step 5).
If "No Custom Financial Periods have been created." is displayed, then this is causing the import error.

To correct this error, do one of the following:

Create a valid Custom Financial Period (you will need to be a local administrator):

Select Administration.
Select Financial Periods.
Select New.
Select Save when done.

Instead of using Custom Financial Periods, switch to Calendar (you will need to be a local administrator):

Select Administration.
Select Settings.
Select Accounting.
Change Financial Periods to "Calendar".
Select Save.

URL Name

Object-Reference-Error-on-an-Import

Object Reference Error on an Import

Information

Content

Trending Articles