Skip to content
Clarative

MatchPoint · Bank reconciliation

Bank reconciliation that only lets you finish when it reconciles.

Import your bank statements, match them to the NetSuite ledger and clear the differences. MatchPoint tells you exactly what stands between you and a reconciled account.

The bank reconciliation matching workspace in MatchPoint: bank statement and GL transactions side by side with suggested matches.

The problem

A bank reconciliation is only finished when the difference is nil. Done in a spreadsheet, it's easy to call it done when it isn't — and to lose the timing items that explain the gap.

In detail

What bank reconciliation gives you.

What you get

  • Statement import

    CSV (including NatWest Bankline), MT940, camt.053 and BAI2.

  • Matching

    Automatic matches and suggestions, with one-to-many and many-to-many matching when you need it.

  • Timing items

    Unpresented payments and deposits in transit are set aside and carried forward until they clear.

  • Bank charges and interest

    Proposed as journals, approved, then exported for NetSuite's import assistant.

  • Submit only when it's right

    Submission is blocked until the statement balance is in, every line is matched or explained, and the difference is nil — and MatchPoint tells you what's left.

  • Payment files

    pain.001 payment files, with maker and checker.

  • Locked months stay locked

    Once a month is approved and closed, it can't be changed by a later import.

From statement to reconciled

MatchPoint tells you exactly what's left.

01

Import & match

Bring in CSV, MT940, camt.053 or BAI2. Automatic matches and suggestions handle the bulk, with one-to-many matching when you need it.

02

Explain the rest

Set aside unpresented payments and deposits in transit as timing items; propose bank charges and interest as journals.

03

Submit when nil

Submission is blocked until the statement balance is in, every line is matched or explained, and the difference is nil.

Explained matching

Every match explains itself.

MatchPoint proposes each match with a plain-language reason and a confidence score. It confirms a match automatically only when it’s clear-cut and the only possible pairing; everything else is a suggestion that someone accepts or dismisses.

An opened suggested match in MatchPoint bank reconciliation: ACME Analytics' £7,661.76 bank line matched to two GL receipts (£2,334.70 and £5,327.06), labelled 1:2 and 75%, with the reason 'one bank line matches 2 GL postings', variance 0.00, and Accept / Dismiss buttons.

An explained match — scroll, or hover a point

Confirm before launch: Hotspot regions measured by eye against this crop; nudge if the capture is re-exported. The match shown is the lower of the two suggestion cards.

The difference

See what explains the difference.

The gap to nil is split into what’s already explained and what isn’t. Explained items include timing items — unpresented cheques and deposits in transit — that carry forward and clear automatically, and fee journals awaiting approval. So you can see exactly what’s standing between you and nil.

Statement balance
£3,512,034.48
GL balance
£3,427,774.24
Difference−£1,643.76
Explained by open lines−£1,769.16
Unexplained£125.40

Example figures from the EMEA Operating reconciliation.

The Timing differences tab in MatchPoint bank reconciliation: unpresented payments, a bank charge awaiting its journal and a receipt not yet in the ledger, each with a reason and the side it sits on, marked to carry forward until they clear.
Timing items roll forward until they clear — unpresented payments, deposits in transit and fee journals awaiting approval.
Confirm before launch: Deliberately the US Operating capture (EMEA has fewer timing items). The breakdown tile on the left uses EMEA example figures (£) while this tab is US Operating ($), so the two illustrate the idea rather than tie line for line.

The finish line

Submit only when the difference is nil.

Nothing unmatched, every timing item set aside, and the statement tied to the ledger — then it goes to a second person to approve.

A bank reconciliation in MatchPoint reconciled to a nil difference, with every line matched and the statement tied to the ledger, ready for approval.

More of MatchPoint

Explore the other modules.

01Reconciliation sign-off02You’re hereBank reconciliation03Cash application & credit control04Intercompany05Balance sheet & journals0606Approvals

See a reconciliation reach nil.

A 30-minute walkthrough on Calder Systems' bank reconciliation — import to nil — then a conversation about yours.

Book a demoBack to MatchPoint