Skip to main content

Payouts: settings, review and batches

This is where you prepare and authorise cashback payouts to your members. There are three screens, used in this order: Payout settings (once), Payout review (when payouts are held) and Payout batches (each time you pay).

Availability

Payout settings: Payout accounts permission (the approval policy also needs Edit approval policy (thresholds)) · Payout review and Payout batches: Approving payouts permission

note

IncentIA does not hold funds: payouts leave the brand's account or its wallet at a regulated institution.

To see each member's individual payouts and export a classic SEPA batch, read Cashback: payouts and runway.

1. Payout settings​

The screen is titled Payout settings: "Configure the brand's own payout account and the default approval policy for cashback payouts".

Payout settings with the payout account and the approval policy

Payout account​

The Payout account table lists your accounts with Name, Funds model, Provider, Debtor IBAN, Default and Is active. With none you see No payout accounts yet. Press New account to create one, or Edit / Delete on a row.

FieldWhat it is
NameAccount name (required)
ProviderHow the payout is made. It cannot be changed when editing
Funds modelBrand's own account (the brand authorises each batch at its bank) or EMI wallet (pre-funded wallet at an electronic money institution; requires activation by IncentIA)
Account holderHolder of the account (required for SEPA payouts)
Initiating partyWho initiates the payment in the bank file
Debtor IBAN and BICThe account the money leaves from. An invalid IBAN shows The debtor IBAN is missing or invalid.
Credentials (write-only)JSON object. Stored encrypted and never shown again; leave empty to keep the current ones
Default / Is activeThe account used by default and whether it is in use

If EMI wallet is blocked, no EMI provider is registered yet: use Brand's own account. To fund a SEPA batch, the account must be active with a valid holder and IBAN.

Default approval policy​

It defines which payouts are approved automatically and which need a person.

FieldWhat it does
Auto-approve up to (€)Payouts of this amount or less are approved automatically
Require dual control for batches above (€)Above this amount, a batch needs two different approvers
Require validated evidence for auto-approvalAuto-approves only if the linked receipt is approved

The first amount must be 0 or more; the dual-control threshold must be at least the auto-approve amount. Press Save.

2. Payout review​

The screen is titled Payout review: these are "payouts held by Verification of Payee because the holder name did not match or could not be checked". Each one is resolved individually. The menu shows a counter with the pending ones.

Payout review with the captured name and the bank-suggested name

ColumnWhat it is
Member and CampaignMember and originating campaign
Net amountWhat will be paid
IBANMasked IBAN
Name captured / Name suggested by the bankWords that differ are marked in red
ResultClose match (similar name) or Unavailable (the bank could not check it)
  1. Press Review on the row.
  2. To approve the payout, write a Comment (required). Pressing Accept confirms "I confirm the account holder is the same person".
  3. To discard it, write the Reason (required) and press Reject.
warning

Accept only if you are sure the IBAN belongs to the member. A payout sent to someone else is hard to recover.

3. Payout batches​

The screen is titled Payout batches: "Group approved cashback payouts into batches, authorise them and download the pain.001 file".

Payout batches with status, total and rows

The table shows #, Status, Total, Rows, Created by and Date. Press View to open the batch detail.

Batch statuses​

StatusWhat it means
DraftJust created, still to authorise
Awaiting second approverHas the first approval; another person is needed
AuthorisedReady to download or send to the bank
SubmittedSent to the bank
SettledThe bank has paid it
Partially failedSome rows were not paid
CancelledVoided; its rows are released

Steps​

  1. Press Create batch and confirm Create a batch with all approved payouts that are ready? With no payouts you see There are no approved SEPA payouts waiting for a batch. Payouts without a valid SEPA IBAN are left out (N payouts were left out).
  2. Open the batch with View and press Authorise. Approvals shows how many it has (for example 1 / 2).
  3. If the batch exceeds the dual-control threshold, it becomes Awaiting second approver (Requires a second approver). Another person with the Second approval (dual control) permission must press Authorise. Whoever gave the first approval cannot give the second.
  4. With the batch Authorised, press Download pain.001. Notice: "Upload this file to the brand's online banking and authorise it there. IncentIA does not execute the payment."
  5. Once the bank has executed it, press Mark as confirmed or use Import statement.
  6. Before authorising you can press Cancel: "Its rows will be released".
danger

The money moves when you upload the file to your bank and authorise it there. Review the batch first.

Import statement​

Import statement accepts an .xml, .csv or .txt file from your bank and reconciles the payouts. When done you see Statement result with Entries read, Reconciled (confirmed), Failed, Needs manual review, Unchanged, Pending and Not reconciled. Unreconciled entries state the reason: No end-to-end reference, Unknown payout, Amount does not match or Other.

Permissions​

ActionPermission (UI text)Technical id
View and edit payout accountsPayout accountsPages.Payouts.Accounts
Review payouts, create, authorise, download and cancel batches, import statementsApproving payoutsPages.Payouts.Approve
Give the second approval of a batchSecond approval (dual control)Pages.Payouts.Approve.Dual
Edit the approval policyEdit approval policy (thresholds)Pages.Payouts.Approve.Policy