Skip to content

Trace unmatched entries on the bank’s nostro accounts

A nostro break can come from a correspondent charge, a value-date difference or a payment booked on one side only. Duvo compares the correspondent statement with the ledger, finds the supporting evidence and drafts the query for each open break.

Book a process call

Nostro break resolution

Needs review

Break NB-501

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

The correspondent statement shows a debit with no matching ledger entry in the extract. The reference needs supporting payment or charge evidence.

Next action

Request debit evidence: the correspondent is queried and NB-501 stays open until the controller approves the resolution evidence.

Route to accounting: an authorised accountant receives both extracts and decides whether a posting is needed.

Controller approval

The reconciliation controller approves each query, case update and closure before Duvo carries it out.

View the wider product queue

Nostro break resolution

Nostro break with a correspondent debit and no ledger match.

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
Debit with no ledger entry
Correspondent statement
Request debit evidence
1
Break NB-502
In Progress
Value dates differ
Outgoing transfer
Review timing
0
Break NB-503
Completed
Charge not advised
Statement fee line
Request charge advice
0
Break NB-504
Pending
Two possible matches
Repeated 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 statement debit has no ledger entry in the extract, so the break stays open with its amount visible until the controller approves a resolution.

From unmatched entry to evidenced case closure

The matching engine leaves a debit on the correspondent statement with no ledger entry. It could be a charge the correspondent took, a payment booked under a different reference or a value-date difference that will clear on its own. Someone has to pull the statement line, search the ledger and payment archive and write to the correspondent, while the break ages.

  1. 0101

    Collect the break

    Duvo reads the unmatched entry with its account, currency and age, and links the statement line to the relevant ledger extract.

  2. 0202

    Trace the supporting records

    Duvo compares references, debit or credit direction, amount and value date, and attaches payment or charge evidence without forcing an ambiguous match.

  3. 0303

    Draft the query or accounting task

    Duvo drafts a query to the internal owner or correspondent, or an accounting-review task, with the unexplained amount kept visible.

  4. 0404

    Your team decides

    Approve the action or closure

    The reconciliation controller approves the query, case update or accounting handoff, and approves closure once the resolution evidence is in the case.

  5. 0505

    Track to closure

    The controller's approved query goes to the correspondent bank or the internal booking team, and the acknowledgement is saved. Evidence that comes back returns to the controller, who approves the closure. Unsupported differences stay open.

Trace the break across the two account records

Systems and control details

Duvo works from the open breaks your reconciliation engine already raises, starting with masked exceptions. Reference rules, amount and ageing thresholds, permitted case updates and the evidence required for closure are agreed first.

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

  • Controller approval

    The reconciliation controller approves each query, case update and closure before Duvo carries it out.

  • Ambiguous and material breaks stay with the bank

    Non-unique references, currency conflicts and items above the bank’s materiality or age thresholds go to review. Duvo does not post journals, write off items, move funds or sign off the account reconciliation.

  • Keep the unresolved balance

    Source lines, original amount and age, replies, the controller’s decision and action receipts stay together. Unresolved accounting differences remain visible after an investigation closes.

What teams ask about Nostro break resolution

  • Does Duvo replace our reconciliation matching engine?

    No. Duvo investigates the breaks your existing engine leaves open. The engine and its matching rules stay as they are.

  • Which correspondent statement formats does Duvo work with?

    MT940, MT950 or camt.053 statements as your bank receives them, alongside your ledger extract. Formats and reference rules are confirmed during scoping.

  • How does Duvo treat a break with two possible ledger matches?

    It attaches both candidates and refers the break to the controller rather than picking one. Ambiguous matches are never closed without the controller’s decision.

Related processes