Difference between revisions of "News:Approval of Vouchers/sv"

Revision as of 14:03, 19 May 2022

Attest av verifikationer

Manuellt registrerade verifikationer (i BOK/Verifikationer) på konton som har Attest =Ja initierar ett attesteringsflöde för verifikationer. Det är inte möjligt att:

1) ha attest = Ja på ett integrerat konto eller

2) skapa en verifikation me ett konto som har attest =Ja och ett annat konto som har en integration.

När man sparar en verifikation som kräver attest bokförs den inet direkt. I stället skapas en preliminär kontering utan verifikationsnummer (märkt med *Preliminär iverifikationslistan)

När man sparar en verifikation som kräver attest görs samma kontroll av konton, kostnadställen, etc. som idag.

Verigikationen valideras en gång till efter att den blivit bokförd för att säkerställa att inget ändrats sedan den preliminära konteringen skapades.

Att öppna en parkerad verifikation görs på samma sätt som man öppnar en bokförd verifikation. Attestörer kan ändras/justeras tills verifikationen blir bokförd.

Användare med behörighet kan kan attestera verifikationer

När den sista attesteringen är gjors bokförs verifikationen automatiskt. Det behöver inte bokföras manuellt.

Förberedelser

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

Base register | G/L | Accounts

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

System | Authorisation

Authorisation for Approval: General ledger/Vouchers/Approval

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.

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).

"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).

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