MatchPoint / Bank Reconciliation
Bank Reconciliation
Matching that works from certainty down to judgement — starting with the payment files NetSuite already generates, and never confirming anything it can't justify.
We made the payment — so we know what's on the statement
When you pay suppliers through NetSuite Electronic Payments, NetSuite produces a payment file (a pain.001) and the whole run lands on your statement as a single debit. By the time it arrives, the answer already exists: the file says exactly what was paid, to whom, settling which bills. MatchPoint reads that same file and clears the entire batch in one move — file, statement and ledger all agreeing. A three-way check, not a hopeful amount match.
Certainty first, guesswork last
The engine works the statement in layered passes — deterministic first, fuzzy last — so the safest matches confirm automatically and only genuine exceptions reach a person. Every candidate is scored: exact amount is just the baseline, and the score climbs as dates, references and the counterparty line up. Matches must also be unique — three identical amounts on each side are never gambled on.
Matching on who, not just how much
A statement line nearly always says who the money went to or came from, and NetSuite knows the entity on every transaction. MatchPoint compares the two — forgivingly, because banks truncate and mangle names ("1001 - Google LL" still ties to "Google LLC"). It's what makes round-number matches safe: £100 alone is a coin toss; £100 to a counterparty you recognise on the right date is a match you can stand behind.
Suggestions with their reasoning
Below the auto-confirm threshold nothing posts silently. Fuzzy descriptions, near dates, and the awkward shapes — one BACS debit covering five invoices, a clutch of receipts making up one posting — surface as ranked suggestions with the why attached. You approve its thinking rather than hunting for the answer.
Timing differences, kept
Outstanding cheques and deposits in transit are proper objects with a type, a reason and a history — they carry forward into next period automatically. None lost since launch.
It learns your coding
Bank fees, FX charges and standing payments look the same every month. Code one by hand once or twice and MatchPoint proposes the same treatment next time.
Approval & audit trail
Preparer submits, approver signs off — separation of duties enforced, every action timestamped, supporting documents attached. SOX-ready out of the box.
Statements in, however your bank works
CSV, BAI2 and MT940 file upload, or a direct open banking feed where your bank supports it. Accounts map to NetSuite subsidiaries and GL accounts automatically; multi-entity and multi-currency run in parallel within the same close.
90%+
of lines auto-matched from the first month
100%
match rate on supplier payment runs
75%
reduction in time spent per period
Read more on the blog: Introducing Bank Reconciliation in MatchPoint · Why we reconcile against NetSuite's own payment files