Sweep breaks

A sweep run moves money between the accounts of a liquidity structure. Each movement between one pair of accounts is a sweep leg. If a leg cannot finish, it breaks. The rest of the run carries on.

A broken leg is a named, worked item. It appears on the Sweep breaks worklist until someone resolves it, or until the pair’s next run takes over.

Find a break

Open Back office → Payments & Collections → Sweep breaks. The worklist shows every broken leg across all structures, the oldest first.

Column What it shows
Broken on The trading date the leg broke
Days open How long the break has waited
Client The client that owns the structure
Structure The liquidity structure the leg belongs to
Amount What the leg should have moved, in the structure’s currency
Why it broke The reason, in plain words

Filter by Why it broke or by Client to narrow the list. Select a row to open the leg.

Why a leg breaks

Reason on screen What happened
The paying account could not cover the amount The paying account lacked the funds when the leg posted
One of the accounts could not be posted to An account was frozen, closed or blocked
The posting was refused The ledger refused the movement for another reason
The payment route changed before the leg was sent An account moved to a different venue between the run and the retry
The payment could not be sent The instruction to another system failed
The receiving bank rejected the payment The other bank refused the instruction
The receiving bank has not confirmed the payment No statement confirmed the movement in time

The last three apply only to legs that leave your books. Today every sweep is a book transfer between accounts your organisation holds.

Read a leg

The leg opens on Details. It shows the state, the reason, the amount, both accounts and the venue. Select an account name to open that account.

If the leg was settled by another movement, Details also shows the settled amount and the difference. If a later run took the leg over, it shows the date that happened.

History lists every change of state, with when it happened.

stateDiagram-v2
  [*] --> Executing
  Executing --> Completed
  Executing --> Broken
  Broken --> Completed: Retry succeeds
  Broken --> Broken: Retry breaks again
  Broken --> Cancelled: Cancel
  Broken --> SettledByMovement: Record settling movement
  Broken --> Superseded: Next run for the pair

Resolve a break

You have three choices. The leg shows only the ones open to it. If your organisation requires a second approver, each choice waits for approval before it takes effect.

Retry the leg

Retry sends the same movement again. It uses the same amount and the same value dates, on today’s trading date.

  1. Fix the cause first, for example lift the freeze on the account.
  2. On the leg, select Retry.
  3. Select Retry in the sheet.

If the cause is fixed, the leg completes. If not, it breaks again with the new reason. Retry is refused while the client’s liquidity service is suspended.

Retry does not work the amount out again. If the balances have moved since the run, cancel the leg instead and let the next run sweep the true position.

Cancel the leg

Cancel closes the leg with no money moved. The next run works from the balances as they stand.

  1. On the leg, select Cancel leg.
  2. Enter why you are cancelling it. A reason is required.
  3. Select Cancel leg in the sheet.

If the receiving bank has not confirmed the payment, you cannot cancel. The money may already have moved. Record the settling movement instead, or wait for the statement.

Record a settling movement

Use this when the money moved by another route, for example a manual transfer. Nothing posts. The leg closes against the transaction you name.

  1. On the leg, select Record settling movement.
  2. Check Account the transaction posted to. It starts as the receiving account.
  3. Enter the Transaction.
  4. Select Record.

The transaction must post to one of the leg’s two accounts. It must post on or after the leg’s trading date. It cannot already settle another leg. Its amount may differ from the leg’s.

A worked example

A leg from account B to header account H should move 3,000.00. It broke on 16 November. On 17 November, Sam posts a manual transfer of 2,500.00 from B to H. Sam records that transfer as the settling movement.

Field Value
Amount 3,000.00
Settled amount 2,500.00
Difference 500.00

The leg closes as settled by movement. The next run sweeps whatever is then above B’s target.

When the next run takes over

If a leg is still broken when the pair’s next run evaluates, that run closes it as superseded. The new run already moves what the old leg would have moved. A retry afterwards would sweep the account twice.

A superseded leg leaves the worklist. For a pair swept every night, you have about a day to retry. For a pair swept monthly, you may have weeks.

The run supersedes the leg even if the pair needs no sweep that night.

What the client sees

The client sees each structure’s sweep history in the client app, read-only. Each leg shows its accounts, amount and state. A broken leg shows its reason in the same plain words. The client cannot retry, cancel or settle a leg. See the sweep history.

How a sweep appears on a statement

Each sweep posts one debit and one credit for every value-dated part. Both carry the ISO 20022 bank transaction code CAMT/ACCB/SWEP, as the standards register row for that code records. The value date is the date the swept funds were held, and the booking date is the sweep’s trading date.

What your organisation configures

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.