Creating Separate Paycheck with Aggregate Taxes

Did you use an alpha character in the process group field on the time record for the extra wages?

No, our understanding is that would create a single payment where we really want to have two separate checks that are considered as one for taxation.

A value in the check group will create separate checks

But will it tax them together? We know how to create a second check, what we're having difficulty with is how they are taxed. The taxable wages for each check need to be calculated together.

Personally, I don't understand exactly what you're trying to do. Hopefully, one of these options will be what you're looking for -

Field Help for Check Group = Type a check group value.
Type a check group value.
On inquiry, check group values for existing time records display, but can be changed.
All time records with a common entry in this field are grouped on one payment record for the employee. If multiple payments are desired, type a different value. You can type alpha or numeric values.
If you type a numeric value, the corresponding deduction cycle is applied to the pay associated with that check group.
If you type an alpha value, the system takes the deductions based on the cycle defined in PR140 (Earnings and Deductions Calculation).

Field Help for Process Group - Type a process group value.
On inquiry, process group values for existing time records display, but can be changed.
All time records with a common value in this field are grouped for tax calculation purposes. Process groups let you tax pay codes separately, but combine earnings in a single payment.
If you type a numeric value, the corresponding deduction cycle is applied to the pay associated with that process group. In this case, the system can take miscellaneous deductions more than once per payment.
If you type an alpha value, the system only takes miscellaneous deductions once per payment.

We know how to create a second check within the same pay cycle. We are trying to aggregate the taxable wages for both checks, so that the second check is not taxed separately from the regular bi-weekly check. We have tested Supplemental Tax Codes 2 and 5 without success. Code 5 aggregated for some examples, but overall their was a difference in the amount of federal tax deducted of between $5-10. The taxable wages for both checks match.

Since those fields are used by BSI for calculations, sounds like a call to their support, particularly if it's working for some, but not all examples.

I'm not sure I follow the desired intent on this one...

Are you trying to essentially split a net payment to the employee (net of taxes, deductions, and garnishment) in two payments without doing an off cycle check?
Essentially you want to check numbers assigned to a net payment with an arbitrary split in the amount?

If so, the only *fool-proof* way I could think of is to setup two payment entities for the employee (either two employee numbers, or an employee and a vendor). One would be taxed, and the other wouldn't be.

If my understanding is incorrect, could you post an example scenario.

I'm not sure how you can BSI calculate the exact same number every time (no matter the split between the checks) using the method Lawson provides, as I would imagine some tax rules would apply at different percentages based on the payment sizes.

Kwane

We have a support ticket open with BSI to test the tables they have assigned to the Supplemental Tax Codes. They all appear to be taxing at the US flat rate even though the descriptions differ. Using the same values on all of our testing results in variances. Thanks for everyones response.

Update: we resolved this with BSI by assigning Supplemental Tax Code = 2 US Separate Aggregation. BSI uses Supplemental Method = 1 for this option to assign the rate table. Using this method we were able to successfully create two payroll check payments for the same date, aggregate the taxable wages, and have the federal and state taxes balance.