SAP Knowledge Base Article - Public

3657653 - Verification of Payee (VoP) and Confirmation of Payee (CoP) – Mapping External Statuses to Internal Statuses and Monitoring in Monitor Payments

Symptom

  • Requirement to use the new Verification of Payee (VoP) and Confirmation of Payee (CoP) feature.
  • How to configure external-to-internal status mapping for VoP and CoP?
  • What new statuses are available?
  • How do VoP and CoP results appear in Monitor Payments?

Disclaimer: "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP S/4HANA Cloud Public Edition

Cause

Enhancements to Map External Status to Internal Status configuration were delivered with CE 2508.2 to support VoP/CoP validations received from banks and payment service providers.

  • Verification of Payee (VoP): Internal pre-payment or external check by the bank to validate that the account number and name provided for the beneficiary are consistent.

  • Confirmation of Payee (CoP): Final confirmation step returned by the bank, validating the beneficiary account details before settlement.

Both are returned in ISO 20022 pain.002.001.10 messages and need to be mapped to internal statuses for visibility in Monitor Payments.

Resolution

1. Mapping External Statuses to Internal Statuses.

  • The configuration step Map External Status to Internal Status (SSC-UI ID: 104313) now supports new statuses for VoP/CoP.
  • The mappings are not delivered by default. They must be configured manually in the system.
  • New internal statuses and corresponding external codes

New Internal Status

External Status Code

Level

BCVC VoP Completed

PAIN_RCVC

Batch

BVCM VoP Completed with Mismatches

PAIN_RVCM

Batch

BCVC VoP Completed

PAIN_RCVC

Payment

BVNA VoP not Applicable

PAIN_RVNA

Payment

BVNM VoP Completed with no Match

PAIN_RVNM

Payment

BVMC VoP Completed with Close Match

PAIN_RVMC

Payment

  • Add new entries mapping the external VoP/CoP status codes (PAIN_RCVC, PAIN_RVCM, PAIN_RVNA, PAIN_RVNM, PAIN_RVMC) to the internal codes (BCVC, BVCM, BVNA, BVNM, BVMC).
  • Save configuration.

A sample mapping of the new internal statuses mapped to the external status codes:



2. Monitoring VoP/CoP Statuses in Monitor Payments.

  • Open Monitor Payments (App ID: F2388). 
  • Use All Batches, Sent to Bank, and Exceptions views to analyze VoP/CoP results. 
  • Drill down to see batch-level vs. individual transaction-level statuses. 
  • Batch Level Statuses:
    VoP/CoP Completed (BCVC) → Appears in All Batches and Sent to Bank tabs.
    VoP/CoP Completed with Mismatches (BVCM) → Appears in All Batches and Exceptions tabs.

  • Payment Level Statuses:
    VoP/CoP Completed (BCVC)
    VoP/CoP not Applicable (BVNA)
    VoP/CoP Completed with No Match (BVNM)
    VoP/CoP Completed with Close Match (BVMC)

Keywords

VoP, Verification of Payee, CoP, Confirmation of Payee, External Status Mapping, Monitor Payments, ISO 20022, Pain.002.001.10, Multi-Bank Connectivity, BCVC, BVCM, BVNA, BVNM, BVMC, FI-FIO-AP-2CL, SSCUI 104313, F2388 , KBA , FIN-FSCM-BNK-2CL , Direct Bank Communication (Public Cloud) , How To

Product

SAP S/4HANA Cloud Public Edition 2508

Attachments

Pasted image.png