Staff compensation rarely fits one universal bonus formula. Some organizations use weekly productivity incentives. Others need a single payout across an entire payroll period. Some want documentation compliance to influence a bonus, while others track compliance separately from compensation.
SPI — Staff Pay Intelligence has been updated to make those real-world differences easier to model without turning Bonus Plans into a complicated rules engine.
Pay-period bonuses now follow the pay period you choose
The biggest change is a new one-time pay-period payout bonus option. Instead of forcing every bonus into a Monday–Sunday weekly calculation, SPI can evaluate a threshold across the selected pay period and add one flat payout when the requirement is met.
That means a weekly, biweekly, semi-monthly, monthly, or custom/manual pay-period workflow can evaluate the work that belongs to that period as a whole. The bonus follows the pay-period record you are reviewing rather than requiring you to rebuild the logic around a separate weekly bucket.
Set the pay-period threshold, choose the qualifying service scope, and define the flat payout. SPI evaluates the selected pay period and records the bonus with that period when the configured rule is satisfied.
Documentation compliance can influence the payout—or stay out of it
Documentation compliance is now an optional part of the pay-period bonus instead of an all-or-nothing assumption.
When Require documentation compliance? is set to No, compliance values do not affect that payout and missing compliance does not create a compliance-specific review issue for the bonus.
When it is set to Yes, you can configure the compliance threshold for the plan. The default can remain 100% for workflows that require every applicable imported row to be marked compliant, but the threshold can be adjusted when an organization uses a different policy.
Importantly, the compliance rule affects the bonus. Base and service compensation remain unaffected when the bonus is not earned.
Staff can now have multiple Bonus Plans
A staff member is no longer limited to one Bonus Plan within a Company assignment. SPI now allows multiple Bonus Plans to be selected for the same staff member.
Each assigned plan evaluates independently. If more than one plan is earned, the payouts can stack. This makes it possible to represent combinations such as a productivity incentive plus a separate pay-period bonus without collapsing them into one oversized rule.
SPI also makes overlapping selections visible in Staff Setup. Overlap is allowed intentionally—the goal is to show the configuration clearly so the organization can decide whether the same eligible work should participate in multiple plans.
A Company-specific Staff ID / Reference # is now available
SPI also added an optional Staff ID / Reference # to each Company-specific staff assignment.
The reference can be used when matching imported service data, which reduces reliance on staff names alone. That is especially useful when the same person works across multiple Companies, when different systems use different employee references, or when two staff members have similar or identical names.
The reference belongs to the Company assignment, so the same staff profile can participate in different organizational workflows without forcing every Company to use the same external identifier.
Why these changes matter
The purpose of SPI is not to decide an organization’s payroll policy. It is to give the organization a clearer place to represent the policy it already uses and make the resulting calculation easier to review.
These updates make the Bonus Plans section much more adaptable: weekly rules remain available, pay-period payouts can match the period being processed, compliance can be included only when it belongs in the rule, and multiple independent Bonus Plans can coexist for the same staff member.
Logic Bunting is a new software suite, and real-world use is one of the most important parts of polishing it. As actual billing, payroll, and operations workflows reveal places where a setting, label, or rule can be clearer, we are focused on improving the product thoughtfully without making it heavier than it needs to be. Thank you for using it, testing it, and progressing with us. We are building this one practical improvement at a time.
See the updated SPI workflow.
Explore the SPI preview to see Staff Pay Intelligence in context, then open SPI from your Logic Bunting account when you are ready to work with your own staff-pay configuration.
Preview SPI