Skip to main content
Solved

Issue with loading Pain002 files. (Response from Bank on Payments made)

  • December 22, 2020
  • 6 replies
  • 291 views

Forum|alt.badge.img+9
  • Sidekick (Customer)
  • 80 replies

Hi all,

 

On IFS10, we are trying to load PAIN002 message (response from Bank on Payments made), however we are getting the error “No API to call...”
When we check the standard File Template (PaymentStatusFile), there is no API configured. 

Who knows where we go wrong?

Best answer by Eranda

Hi Arend,

You are referring to payment status message file (pain.002.001.03). Please make sure to drop the file to Application Server IN folder same as Bank Statement file (CAMT). If the file is successfully loaded, you can view it from system. Go to acknowledge Supplier Payment order window and use right mouse button Payment Status File. You can see the new load id.

Best Regards

Eranda

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

6 replies

Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 32 replies
  • December 22, 2020

Hi,

Is this CAMT files, that you are trying to upload?

If yes, you need to place them in SERVER IN folder, to read through Application Messages.

Thanks


Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 80 replies
  • December 22, 2020

Hi Lahiru,

 

Not, it is not a CAMT file, it is an PAIN file.


Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 32 replies
  • December 22, 2020

Hi,

OK. Then I am not sure.

Thanks


Eranda
Hero (Partner)
Forum|alt.badge.img+11
  • Hero (Partner)
  • 204 replies
  • Answer
  • December 22, 2020

Hi Arend,

You are referring to payment status message file (pain.002.001.03). Please make sure to drop the file to Application Server IN folder same as Bank Statement file (CAMT). If the file is successfully loaded, you can view it from system. Go to acknowledge Supplier Payment order window and use right mouse button Payment Status File. You can see the new load id.

Best Regards

Eranda


Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 80 replies
  • February 10, 2021
Eranda wrote:

Hi Arend,

You are referring to payment status message file (pain.002.001.03). Please make sure to drop the file to Application Server IN folder same as Bank Statement file (CAMT). If the file is successfully loaded, you can view it from system. Go to acknowledge Supplier Payment order window and use right mouse button Payment Status File. You can see the new load id.

Best Regards

Eranda

 

Hi Erenda,

 

We managed to load the messages in the IN1 queue (It needed to be send without a SoapAction) However we get 3-4 files for the same order. However, the status update is only working for the first loaded file. Anything on this? (Bug?)

 

Payment factory and Bank send a “receipt message”, “pending message,” “acceptance pending” and “accepted message”.

 


Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 80 replies
  • February 12, 2021
Arend wrote:
Eranda wrote:

Hi Arend,

You are referring to payment status message file (pain.002.001.03). Please make sure to drop the file to Application Server IN folder same as Bank Statement file (CAMT). If the file is successfully loaded, you can view it from system. Go to acknowledge Supplier Payment order window and use right mouse button Payment Status File. You can see the new load id.

Best Regards

Eranda

 

Hi Erenda,

 

We managed to load the messages in the IN1 queue (It needed to be send without a SoapAction) However we get 3-4 files for the same order. However, the status update is only working for the first loaded file. Anything on this? (Bug?)

 

Payment factory and Bank send a “receipt message”, “pending message,” “acceptance pending” and “accepted message”.

 

 

This we found out that this was due to a coding added in our middleware software. Try to solve this there now.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings