F110 : payment not possible because of reported error

[oumouKD]

Hello everyone,

We have created a new company code in SAP, and the configuration appears to be complete. Nothing seems to be missing in the FBZP setup.

However, I am unable to process any payments using F110. The system returns the message “Payment not possible because of reported error” without indicating which error it refers to.

At first, I suspected that the issue might be related to errors not appearing in the log. But after running tests that intentionally blocked the payment, the corresponding errors did appear in the log.
This makes it unclear why, when everything seems correctly configured, the payment still fails while showing an error without any details.

Can anyone help ? 

[Divyesh_Mistry]

Hello @oumouKD ,

Pl. try below options and let me know.

Area	Details / Explanation	What to Check / Fix
Error Shown	Payment run stops with generic message: “Payment not possible because of reported error.” In detailed logs: FZ 642 – Bank details of the partner with bank LU account XXXXXXXX are being used.	Indicates the system found bank details that do not meet payment program requirements.
Meaning of FZ 642	The bank account or bank country code ("LU" in your case) is being used but does not meet the payment method requirements, or required fields for that bank are incomplete.	Fix vendor/customer bank master or payment method bank rules.
Common Causes	1. Missing IBAN for LU bank2. Bank key not defined in system3. Payment method does not allow bank country LU4. Payment method does not allow foreign payments5. House bank not configured for LU destinations6. Incorrect account type (Bank account vs. IBAN mismatch)7. Paying company code not assigned fully	Validate master data + FBZP config.
Vendor/Customer Master Checks	Bank account assigned under BP master may be incomplete: IBAN missing, incorrect bank key, wrong bank country.	BP → Payment Transactions → Bank Details. Ensure valid LU bank key + IBAN.
FBZP – Payment Method (per Company code)	Payment method may not allow payments to LU bank accounts.	FBZP → Payment Methods in Company Code → Check “Country of Bank” allowed.
FBZP – Payment Method (in Country)	Rules for foreign banks may be restricted (e.g., requiring IBAN/BIC).	Ensure LU is not blocked. Check validations for IBAN, Bank Account No., BIC.
FBZP – Bank Determination	House bank may not support payments to LU (missing bank chain/bank key relationship).	Assign valid ranking order + bank account with correct currency/country.
House Bank Setup	New company code house banks might be incomplete (missing bank key for LU routing).	Maintain house bank → Bank key → SWIFT → IBAN structure.
Vendor Payment Data	Vendor's payment method may not match the company code payment method.	BP → Supplier → Payment Transactions → Ensure “payment method” matches F110 run.
Currency Issues	House bank does not support payment currency.	Ensure bank account currency matches F110 proposal requirements.
Testing Result Observation	Intentional blocking errors appear normally → means logging works → issue occurs before payment proposal is evaluated.	Confirms error is caused by bank master / payment method validations.
Recommended Fix Steps	1. Maintain IBAN for LU bank account2. Validate LU bank key exists in BNKA3. Ensure payment method allows LU4. Validate payment method assigned in BP5. Maintain bank determination for LU banks6. Re-run proposal after fixes	After corrections, delete proposal & restart F110.
Additional Tools to Debug	- FPAYH / FPAYP (check proposal items)- BNKA (check bank key)- FIBPU (payment method usage)- F110 simulation with log level “Extended”	Helps identify missing bank fields.
Conclusion	Payment fails due to incomplete/incorrect LU bank data or payment method restrictions for bank country LU in FBZP. Once fully maintained, F110 will process normally.	Fix master data + payment config + rerun.

If you find my response helpful, kindly accept the answer and award a Kudos. This motivates me to serve you better.
Appreciate your feedback.
Thanks,
Divyesh

[oumouKD]

Hello, thanks a lot for your reply. I have checked all these points and everything is correct as well. I am a bit lost, still can't identify the problem

[RODRIGUES_MACEDO]

Olá

Pode ser alguns casos dentre eles:

• Método de pagamento / house Bank incompatível ou ausente
  Mesmo com FBZP configurada, pode haver falta de combinação válida entre método de pagamento, banco conta bancária e moeda. Se essa combinação não existe, o sistema não consegue gerar o pagamento.
• Ausência de método de pagamento válido para os documentos (fatura/fatura aberta)
  Se os itens a pagar (faturas, notas) não têm método de pagamento definido, mesmo que a FBZP esteja configurada, a proposta/pagamento pode falhar com erro genérico.
• Configuração incorreta ou incompleta de “determinação automática de contas” (automatic account determination / GL accounts)
  Com novas company codes, talvez falte configuração de contas contábeis relevantes (GL accounts) para determinados eventos — sobretudo se há descontos, impostos retidos, ou transações especiais.
• Itens bloqueados ou condições de seleção não atendidas
  Se há bloqueio no cadastro do fornecedor, na fatura, ou se os critérios da execução de pagamento (data, moeda, limites mínimos/máximos, etc.)
• Limites de valor mínimo/máximo para a forma de pagamento configurada
  A definição de faixas de valor para métodos de pagamento pode impedir o pagamento de valores fora de faixa, e esse tipo de bloqueio às vezes não gera uma mensagem de erro clara.
• Configuração obrigatória de campos mestre de fornecedor não preenchida
  Por exemplo: se na configuração da forma de pagamento for obrigatório endereço, banco, CEP, cidade, etc., e o fornecedor não tiver esses dados, a seleção falha.

[oumouKD]

Olá, obrigada pela sua resposta. Eu já verifiquei todos esses pontos e está tudo correto também, por isso estou com muita dificuldade em entender de onde vem o problema.

[oumouKD]

Hello, thank you for your reply. I have checked all these points and everything is correct as well, which is why I’m really struggling to understand where the issue is coming from.