Skip to content

Trace unmatched entries in the bank’s correspondent accounts

An unmatched correspondent entry needs an explanation. Duvo would trace the source records, coordinate the approved investigation and close the case on evidence accepted by the bank.

Get a demo

Proposed application

The proposed scope investigates existing reconciliation breaks, updates their records and closes investigation cases on bank-approved evidence. Journal posting, write-offs, funds movement and final account reconciliation sign-off remain with authorised bank teams.

Nostro break resolution · Illustrative

Illustrative review

Break NB-501 · Synthetic

Account break
Open
Source difference
Debit has no ledger match
Control owner
Reconciliation controller

The correspondent statement contains a debit with no matching ledger entry in the permitted extract. The payment reference needs supporting evidence.

Next action

Request debit evidence: send the approved query, track its response and keep NB-501 open until the controller approves resolution evidence; retain the closure receipt.

Route to accounting: assign the approved review task with both source extracts; an authorised accountant decides whether a posting is needed.

Reconciliation controller approval

The controller approves each investigation action, case update or evidence-supported case closure before Duvo would execute it through the same approval gate.

Illustrative workflow example
View the wider product queue

Nostro break resolution · Illustrative

Proposed workflow using synthetic records.

Adds cases
Reconciliation exception queue
Processes cases
Nostro break resolution
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Unmatched correspondent debit
Scope
Decision
Exceptions
Next action
Break NB-501
Needs Input
Ledger entry unmatched
Correspondent debit
Request debit evidence
1
Break NB-502
In Progress
Value dates differ
Transfer reference
Review timing
0
Break NB-503
Completed
Fee unexplained
Statement charge
Request fee advice
0
Break NB-504
Pending
Two possible matches
Duplicate reference
Refer ambiguous match
1
Break NB-505
Postponed
Resolution evidenced
Controller review
Prepare case closure
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Unmatched correspondent debit

    Unmatched correspondent debit is visible before the action

    The proposed review would trace the statement entry and preserve the unexplained amount until the bank records a supported resolution.

Illustrative workflow example

From unmatched entry to evidenced case closure

A reconciliation engine can identify an unmatched entry without explaining it. The team then has to find the ledger reference, correspondent statement and earlier correspondence, while the unresolved item continues to age.

  1. 0101

    Collect the reconciliation break

    Duvo would read the unmatched entry, original age, account and currency, linking the ledger extract to the relevant correspondent statement.

  2. 0202

    Trace the supporting payment records

    Duvo would compare references, debit or credit direction, amount and value date, then attach available payment or fee evidence without forcing an ambiguous match.

  3. 0303

    Prepare the investigation or finance handoff

    Duvo would draft a query for the record owner or prepare a supported accounting-review task, retaining the unexplained balance.

  4. 0404

    Your team decides

    Approve the break investigation

    The reconciliation controller would approve the request, case update or accounting-review handoff, and approve closure when the required resolution evidence is present. Posting, write-off and final account reconciliation sign-off remain with authorised bank teams.

  5. 0505

    Track the investigation to approved closure

    Within agreed access, Duvo would route the approved action, save its acknowledgement and track the response. Returned resolution evidence would pass through the same controller approval before Duvo would close the investigation case and save the closure receipt. Unsupported differences would remain open.

Trace the break across the two account records

Systems and control details

Begin with masked exceptions from the existing reconciliation engine. Agree reference rules, amount and ageing thresholds, permitted case updates and the evidence required for closure.

Reconciliation exception queue, Correspondent account statement, Bank ledger extract, Payment and fee evidence

  • Reconciliation controller approval

    The controller approves each investigation action, case update or evidence-supported case closure before Duvo would execute it through the same approval gate.

  • Preserve ambiguous and material breaks

    Non-unique references, conflicting currencies and items above the bank’s materiality or age thresholds would remain for review. This workflow would not post a journal or write off an item.

  • Retain the unresolved balance

    Keep source lines, original amount and age, responses, the controller’s decision and action receipts. Duvo would close the investigation only on bank-approved evidence; unresolved accounting differences would remain visible.

Contracted guarantee

5x ROI, guaranteed

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Nostro break resolution

  • When does Nostro break resolution run?

    The bank’s reconciliation run leaves an unmatched or conflicting correspondent-account entry.

  • Who owns Nostro break resolution?

    Bank reconciliation managers and payment control leads

Related processes