Skip to main content

Error: 'Could not determine recipient address' when submitting or approving a transaction

This message indicates that the approval processes set up within FocalPoint Administrator are configured to send an email alert out during the approval process and that FocalPoint cannot find a relevant email address to send the alert to, or that the email address entered is configured incorrectly.

You can check how the alerts are working via FocalPoint Administrator

  1. Locate the relevant stage of approval and click 'Edit'.

  2. Check the 'Alerts' tab. This will show the alerts that are configured for the process.

  3. Open the alert by selecting it and clicking **Edit**.

  4. Note that email alerts can be configured to go to someone involved in the transaction (for example the transaction initiator) or to a specific address.

  5. Check the alert to determine where the alert is being sent. If the alert is configured for a Specific Recipient type, check the email address being used is correct and valid.

  6. If the alert is sent to a user involved in the transaction (for example the initiator) you will need to establish which user this is and then check their member record (see Check the member record below)

If it is not clear which of the alerts are causing the error message, some key users to check the email address for are as follows (these are the user types most commonly used in approval alerts):

  • The initiator of the transaction — i.e. the user that created the transaction.

  • The approver of the transaction

  • The approver who will be responsible for approving the next stage of approval

Check the member record:

  1. Log in to FocalPoint Administrator.

  2. Click System Control.

  3. Click Security Profiles.

  4. Select the profile that the user you wish to update is in.

  5. Click Members.

  6. Select the user in the left-hand list.

  7. Click the Contact tab.

  8. Ensure their email address is completed and is correct.

  9. Click OK to save.

If you are using Office 365 as your mail server, this error can also occur if it has not been set up correctly. If your alert is configured to use a Specific recipient type that uses an SQL server routine, contact support.

Did this answer your question?