# An Introduction to Pay Bumps for Background Performers Pay bumps are common on set, but processing them for background performers is rarely simple. Once those adjustments reach payroll, small changes can quickly add complexity. Written by The Everyset Team ## Why Pay Bumps Are More Complex Than They Look Pay bumps exist to compensate performers for additional requirements. That could mean wearing their own wardrobe, working in difficult conditions, or handling something outside of standard background work. On set, that usually feels straightforward. In payroll, it is not. Take a wet bump. The intent is clear in the moment. But that still needs to be coded correctly, classified properly, and processed in line with union and state rules. If any of that is off, it does not show up immediately. It shows up later, when payroll is already in motion. Custom bumps add another layer. They often start as a practical decision on set, but without a clear definition, they introduce ambiguity into payroll. That ambiguity is where errors, delays, and cost discrepancies begin. ## The 6 Essentials to Getting Pay Bumps Right Most issues with pay bumps are not caused by the rules. They come from how bumps are defined, recorded, and processed. These are the six areas where productions most often see errors, delays, or added payroll complexity. ## 1. Standard vs Custom Pay Bumps Standard pay bumps are defined within union agreements and supported by payroll systems. Custom bumps are not. They are created to meet specific production needs, often without a clear definition of how they should be treated. **Why it matters:** Once a pay bump is unclear, it tends to be handled differently across departments and vouchers. That inconsistency carries through payroll, where it affects how calculations are applied and how costs are tracked. **Best practices:** - Define custom bumps before production begins - Align with the accounting team on classification and treatment - Avoid introducing new bump types mid-production without review ## 2. Flat Bumps vs Rate Adjustments Some pay bumps are simple flat payments. Others increase the performer’s rate, which affects how their entire day is calculated, including overtime and penalties. The difference is that one is treated as an added payment, while the other changes how earnings are calculated across the entire voucher. **Why it matters:** Rate adjustments do not just affect one line item. They change the base for multiple calculations. That impact is often not visible upfront, but it compounds across payroll. **Best practices:** - Confirm whether each pay bump is flat or rate-based - Ensure payroll systems apply the correct calculation logic - Validate early payroll runs to confirm expected outcomes ## 3. Pensionable vs Non-Pensionable Not all pay bumps are treated the same for fringes. Some are included in pension and health calculations, while others are excluded. **Why it matters:** Misclassification impacts both compliance and budget. - Incorrectly marked as non-pensionable → underpayment of fringes → compliance risk - Incorrectly marked as pensionable → overpayment → unnecessary cost At scale, even small misclassifications can materially affect total payroll. **Best practices:** - Confirm pensionability during project setup - Standardize bump codes to avoid inconsistencies - Review fringe calculations early in the production ## 4. Taxation Pay bumps are generally treated as taxable wages, but how they are taxed depends on how they are structured and processed. Flat pay bumps are added to gross wages. Rate-based pay bumps increase the taxable base. Custom bumps can introduce additional complexity depending on classification and jurisdiction. **Why it matters:** Tax errors create downstream issues that extend beyond payroll. - Under-taxation → penalties and corrections - Over-taxation → talent dissatisfaction - Misclassification → inaccurate reporting These issues often surface later, when they are more difficult to resolve. **Best practices:** - Confirm tax approach before processing - Avoid manual overrides unless necessary - Use systems that apply compliant tax logic automatically ## 5. Inconsistent Pay Bump Coding The same pay bump can appear in different ways across a production. One voucher says “wardrobe,” another says “wardrobe bump,” another just says “bump.” In payroll, those are not equivalent. Without standardized inputs, systems cannot reliably apply the correct rules. **Why it matters:** Inconsistent data leads to inconsistent calculations. That affects fringes, taxation, and reporting. These issues are difficult to detect early because they do not appear as obvious errors, but they accumulate over time and across volume. **Best practices:** - Standardize pay bump codes before the first voucher - Use predefined selections instead of free text - Spot check early vouchers for consistency - Address variations immediately before they scale ## 6. Missing or Vague Voucher Details On set, speed matters. A note like “bump” may be clear in the moment, but that context does not carry into payroll. Without clear detail, payroll teams are left to interpret, confirm, or delay processing. **Why it matters:** Unclear inputs create friction across the workflow. Payroll cannot process what is not clearly defined, which leads to back-and-forth, delays, and increased risk of error. At scale, this slows down the entire payroll cycle. **Best practices:** - Be specific when recording pay bumps on vouchers - Avoid generic labels without context - Confirm custom bumps before they are documented - Double-check common items like wardrobe, props, and wet work ## Bringing It All Together Pay bumps may seem like small line items, but they carry outsized impact. They affect payroll accuracy. They affect compliance with union and state rules. They affect total production cost. When handled consistently, they move through payroll without issue. When they are not, they introduce delays, rework, and risk. The difference is not understanding what a bump is. It is having the structure to handle them correctly at scale.