Skip to main content
Share / Export

PO Compliance

Company Tracker action: implementation-setup-po-compliance Milestone: Purchase Order / Module Setup (milestone_id=11, core_milestone_id=2) Order: 3 Estimated duration: 0.5 hours Typical owner: Controller / Purchasing

Purpose​

Optionally set compliance codes used on purchase orders when the client will track PO compliance in Vista.

Prerequisites​

  • Know whether PO compliance is in scope at go-live (many implementations skip deep setup).
  • If backfilling open POs: list of compliance codes and correct values for those POs.

Vista configuration article​

See the detailed Vista guide:

PO Compliance

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

Implementation guidance​

  • Typical implementation: you often do not fully set this up during implementation. Codes can be practiced on POs entered in test, but go-live depth is a client call.
  • Go-live if tracking historical/open POs: load compliance codes and apply correct values on open purchase orders that should be tracked.
  • Forward-only option: many clients skip backfill and track compliance only on new POs after go-live.
  • Decide / load / accept: in scope or N/A; if in scope, backfill open POs vs forward-only; accept with Purchasing/Controller.

Tips and gotchas​

  • Not required for every go-live — default thin unless the client wants PO compliance tracking.
  • Backfill vs forward-only is the main decide; do not invent a mandatory historical load.

Done when​

  • Either: PO compliance is N/A / hidden for Module Setup, or
  • Codes exist and open-PO backfill vs forward-only policy is accepted.