Approval of vouchers/en - Revision history

FuzzyBot: Updating to match new version of source page

2026-06-29T10:59:21Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2026-06-29T10:54:41Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2026-06-29T09:36:10Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2026-06-29T09:34:22Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2026-06-29T09:32:00Z

Updating to match new version of source page

TR at 09:30, 29 June 2026

2026-06-29T09:30:32Z

FuzzyBot: Updating to match new version of source page

2026-06-29T09:08:41Z

Updating to match new version of source page

New page

<htmltag tagname="style">p a.image{border:1px rgb(0,0,0) solid;box-sizing:content-box;}</htmltag>

== General ==
Manually registered vouchers (in Accounting | Vouchers) on accounts that are set with approval requirement, initiate an approval workflow for vouchers. It is not possible to:
* have approval requirement on assigned accounts or
* create a voucher with one account with approval requirement and another account with an assignment.

When a voucher with approval requirement is saved, it will not be booked directly. Instead, a preliminary voucher is created, without voucher number (marked with *Preliminary in the voucher list)
When a voucher with approval requirement is saved, the same checks are carried out as today, i.e. accounts, cost centres, etc.
The voucher is validated once more after it has been posted to ensure that nothing has changed since the provisional entry was created.
Opening a parked voucher is done in the same way as opening a booked voucher. Approvers can be changed or adjusted until the voucher is booked.
Users with the appropriate authorisation can approve vouchers.
Once the final approval has been given, the voucher is booked automatically. It does not need to be booked manually.

== Preparations ==

{{ExpandImage|ACC-AOV-EN-Bild1.png}}

Accounting | Backoffice | Base registers, tab General ledger, Parameters
From amount and number of approvals are registered here.
In the example above, the system requires one (1) approver for postings between 1,000 and 99,999, and two (2) approvers for postings of 100,000 or more.
To activate the approval workflow, at least the first row of the table must be completed. The minimum values are 1 and 1.

{{ExpandImage|ACC-AOV-EN-Bild2.png}}

There is also a parameter that can be used for not having to choose approvers. Then all users authorised to approve vouchers can do it without being appointed as approver on the voucher.

{{ExpandImage|ACC-AOV-EN-Bild3.png}}

Accounting | Backoffice | Base registers, tab General ledger, Accounts
Check box on account. Determines if posting on the account requires approval.

{{ExpandImage|ACC-AOV-EN-Bild4.png}}

System | Authorisation
Authorisation for approval: Accounting/Vouchers/Approval

{{ExpandImage|ACC-AOV-EN-Bild5.png}}

Approval workflow
When creating a new voucher, there is a new field called Approvers where you can enter the approvers.
Each approver gets a notification reminding them about vouchers to approve.
If necessary, the person who created the voucher can open it and change the approvers and the booking date.
When saving the voucher, a message appears showing the number of approvers selected.

{{ExpandImage|ACC-AOV-EN-Bild6.png}}

Approvers validate and approve or reject the voucher using the Approve button. A dialogue box opens for the approval process.
When you save, the voucher is closed. Once the final approval has been given, it is booked and you receive a message containing the voucher number.
It is possible to change your approval by opening the voucher and repeating the process. This will also trigger a new attempt to book the voucher (provided the checks are OK).

{{ExpandImage|ACC-AOV-EN-Bild7.png}}

Unlike posted vouchers, preliminary vouchers do not have a reference number. Instead, they are displayed as *Preliminary to indicate that they have not yet been booked.
Two columns show the approval status and remaining approvers.
The Approval column shows the approval status, the approver’s user code and the date of approval.
The Delete button can be used to remove preliminary vouchers (to clear out incorrect vouchers that are not to be booked).

{{ExpandImage|ACC-AOV-EN-Bild8.png}}

Corrections to a voucher that requires authorisation can only be made using a new voucher number.
This means that when a correction is made to a voucher, the tick box below is ticked and cannot be unticked.
Approval is possible for a voucher that is assigned to (I) Purchases, (K) S/L, (L) P/L (J) INV and (P) Periodical allocations.

{{ExpandImage|ACC-AOV-EN-Bild9.png}}

If the logged-in user has authorisation to approve, a red badge showing the number of vouchers appears in the left-hand menu. This is only displayed if the Appoint approvers parameter is active.

@@ Line 24: / Line 24: @@
 To activate the approval workflow, at least the first row of the table must be completed. The minimum values are 1 and 1.
-{{ExpandImage|ACC-AOV-EN-Bild2.png}}
+{{ExpandImage|ACC-AOV-EN-Bild2.jpg}}
 There is also a parameter that can be used for not having to choose approvers. Then all users authorised to approve vouchers can do it without being appointed as approver on the voucher.
-{{ExpandImage|ACC-AOV-EN-Bild3.png}}
+{{ExpandImage|ACC-AOV-EN-Bild3.jpg}}
 Accounting | Backoffice | Base registers, tab General ledger, Accounts
 Check box on account. Determines if posting on the account requires approval.
-{{ExpandImage|ACC-AOV-EN-Bild4.png}}
+{{ExpandImage|ACC-AOV-EN-Bild4.jpg}}
 System | Authorisation
 Authorisation for approval: Accounting/Vouchers/Approval
-{{ExpandImage|ACC-AOV-EN-Bild5.png}}
+{{ExpandImage|ACC-AOV-EN-Bild5.jpg}}
 == Approval workflow ==
@@ Line 46: / Line 46: @@
 When saving the voucher, a message appears showing the number of approvers selected.
-{{ExpandImage|ACC-AOV-EN-Bild6.png}}
+{{ExpandImage|ACC-AOV-EN-Bild6.jpg}}
 Approvers validate and approve or reject the voucher using the Approve button. A dialogue box opens for the approval process.
@@ Line 52: / Line 52: @@
 It is possible to change your approval by opening the voucher and repeating the process. This will also trigger a new attempt to book the voucher (provided the checks are OK).
-{{ExpandImage|ACC-AOV-EN-Bild7.png}}
+{{ExpandImage|ACC-AOV-EN-Bild7.jpg}}
 Unlike posted vouchers, preliminary vouchers do not have a reference number. Instead, they are displayed as *Preliminary to indicate that they have not yet been booked.
@@ Line 59: / Line 59: @@
 The Delete button can be used to remove preliminary vouchers (to clear out incorrect vouchers that are not to be booked).
-{{ExpandImage|ACC-AOV-EN-Bild8.png}}
+{{ExpandImage|ACC-AOV-EN-Bild8.jpg}}
 Corrections to a voucher that requires authorisation can only be made using a new voucher number.
@@ Line 65: / Line 65: @@
 Approval is possible for a voucher that is assigned to  (I) Purchases, (K) S/L, (L) P/L (J) INV and (P) Periodical allocations.
-{{ExpandImage|ACC-AOV-EN-Bild9.png}}
+{{ExpandImage|ACC-AOV-EN-Bild9.jpg}}
 If the logged-in user has authorisation to approve, a red badge showing the number of vouchers appears in the left-hand menu. This is only displayed if the Appoint approvers parameter is active.

@@ Line 16: / Line 16: @@
 == Preparations ==
-{{ExpandImage|ACC-AOV-EN-Bild1.png}}
+{{ExpandImage|ACC-AOV-EN-Bild1.jpg}}
 Accounting | Backoffice | Base registers, tab General ledger, Parameters

@@ Line 22: / Line 22: @@
 In the example above, the system requires one (1) approver for postings between 1,000 and 99,999, and two (2) approvers for postings of 100,000 or more.
 To activate the approval workflow, at least the first row of the table must be completed. The minimum values are 1 and 1.
@@ Line 71: / Line 68: @@
 If the logged-in user has authorisation to approve, a red badge showing the number of vouchers appears in the left-hand menu. This is only displayed if the Appoint approvers parameter is active.