Skip to main content

Workflow Filters – Payments (PSP) & Payments (ERP)

Use Payment filters to track PSP transactions and ERP-recorded payments for retries, allocations, and reconciliation.

Kolleno Support avatar
Written by Kolleno Support
Updated today

Payment Filters ensure workflows handle both real-time provider transactions (PSP) and ERP-recorded payments effectively.

  • Payments (PSP): These filters focus on live transactions processed via providers such as Stripe, Adyen, or GoCardless. They help identify failed attempts, trigger retries, send receipts, and apply provider-specific playbooks.

  • Payments (ERP): These filters monitor payments from your ERP system. They detect large payments, overpayments, unallocated balances, and currency mismatches to keep accounts reconciled.

Kolleno Payment (PSP) Filter List:

Adyen refusal reason code

Adyen‑specific failure code

Send “update card” email on REFUSED

Amount

Charge amount

Manual review if unusually high

Automatic payment

Whether charge was automatic

Gentle tone for autopay fails

Currency

Charge currency

Route to FX team

Date paid

Date the charge settled/paid

Send receipt

Kolleno Payment PSP reference

PSP reference for the charge

Audit & reconciliation

Direct debit failure reason code

DD failure reason (e.g., GoCardless)

Auto‑retry + mandate guidance

Payment method

Method used (ACH, ACSS, Card, DD, etc.)

Payment‑method specific copy

Provider

PSP/provider (Stripe, Adyen, GoCardless, etc.)

Provider‑specific playbooks

Status

Paid / Pending / Failed

Branch success vs failure

Tags

Custom tags on charge

Route special cases

Payment (ERP) Filter List:

Filter name

What it detects

Example use case

Amount

Payment amount recorded in ERP

Flag very large payments

Amount remaining

Unallocated balance remaining

Prompt allocation

Date paid

Payment date

Send receipt/thanks

Overpayment

Amount paid above balance

Offer refund or allocate

Payment currency

Currency used

Route FX items

Payment source

Channel/method (bank, card, PSP)

Payment‑channel reporting

Payment source ID

Identifier at the source

Match to bank/PSP exports

Prepayment

Whether paid in advance

Apply to future invoices

Status

ERP payment status

Awaiting vs posted logic

Did this answer your question?