Skip to content
Sonic AI
Colleagues reviewing printed statements on a table

10 · Bank rec

Paid is a claim. A deposit is a fact.

Reconciliation is the agreement between billing and the bank. Confident matches settle. The rest wait in a queue for a person.

Book a demoIntegrations

The queue

Read the statement. Don’t chase the already-paid.

Lines arrive from a CSV, a banking connection, or a processor payout. Sonic proposes a match on amount, reference, and the billed party’s name — plus that party’s contacts. In a shipment workspace that party is the shipper, and Paid by asks for a shipper or merchant name.

Sonic AI
S

Matched

₹ 2,14,400

4 lines

Unmatched

₹ 1,00,000

1 line

Open invoices

3

sent unpaid

Needs review

1

operator queue

Statement
12 AprNimbus Cloud NEFTINV-1042₹ 1,00,000SUGGESTED
11 AprWestbound / UTRINV-4418₹ 39,330MATCHED
10 AprDelta PackINV-4431₹ 9,780MATCHED
09 AprApex ToolsINV-0901₹ 64,200MATCHED
08 AprNorthwindINV-0888₹ 1,01,090MATCHED
07 AprWestbound / UTRINV-4400₹ 0MATCHED

Suggested match

₹ 1,00,000

Paid byNimbus Cloud
InvoiceINV-1042
Bill-toNimbus Cloud
Due11 Apr
Confidence98%
Suggested match · you confirm

How it runs

Confident matches settle. The rest wait for a person.

This is the path every line takes. Unknown senders, fee gaps, and split deposits stay in the queue on purpose — they are not a failed match.

  1. 01

    Ingest

    Statement file, connection, or processor payout. A payout net of fees is smaller than the invoice — that gap is variance, not a shortfall.

  2. 02

    Suggest

    Paid by is compared to the billed party and their contacts, so a finance manager’s name can still match the company’s invoice.

  3. 03

    You approve

    Accept the suggestion when it looks right. Match by hand when it doesn’t. Never force a deposit onto the closest invoice to clear the queue.

  4. 04

    The invoice is paid

    A full match creates the payment and Watchtower stops. A partial leaves it sent, with dunning on the remainder.

How they map

A deposit and an invoice are not always one line each.

Cash does not arrive as neatly as billing. Match the shape in front of you — do not force a one-to-one when the bank did something else.

DepositInvoice

1 : 1

One to one

One deposit, one invoice. Confirm it and that invoice is paid.

1 : N

One to many

One transfer covering several invoices. Split the deposit across them rather than parking it on the largest.

N : 1

Many to one

Several deposits for one invoice — instalments, two UTR lines, a remainder after fees. Group the lines so they settle as one payment.

N : N

Many to many

Several deposits, several invoices, one settlement. Group the bank lines, then split across the invoices they actually paid.

What you can do

Four moves on a line. Unmatch before close.

Reverse a mistake before month-end, not after. A partly paid invoice still gets chased, for the right amount.

Accept
Sonic is confident, and it looks right.
Split
One deposit, several invoices. Do not force it against the biggest one.
Write off
A small gap from bank fees or exchange rates. That is variance, not a customer shortfall.
Ignore
It is not a customer payment at all — interest, a transfer, a fee.

The numbers

Both unmatched columns are problems, in opposite directions.

Unmatched deposits mean someone has paid and is still being chased. Unmatched invoices mean the books say money arrived when it didn’t. Work the queue during close — it grows faster than anyone expects.

Sonic AI
S

Unmatched deposits

₹ 1,00,000

1 in queue

Unmatched invoices

3

Sent, no deposit

Matched this month

₹ 2.14 L

4 lines

Variance

₹ 1,890

Fees

Statement
DateDescriptionStatusAmount
12 AprNimbus Cloud NEFT · INV-1042Suggested₹ 1,00,000
11 AprInterest creditUnmatched₹ 420
11 AprWestbound / UTR · INV-4418Matched₹ 39,330
09 AprApex Tools · INV-0901Matched₹ 64,200
08 AprNorthwind Analytics · INV-0888Matched₹ 1,01,090

A payer name that matches nobody stays in the queue.

Overview · unmatched still in the queue

  1. 00

    Platform

    One chain. The order.

  2. 01

    Contracts

    PDF to a typed agreement

  3. 02

    Catalogs

    Who you bill, what you sell

  4. 03

    Subscription

    The schedule is the core

  5. 04

    Shipment model

    Rate cards, not months

  6. 05

    Usage & seats

    Events and snapshots

  7. 06

    Shipment uploads

    Process, confirm, create, invoice

  8. 07

    Invoices

    Drafts grow. Sent do not.

  9. 08

    Watchtower

    Inbox, cadence, a person

  10. 09

    Revenue

    Billed is not recognised

  11. 10

    Bank rec

    A deposit is a fact

  12. 11

    Integrations

    Pipes in and out

Next

See it on your contracts

A walkthrough on the agreements and files you actually bill from — not a slide deck.

Book a demoPlatform overview