Separate User Approval on voucher types B and N in IFS Cloud: control it before posting, not after

Approval is not offered on B and N vouchers by design, so the control has to sit earlier in the process.

1. Understand why approving the voucher adds nothing: B and N vouchers are created from Mixed Payments and Offsets that have already been approved. The resulting voucher cannot be changed or cancelled on its own; the only way to reverse it is to cancel the source transaction.
2. Move the review to the source: review Mixed Payments and Offsets before they are approved, and grant the right to approve them only to selected users. This is done through normal permission set and role design, restricting the approve functions to specific roles.
3. Optionally split entry and approval with user groups: combine user groups with the voucher series and voucher type. For example, a user who enters mixed payments belongs to user group X, which has no access to voucher types N and B, so they can enter the mixed payment but it cannot be finalised by them. A second user in user group Y, which does have access to N and B, approves it. An IFS employee in the thread reports using this setup with many clients.

Status: suggested by a partner and an IFS employee; the original poster had not confirmed the result at the time of reading.

Prerequisites and limitations Requires permission set and role administration plus voucher series user group setup. Does not add a voucher-level approval step for B and N; it relies on controlling who may approve Mixed Payments and Offsets and who has access to voucher types N and B. Not confirmed by the original poster.