addSourceList Bank File Imports in NetSuite 2026.2
NetSuite 2026.2 adds addSourceList() for ordered bank file imports, with a 100-file cycle limit and plug-in-managed duplicate prevention.
NetSuite 2026.2 introduces addSourceList() for ordered bank statement file selection through a Financial Institution Connectivity Plug-in. NetSuite processes up to 100 files per import cycle across all calls and silently ignores additional entries. The plug-in must supply remaining files in later cycles and separately prevent duplicate submissions.
What Changes with Bank File Selection?
The new addSourceList(options) function lets a connectivity plug-in identify the files NetSuite should retrieve during an import cycle. Called through the context supplied to getTransactionSources(), it accepts an ordered array of file-name objects. The plug-in controls both file selection and processing order.
This submits a file list, not file contents. For each selected file, NetSuite invokes getTransactionData() and supplies its name through context.sourceName. The plug-in uses that value to identify which file to retrieve, then supplies its contents through addDataChunk() during that invocation.
Selecting a file and delivering its data are therefore distinct responsibilities. During implementation review, verify that every submitted name can be resolved when NetSuite requests its contents.
How Do You Call addSourceList()?
The function is an object function with the declaration function addSourceList(options) and a return value of void. Its parent is the context supplied to getTransactionSources().
| Parameter | Type | Required | Description |
|---|---|---|---|
options | Object | Yes | Contains the source list. Available since NetSuite 2026.2. |
options.sourceList | Object[] | Yes | Ordered array of file-identifying objects. NetSuite accepts up to 100 files across all calls in one import cycle. Available since NetSuite 2026.2. |
options.sourceList[].name | String | Yes | Identifies the file to retrieve. Must contain at least one non-whitespace character and must not exceed 255 characters. NetSuite preserves the supplied name. Available since NetSuite 2026.2. |
Example: Submit Two Bank Statement Files
context.addSourceList({sourceList: [ {name: 'bank-transaction-01.csv' }, {name: 'bank-transaction-02.csv' }]});NetSuite processes these files in the supplied order. When requesting each file’s data, it passes the corresponding name through context.sourceName.
Implementation check: Validate names before submitting the list. Test empty names, whitespace-only values, and the 255-character boundary. Because NetSuite preserves names, retrieval logic should work with the exact values submitted rather than assume NetSuite will normalize them.
What Happens After the 100-File Limit?
The 100-file limit applies to the entire import cycle, not separately to each addSourceList() call. Splitting a larger list into multiple calls does not increase the number of files NetSuite processes. Entries beyond the first 100 are ignored without an error in either Bank Import History or the logs.
For example, submitting 70 files followed by another 50 in the same cycle supplies 120 entries, but only the first 100 are processed. The remaining 20 must be supplied during subsequent import cycles. That follow-up is the plug-in or SuiteApp’s responsibility; do not design the integration around an assumption of automatic carry-forward.
For implementation planning:
- Select no more than 100 intended files for each cycle.
- Maintain a record of files submitted across cycles.
- Retain remaining files for later selection.
- Check that selection order does not repeatedly leave older files behind.
- Compare the intended selection with your tracking records rather than relying only on import errors.
Monitoring implication: An absence of errors does not establish that every file offered to the interface was processed. Overflow is explicitly silent, so integrations that may exceed the cap should track pending files independently of import errors.
How Are Empty Lists and Duplicate Names Handled?
An empty source list produces a successful Bank Import History record indicating that no files were selected. NetSuite does not invoke getTransactionData() in that case. Administrators reviewing a successful history entry should therefore distinguish a no-files-selected outcome from an import that actually retrieved statement data.
Duplicate file names are accepted by the interface. The plug-in must track files across import cycles and prevent duplicate submissions and unintended reprocessing. File-name acceptance is not a duplicate-control mechanism, and preserving the supplied name does not make it unique.
As a practical test, run the selection logic across consecutive cycles with the same available files. Verify that previously submitted files are not unintentionally selected again and that deferred files remain eligible. The supplied documentation does not prescribe a tracking storage design, so that choice belongs to the implementation.
What Prerequisites and Existing Limits Still Apply?
The Financial Institution Connectivity Plug-in interface uses SuiteScript 2.0, and both entry point scripts and supporting libraries must use SuiteScript 2.0. Creating an implementation requires creating and uploading the plug-in script file, together with any required utility files. Alternative implementations can customize the core logic using the interface’s defined function names, parameters, and return types.
To run the plug-in, configure and save a format profile that uses it. Connectivity plug-ins support direct financial-institution connections and automated daily inbound transmissions for cash balance reporting and scheduled statement downloads. Working with a Bank Statement Parser Plug-in enables bank-data imports for reconciliation.
Account for these constraints when implementing source-list selection:
- No IP allow-list: The connectivity plug-in does not let you add IP addresses to an allow-list.
- Conditional ZIP support: ZIP retrieval is supported only when the Bank Statement Parser Plug-in can handle the files.
- Existing chunk limits: File contents must be supplied through
addDataChunk()during the correspondinggetTransactionData()invocation. Existing chunk-size limits still apply; their numeric values are not specified in the supplied documentation.
Some connectivity plug-ins may require financial-institution credentials. NetSuite itself does not request or store those credentials, but permits the plug-in to save them securely through a third-party service or customization. Review credential handling separately from file-list selection.
Who This Affects
- SuiteScript developers and SuiteApp maintainers: Implement ordered selection, content retrieval, cross-cycle tracking, and duplicate prevention.
- NetSuite administrators: Verify the saved format profile, parser compatibility, and monitoring for deferred files and empty selections.
- Banking and reconciliation teams: Recognize that successful history can mean no files were selected, and that excess files require later cycles before their data can be imported.
Key Takeaways
- NetSuite 2026.2 adds
addSourceList()for ordered bank statement file selection. - The 100-file cap spans all calls within one import cycle; overflow generates no error in Bank Import History or the logs.
- The plug-in must supply remaining files in later cycles and prevent duplicate submissions across cycles.
- File names must contain a non-whitespace character and stay within 255 characters.
- Empty lists create successful history without calling
getTransactionData().
Frequently Asked Questions (4)
Does the 100-file limit apply to each `addSourceList()` call or to the entire bank import cycle?
How does NetSuite retrieve the contents of files submitted with `addSourceList()`?
Does NetSuite prevent duplicate bank file submissions across import cycles?
What happens when the plug-in submits an empty source list?
Weekly Update History (1)
Updated Limitations of Using a Financial Institution Connectivity Plug-in to include file limits and requirements.
View Oracle DocsWas this article helpful?
More in Banking
- Enriched Bank Data for Improved Transaction Matching in NetSuite
Updated for NetSuite 2026.1: Enriched Bank Data feature enhances transaction matching accuracy using generative AI.
- NetSuite Match Bank Data: Match, Clear and Reconcile
Use Match Bank Data to review bank lines, resolve exceptions and submit transactions before completing a NetSuite statement reconciliation.
- Testing Versapay Payment Gateway Connection in NetSuite Pay
Connect and test Versapay Payment Gateway for NetSuite Pay, verifying configurations safely without financial risk.
- Australia Bank Feeds SuiteApp Enhancements for NetSuite 3.0.0
NetSuite 2026.2 adds ANZ reporting updates, Singapore billing validations and GST InvoiceNow access, and UAE electronic invoicing.
Also from NetSuite 2026.2
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- NetSuite Next: Readiness, Preview, and Ask Oracle
Eligible administrators can request a NetSuite Next preview, set up Ask Oracle, and prepare data, roles, customizations, and navigation.
Advertising
Reach Banking Professionals
Put your product in front of NetSuite experts who work with Banking every day.
Sponsor This Category