How To Fix BFIBL02170 - Format &1 of payment run and format &2 in Customizing are not consistent

SAP Error Message - Details

• Message type: E = Error

• Message class: BFIBL02 - Payment Medium: Messages

• Message number: 170

• Message text: Format &1 of payment run and format &2 in Customizing are not consistent

CAUSE&
The format &V1& assigned for this payment medium run has been replaced
in Customizing by format &V2& for payment method &V4& in company code
&V3&. This is only possible after all payment media with payment runs
configured with the old Cutomizing settings have been created.
This restriction is due to the format characteristics: The payment run
has already grouped the payments for the payment media.

System Response

Processing terminated

How to fix this error?

Make sure that the Customizing settings are activated when maintaining
parameters. It is particularly important that the format &V1& be
defined once again. After the payment media have been created, the next
payment run can be started with new Customizing settings.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BFIBL02170 - Format &1 of payment run and format &2 in Customizing are not consistent ?

  The SAP error message BFIBL02170 indicates that there is a mismatch between the format of the payment run you are trying to execute and the format defined in the Customizing settings. This typically occurs in the context of payment processing in SAP, particularly when dealing with electronic payments.
  Cause:
  The error arises when:
  
  The payment run format (e.g., SEPA, DTAUS, etc.) you are using does not match the format that has been configured in the system for that specific payment method.
  There may be a configuration issue in the payment method settings in the SAP system.
  The payment run might be set up to use a specific format that is not aligned with the settings in the Customizing (transaction code OBPM1 for payment methods).
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Payment Method Configuration:
  
  Go to transaction code OBPM1 (or navigate through the menu: Financial Accounting > Accounts Payable > Payment Transactions > Payment Program > Define Payment Methods in Country).
  Verify the payment method you are using and ensure that the format specified in the payment method configuration matches the format of the payment run you are trying to execute.
  
  
  
  Adjust Payment Run Settings:
  
  When creating or executing the payment run (transaction code F110), ensure that you have selected the correct payment method that corresponds to the format you want to use.
  
  
  
  Review Customizing Settings:
  
  Check the Customizing settings for the payment method in SPRO (SAP Reference IMG) under Financial Accounting > Accounts Payable > Payment Transactions > Payment Program > Define Payment Methods for Company Code.
  Ensure that the format settings (like file format, bank details, etc.) are correctly configured.
  
  
  
  Test with Different Formats:
  
  If you have multiple formats available, try running the payment with a different format to see if the issue persists.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to payment formats and configurations for any specific requirements or updates.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest patches and notes, as there may be fixes related to payment processing.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  F110: Automatic Payment Transactions
  OBPM1: Define Payment Methods
  SPRO: SAP Reference IMG for configuration
  
  
  
  Common Payment Formats:
  
  SEPA (Single Euro Payments Area)
  DTAUS (German payment format)
  BACS (UK payment format)
  ACH (Automated Clearing House in the US)
  
  
  
  SAP Notes:
  
  Check SAP Notes for any known issues or additional guidance related to payment formats and error messages.
  
  
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the error message BFIBL02170.