Line4

1 min readWarningEBA reporting framework 4.2Updated 10 November 2026

Payment transactions cannot be negative (Y 06.01, EBA rule v09252_s)

A warning in the payment fraud return (PSD2 fraud reporting), on template Y 06.01, e-money payment transactions.

Check your file against this ruleWhat to do if it fails

The rule in plain words

Payment transactions cannot be negative.

EBA checks it for 20 rows, from E-money payment transactions (0010) to other (0380). And on six sheets: domestic amount of payment, domestic number of transactions, cross-border within the EEA amount of payments, cross-border within the EEA number of transactions, cross-border outside the EEA amount of payments and cross-border outside the EEA number of transactions. That makes 120 checks. A failure names the one that failed.

How the Line4 Check report words itShow

The first of its checks, word for word as the report shows it when it fails. The others read the same, with their own column, row or sheet.

Payment transactions: Of which authenticated via non-strong customer authentication, Cross-border outside the EEA number of transactions >= 0

What to do if your filing fails it

  1. 01Open the template below and find the cells the rule reads.
  2. 02Look for a value with the wrong sign in these cells, such as an amount entered as a negative number.
  3. 03EBA compares the values exactly here: there is no rounding tolerance.
  4. 04It runs only when your filing indicators mark Y 06.01 as reported.
  5. 05This is a warning. It does not stop the filing on its own, but your authority may ask you to explain it.

The cells it reads

E-money payment transactions (Y 06.01)

Rows

  • 0010E-money payment transactions
  • 0020Of which via remote payment initiation channel
  • 0030Of which authenticated via strong customer authentication
  • 0080Of which authenticated via non-strong customer authentication
  • 0140Low value (Art.16 RTS)
  • 0150Trusted beneficiary (Art.13 RTS)
  • 0160Recurring transaction (Art.14 RTS)
  • 0170Payment to self (Art. 15 RTS)
  • 0180Use of secure corporate payment processes or protocols (Art. 17 RTS)
  • 0190Transaction risk analysis (Art.18 RTS)
  • 0200Merchant initiated transactions
  • 0210Others
  • 0220Of which via non-remote payment initiation channel
  • 0230Of which authenticated via strong customer authentication
  • 0280Of which authenticated via non-strong customer authentication
  • 0340Trusted beneficiary (Art.13 RTS)
  • 0350Recurring transaction (Art.14 RTS)
  • 0360Contactless low value (Art.11 RTS)
  • 0370Unattended terminal for transport or parking fares (Art.12 RTS)
  • 0380Other

Column

  • 0010Payment transactions

Sheets

  • 0010Domestic amount of payment
  • 0020Domestic number of transactions
  • 0030Cross-border within the EEA amount of payments
  • 0040Cross-border within the EEA number of transactions
  • 0050Cross-border outside the EEA amount of payments
  • 0060Cross-border outside the EEA number of transactions

A worked example

The first of its checks, with simple numbers.

What the rule then expects

Via remote payment initiation channel without strong customer authentication, payment transactions must then be at least 0.

0Passes
-100Fails

A file that reports 0 passes. One that reports -100 fails, by 100.

The numbers are illustrative.

Show the rule as writtenShow

EBA's formula, as written out for the first of its checks. Cells are written as {template, row, column, sheet}.

{Y_06.01,r0080,c0010,s0060} >= 0

The next five:

{Y_06.01,r0200,c0010,s0030} >= 0{Y_06.01,r0020,c0010,s0050} >= 0{Y_06.01,r0350,c0010,s0040} >= 0{Y_06.01,r0150,c0010,s0050} >= 0{Y_06.01,r0180,c0010,s0030} >= 0

And 114 more, the same formula for the other cells it covers.

Every PSD2 fraud reporting rule, by template

Checks like this one, run at the point of submission, are the first step to real-time supervision.