Skip to main content

How It Works

Each clearing system connection (BIC) maintains separate settlement accounts for SCT (SEPA Credit Transfer) and INST (SEPA Instant). The liquidity engine periodically checks these balances against your configured minimums and takes action when needed.
Automatic liquidity is available for CENTROlink and EKS. To move liquidity manually, see Transfers between settlement accounts; to move excess liquidity out, see Withdraw to safeguarding.
EKS participants: automatic transfers are sent as payments from your operational account, so set it up before you enable automatic liquidity:
  1. Add an operational account in the dashboard under Settings > Liquidity.
  2. Register the same IBAN with Latvijas Banka as a pre-fund increase source in your EKS registration forms (fields 1.3.1 and 1.5.1). Until Latvijas Banka confirms the registration, transfers can be rejected.
Balance alerts work without these steps. See Transfers between settlement accounts for details, or contact Inventi support if you need help with the forms.

Balance Thresholds

You configure four values that control the engine’s behavior:

Configuration

Configure liquidity settings through the Dashboard under Settings > Liquidity. These settings are not available through the API; the transfers the engine creates can be followed with Get liquidity transfers.

Enable Auto-Liquidity

  1. Navigate to Settings > Liquidity
  2. Enable Auto-Liquidity
  3. Set SCT Minimum, INST Minimum, and Transfer Amount
  4. Optionally set a Warning Balance above the critical minimum
  5. Save the configuration

What-If Calculator

The settings page includes a what-if calculator. Enter hypothetical SCT and INST balances to see what the engine would do - which alerts fire, whether a transfer is triggered, and in which direction. Use the sliders to explore thresholds.

Automatic Transfers

When auto-liquidity is enabled and a scheme balance drops below its minimum, the engine:
  1. Checks if the opposite scheme account has enough surplus (its own minimum + transfer amount)
  2. If yes, initiates a transfer of the configured amount from the surplus account to the deficit account
  3. Sends the transfer to the clearing system:
    • CENTROlink: as a dedicated liquidity transfer instruction, not a regular customer payment. It is recorded as an Adjustment transaction and cannot be cancelled or returned
    • EKS: as a SEPA payment from your operational account to Latvijas Banka. The scheme the payment is sent on decides which account is debited, see Transfers between settlement accounts. Automatic EKS transfers do not go through 4-eyes signing
Transfers only execute during the clearing system’s operating window. For SEPA via CENTROlink, this is typically 08:00-18:40 EET on business days. For EKS, the cut-off is 17:19 Latvian time for transfers to the SCT Inst account and 17:59 for transfers to the SCT account.

Notifications

Configure webhook URLs to receive alerts when balance thresholds are breached or when automatic transfers occur.

Signing and delivery

Liquidity notifications carry the same finventi-signature-N, finventi-signature-timestamp and finventi-receiver-tenant-id headers as payment webhooks, and the signature is built the same way. See Signature verification. Delivery differs from payment webhooks:
  • Liquidity notifications are sent to the URLs set under Settings > Liquidity, not to the webhooks you manage under Settings > Webhooks, and they do not appear in the webhook delivery history.
  • They are delivered independently of payment webhooks. A slow or failing liquidity endpoint does not delay payment status notifications.
  • A failed delivery is retried a few times in quick succession. After that the notification is not sent again, so use Get liquidity transfers and Account balances as the source of truth.

Low Balance Notification

Payload
string
required
Which limit was breached. One of: RECOMMENDED_TOTAL_MINIMUM_BREACHED, ABSOLUTE_TOTAL_MINIMUM_BREACHED, SCT_MINIMUM_BREACHED_NO_TRANSFER, INST_MINIMUM_BREACHED_NO_TRANSFER
array
required
IBANs of the impacted settlement accounts
number
required
The configured limit that was breached
number
required
The balance at the time of the alert

Liquidity Transfer Notification

Payload
integer
required
Liquidity transfer identifier
string
Identifier of the SEPA message carrying the transfer
string
required
Source settlement account IBAN. For EKS, the IBAN of your operational account
string
required
Destination settlement account IBAN
number
required
Transfer amount
string
required
Currency code (ISO 4217)
string
required
Transfer status. One of: CREATED, SENT_TO_CLEAR, ACCEPTED, REJECTED, COMPLETED
Set the Minutes between notifications value to control how often repeated alerts are sent for the same condition. This prevents notification floods when balances remain low.
Test your webhook URLs using the Test button next to each URL field in the settings page before saving.

API Reference

Account balances

View current settlement account balances

Initiate transfer

Move funds between settlement accounts or withdraw to safeguarding

Liquidity transfers

View past liquidity transfers and withdrawals

Account statements

View settlement account statements
Last modified on November 11, 2026