The Item Detail view allows you to edit the Required field and displays several new fields.
Fields
| Description | A longer description os the compliance item, if any. |
| Carrier | The name of the carrier for this compliance item. |
| Amount | The amount of coverage. |
| Effective | The date the compliance item goes into effect. If the Effective field is active (ie, you can select a date from the calendar icon), and you leave the field blank, the item will be out of compliance. If you enter an Effective Date, it will be checked against the Current Start Date and Finish Date on the Dates tab. |
| Expiration | The date the compliance item expires. |
| Released | The date the compliance item is released. Releasing the compliance item overrides the Effective/Expiration dates and the Required/Received dates. |
| Lead Days | The number of days before the Expiration Date a Compliance Alert should be sent. |
| Recurs | How often the Compliance Alert should be sent. |
| Pay Control | The Pay Control option for this compliance item. Pay Control options: – Auto: the compliance item is evaluated based on the Commitment’s Current Date and the Compliance requirements. If anything is out of compliance, the Pay Request associated with the Commitment or Vendor will not allow approval. – Block: The compliance item is manually set to out of compliance, and the Pay Request associated with the Commitment or Vendor will not allow approval. – Warn: The compliance item is evaluated based on the Commitment’s Current Date and the compliance item’s requirements. If anything is out of compliance, warning messages appear on Commitment and Pay Request documents. The Pay Request can be approved. |
| Last Evaluation | A message indicating why the item is in or out of compliance. |
Last Evaluation Messages
| Required, not met | Out of compliance because of a Required Date but no Received Date. |
| Expired | Out of compliance because of an Expired Date that is within the Start and Finish dates of the Commitment. |
| Required, but not Effective | Out of compliance because of a Required Date but no in-range Effective Date. |
| Amount insufficient | Out of compliance because of a required Amount, but the amount is less than the total current amount of the Commitment. |
| TIN missing | Out of compliance because of a missing Vendor Taxpayer Identification Number. |
| Manually blocked | Out of compliance because the Pay Control for this requirement is set to Block. |
| Released | In compliance because of a Released date for or prior to today. |
| Conditions met | In compliance because it has met all conditions. |
| Commitment covers requirement | In compliance because the commitment has a compliance item of the same type that is in compliance |
| Vendor covers requirement | In compliance because the associated Vendor has already complied with the requirement of the same type. |
| Expired, but work ended | In compliance because the work period is not ongoing. See KBA-01601 |
| Expires soon* | In compliance but the Expired date is approaching and within the lead days interval. |
| Required, but work ended | In compliance because the work period is not ongoing. |
| Required soon* | In compliance because the Required date in the future, but that date is approaching and is within the lead days interval. |
| Required soon (Effective late)* | In compliance because the Required date is in the future, but the Effective date will not cover the Required date with it arrives. |
| Not required yet* | In compliance because the Required date is far in the future (outside the lead days interval). |
*These messages will generate a Compliance Alert even through the compliance items are still active.