How is a ProPay calculated when budgets are at the task level?

Purpose

Task-level budget types are for jobs where each task or line item has its own budget. Two flavors: Task Hours and Task Amount.

When To Use This

Use this when:

• Your jobs have multiple line items with different budgets
• You quote per-task instead of per-job
• You want bonus precision at the line-item level

Task Hours

Each line item has its own hours budget.

Per-line-item: Saved hours = Budget hours - Actual hours
Total saved = Sum of all line items
Bonus = Total saved × wage rate × split %

Example:

Job has 3 tasks:

• Task 1: Drywall — 8 hours budget, 6 actual = 2 saved
• Task 2: Paint — 12 hours budget, 14 actual = -2 over
• Task 3: Trim — 6 hours budget, 5 actual = 1 saved

Total saved hours = 2 - 2 + 1 = 1 hour

Less granular than rolling all hours together, but gives you visibility into where time was won or lost.

Task Amount

Each line item has its own dollar budget.

Per-line-item: Saved labor = Budget amount - Actual labor cost
Total saved = Sum of all line items
Bonus = Total saved × split %

When Task Types Make Sense

• Multi-trade jobs — Different specialties on the same job
• Estimating shops — Where each task gets a separate estimate
• Granular reporting — You want to see which tasks are profitable

When Task Types Don't Make Sense

• Simple single-task jobs (use Hours or Amount instead)
• When tasks aren't tracked separately in your integration

Common Mistakes & How To Fix Them

• "Tasks aren't itemized in my integration" Task budget types need per-task data from sync. If your integration doesn't track tasks separately, use job-level Hours or Amount.

• "Some tasks are over budget but the total still pays a bonus" Expected. Task budgets aggregate. Over-budget tasks reduce the total but don't block the bonus.

Related Articles

• How is a ProPay calculated? (Hours budget type)
• How is a ProPay calculated? (Amount budget type)
• What are the 4 bonus distribution types?