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

From Marathon Documentation
Jump to: navigation, search
(Created page with "'''Grunnregister/BOK/Parametre'''")
(Created page with "Fra og med-beløp og antall attestanter angis her")
Line 36: Line 36:
 
'''Grunnregister/BOK/Parametre'''
 
'''Grunnregister/BOK/Parametre'''
   
  +
Fra og med-beløp og antall attestanter angis her
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.
 
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.

Revision as of 15:18, 27 May 2022

Attest av bilag
Published 2022-5-18
Module Økonomi
Version 546W2204
Revision 0
Case number CORE-3351

Generelt

Manuelt registrerte bilag som registreres i BOK/bilag på kontoer med Attest-Ja setter igang prosessen for attestering. Det er ikke mulig å:

1) ha Attest= Ja på et integrert konto eller

2) skape et bilag med konto som har Attest = Ja og et annet konto med integrasjon.

Lagring av et nytt bilag som krever attest leder ikke till bokføring direkte. Det blir i stedet merket som *Planlegget* i bilagslisten.

Lagring av nytt bilag som krever attest gjennomfør same validering av kontoer, koststeder mm. som idag.

Bilaget valideres en gang til etter bokføring dersom det er blitt endringer etter førrige bilag skaptes.

Å åpne ett parkert bilag er som å åpne et bokført bilag. Attestantene kan endres/redigeres inntil bilaget blir bokført

De valgte attestantene må vara autoriserte til attestering

Da den siste attesten er gjort bokføres bilaget automatisk.


Forberedelser

Grunnregister/BOK/Parametre

Fra og med-beløp og antall attestanter angis her

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