I am confused by the Next Approver field on transactions. Does it drive specific functionality in NS and must be used for approval workflows? Our approval workflow is setup this way: There are custom fields to store the individual approvers per approval level. In this way, we can hop on to multiple joins - supervisor of the supervisor of the supervisor, etc. We don't use the Next Approver field anymore because we rely on the values in the custom fields (arranged from first approver to the last one vertically). The last one with the value in the list is the 'next approver'. Is this the best way to handle it? Or should we make use of the native Next Approver field? Thank you.

Are any of your approvers using the employee centre or do they have full access licenses? When we assign an employee value into Next Approver it makes that PO visible in the employee centre

I would use the next Approver field if you can. That way you can utilize the native Bills to Approve, Purchases to Approve, Expenses to Approve (or whatever transactions you need) screens. Those are triggered by that next Approver field and the states in your workflow