Skip to main content
Question

Customer Statement of Account "Created From"

  • August 17, 2026
  • 7 replies
  • 86 views

Forum|alt.badge.img+11

I am using Cloud 25R1 and Customer Statements of Account are not sending, I think because the “Created From” account is set to IFSPRINT. It should be IFSCONNECT (see screencap). I don’t know how to change that, hopefully someone can help.

7 replies

Tharshan SM
Hero (Customer)
Forum|alt.badge.img+6
  • Hero (Customer)
  • August 17, 2026

Hi ​@jdoherty,

I don’t think Created From IFSPRINT is the issue. Since the Customer Statement of Account is generated through the print process, IFSPRINT is an expected origin. IFSCONNECT is used for messages originating from IFS Connect and is not normally something you manually change on the application message.

Could you open one of the failed messages and share the Error Text? It would also help to check the address line at the bottom of the message and provide its State, Error Text and Sender Instance.

That should show whether the actual problem is related to.

Regards,


Forum|alt.badge.img+11
  • Author
  • Hero (Customer)
  • August 17, 2026

Hi ​@jdoherty,

I don’t think Created From IFSPRINT is the issue. Since the Customer Statement of Account is generated through the print process, IFSPRINT is an expected origin. IFSCONNECT is used for messages originating from IFS Connect and is not normally something you manually change on the application message.

Could you open one of the failed messages and share the Error Text? It would also help to check the address line at the bottom of the message and provide its State, Error Text and Sender Instance.

That should show whether the actual problem is related to.

Regards,

Error text is 

 

ExecutionException from Sender thread 
Caused by: ifs.fnd.connect.senders.ConnectSender$PermanentFailureException: Fatal error while sending data... 
Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Error while sending data... 
Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.57 Client not authenticated to send mail. Error: 535 5.7.3 Authentication unsuccessful [DU7P250CA0019.EURP250.PROD.OUTLOOK.COM 2026-08-17T14:16:37.661Z 08DEFA8BDB638D86]

 


Tharshan SM
Hero (Customer)
Forum|alt.badge.img+6
  • Hero (Customer)
  • August 18, 2026

Hi ​@jdoherty,

Thanks for sharing the error. It is mostly that the issue is with SMTP authentication, not the created from value. Please check the Mail Sender’s credentials and authentication type.

You can find the sender through Application Message → Routing Rule Used → Mail Routing Address → Sender Instance, or under Setup IFS Connect → Senders. Once corrected, retry the failed message.

FYI,

 


Tharshan SM
Hero (Customer)
Forum|alt.badge.img+6
  • Hero (Customer)
  • August 18, 2026

Hi ​@jdoherty,

Thanks for sharing the error. It looks like the issue is with SMTP authentication, as clearly stated in the error text, not the "created from" value. Please check the Mail Sender's credentials and authentication type.

You can find the sender through Application Message → Routing Rule Used → Mail Routing Address → Sender Instance, or under Setup → IFS Connect → Senders. Once corrected, retry the failed message.

 

FYI,

 


Tharshan SM
Hero (Customer)
Forum|alt.badge.img+6
  • Hero (Customer)
  • August 18, 2026

Hi,

Thanks for sharing the error. It looks like the issue is with SMTP authentication, as clearly stated in the error text, not the created from value. Please check the Mail Sender's credentials and authentication type.

You can find the sender through Application Message → Routing Rule Used → Mail Routing Address → Sender Instance, or under Setup → IFS Connect → Senders. Once corrected, retry the failed message.

 


Forum|alt.badge.img+11
  • Author
  • Hero (Customer)
  • August 19, 2026

The issue has been resolved, it was related to the Application registered in the Azure portal that sends the mail. Nothing to do with the IFS configuration.

But now there is a separate issue; when there is a customer registered under two separate companies, the statement is sent with the wrong report layout for the company that has been selected.


Tharshan SM
Hero (Customer)
Forum|alt.badge.img+6
  • Hero (Customer)
  • August 19, 2026

Hi ​@jdoherty,

Yes, it looks like the issue was related to the email server authentication configuration.

For the wrong layout selection, better to look at the Report Rules for the report id, particularly any company specific conditions and layout actions that may be set up.

It's possible that different rules are selecting different layouts depending on the company or can any other conditions.