Troubleshooting Bulk Import Errors
Check the areas below if you are having trouble importing leases in bulk
Tips for Getting Started
- If you have fewer than 30 leases, we do not recommend the bulk import feature. You will have a faster experience by adding leases through the add lease workflow, either manually or by using our AI lease abstraction feature.
- We recommend splitting your file into 50 or fewer leases per import file.
- Before attempting bulk import, make sure to complete all administration setup steps (FASB, GASB, or FRS), including Reporting Entities, GL Accoutns, and Customizaiton.
- Enter only one lease per row.
- Be sure to follow all the instructions on row 3 when entering data for that column. Some columns will have special formatting requirements and cannot include special characters (e.g., percentages should be entered as decimal values).
- All cells should be formatted according to the field/data type. Dates can be formatted as MM/DD/YYYY or DD/MM/YYYY. Follow the instructions in row 3 or refer to our more detailed formatting requirements (FASB/GASB/IFRS or FRS).
- Some fields carry dependencies with other fields. For example, if you are adding a second payment stream for a lease, there must be values under the following columns: Payment Amount - 2, # of Payments - 2, and Payment Start - 2.
Template Error
- Make sure you're using the most recent Bulk Lease Import Template for your standard. This template can be downloaded from the Bulk Import screen. Multiple templates may be displayed depending on your organization's configurations. The version is shown in the System tab of the template and should match the Import Leases screen.
- Review the template for multiple tabs (Leases and System) and do not make changes. There should be no additional columns and no blank rows in between leases.
- If you use the wrong template version or make invalid changes to headers or other areas, you will receive a template error similar to the one shown below:

TIP
To resolve a template error, download the current template version, copy/paste the lease rows to the new file, and try the upload again.
Validation Error
The spreadsheet will only import if all lease rows are successfully validated. If one or more leases have errors, the entire import will fail and you will receive the following validation error:

Click the download icon to the left of the error tag to export and view the error log.
The error log is color-coded, with leases that could not be validated labeled yellow and the cells or cells that caused the validation error labeled in red. See the example below:

In the above example, row 6 is colored yellow, indicating an error has occurred on this lease row. Cell A6 is colored red, indicating that something could not be validated with the name of this Reporting Entity. In this case, the spelling did not match the value under Administration > Reporting Entity in Crunchafi Lease Accounting.
TIP
Changes to cells with errors can be made directly to the error log, which can then be saved to your device and uploaded again to retry the import.
Validation Error Types
These are some of the more common validation errors that can occur. If a lease row is showing an error cell in one of the columns listed below, here are some tips for fixing the error.
Reporting Entity
- If the name of a Reporting Entity in the bulk import template does not have a corresponding Reporting Entity setup in the Administration menu, a validation error will occur and the Reporting Entity column will be highlighted in red.
- Confirm that the Reporting Entity names in your file exactly match the spelling that appears under the Administration tab in the software.
NOTE
If a Reporting Entity cannot be validated, it may also cause errors in the following columns: Start Date, GL Account Number, Asset Type, Location, or Lessor Name.
Asset Type, Location, or Lessor Name
- If a row has an error under the Asset Type, Location, and/or Lessor Name columns in the bulk import file, confirm that the spelling exactly matches what appears under Administration > Customization in the software.
- Confirm that you have entered the Asset Type, Location, and/or Lessor Name associated with the Reporting Entity specified in the bulk import file.
- Check for any trailing or leading white spaces for the values in these cells that would cause validation errors.
# of Payments
- An error in the # of Payments column usually means that the lease payments extend beyond the end date of the lease.
- Confirm that, when combined, the Payment Start and # of Payments columns do not cause a payment date to occur after a date that is listed in the End Date column. In the example below, the lease Payment Start date is 3/15/2023. With 72 payments, that would cause the final lease payment to occur on 2/15/2029, which would exceed the lease End Date of 2/1/2029.

Cost Center Allocations
-
If you are adding any cost centers and allocations, the allocation(s) must equal 100%.
- Even if the cost center allocation is 100% for one cost center, you must enter 1 under the corresponding Allocation% - 1 column.
Bulk Import Data Limitations
Below are the limitations for the data that can be imported for individual leases.
- Limit of 5 payment streams per lease. Do not enter more payment streams on another, as each row corresponds to an individual lease.
- Limit of 2 cost center allocations per lease.
- Limit of 3 existing balances from previous lease accounting guidance.
- Limit of 5 custom fields.
NOTE
If your leases require more entries that what can be imported, the information can be added directly to the lease after the initial data is successfully imported. This can be done by going to the My Leases page to find, open, and edit the lease.
If you need additional assistance with troubleshooting bulk import errors, reach out to support@crunchafi.com and include the original bulk import file.