Draft Certificate processing provides an authorisation process for subcontract certificates prior to them being posted to the ledger. Certificates can be entered and authorised by different individuals, and authorisation can be carried out in separate stages (that is, by up to three different individuals) if required. Once draft certificates have been authorised, they can be included in a batch and posted to the ledgers in the standard Coins ERP+ way.
A draft certificate passes through different authorisation stages:
Input/Entry Stage, attention required. At this level certificates can be amended. They can be put on commercial hold. They can also be released.
Released, awaiting Level 2 authorisation. They can be recalled (set back to the input stage).
Authorised at level 2, awaiting level 3 authorisation (when SC/NOTIERS is set to 3 or 4).
Authorised at level 3, awaiting level 4 authorisation (when SC/NOTIERS is set to 4).
Authorised at the highest available level, awaiting batch creation.
For low-value transactions, you can allow a lower level of authorisation. You can set the default value below which this applies, and can also define the values on a contract-by-contract basis.
Draft Certificate Process Diagram
This diagram illustrates the process when SC/NOTIERS is set to 3.
