n-How Bank Reconciliation Works in NetSuite (and Where It Stops Being a Five-Minute Job)
NetSuite reconciles a bank account by comparing your NetSuite register against the real bank statement, either through Transactions > Bank > Reconcile Bank Statement for a manual match, or the newer Match Bank Data screen if you've got a live bank feed connected. Either way, you're confirming which transactions actually cleared and chasing down the ones that don't match on their own.
The full walkthrough
1. Get the statement data into NetSuite. If you've connected a live bank feed (through the Bank Feeds SuiteApp or a direct bank connection), transactions download automatically. If not, you import a statement file, usually CSV or OFX, from your bank's online portal.
2. Let NetSuite suggest matches. On the Match Bank Data page, NetSuite lines up downloaded bank transactions against existing NetSuite records, checks, deposits, bill payments, by amount and date. You review and accept the matches it got right.
3. Handle what didn't match. Bank fees, interest, a wire that hit the account before anyone recorded it in NetSuite: anything without a matching NetSuite transaction needs a new journal entry or payment created on the spot before it can clear.
4. Enter the statement ending balance and date. On the classic Reconcile Bank Statement page, you type in what the bank statement says the balance should be as of that date.
5. Resolve the difference. NetSuite shows you the gap between the statement balance and your cleared register balance. If it's zero, you finish the reconciliation. If it's not, you're going line by line until you find what's missing or duplicated.
Why this still eats half a day at month end
NetSuite's own matching handles the easy case well: a transaction that already exists in NetSuite at the exact amount and date the bank reports it. Real businesses don't run on the easy case alone.
The transactions that actually cause the pain are the ones that never had a clean 1:1 match to begin with. A Stripe or PayPal payout lands as a single lump deposit covering forty separate invoices. A payment processor's batch settles three days after the sale it's attached to. A wire transfer between subsidiaries needs to be split across two entities before it means anything on either set of books.
None of that is a NetSuite bug. It's just more transaction volume and more payment complexity than a line-by-line matching screen was ever going to absorb cleanly, no matter how good the auto-match logic gets.
What we build on top of NetSuite reconciliation
Batch payouts split and matched automatically
A Stripe, PayPal, or Shopify payout arrives as one lump deposit covering dozens of invoices. We build the automation that splits it back out and matches each piece to the right NetSuite invoice, instead of someone doing that math by hand every payout cycle.
Recurring unmatched lines that stop needing a human
The same bank fee or interest charge shows up every month and needs the same journal entry created before it'll clear. Once the pattern is real, we automate creating and posting it, so reconciliation isn't re-solving the same five-minute problem fifty times a year.
What's sitting in your unmatched list right now?
Tell us what won't clear on its own, batch deposits, intercompany transfers, a payment processor's timing, and we'll look at whether it's worth automating.
Still clearing NetSuite's unmatched transactions by hand every month?
Reconciliation is one specific place this shows up, but it's rarely the only one. If your team is re-doing the same matching, splitting, or journal entry work every single cycle because NetSuite's native tools weren't built for your exact transaction pattern, that's the kind of thing we build around. NetSuite doesn't have to be the system in question either; we automate whatever's eating time, wherever it lives.
Let's talk