Skip to main content

Conditional Payee Name Parsing Based on Transaction Fields

Thank you for providing automatic bank connections with YNAB. I have a feature request to enhance payee name parsing due to varying data structures from banks for different transaction types.

Issue:

  • Card Payments: Payee information is embedded in the remittanceInformationUnstructured field.

  • SEPA Transfers: Payee name is provided in the debtorName or creditorName fields.

Examples:

  1. Card Payment:

    {
      "bookingDate": "2024-01-01",
      "transactionAmount": { "amount": "-10.00", "currency": "EUR" },
      "remittanceInformationUnstructured": "(..1234) 2024-01-01 12:00 Example Service ABC123\\Example Street 1\\Example City\\12345 ABCDEF",
      "bankTransactionCode": "PMNT-CCRD-POSD",
      "internalTransactionId": "0123456789abcdef0123456789abcdef"
    }
    
  2. SEPA Transfer:

    {
      "bookingDate": "2024-01-01",
      "transactionAmount": { "amount": "-1.00", "currency": "EUR" },
      "creditorName": "John Doe",
      "creditorAccount": { "iban": "EE000000000000000001" },
      "debtorName": "John Doe",
      "debtorAccount": { "iban": "EE000000000000000002" },
      "remittanceInformationUnstructured": "Test Transaction",
      "bankTransactionCode": "PMNT-ICDT-OTHR",
      "internalTransactionId": "0123456789abcdef0123456789abcdef"
    }
    

Feature Request:

Please implement conditional parsing for the payee name:

  • If debtorName or creditorName exists, use that as the payee name.

  • Else, apply a custom Regex to a chosen field like remittanceInformationUnstructured.

This addition would ensure accurate payee name extraction across different transaction types.

Thank you for considering this request.

Status: Completed2 comments

Log in to comment and vote

Comments2

  • Priit Pihus

    •

    Jan 18

    It seems there is a new powerful rules feature, but I’ve had no luck solving this issue with that feature either. I wonder if it is even possible?

  • Christina Gahn

    •

    Jul 27, 2025

    Please prioritize! We can always EITHER get the payee right for incoming or outcoming transactions due to this problem.