Hi, The reason for the problem doesn't seem to be related to the payment date and header date (it's the same, in the files I've checked). There is also an EndToEndID in the file.Turned out that it's actually CAMT053 that is used, and not CAMT054. Don't think this matters here, since we've found the same behaviour in other customer's environment, where CAMT054 is used.But - one thing I forgot to mention earlier, is the different behaviour in "External Payment Details", before the transactions are loaded into a mixed payment.In UPD6 version, the column "Proposed Action" in "External Payment Details" for these transactions, were set to "Load Payment Order" and no invoice details were fetched.Since UPD15, the value in column "Proposed Action", is set to "Load Invoice" instead and invoice information is fetched.I guess this is the reason why these rows now end up in the upper part of the "Mixed Payment"-window, as separate lines, and not as a lump sum.Does anyone know the difference between
Hi This may happen when the payment date is different form the header date, some changes had been introduced by bug 153884 in UPD9 Note: In the instances when there is no EndtoEndID in the return file, the creation date and time will be considered as the statement date of the External Payment Transaction. The dates of the transactions will not be sorted in the external payment window, based on the statement date, a separate external payment will be created with the date available in the CreDtTm tag. Hi Kanishka, Thanks a lot for the information and your quick answer 😊. Will investigate this further, to see if this might be the reason for my customer's problems./Karin
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
