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
Hi Lahiru,
Not, it is not a CAMT file, it is an PAIN file.
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 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”.
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.