Bundle vs. Batch vs. Consolidate
These three concepts are distinct and frequently confused. Understanding the difference helps you configure service rules correctly.
BUNDLE — Many Encounters → 1 Service
Multiple encounters collapse into a single service line item.
Requirements: same date of service, same rendering provider, same CPT code, same modifiers.
Encounter type does not need to match.
Cannot cross date-of-service boundaries.
Used at IOP/PHP for daily bundled billing. When bundling is enabled, all qualifying same-day encounters produce one service.
BATCH — Many Services → 1 Claim with Multiple Line Items
Multiple services are placed on one claim as separate line items.
Services must share the same authorization, client, and payer to be batched together.
Individual line items do not need to match each other.
CONSOLIDATE — Many Services → 1 Claim Line Item with Aggregated Units
Multiple service lines collapse into one claim line item with combined units.
Requirements: CPT code and line item configuration must match. Date of service and encounter type do not need to match.
Designed for cross-date-of-service consolidation — bundling cannot do this.
Adds units together across multiple dates into one line item.
Do not use Consolidate for same-day sessions with different credential modifiers — those lines cannot be merged.
Which to Use
For same-day sessions, use Bundling rather than Consolidate. Sessions with different credential modifiers stay as separate lines and cannot be merged into a single line item.