The payments area

Payments on the main menu is your payments day in one place. What needs working now, the instruction lists behind it, and the exceptions that need a decision.

Everything it shows lives somewhere else — on an account, on a bank account, on a counterparty. This is the queue over them, so you start from the work rather than from the record.

What is in it

Group What it holds What it is for
Today Releases · Returns The two things that need working today
Instructions Direct Debits · Direct Credits · Standing Orders · Debit Orders Every instruction of each kind, whatever its state
Exceptions Blocked Collections Collections held back because the authority is not in order

You only see the groups your organisation licenses. A tenant that licenses no payments feature has no Payments item at all.

Today

Releases is every payment file a check held back for a person. A file that passes its checks is sent without waiting here. See releasing a payment file.

Returns is every return file the schemes have sent back, including the ones that belong to no single legal entity and the ones that were refused. See return files.

Both are the day’s work across your whole organisation, so each row names the legal entity it belongs to. Select a row to open the file: a release opens the payment file, and a return opens the return file. The Release button on a release row releases the file without opening it.

Instructions

Each instruction list holds every instruction of its kind, however many there are. The count beside the title covers the whole list, and Next pages through it. The amount at the foot is the total of every instruction, one line per currency. Search finds an instruction by its external account number, its trace number or its amount. Debit and standing orders are found by account number too. Export CSV downloads every instruction, if you hold that list’s export permission. See finding rows in long lists.

A payment a client raised

A client can raise a direct credit in the client portal. It appears in Direct Credits like any other, so you can answer a call about it and reconcile it.

While the client’s own signatories have not approved it, the row reads Awaiting client signatures. Once someone has signed, it adds the count, such as 1 of 2. The row offers no Approve or Reject. The client decides whether to pay, and Approve All never selects a client’s payment. See payments on an account.

Joint accounts

If an account has more than one owner, a client cannot send money from it in the client portal. That covers raising, changing, approving and releasing a payment. It also covers setting up, changing, approving and resuming a payment schedule. The client sees “Payments from joint accounts aren’t available here yet — contact your bank.”

A client can still stop money going out. They can cancel, pause or end a schedule, and reject a payment. If a second owner joins after a payment was raised, approving it is refused too. If a second owner is due to join by the payment’s value date, raising it is refused. Make the payment for them here instead.

Working one entity at a time

If your organisation has more than one legal entity, the two queues offer an entity filter. Choose one and the queue narrows to its work; the choice does not change what you can release or accept, only what you are looking at.

With a single legal entity there is no filter, because there is nothing to choose between.

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.