My import file has errors
Use row errors and column mapping to correct a data import before committing it.
- Who can do this
- Owners, or people with the create and posting permissions for the import type
- Where
- Books, then Import data
- You'll need
- Your source CSV and its review page; statement files use the separate bank importer
One invalid row or missing required column blocks the whole data import. Ready rows are not added around the errors.
Fix the first error
- Open the upload's review page under Import data.
- Read each row number and reason under Commit is blocked. Fix every error.
- Correct a wrong column selection in the mapping controls.
- Select Update mapping and review.
- For errors in row contents, correct the CSV and upload it again.
Use the source row number to find mismatched cell counts, invalid amounts or missing data. If a thousands comma split one amount into cells, quote that amount or remove its thousands comma. A required column must be mapped even if the source uses a different heading.
Check the result before committing
Review duplicate skips as well as errors. A duplicate skip is not a new record. Expired uploads have cleared rows and need a new upload. Permissions and posting rules are checked again when committing.
Nonprofit supports list imports, but not open invoice, open bill or opening-balance imports. Use the move guide for the supported sequence.
If the same error remains, contact support with the import type, row number and exact message. Remove personal data before sharing a sample. Bank statement uploads use the separate statement importer.