Inside your NetSuite account
Loading and extracting data
The import says the journal doesn't balance, and I can't see why.
Journal imports checked before anything loads. Exports in your layout.
For accountants and controllers who load journals and pull data from NetSuite.
Month-end, the same loop
You load the month's journal entries through the CSV Import Assistant. Part loads, part fails, and the error file returns the failed rows with an error message. You guess, fix and reload what failed.
Exports are their own loop: run the saved search, fix the columns, send it.
Meanwhile the close waits, and people work from exports of data already live in NetSuite.
An import that explains itself. Exports that arrive ready.
Native first, with pragmatism. If a native feature covers the need, SeamSet sets it up (a saved search, a workflow, an approval rule), through your NetSuite admin's approval, and writes no code. If the native route would cost more to set up and run than the need is worth, SeamSet says so and proposes the lighter option. Account features stay your admin's switch.
- Checks before anything loads. Grouping, balance, open periods and your account's rules, entry by entry. By default, nothing loads until every entry passes.
- Errors you can act on. "Rows 1 to 9 share one external ID, so NetSuite reads them as one entry, and it does not balance."
- Order files too. From customers, web shops or marketplaces, checked before they load: each held order waits, with its reason.
- Exports on a schedule. Your columns and subtotals, emailed on the schedule you set.
Example with a fictional company and figures. An import screen for the file je-2026-08-close.csv, 38 journal entries for Orrin & Vale Ltd, August 2026. Every entry is checked before anything loads: grouping, balance, open periods and the account's rules. 36 entries are ready and 2 are held.
Held entry ACR-0831-07, rows 12 to 15: the rows share one external ID, so NetSuite reads them as one entry, and it does not balance. Row 12, 6420 Freight and delivery, debit 2,400.00. Row 13, 2150 Accrued expenses, credit 2,400.00. Row 14, 6310 Software subscriptions, debit 1,275.00. Row 15, 2150 Accrued expenses, credit 1,257.00. Debits 3,675.00, credits 3,657.00, 18.00 apart.
Held entry RCL-0729-02, rows 31 and 32: dated 29 Jul 2026, and July 2026 is a closed period. Row 31, 6100 Office supplies, debit 312.40. Row 32, 6420 Freight and delivery, credit 312.40.
Option selected by default: Load nothing until all entries pass. The alternative: Load the 36 ready entries. Marked as native: entries that load become journal entries in the NetSuite account.
Inside your NetSuite account
Your admin connects SeamSet to your account and decides what it can access.
The import screen sits in your NetSuite account, and your files load there. Emailed exports leave NetSuite with the email.
This is the last mile between NetSuite and a person: a file, a format, an error message. Syncing two systems is an integration platform's job.
Your admin sees this list before approving.
| What | Access |
|---|---|
| Journal entries and sales orders | Write, only the fields in your file |
| Accounts, periods, subsidiaries and your other lists | Read, to check the file |
| Saved searches | Read, for exports |
| What SeamSet installs | The import screen and its scripts, in one SDF project, after your admin approves |
SeamSet builds a first version in minutes. Every change is tested before it goes live, and your admin approves it before go-live. The log records who asked, who approved, what changed and when. SeamSet keeps it, and you can export it at any time. Each change is tagged Reversible, Removes stored data or Cannot be undone before approval.
Bring the import that fails.
Tell us about the import or the export your team fixes by hand each month. We'll talk it through.