Flowwiz / Reconciliation

[Cash application]

Match the payment.
Explain the exception.

One payment, several invoices, and the allocation still sitting in a remittance email. That gap is where unapplied cash lives.

01

Detect the payment

The incoming amount, bank reference, and date picked up from the feed.

02

Find the remittance

The email that explains how the payment should be allocated.

03

Match and validate

Invoice references read, totals checked, partial payments kept visible.

Cash application workflow

From an incoming payment to a cleared invoice.

One consolidated payment, several invoices, and the allocation still sitting in a remittance email. That gap is where unapplied cash accumulates.

  1. 01Detect

    The incoming payment is picked up from the bank feed with its amount, reference, and date.

  2. 02Find

    The remittance email that explains the allocation is located in the customer thread.

  3. 03Match

    Invoice and project references are read out of the remittance and matched to open items.

  4. 04Validate

    Totals are checked against the invoices, including partial payments and short payments.

  5. 05Apply or route

    The match is posted, or the exception goes to a person with the evidence attached.

Payment context · Meridian LabsHigh confidence
Incoming payment$6,000Reference ML-1042
Invoice INV-1042$6,000Remittance attached
AmountAgrees to the cent
ReferenceML-1042 appears on the invoice and in the remittance
RemittanceApplies the full balance to a single invoice
Next stepPost the match, or hold for review before applying

One payment, many invoices

When the allocation is not one-to-one.

A single transfer often settles several invoices, spans projects, or arrives short. The workflow reads the intended allocation rather than guessing from the total.

Atlas Services · payment $9,200Needs review
InvoiceRemittance lineAmountState
INV-1051Applied in full$6,000Ready
INV-1055Applied in full$2,400Ready
INV-1058Short by $180$800Short payment

Exceptions

What holds a match back.

An unclear reference is not a failure. It is a task for a person, and it should arrive with everything they need to decide.

  1. 01Keep the evidence

    Payment, remittance, and candidate invoices stay together on one screen.

  2. 02Explain the gap

    The workflow says what does not line up: amount, reference, period, or confidence.

  3. 03Route to an owner

    The exception goes to the person responsible, not to a shared queue.

  4. 04Resolve and resume

    Once decided, the match is posted and the collection sequence continues.

Unapplied cash · exceptions3 open
Unidentified payer$3,400 · no remittance found$3,400Needs owner
Northstar StudioPays $180 short of INV-1058$800Short payment
Meridian LabsReference matches two open invoices$2,850Ambiguous

Coverage

Everything that goes into clearing unapplied cash.

Reconciliation works from the same records the collections workflow uses, so a match and a reminder never disagree.

FAQ

Before you go further.

What should I review before accepting a match?

The amount, the bank reference, and the remittance line together. The evidence panel shows all three against the candidate invoice so the decision takes seconds rather than a search.

How are unclear references handled?

They stay visible as exceptions with their supporting detail attached, and route to the person responsible rather than being auto-applied or dropped.

What happens to short payments?

The difference is kept as an open item on the invoice, and the collection workflow picks it up rather than treating the invoice as settled.

Does this reduce unapplied cash?

It is designed to. Payments that would otherwise sit unmatched until someone reads the remittance email are matched from the allocation details instead.

Does it work with one payment covering several invoices?

Yes. The remittance lines are read individually and matched to their invoices, so a consolidated transfer is allocated correctly.

Where does the remittance come from?

The customer email thread. Finance Inbox has already classified it as a remittance, so the allocation detail is already tied to the right account.

Start

See it with your team’s context.

Bring your workflow, your systems, and who approves what.

Book a demo

REVIEW Before the decision

The context, then the call.

Atlas Services has disputed invoice INV-1039 ($8,400). The purchase order reference on the invoice does not match the PO on file, and the customer has asked for a corrected copy before paying.

Agent recommendation

Confirm the correct purchase order with the account owner, reissue the invoice, and hold the collection reminder until the dispute is closed.

See this workflow in a demo