Notes and observations
Team Notes (Diego & Ben)
awc.pdf | |
File Size: | 63504 kb |
File Type: |
american_woodmark_ben_notes.pdf | |
File Size: | 221 kb |
File Type: |
Pain Points & Discussions by Clients
- Paygroups must be configured by state for SUI, can take up to 3 days to be implemented in Autopay
- Should HR be assigning Tax Jurisdictions to Employee at time of onboarding?
- ADP recommended manual assignment by payroll practicioner as best practice
- Other tax questions including work location vs. reported location as where they work is not necessarily where their payroll is "charged" to in GL, other reporting
- Edge Case - Arizona asks in tax set up if employee is set up for ACA - this is not currently integrated in EE Benefit Selection
- Confusion about Employee ID # vs. Pay Group and File Number
- File Number lifecycle is very confusing to clients
- Lots of anxiety around impacts of changes on file numbers due to transfers and/or schedule changes
- Clients are excited about killing file numbers
- Rehires and Transfers are huge pain points in their current system
- Clients want the ability to import "batches of changes" to additional Federal Tax options like "Qualified Pension"
- Long discussion around withholding taxes for worked in state based on hours reported on time system for a given location
- Clients wanted to know about "Prenoting" Direct Deposit and whether they should allow the Employees to do it at onboarding and let Payroll Validate - long discussion here
- Deduction Priorities - when net goes negative, there is no controls for Stat Deductions, but Add back order is something client will configure with the implementer
- Mapping of jobcodes to Worker Comp Codes can fall short since certain states worker's comp codes change for the same job
- Question about how to flow data from time to General Ledger without going through Payroll (example, with contracting agencies have the data flow through to reconcile agency invoice and produce productivity metrics)
- Long discussion about Worked In vs. Where the payroll is charged to, (example they have outside sales reps whose "Worked In" location is remote but their time to system constraints in charged to the closest manufacturing plant). They want the "system" to figure out "worked in" tax implications but to flow to the GL for a different department or location.
- As the ADP ICs worked through the existing earning codes like Bonus & Sick pay. There was confusion around "splitting codes" (reporting vs. GL). ADP ICs presented limitations on what is possible to do if Bonuses are combined in to one code in terms of customizing taxability, another limitation for code consolidation is the need for reporting to different GL Accounts and same location/department
- Deductions Client wants to know if it is possible to configure partial deductions at the individual deduction level, ADP IC says it can only be done at Macro Level for all deductions. Client expressed confusion whether this would accomplish their goals
- Liens and Garnishments - Client tried to use the "Portal Search" and got confused with multiple search buttons on page
Liens and Garnishments
Long discussion about the interaction and function around this screen. "Correct or Delete the Data" & "Correct the Effective Date"
This is the name card from the project sponsor. To almost each question the Implementer posed:
"How do you want to......." She responded with "What do you advise? What do other companies like us do? What is Best Practice?" The Implementers were initially reticent to provide "Best Practice" until she just started holding this up on the 2nd day of Payroll Implementation. How do we build a process that leverages the expertise of the Implementer and the tools to support them? Due to Autopay's data structure we are forcing clients to create naming/data conventions that are often not relevant to them or constricting to the point where the conventions are confusing. Examples: Paycode = 3 positions Description = 5 positions Earning Statements = 15 positions on Paycheck Dates = Only 13 HR/Payroll dates can be tracked by system Labor Distribution = Client can only configure 7 labor levels, paygroup is always 1st UX issue
This is throwing an error (in Red) for data missing in a non visible tab. |