Skip to main content
Share / Export

JC Allocation Codes

Company Tracker action: implementation-setup-jc-allocation-codes Milestone: Job Cost / Module Setup (milestone_id=5, core_milestone_id=2) Order: 12 Estimated duration: 0.5 hours Typical owner: Controller

Purpose​

Define JC allocation codes (basis, date option, amount / rate, include lists, target phase / CT, debit / credit GL) used by Process Cost Allocations. Processing runs are later daily ops, not this Module Setup card.

Prerequisites​

  • JC Cost Types, jobs, and JC Departments you will include exist.
  • Know allocation basis (Costs, Hours, or Revenue), date option, and amount or rate.
  • Debit and credit GL accounts ready for when allocation costs post.
  • Confirm the client actually runs Process Cost Allocations. Hide when out of scope.

Vista configuration article​

See the detailed Vista guide:

Setting Up JC Allocation Codes

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

Implementation guidance​

Decide (client / kickoff)​

  • Enable only when the client will run true monthly allocations (Process Cost Allocations). Hide via Tracker otherwise — do not set this up “just in case.”
  • Most common pattern: a flat % of that month’s job cost (for example $10,000 × 2%) redirected to a target phase and/or cost type.
  • By department: when rates differ by department, use separate allocation codes filtered to each department.
  • By hours: also common. Hours live on labor — include only the Labor cost type when the basis is hours.
  • By cost %: choose which cost types feed the basis (labor, material, subcontract, equipment, or all).
  • Before load: code list (up to 255), basis, include lists, target phase / CT, and both debit and credit GLs.

Load / accept (implementation defaults)​

  • Load only codes they will actually run each period. Do not pre-build speculative codes.
  • For Costs or Hours basis, set Cost Types to Include (manual or Initialize Cost Types). Filter Jobs / Departments to Include when using per-department rates.
  • Specify both GL debit and GL credit accounts (not credit-only).
  • Accept means Controller confirms basis, filters, targets, and GL legs for each in-scope code.

Tips and gotchas​

  • Process Cost Allocations is a separate daily-ops step. This card only defines the codes.
  • Flat % of monthly job cost is the usual first allocation; department filters and hours-based codes are the other common shapes.
  • Hours basis → Labor cost type only. Cost % basis → pick the cost types that should drive the %.
  • Missing include lists or one-sided GL accounts fail or mis-post when Process runs.
  • After Process runs, the code Info tab shows last-run date and date range. Use that in training so owners know where to look.

Done when​

  • Either: allocation codes out of scope (N/A / hidden), or
  • In-scope codes exist with accepted basis, targets, and GL legs, ready for Process Cost Allocations.