Skip to main content
Share / Export

HQ Compliance Groups

Company Tracker action: implementation-setup-hq-compliance-groups Milestone: Headquarters / Module Setup (core_milestone_id=2) Order: 16 Estimated duration: 0.5 hours Typical owner: Controller

Purpose​

Organize compliance codes into groups so assigning a group on a subcontract or purchase order applies every code in the group.

Prerequisites​

  • HQ Compliance Codes created first.
  • Know which compliance bundles apply to subcontracts vs purchase orders for typical projects.
  • Design groups so only relevant codes are included (irrelevant codes create false holds).

Vista configuration article​

See the detailed Vista guide:

Configuring HQ Compliance Groups

Field meanings and form steps live there. Do not restate them on this page.

Implementation guidance​

  • Groups bundle codes: assign the group on an SL or PO and every code in the group applies.
  • Groups are shared across companies. A single code can belong to multiple groups.
  • Default assignment points: JC Jobs / PM Projects have separate fields for subcontract vs PO groups. When a user enters a new SL or PO on a job/project with a default group, codes initialize automatically. Or assign a group directly on the commitment when the default does not apply.
  • Only include relevant codes. Irrelevant codes create false compliance holds.
  • Gotcha: design each group for a specific commitment type, not a kitchen-sink list.

Done when​

  • Compliance groups exist that bundle the correct codes for common SL and PO scenarios.
  • Default assignment points known: JC Jobs / PM Projects subcontract vs PO group fields (or direct assign on commitment).