JB Processing Groups
Company Tracker action: implementation-setup-jb-processing-group
Milestone: Job Billing / Module Setup (milestone_id=8, core_milestone_id=2)
Order: 11
Estimated duration: 0.5 hours
Typical owner: Controller / Billing
Purpose
Define processing groups so a set of contracts (or customers / T&M templates) can be initialized together on a schedule instead of one invoice at a time.
Prerequisites
- Contracts (and customers / T&M templates if used as the group basis) exist for go-live billing.
- Know which invoices are always initialized together each month (by customer, contract set, or T&M template).
Vista configuration article
See the detailed Vista guide:
Field meanings and form steps live there. Do not restate them on this page.
Implementation guidance
- When in scope: the client wants to initialize invoices for a group at a set time each month, rather than one contract at a time.
- Group basis: processing groups can be contract-specific, customer-specific, or T&M template-specific — whatever defines “what to include” in that initialization run.
- Decide / Load: create groups that match real monthly billing batches; assign the contracts / customers / templates that belong. Skip/hide if every bill is initialized individually and no batch init is planned.
- Accept means Billing/Controller confirms which groups exist, what they include, and that init-by-group is how those bills will start each period.
Tips and gotchas
- Individual contract init still works without processing groups — groups are for batch efficiency.
- Wrong membership = wrong set of invoices in the monthly init; keep the group list aligned with who bills together.
- Template-specific groups are useful when a T&M pattern (not just a customer list) drives the batch.
Done when
- Either: processing groups are out of scope (action N/A / hidden), or
- In-scope groups exist with the correct contract / customer / T&M template membership for monthly init.