Payment run statuses

A payment run moves through calculation, review, approval and bank processing. The exact path depends on the exporter and the bank response.

Preparation and approval

• Calculating: Flinq is calculating the account-level payment entries.

• Draft: calculation is complete and the run is ready for review.

• Awaiting approval: the run has been submitted to an approver.

• Awaiting payment: approval is complete, or a manual file has been downloaded, and payment still needs to be sent or confirmed.

• Payment file queued: Flinq is preparing and sending a queued EOS payment file. The run updates to Sent to bank only after delivery completes.

Bank processing

• Sent to bank: Flinq submitted the run through an automated exporter.

• Received by bank: the bank acknowledged receipt.

• Accepted by bank: the bank accepted the instruction.

• Awaiting bank authorisation: one or more payments need additional approval in the bank platform.

• Pending settlement: the bank accepted the instruction and settlement is pending.

• Paid: Flinq has confirmed that the run is settled, or an authorised user has marked a manual run as paid.

Automatic settlement for Standard Bank runs

A payment run sent through the Standard Bank automated exporter remains Sent to bank until Flinq can confirm every positive client payment entry from imported Standard Bank transactions.

Each payable client entry must have exactly one matching credit to the client account and one matching debit from the management account. The credit and debit must share the same bank reference and match the expected accounts, currency, amount to two decimal places and interest-period narrative. Their transaction dates must be on or after the payment run was submitted.

If a posting is missing, ambiguous, already used for another match or returned, the payment run remains Sent to bank. When every payable entry has been confirmed, Flinq changes the payment run to Paid.

Flinq sends one in-app notification to each eligible recipient: the payment run creator and the user who approved and sent the automated run, provided they are still members of the office and can view the run. Flinq does not send an email for this automatic status change. The notification opens the payment run in the correct office.

Exceptions

• Partially accepted: the bank accepted some payments and rejected others. Review is required.

• Failing: an error occurred during payment processing. Establish whether the bank received anything before retrying.

• Payment file needs attention: Flinq could not confirm that a queued EOS payment file was sent. Contact Flinq Support before retrying so the existing delivery can be checked without risking a duplicate instruction.

• Rejected: an approver or the bank rejected the run.

• Archived: the run was taken out of the active workflow. It remains part of the audit history.