Extra release for cases related to e-Invoice.

• Final approver cannot change coding
  • After the release, final approvers will be able to change the coding on all invoices before final approval. Initially, this will apply to all users who are part of a group that provides final approval for a cost center and for whom it was previously not possible to make changes. Note that this applies to invoices that have not been handled by the integration. If a supplier invoice has been handled by your integration, it is not possible to change the coding.
• Final approver cannot change another final approver's approval
  • The current logic is that a final approver can provide final approval for any invoice within the cost center, but undoing the approval is personal. This is now changed so that a final approver within a cost center can undo the approval of another final approver within the same cost center, as in the previous version. Note that this applies to invoices that have not been handled by the integration. If a supplier invoice has been handled by your integration, it is not possible to undo a final approval, except when the invoice has received an error message and could not be exported.
• Users only see their projects as approvers in the coding
  •  This filtering was redesigned to only show the projects where the user in question is part of the approval flow. The logic is now changed to show all projects the user has permission to view, including other projects belonging to other project managers. A user can then “send” the invoice to another project and therefore to another approval flow. Note that this only applies to being able to select another project; a user does not have the ability to manage coding for other projects. If a user still cannot see any projects, check that project permissions have not been activated and that the user lacks permission through that function!
• Indications of performance issues
  • We have received several reports that Next e-Invoice is perceived as slow, particularly in connection with approving invoices. Changes have been made to parts of how an invoice is processed so that the system goes through less information, with the same accuracy but at a faster speed, to prevent these delays from occurring.
• Approval limit cannot be changed in an active approval flow
  • It is now possible to change the approval limit in an active approval flow. The change takes effect immediately for all invoices in the approval flow (invoices that have already received final approval are not affected). However, if an invoice has already been approved in step 1 and the limit is raised for approver 1 so that the invoice is approved according to the limit, it will not receive final approval automatically but will remain awaiting approver 2 or the final approver.
• Non-admin users lose access to certain invoices
  • Users who are not finance admins lost access to an invoice if the invoice had been exported once and received an error message. The reason was incorrect filtering that hid invoices with an export date, regardless of whether the export was successful. This has now been fixed so that an invoice is visible to the appropriate approver as long as it has not been fully exported.
• Approver in step 1 cannot manage invoices with an amount difference
  • The difference field is not displayed for users who are not finance admins. This field will now be displayed again. The point above regarding displaying coding lines also makes it easier to identify where the difference occurred and any corrections that need to be made. 
• It is not possible to undo accrual
  • If the user checks “Accrual” and then changes their mind and unchecks the checkbox, the checkbox becomes locked and cannot be checked again. This is an identified bug, and it is now being fixed so that it is possible to check accrual again.
• “Manage coding” is not applied in step 2 if step 1 has approved the invoice
  • The ability for approver 2 to manage coding disappears when approver 1 has approved the invoice, even if approver 2 has the right to “Manage coding” according to the approval flow. This is now changed so that “Manage coding” always grants the right to change the coding information. Note that this applies to all coding information and that it is possible to change the coding on an invoice that has already been approved in step 1!
• Error message when using “Get coding”
  • Using the “Get coding” function from the history generated the error message “Could not initialize the item.” A bug has been identified and is now being fixed so that the function for retrieving coding works as intended.
• Display all coding lines on the invoice
  • A new filter in Next e-Invoice sorts out all coding lines that are not on a project where the user is an approver at any step. This is now changed so that all coding lines are displayed. The rules for the approval flow still apply at the line level.
• The “Ready for approval” and “Undo ready for approval” buttons are now activated immediately: 
  • A bug caused the “Ready for approval” button to be unclickable even though the invoice was complete; the user had to switch between tabs or other invoices to make it work. This has been fixed, and the button is now activated immediately when you save changes to the invoice.