Releasing a payment file

A payment file is the instruction your bank acts on. When it leaves, money moves.

Each payment in a file was already approved by its owner. A client’s own signatories approved a client’s payment, and your approvers approved your bank’s own. So a file that passes its checks goes out as soon as it is built. A person releases a file only when a check fails.

The checks every file passes

Check What it catches
The file is unchanged since it was built An altered or injected file
The lines add up to the file’s header, and to the payments released into it A short, padded or doubled file
The file total is at or under your automatic release limit A fault that inflates a whole run, such as every payment doubled

If all three pass, the file is sent. If the lines or the total fail, the file is held on Releases for a person. If the file was altered, it is refused outright. A person cannot release an altered file.

What you see

Open Releases to see every payment file held for a person — across all your operating entities, because you release the day’s files, not one entity’s.

Each file shows its channel, its value, and how many payments it contains. The Held Because column says which check held it.

Held Because shows What to do
Lines do not add up to the file total Do not release it. Raise it with your payments support team.
Over the automatic release limit Check the total against the day’s payments. Release it if it is right.

Check the channel, value and item count against what you expect before you release anything.

Select a row to open the file itself. You see its header, the payments it carries and any returns against them. The Release button on the row still releases the file without opening it.

The identity a file goes out under

A file also names its participant — the identity the clearing scheme issued you, through the bank that sponsored it. That identity is what the scheme reads in the file header, and it is what the scheme’s return file is addressed back to.

The system chooses it when the payments are collected, from the entity the payments belong to and the bank account they settle through. You do not pick it per file. If no identity fits, the payments are not collected at all and nothing reaches this queue — the system will not send money out under an identity you do not hold.

The Submissions panel on an operating entity names the participant on each submission, so you can see which identity a day’s payments went out under.

See scheme participants for how these are recorded.

Releasing a held file

  1. Open Releases.
  2. Read Held Because.
  3. Check the file’s channel, value, and item count.
  4. Select Release.
  5. A second approver signs it off.

Nothing is sent until that second person approves. Until then the file stays in the queue and the money stays put. You cannot release a file that was never held.

Why a person releases only a held file

The approval belongs to the payment, not to the file. A person reading thousands of lines cannot spot the one that was altered. The checks can. So the person’s job is the file the checks could not clear, and a second approver still signs that release.

stateDiagram-v2
    [*] --> AwaitingFile: payments collected
    AwaitingFile --> Sent: file built and every check passes
    AwaitingFile --> AwaitingRelease: file built, a check fails
    AwaitingRelease --> AwaitingApproval: someone releases it
    AwaitingApproval --> Sent: a second person approves
    AwaitingApproval --> AwaitingRelease: approval refused
    Sent --> [*]

Worked example

Woodgrove Bank sets its automatic release limit at CAD 1,000,000.00.

File total What happens
CAD 999,999.99 Sent as soon as it is built
CAD 1,000,000.00 Sent as soon as it is built
CAD 1,000,000.01 Held, reading Over the automatic release limit

A limit applies only to its own currency. If the only limit set is ZAR 1,000.00, a CAD 1,200,000.00 file is sent.

If a file is missing

If a submission reads Awaiting File, its payments were collected but no file was built yet. Day-end builds any missing file that night, in the step Generate missing payment files. The file then joins the release list as usual.

If a file cannot be built, day-end counts it as failed every night until someone fixes the cause. Causes include a removed channel participant, an incomplete mandate, or a submission whose payments do not add up to its total.

The attestation

When the system builds a file, it records a fingerprint of the exact bytes it built. The Attested column shows the first part of that fingerprint.

Just before the file goes to the bank, the system fingerprints it again and compares. They must match.

What happened What you see
The file is unchanged since it was built It is sent
The stored file has been altered It is refused, and nothing is sent
No fingerprint was recorded It is refused, and nothing is sent

A refusal is not a delivery failure, and you cannot retry your way past it. A delivery failure means the bank could not be reached, and you can retry that. A refused file means what is stored is not what was built — raise it rather than retry it.

The fingerprint is kept in a record that cannot be edited afterwards, which is what lets anyone prove later what the file contained.

Files generated overnight

End of day builds the day’s payment files and sends each one that passes its checks. A file that fails a check is in the queue the next morning, waiting for you.

Retrying failed deliveries never sends a held file. Only a person’s release does.

What this does not prove

The fingerprint proves what was built and that two people authorised it. It does not prove to your bank that the file came from you — that needs a signing key your bank issues, which is not yet in place.

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.