NetSuite CSV Import: Customers, Transactions, and Saved CSV Imports

NetSuite CSV Import Is a Privileged, Template-Driven Path

NetSuite (Oracle) finance and ops teams in the US, UK, Australia, Canada, and Europe use CSV Import for customers, vendors, items, journal entries, and more. Unlike casual SaaS uploads, NetSuite expects saved import maps, external IDs, subsidiaries, and exact field IDs. A QuickBooks-style sheet will not survive without remapping.

Pick the Record Type First

Wrong record type is an instant fail.

Step-by-Step: First Successful CSV Import

Admin/implementer path.

• Confirm CSV Import permission and the target role.
• Start Import Assistant → choose record type → download/use a sample when available.
• Populate External ID (or the key your map uses) for upserts.
• Match subsidiary/currency values to NetSuite lists exactly.
• Normalize dates to the format your NetSuite company preferences expect.
• Clean in Online CSV Editor; keep IDs as text.
• Create/save an Import Map; run in Test/Validate mode if offered.
• Import a 5-row pilot; fix errors from the CSV response; then scale.

externalId,companyName,email,subsidiary,currency
CUST-1001,Acme Ltd,ap@acme.example,Parent Company,USD
CUST-1002,Beta GmbH,ap@beta.example,EU Subsidiary,EUR

External IDs Beat Name Matching

Names drift; IDs should not.

• Assign stable externalId values from the source system (ERP/CRM/legacy).
• Use Add or Update / upsert behaviors intentionally.
• Never re-import the same conference list weekly without keys — duplicates follow.
• Document the externalId scheme in the integration runbook.

Dates, Periods, and Multi-Subsidiary

International NetSuite orgs collide here.

• Date format must match company preference (often M/D/YYYY in US accounts; confirm).
• Prefer generating dates from a known locale transform rather than Excel guesses.
• Posting period must be open for transaction imports.
• Subsidiary values must be valid for the role running the import.
• Multi-currency: amount + currency fields must align with account setup.

Transaction Imports: Balance the Lines

Journals and invoices fail when lines do not balance.

• Header + line structures must follow NetSuite’s multi-line CSV conventions for that type.
• Debits equal credits for journals.
• Item/tax/shipping lines need accounts that exist.
• Pilot one transaction end-to-end before a month’s worth of AP bills.

Excel Landmines

Classic ERP CSV damage.

• External IDs in scientific notation.
• Leading zeros stripped from SKUs/entity IDs.
• UTF-8 vs ANSI for EU customer names.
• Semicolon EU files vs comma maps.
• Silent date rewrites on open/save.

NetSuite vs QuickBooks / Xero / Sage CSV

Do not reuse SMB templates.

• Maintain a transformation layer from source → NetSuite field IDs.
• See QuickBooks, Xero, and Sage guides for mid-market formats.
• DATEV-style DE files need locale conversion before NetSuite US/UK maps.

Common Mistakes

Expensive to unwind.

• Skipping saved import maps (re-mapping every time causes drift).
• Updating by name instead of externalId.
• Importing into a closed period.
• Wrong subsidiary on child records.
• Ignoring the error CSV NetSuite returns.

Best Practices

Treat imports like financial deployments.

• Sandbox first when available.
• Version every file + map name + operator.
• Separate master data loads from transactional loads.
• Automate transforms; keep humans for exception review.
• Cleanse in-browser for sensitive entity files.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Prep NetSuite import files in the Online CSV Editor, fix EU delimiters, and convert review copies to Excel for controllers across US, UK, AU, CA, and EU subsidiaries.

Conclusion

NetSuite CSV success is external IDs, open periods, valid subsidiaries, and saved maps. Pilot every record type, respect locale date rules, and never treat a QuickBooks export as NetSuite-native.