Two Ways to Import Bank Data into NetSuite
NetSuite provides two distinct methods for getting bank transaction data into the system. Understanding the difference helps you choose the right approach for your situation.
| Method | Best For | Format | Setup |
|---|---|---|---|
| Bank Feeds | Ongoing transaction sync from supported banks | Automatic (OFX/QFX) | One-time bank connection |
| CSV Transaction Import | Historical data, unsupported banks, PDF-sourced statements | CSV file upload | Per-import file prep |
| GL Journal Import | Custom chart of accounts, complex multi-entity entries | CSV with segment values | COA mapping required |
For most accounting teams handling prior-period reconciliations or clients at banks without Bank Feeds support, CSV Import is the go-to method.
CSV Format Requirements for NetSuite Import
NetSuite's CSV Import (also called SuiteImport or Transaction Import) requires specific column mappings. The exact fields depend on the transaction type you're importing, but for bank statement transactions these are standard:
| Column | Required? | Format Notes |
|---|---|---|
| Date | Yes | MM/DD/YYYY or YYYY-MM-DD depending on locale settings |
| Amount | Yes | Negative for debits, positive for credits (or use separate Debit/Credit columns) |
| Description / Memo | Yes | Freeform text, maps to transaction memo field |
| Account | Yes for GL | Must match exact account name or internal ID in your CoA |
| Reference / Check Number | No | Used for reconciliation matching |
| Currency | No (defaults to base currency) | ISO 4217 code if multi-currency |
| Subsidiary | OneWorld only | Must match subsidiary name or internal ID |
Converting PDF Bank Statements for NetSuite
Banks deliver statements as PDFs, but NetSuite's import tools only accept structured data files. This conversion step is where most accounting teams lose time — manually copying transaction data from a PDF into a spreadsheet is error-prone and slow for statements with hundreds of transactions.
Zera Books automates this step — it reads bank PDFs (digital and scanned), extracts all transactions, and outputs a CSV formatted for NetSuite's Transaction Import, including correct date formatting, signed amounts, and memo descriptions.
PDF to CSV
Converts any bank PDF — scanned or digital — to NetSuite-compatible CSV without templates.
Multi-Period
Process 12 months of statements in one batch for prior-period reconciliations.
Multi-Account
Automatically separates checking, savings, and credit card transactions into separate files.
Accurate Amounts
99.6% transaction accuracy — critical for reconciliation against NetSuite GL balances.
Step-by-Step: CSV Transaction Import in NetSuite
Prepare Your CSV File
Ensure your CSV has the required columns: Date (MM/DD/YYYY), Amount (signed), and Description/Memo. Add Account if you're importing directly to GL.
Navigate to CSV Import
Go to Setup > Import/Export > Import CSV Records. Select record type — for bank statements, choose Transactions > Journal Entry or Bank Transaction depending on your workflow.
Upload and Map Columns
Upload your CSV. NetSuite will show the column mapping screen — map your CSV headers to NetSuite fields. Save the mapping as a template if you'll run this import regularly.
Run the Import
Click Next and then Run. NetSuite processes the file and shows a job status. Check the error log if any rows are rejected — date format mismatches are the most common issue.
Reconcile in Bank Feeds
After import, navigate to Transactions > Bank > Reconcile Bank Statement to match imported transactions against your bank statement balance.
NetSuite-Ready CSV From Any Bank PDF
Zera Books converts bank statements to NetSuite Transaction Import format automatically — correct dates, signed amounts, no manual column mapping.
Try Zera Books Free ›Setting Up NetSuite Bank Feeds
Bank Feeds is NetSuite's automatic bank connection module for ongoing transaction sync. It's separate from CSV Import and works best for day-to-day reconciliation once historical data has been loaded.
- Navigate to Setup > Accounting > Bank Feeds
- Click Add Bank Account and search for your institution
- Authenticate using your online banking credentials
- Select the account(s) to sync and confirm the GL account mapping
- Transactions sync daily (or on demand via Refresh)
For those situations — or for any historical import going back further than the Bank Feeds sync window — Zera Books' NetSuite import workflow provides the most reliable path.
Common Import Errors and Fixes
| Error | Cause | Fix |
|---|---|---|
| Invalid date value | Date format doesn't match NetSuite locale | Check Setup > Company > Date Format; match CSV format exactly |
| Account not found | Account name doesn't exactly match CoA | Use account internal ID instead of name, or copy exact name from CoA |
| Subsidiary required | OneWorld instance requires subsidiary field | Add Subsidiary column with exact subsidiary name from your setup |
| Duplicate transaction | Same date + amount + reference already exists | Enable "Allow Duplicates" in import settings, or remove duplicate rows |
| Currency not recognized | Using currency name instead of code | Use ISO 4217 three-letter codes (USD, EUR, GBP, CAD, AUD) |