ERP import rejected 200 rows: "account code not found" error on valid-looking codes

TL;DR

Two hundred rejections on valid-looking codes mean the file and the chart disagree systematically: codes exported as numbers lose leading zeros, a segment separator differs, the import targets the wrong company or entity chart, or the accounts were made inactive. Pick three rejected codes and find them in the chart by exact search, including invisible formatting. The pattern across the three tells you which systematic cause to fix in the file generation or the import target.

ERP import rejected 200 rows: "account code not found" error on valid-looking codes

Use this when

• About 200 rows reject with account code not found while the codes display correctly.
• The source file comes from another system, a spreadsheet, or a prior chart version.
• Codes contain leading zeros, dashes, or multiple segments.

Not for this skill when

• Only a handful of rows reject and those codes are truly absent. Add or correct those codes individually.
• The whole import fails on file structure before row validation. That is a template problem, earlier than account lookup.

Steps

1. Take three rejected codes and search the chart of accounts for each by exact value, then by segments, then by name. Verify: each code is found in a variant form or proven absent
2. Inspect the raw file values for those codes: leading zeros stripped, separator characters, trailing spaces, or numeric formatting from a spreadsheet. Verify: the file representation is seen as stored, not as displayed
3. Confirm the import's company, entity, and chart context matches the chart you searched. Verify: the import is pointed at the chart the file was built for
4. Check the found accounts' status: inactive, blocked for posting, or valid only in another period. Verify: status explains any code that exists but still rejects
5. Fix the systematic cause in the export or mapping, regenerate or remap the file, and reimport with a small sample first. Verify: the sample imports clean, then the full 200 rows post

Variant phrasings

account code not found import rejected rows leading zeros

The code-format phrasing.

ERP import account codes valid but rejected bulk

Searching by the bulk symptom.

Compatibility: Bulk journal and transaction imports in NetSuite, Sage, SAP, Dynamics, and spreadsheet-fed import tools.

Why it happens

Account codes are identifiers, not numbers, but spreadsheets and exports treat them as numbers and strip leading zeros, or reformat segments, without changing how they display. The lookup compares exact strings and fails, while human eyes see the same code. At 200 rows the disagreement is never 200 individual typos; it is one transformation applied to the whole file, and sampling a few codes exposes it faster than reviewing every row.

Edge cases / pitfalls

• Entity context is the silent variant: the codes exist, in the other company's chart. Multi-entity import files need the entity per row or a correct import default.
• If accounts were renumbered recently, the file may be built on the old chart. The fix is regenerating from the new chart, not resurrecting old codes.
• Trailing spaces from fixed-width exports fail exact lookups invisibly. A trim in the mapping is a permanent cure.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_5g2gloKXIt9sXw-XxhYzTQ