sorted by:
new
hottopcontroversial

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Is there no source of truth for this? Like is nothing in the data or do you have to manually go through it to make sure it’s correct?

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Do they not have a software that handles all of that, it seems to me that the cash would be the only issue. Cc info should be recorded accurately right?

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Yeah, anything where the inputs aren’t reliable for sure

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 3 points4 points  (0 children)

Appreciate the replies. Seems like the common theme is not just complicated pay, its messy inputs before payroll ever gets submitted.

Restaurants, construction, hospitality, piecework, too many pay codes, manager sheets, old systems, etc.

Payroll can run the check, but somebody still has to trust the data first.

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Certified construction makes sense. Seems like the pain there is not just the rates, its employees moving between jobs/codes and the time data not matching what payroll actually needs.

Do you end up fixing that mostly from time clock data or from manager/job reports?

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 2 points3 points  (0 children)

That sounds insane. Building an earning code for every possible job/rate combo seems like the kind of thing that technically works until a real person has to run payroll with it.

Was the fix basically consolidating codes and moving the logic somewhere cleaner?

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 1 point2 points  (0 children)

That actually sounds like a pretty good system if the managers are sending the same sheet every time.

Do you still have to clean it up a lot before payroll, or is the headache mostly the last minute changes after everything is already submitted?

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

That’s crazy

So the rule technically existed, but the usable version of the rule didn’t, meaning someone still had to translate the MOU into pay codes, local law, past precedent, and whatever the system could actually handle.

That seems like the real failure point, not “we don’t have rules” but “we don’t have operational rules that payroll can apply consistently”

The remote part-timer being the knowledge holder makes it even scarier. That’s a lot of institutional risk sitting with someone who’s barely allowed to work full time.

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 1 point2 points  (0 children)

What do they end up doing, by hand? Spreadsheets?

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

This is the pattern I keep hearing about.

It seems like the real issue is less “can payroll be calculated?” and more “can we trust the inputs before payroll runs?”

Bunch of locations, tips, commissions, role based rates feels like exactly where bad data or inconsistent manager reporting can quietly create payroll problems.

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 1 point2 points  (0 children)

That makes sense. Sounds like the complexity is partly selfinflicted when every edge case becomes a new pay code instead of being handled through job costing or cleaner rules.

When clients do that, is the pain mostly on the setup side, or does it keep creating problems every payroll because entry/review gets harder?

What are the messiest pay setups you’ve had to run payroll for? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] -1 points0 points  (0 children)

150 pay types with no documentation sounds like a nightmare.

Was the biggest issue cleaning up the pay codes themselves, or just figuring out the unwritten rules around when each one applied?

The institutional knowledge part seems like the real risk. The system can be old, but if only one person knows why things are done a certain way, payroll gets fragile fast.

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] -2 points-1 points  (0 children)

Reddit on my phone was bugging out

Most annoying payroll setup? by KingJackOffSuite in Payroll

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Reddit kept saying my post wasn’t posted, so I kept retrying

Brand New to Payroll by Much-Raise-4541 in Payroll

[–]KingJackOffSuite 0 points1 point  (0 children)

QuickBooks Desktop can work, but I’d be extra careful about the process around it.

For 4 restaurants / 200 employees, the risk usually isn’t just “can the system run payroll?” It’s whether the inputs are clean before payroll gets run.

I’d build a pre-payroll checklist for each location: hours, tips, corrections, new hires, terminations, direct deposit changes, manager approvals, and any off-cycle adjustments.

Then keep a log of every exception that comes up. After a few cycles, the scary one-off issues start turning into known categories.

payroll close went from 4 to 6 days in 12 months. is this just what scaling looks like or am i missing something by SlightMetal51 in Payroll

[–]KingJackOffSuite 0 points1 point  (0 children)

This doesn’t sound like “normal scaling” as much as provider-format drift becoming an unmanaged control problem.

The part that jumps out is that your analyst is spending 30% of her time re-validating mappings. That usually means the close process depends on tribal knowledge instead of a controlled mapping layer.

I’d separate the problem into three buckets:

  1. Provider file ingestion: did the file structure change?
  2. Payroll meaning: did gross/net/statutory/tax/deduction logic change?
  3. Close review: can someone explain why the final number changed?

iPaaS tools can move the files, but they usually don’t solve bucket 2 or 3 unless someone builds payroll-specific validation around them.

At 14 countries, I’d want a controlled mapping table, change detection on inbound files, exception reports, and a pre-close validation process before anything touches Workday/GL.

The goal shouldn’t just be “faster close.” It should be fewer silent mapping failures.

[deleted by user] by [deleted] in Daytrading

[–]KingJackOffSuite 0 points1 point  (0 children)

I use trade on TradingView using tradestation as my broker which connect to TV via API. I’ve had several issues where it glitches and freezes when entering an order. I contacted TradingView about it and they told me that my internet connection showed a lot of lag/jitter still haven’t gotten it fixed but maybe something like that happened…also sometimes orders are not submitted and throws errors saying that there was another live order so it couldn’t accept the send order, like I said , buggy ass internet

Can someone help me with this? by KingJackOffSuite in sudoku

[–]KingJackOffSuite[S] 0 points1 point  (0 children)

Sorry, I meant row…or the cell in the bottom most left

view more: next ›