FuzzyBot: Updating to match new version of source page

2022-11-15T14:54:44Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2022-05-19T07:00:02Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2022-05-18T22:00:04Z

Updating to match new version of source page

New page

{{News
|Approval of Vouchers
|module=Finance
|group=
|version=546W2204
|revision=0
|case=CORE-3351
|published=2022-5-18
}}

'''General overview Approval of Vouchers'''

Manually registered vouchers (registered in G/L | Vouchers) on accounts that has ""Approval=Yes"" will trigger approval flow for vouchers. It's not possible to:

1) have approval=Yes on account with integration or

2) create a voucher with one account that has approval=Yes and another account that has an integration.

Saving a new voucher that demands approval will not book the voucher directly. Instead a preliminary posting without a voucher no. is created (indicated by *Preliminary* in the voucher list).

Saving a new voucher that demands approval will perform the same validation of accounts, cost centers etc. as done today. The voucher is validated once more when booked in case something has changed since the preliminary voucher was created.

Opening a parked voucher is similar to opening a booked voucher. Approvers can be changed/edited until the voucher is booked.

Appointed users with approval authorization can approve a voucher.

When the last needed approval is made the voucher is booked automatically. There is no separate action needed for "booking" the voucher.

'''Preparations'''

{{ExpandImage|Vapproval1.png}}

'''Base register | G/L | Parameters'''

From amounts and needed number of approvals is registered here.

In the above example the system will demand 1 approver for postings with amount spanning from 1 000 to 99 999 and 2 approvers for postings with a total of 100.000 or more.

To activate the approval flow at least the first line in the table must have a content. Minimum is 1 and 1

{{ExpandImage|Vapproval2.png}}

'''Base register | G/L | Accounts'''

Checkbox on account. Determines if posting on account needs approval.

{{ExpandImage|Vapproval3.png}}

'''System | Authorisation'''

Authorisation for Approval: General ledger/Vouchers/Approval

{{ExpandImage|Vapproval4.png}}

'''Approval flow'''

When creating a new voucher there is a new field "Approvers" in which the user creating the voucher can assign approvers.

Each assigned approver will get a notification as a reminder that they have a voucher to approve.

If needed, the user that made the preliminary posting can open the voucher and change approvers and accounting date.

When saving a voucher a message is shown with the number of appointed and required approvers.

{{ExpandImage|Vapproval5.png}}

Approvers validates and approve/reject the voucher by opening the voucher and clicking on button "Approval". This opens a pop-up in which the approver is promted for an approval.

On save the voucher is closed. If the approval made is the last one needed the voucher is booked and the message is followed by the assigned voucher no.

Approvers can change their approval by opening the voucher and re-do the same process once more. This will also trigger another atempt at booking the voucher (if the approval checks pass).

{{ExpandImage|Vapproval6.png}}

"Preliminary" vouchers are separated from booked voucher by not having a voucher no. Instead these are shown as *Preliminary* to indicated that these are not yet booked.

Two new columns shows approval status and remaining approval

Approval column shows Approval status, Approver user code and date for when the approval was made.

New button "Delete" can be used to remove preliminary vouchers (to clean up incorrect vouchers which will not be booked).

{{ExpandImage|Vapproval7.png}}

Corrections on a voucher that demands approval can only be done on a new voucher no.

This means that when making a correction on a voucher the below checkbox is checked and not possible to uncheck

@@ Line 6: / Line 6: @@
 |revision=0
 |case=CORE-3351
-|published=2022-5-18
+|published=2022-05-18
 }}

@@ Line 19: / Line 19: @@
 Saving a new voucher that demands approval will not book the voucher directly. Instead a preliminary posting without a voucher no. is created (indicated by *Preliminary* in the voucher list).
-Saving a new voucher that demands approval will perform the same validation of accounts, cost centers etc. as done today. The voucher is validated once more when booked in case something has changed since the preliminary voucher was created.
+Saving a new voucher that demands approval will perform the same validation of accounts, cost centers etc. as done today.
 Opening a parked voucher is similar to opening a booked voucher. Approvers can be changed/edited until the voucher is booked.

News:Approval of Vouchers/en - Revision history

FuzzyBot: Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

FuzzyBot: Updating to match new version of source page