Coding and Navigation - Impacts Operating / Customer companies only
SSO - Impacts Vendors and Customers
IN THIS RELEASE
Change invoice coding after payment approval - new Operating Entity setting, on by default; no Payment Approval reset needed
Reduced automatic navigation away from invoices - behaviour change
Single sign-on with Microsoft or Google - migrate existing accounts or invite new people; by invitation only
Change invoice coding after payment approval
What's new
A new Operating Entity level setting allows users holding the Confirm Coding security role to change the coding on an invoice after that invoice has entered the Payment Approval workflow. Previously, coding could not be changed without resetting payment approval.
The Payment Approval does not have to be reset. When an invoice is rejected by your accounting system because of incorrect coding, you no longer need to reset the Payment Approval in order to correct it. The coding is reset, changed, and approved, and that refreshes the invoice so it is ready to import to your accounting system again.
This setting is enabled by default. Administrators who wish to retain the previous behaviour must disable it for each Operating Entity.
Primary use case for this change: correcting coding rejected by your accounting system
1. An invoice is fully approved for payment.
2. Your accounting system rejects the invoice for invalid coding.
3. A user with the Confirm Coding role resets the coding, changes the coding, and approves the coding.
4. The rejection status is reset and the invoice is ready to be imported into your accounting system again. The Payment Approval stays intact throughout — it never has to be reset.
Reduced automatic navigation away from invoices
You will no longer be automatically navigated away from an invoice when you are done your work (after clicking all the workflow buttons available to you) . This allows you to remain on the invoice to review it or take further action.
Automatic navigation now occurs in two cases only:
You forward the invoice (or work ticket).
Your payment approval fully approves the invoice.
Logging in with Microsoft or Google (single sign-on)
Energy Payables now supports signing in with a Microsoft or Google account. Existing Email/Password accounts can be manually migrated to Microsoft or Google login, and new people can be invited to Energy Payables and sign in with Microsoft or Google from the start.
Per-person setting. Single sign-on is enabled for individual users, not for the company as a whole.
Existing accounts are migrated manually. A current Email/Password account does not switch over on its own. It is migrated to Microsoft or Google login one person at a time.
An invitation is required. A person must be invited before they can sign in. They cannot log in with Microsoft or Google without having been invited first. The invited person must use the invitation email sent to them to correctly cut over from Email/Password login to Microsoft or Google login.