How to generate a payment run

A payment run calculates gross interest, cash management charges and client net returns for a selected period, then prepares the payment instructions for review and processing.

Before you start

• Interest Pooling must be enabled and you need permission to create payment runs.

• The pools must use the same bank and currency.

• Statement data and effective profile periods must cover the full date range.

• An active exporter must be available for the selected pools.

• If the exporter creates an ISO 20022 PAIN.001 payment file and a postal address is saved for the entity linked to the management account or a client account, confirm that each address includes a town or city and country and uses supported field lengths and characters.

Create the draft

1. Go to Interest Pooling > Payment Runs.

2. Select New payment run.

3. Select the Bank and Currency.

4. Select one or more Interest Pools.

5. Select the Exporter.

6. Review the suggested Date range or choose another available range. Dates already covered by a payment run cannot be selected.

7. Review the summary and select Create Draft Payment Run.

If an account moved between pools during the period, a full date range is available only when you select every pool that covered the account and statement and profile coverage spans the full range. Flinq applies each day to the pool assignment that was active on that date, so a transfer day is not calculated twice.

Review the calculation

Flinq calculates the run in the background. When it reaches Draft, review:

• the selected pools, exporter and date range;

• gross interest, cash management charge (CMC), Flinq fee and client net return;

• account-level payment entries;

• negative-balance and standing-rate-floor warnings;

• management-account reconciliation, where enabled; and

• the Flinq fee payment instruction, where applicable.

Approve and process the run

• If approval is required, select Submit for Approval. An approver can then approve or reject the run.

• For an automated exporter, Flinq sends the payment run to the bank after approval and updates the bank-processing status.

• For a manual exporter, complete any required approval, then download the file and upload it through the bank's normal channel. Manual approval may be optional, depending on Office Settings.

• Use Mark as Paid only when the manual payment has been completed and your role permits it.

A PAIN.001 download shows Payment export blocked

If saved payer or payee address details do not meet the ISO 20022 requirements, Flinq shows Payment export blocked and identifies the affected payer, payee or account. Flinq does not create a file or record a download, and the payment run status remains unchanged.

If you have permission to manage the linked entity, correct its saved postal address. Otherwise, ask an authorised administrator or Flinq Support to update it before you retry the download.

When contacting Support, provide the payment run name or reference, office name, the exact Payment export blocked message and whether it names a payer, payee or account. Do not send the full postal address or bank-account data through ordinary email or chat; use an approved secure support channel if Support needs confidential details.

Confirm that the address includes a town or city and country and that no field is too long or contains unsupported characters before downloading the payment file again. The address check applies only when linked address details exist; domestic Interest Pooling runs without a linked owner address remain exportable.

An EOS payment file is not ready to download

For an EOS exporter, Flinq prepares and verifies the payment file before the download starts.

• Payment file preparation: the file is still being prepared. Wait briefly, then select Download again.

• Payment file unavailable with a temporary-unavailability message: wait briefly, then retry the download.

• Payment file unavailable because no valid positive entries exist for the selected currency: review the payment entries and currency before retrying.

• Payment file unavailable with an instruction to contact Support: stop retrying and contact Flinq Support through an approved secure channel. Provide the office, payment run, exporter, approximate time and exact message without sending account data by ordinary email or chat.

Common statuses

A run normally moves through calculation, draft, approval, bank processing and paid states. Failing, Rejected or Partially accepted requires review before you continue.

Archive only a run that should no longer be processed. Paid runs remain part of the payment and audit history.