NetSuite: Import GL Detail

Description

Imports general ledger transaction-line detail from NetSuite over your NetSuite connection into a project table — the posting-level lines behind your balances, for reconciliation, drill-down, or a detailed P&L. Pick the connection, name a target table, and set the period and subsidiary; the step pulls the lines and writes them, with no SuiteQL to author or maintain.

This is one of the canned NetSuite import steps. Each runs on a shared read layer that refreshes the OAuth token, pages through large results, and retries transient errors for you, so a full-period pull comes back complete without hand-tuning. For period balances rather than lines, use NetSuite: Import Balances.

Configuration

Field	Required	Notes
NetSuite Connection	Yes	The NetSuite connection to read through, filtered to connections of type NetSuite.
Target Table	Yes	The project table the transaction lines are written to. It is overwritten in full on every run.
Start Date	No	The earliest transaction date to include, YYYY-MM-DD, inclusive. Leave blank for no lower bound. Given together with End Date, the pull is automatically windowed into date chunks to stay under NetSuite’s SuiteQL row ceiling — see the caution below.
End Date	No	The latest transaction date to include, YYYY-MM-DD, inclusive. Leave blank for no upper bound.
Subsidiary	No	A NetSuite subsidiary internal ID to restrict the pull to one subsidiary. Leave blank for all subsidiaries.
Accounting Book	No	A NetSuite accounting book internal ID. Leave blank to pull the primary book (internal ID 1) only, or enter all to sum across every book.
Account Number	No	An exact GL account number to restrict the pull to one account. Leave blank for all accounts.
Posting Period	No	A NetSuite posting/accounting period internal ID. Leave blank for all periods.

Caution

Multi-book accounts: a NetSuite account running Multi-Book Accounting posts one row per book per transaction line, so pulling every book unfiltered N-times-counts a total. Leaving Accounting Book blank pulls the primary book only. Set it to all only if you deliberately want a cross-book total, or to a specific book’s internal ID for that book alone.

Note

Bound the period to the slice you need. Every run replaces the whole target table, so a scheduled pull re-extracts the full result each time — a rolling date window keeps a recurring GL pull fast rather than re-reading all of history.

Note

NetSuite’s SuiteQL API caps a single query at ~100,000 rows without SuiteAnalytics Connect. Giving both Start Date and End Date lets PlaidCloud proactively window the pull into chunks that stay under that ceiling — GL detail is the pull most likely to approach it, so this matters more here than on Import Balances. An open-ended pull that turns out to cross the ceiling fails with a message asking you to add a date range, rather than silently returning a truncated result.

Related

• NetSuite Steps
• Import NetSuite Financials — step-by-step walkthrough
• Connect to NetSuite
• NetSuite REST Connector