ADP Time And Attendance Not Working | Fast Fix Steps

If your punches won’t save, your timecard won’t load, or a supervisor can’t approve hours, work grinds to a halt right now. The good news is that most failures trace back to a short list of causes. Check them in the right order and you’ll stop guessing.

This guide starts with quick checks, then moves into the fixes that live in policies, roles, and devices. You’ll see clear cues for what employees can do on their own and what needs an admin.

Common Reasons A Timecard Stops Loading Or Saving

Time entry tools look simple on the surface. Behind the screen, your account, your role permissions, your device, and your company’s time rules all have to line up. When one piece is out of place, punches can fail to post, approvals can vanish, or pages can spin forever.

Use the table below to match what you see to the fastest check. Then jump to the section that fits your setup.

First Checks That Fix Most Problems In Ten Minutes

Start here even if you suspect an outage. These checks remove common blockers that imitate outages. They’re quick and they help you collect clean details if your team needs to step in.

1. Check for a downtime notice — Scheduled maintenance can block logins and time entry for a short window. Start by checking ADP’s portal downtime message.
2. Try a second sign-in path — Test web if you use the app, or test the app if you use web. A mismatch narrows the cause fast.
3. Switch networks — Move from office Wi-Fi to mobile data or a different network. Saves can fail when a firewall blocks page calls.
4. Open a private window — If the timecard loads there, old cookies or cached scripts are the likely culprit.
5. Restart the session — Sign out, close the tab, then sign back in and open the timecard again.

If you’ve had a few failed logins, pause before trying again. ADP may lock the account and trigger an identity check, which can look like a timecard outage. Close browser windows, clear cache, then sign in once and follow any activation-code or security-question prompts on screen. If the prompt never arrives, ask your admin to reset the account rather than retrying.

If the problem clears after any step above, stop there and punch once as a test. If it returns, keep going so you can remove the root cause.

ADP Time And Attendance Not Working On Mobile Or Desktop

This section covers the “it works on one device but not the other” pattern. Treat web and mobile as two separate clients that connect to the same account. Your job is to get both clients loading cleanly with fresh site data and a current app build.

Browser fixes for Workforce Now and similar portals

If you’re on desktop and the timecard is blank, slow, or won’t save, start with the browser. ADP’s login help pages point users to clearing browser history and cache when sign-in loops or errors show up.

• Clear site data for ADP pages — Remove cookies and cached files for the ADP domain, then restart the browser. See ADP’s cache-clear guidance here: ADP Workforce Now login and help.
• Allow cookies and pop-ups — Approval flows can open in a new window. If pop-ups are blocked, a button may seem dead.
• Pause extensions for a test — Script blockers can stop the timecard page from loading its widgets. Turn them off for the ADP site only, then reload.
• Try a second browser — If Chrome fails, test Edge or Firefox to rule out a browser-only issue.

Mobile fixes for the ADP app

If you can’t punch in the app, or the timecard view never updates, treat it like any work app that depends on permissions, OS versions, and clean local storage. App stores list the required OS versions for the current build.

1. Update the app and your phone OS — Install the latest ADP Mobile update, then check the listing for required OS versions: Apple App Store listing.
2. Force close and reopen — A stuck session often clears with a full close, not just backing out of the screen.
3. Reset the app storage — On Android, clear cache and storage. On iPhone, reinstalling resets local files.
4. Turn on location services — If your employer uses geofencing, location permission must be enabled or the punch may fail.
5. Set time to automatic — Wrong device time can break sign-in tokens and cause loops.

Once mobile and desktop both load cleanly, try one punch or one edit, then refresh the timecard view. If you still see ADP time and attendance not working after these steps, the cause is often inside approvals, locks, or access rules.

Fixing Missing Punches And Timecard Math That Looks Wrong

Some failures don’t look like a crash. The timecard loads, but a punch is missing, totals look off, or a meal break never applied. These issues are often tied to pay period view, rounding rules, schedules, or approvals that haven’t posted yet.

Start with the simplest data checks

• Confirm the pay period view — Make sure you’re looking at the right week. It’s easy to edit last week while expecting today’s punch to show.
• Refresh after a short delay — Some setups post punches from a clock to the timecard after a brief delay.
• Check for an exception banner — Missed punches or long meals can trigger an exception that blocks approval until it’s fixed.

If you use a physical time clock

If a wall clock or badge reader is the entry point, the clock itself can be the bottleneck. ADP’s timekeeping FAQ for some clock setups recommends a power-cycle restart and a short wait before rechecking the timecard.

1. Reboot the clock — Unplug the clock power, plug it back in, then wait 10-15 minutes before you recheck the timecard: ADP Time and Attendance run FAQs.
2. Test one punch after reboot — Have one person punch once, then check whether that test punch appears.
3. Record the clock details — Note the clock ID and location so your admin can file a precise request.

When approvals or locks hide your edits

In many setups, a supervisor approval locks a timecard. An employee may still see the page, but edits won’t post. A payroll close can also lock a prior period. If you can view but can’t change, you’re likely hitting a lock rule.

• Check whether the day is approved — If it’s approved, the manager may need to unapprove, edit, then approve again.
• Look for a submitted status — If you submitted your timecard, it may need to be returned to you for edits.
• Confirm which edits are allowed — Some policies allow punches only, while pay code edits require a manager.

Role And Policy Settings That Block Time Entry

If the same failure hits multiple people, or if only managers see the missing feature, look at access and policy rules. This is where a lot of “button does nothing” reports come from. The screen is visible, but the role behind it can’t run the action.

Access permissions and security groups

ADP products use role-based access. Admins grant features through security groups or access permissions. If a person can’t see the right timecard tab, can’t approve, or can’t run time reports, permissions are the first place to check.

• Confirm the user’s role — Check whether the user is in the correct security group for time features. ADP’s portal admin guide explains how security groups control feature access: ADP Workforce Now portal administrator guide (PDF).
• Grant timecard access explicitly — In some deployments, admins manage access via Time & Attendance setup screens. A permissions guide shows the “Setup > Security > Access Permissions” path used in certain setups: Managing user access permissions (PDF).
• Test with a known-good account — Sign in with an admin or supervisor who can approve time. If it works there, it’s a permission issue.

Geofencing, device rules, and punch restrictions

Many employers restrict punching to a job site, a Wi-Fi network, or a registered device. When those rules fire, you might see a generic error or a punch that never posts. The fix is often turning on location, moving into the allowed area, or switching to the approved method.

1. Check location permission — On mobile, set the ADP app to allow location while using the app, then retry.
2. Confirm you’re in the allowed zone — If your company uses a geofence, step inside the perimeter before punching.
3. Use the fallback method — If mobile punching is blocked, use the on-site clock or the web portal if those methods are allowed.

Escalation Checklist For Fast Resolution With Your Team

If you’ve cleaned up the device, verified the pay period, and checked role access, you can send your admin a clean report instead of “it’s broken.” That shortens the back-and-forth and keeps payroll on track.

Gather these details before you message payroll, HR, or your time administrator. Keep it factual and complete.

• Capture the exact error text — Copy the message or take a screenshot, including the time and date.
• Write down the device and browser — Include phone model and OS version, or desktop browser name and version.
• Note the entry method — Say whether you punched via mobile, web, kiosk, or physical clock.
• List the affected dates — Include the pay period and the specific day that failed.
• Record what you already tried — Mention network switch, private window test, cache clear, reinstall, or clock reboot.

If a maintenance notice is active, wait until the window ends and try again. You can check ADP’s portal downtime message here: ADP portal downtime notice.

Last step: if you’re a manager and approvals are due, approve from a desktop browser if the app is stuck, or approve from the app if the browser page won’t load. Cross-testing like that often gets you through the deadline while the root cause is fixed.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback