Skip to main content
Share / Export

Setting Up SL Compliance

SL Compliance reviews and assigns compliance codes to subcontractors and/or suppliers and updates compliance status. Examples: certified payroll, certificates of insurance, signed lien waivers; supplier lien waivers; notice of right to lien; deficiency-letter mail date; lien date/amount. SL tracking feeds AP payment compliance. Code types are Yes/No or Date (defined in HQ Compliance Codes; Comp Type is display-only here).

There is no separate “setup codes” form in SL — codes live in HQ Compliance Codes. This form maintains codes on a subcontract.

Before you start​

  • Compliance codes exist in HQ Compliance Codes.
  • Subcontract already exists in Entering Subcontracts.
  • Optional: compliance group on the subcontract initializes the group’s codes when you open SL Compliance.
  • Supplier (if used) is an AP vendor.
  • Verify defaults come from HQ Compliance Codes or the AP Vendor Compliance override.
  • Whether non-compliance blocks payment or only warns is set in AP Company Parameters (Vendor Compliance Tracking) — not on this form.

How codes get onto a subcontract​

  1. Assign a compliance group in SL Subcontract Entry. Opening that subcontract on SL Compliance lists all codes in the group.
  2. If no group was assigned: in SL Subcontract Entry use File → Add Subcontract (current batch), assign a group, post. Codes are added only if they are not already on the grid.
  3. After post, the group cannot be changed. You can still delete codes one by one on SL Compliance.
  4. Add extra codes on SL Compliance beyond AP Vendor Compliance or the group.
  5. To push one code to many subcontracts: File → Initialize Compliance Code (SL Compliance Initialize), then adjust each instance.

Steps — add a code on SL Compliance​

  1. Open SL Compliance and select the subcontract (header shows JC company, job, job description, vendor).
  2. Enter Comp Code (F4). Seq is assigned automatically (new code defaults to 1; repeating the same code, e.g. certified payroll periods, gets the next sequence).
  3. Adjust Description if needed (defaults from HQ; change it when the same code is used more than once).
  4. Optionally enter Supplier (AP vendor). Blank = subcontractor only. Defaults supplier phone/email.
  5. Check Verify if AP should evaluate this code (default from HQ or vendor override). Unchecked = AP does not verify this code.
  6. Optionally enter Limit (informational only — bonds/insurance; not used by the system) and Notes if your build shows Notes.
  7. Save. Attachments are per code only (not at header).

Maintain / track status​

  • Yes/No: check Complied; optionally enter Receive Date (informational only per field defs — not used elsewhere).
  • Date: enter Exp Date / Expiration Date; optionally Receive Date.
  • With Verify checked, AP Payment Preview with Compliance and SL Worksheet review status:
    • Yes/No: warns if Complied is not checked.
    • Date: compares Exp Date to the AP invoice date; warning if invoice date is after expiration. Tracking also says the sub is in compliance while the current date is on or before Exp Date — treat invoice-date vs current-date wording as two tests help mentions; AP invoice processing uses invoice date.
  • AP Ref: tie the code to one AP reference so that invoice can be held while other compliant invoices can still pay. Blank AP Ref = compliance applies to all invoices.

Notes​

  • Hard hold vs warning is AP Company Parameters, not SL Compliance.
  • Trimble Pay button (if present) is US only.
  • Related: Entering Subcontracts, SL Worksheet, HQ Compliance Codes, AP Vendor Compliance, Vendor Compliance Tracking, AP Company Parameters, SL Compliance Initialize.