SL Compliance
Company Tracker action: implementation-setup-sl-compliance
Milestone: Subcontract Ledger / Module Setup (milestone_id=12, core_milestone_id=2)
Order: 3
Estimated duration: 0.5 hours
Typical owner: Controller
Purpose
Complete the Subcontract Ledger Module Setup action for SL Compliance so client decide/load/accept is clear before live use. Form field detail stays on the Vista article.
Prerequisites
- SL Company Parameters are configured.
- Compliance codes and groups are defined for your requirements.
Vista configuration article
See the detailed Vista guide:
Field meanings and form steps live there. Do not restate them on this page. If Phase 1 Vista depth is still incomplete for a subtopic, keep Tracker thin and link the module intro rather than inventing fields.
Implementation guidance
- Decide / load / accept: Decide what must exist for go-live, load the master/config for this action, and accept with the typical owner. Policy notes from Phase 1: For date-driven codes, invoices past the expiration date can put the subcontract out of compliance.
- Prefer TAD for bulk master loads when volumes are large; key small lists.
- Do not invent client-specific starter packs without labeling them as recommended patterns.
Done when
- In-scope setup for this action is loaded (or explicitly N/A / hidden when optional and out of scope).
- Owner accepts the decide/load result for go-live.
- Linked Vista configuration matches what was accepted.