Back to the list of other tables
| Field number | Field Name | Description | Type | Length | Index |
| 6 | ID | The ID of the record | UUID | | Y |
| 4 | priority | If this type of authorisation requires authorisation in a particular order, this value is > 0 and denotes this authoriser's place in the order | Long Integer | | |
| 2 | recordType | TEXT values: customerInvoice, supplierInvoice, requestRequistion, responseRequisition, purchaseOrder. In v4.0, only implemented: customerInvoice and requestRequistion | Text | | |
| 5 | reportType | | Text | | |
| 1 | storeID | The store where this authoriser can authorise this type of transaction | Alpha | | |
| 3 | userID | The user who this record applies to- Authorisers are users with the “Can authorise” type set | Alpha | | |
| Field number | Field Name | Description | Type | Length | Index |
| 3 | authoriserID | The ID of the authoriser (foreign key of Authoriser.ID) | UUID | | |
| 7 | comment | | Text | | |
| 8 | ID | The ID of this record | Alpha | | Y |
| 2 | recordID | The ID of the record to be authorised (could be from transact, Purchase_order or requisition tables | UUID | | |
| 9 | recordType | TEXT values: customerInvoice, supplierInvoice, requestRequistion, responseRequisition, purchaseOrder. In v4.0, only implemented: customerInvoice and requestRequistion | Text | | |
| 4 | status | none (i.e. email not sent), pending: email sent to authoriser, authorised, denied | Text | | |
| 5 | statusDate | | Date | | |
| 6 | statusTime | | Time | | |
| 1 | storeID | The store where this record to be authorised exists | Alpha | | |
| 10 | userID | The | Alpha | | |