Payroll troubleshooting — common errors, fixes, and FAQs

Most Payroll issues in Easedesk fall into one of these five buckets. Identifying the bucket usually solves the issue in under 2 minutes:

These are the specific errors that Payroll module users hit most often, along with the cause and the fix:

Two possible causes. First, your role may not have the payroll.view permission. Your Owner or Admin can grant it under Settings → Users & Roles → select your role → Permissions tab → tick payroll.view.

Second, the Payroll module may be disabled at the tenant level. Owners can re-enable it under Settings → Modules. Disabled modules retain all their data — re-enabling instantly restores access.

As a quick test, ask another user with full access to open the same workspace. If they see Payroll in their sidebar, the issue is permission; if they don't, the module itself is disabled.

Most likely the Department Switcher at the top of the navbar is set to a specific department, and the records you created are scoped to a different one. Switch the selector to "All departments" (if your role allows) to see everything.

Other less common causes: an active filter on the list view (look for a "Filters: 1 applied" pill above the list and click Clear), a date-range filter that excludes recent records, or a status filter hiding draft / cancelled records.

If the list is genuinely empty (you confirmed no filters), check Audit Log → Payroll → Created — it shows every payslip created in the workspace regardless of your scope.

Each action in the Payroll module (view, create, edit, delete, approve, export) is checked separately by the API. The error message names the exact permission missing — for example, "Missing permission: payroll.export".

Your Owner or Admin can grant the missing permission in Settings → Users & Roles → select your role → Permissions tab → tick the specific action. Changes take effect on your next page load.

If you should already have the permission but you're still getting the error, sign out and back in to refresh your session token — permissions are cached in the JWT until expiry.

When Easedesk deploys a new version, your browser may have stale client-side JavaScript cached from the previous version. The fix is a hard-refresh:

On Windows / Linux: Ctrl + Shift + R

On Mac: Cmd + Shift + R

If a hard-refresh doesn't help, sign out and sign back in — this clears your session cookies and forces a fresh authentication handshake. Deploys also occasionally invalidate active sessions; this is normal and intentional.

If you still see issues after both steps, the problem is likely not deploy-related. Open the browser console (F12 → Console tab) and check for any red errors — these usually point to a more specific cause.

Easedesk runs some automations on a cron schedule rather than synchronously — for example, recurring invoices, scheduled reports, reminder emails, and IRP/EWB retries. The cron runs every 5 minutes by default.

If you've just created a payslip and expected an automation to fire, wait 5-10 minutes and check the Audit Log. If still nothing, the source record may be missing a required field that the automation depends on — re-open it and verify all relevant fields are populated.

For real-time automations (auto-journal posting, notifications), the trigger happens instantly. If those don't fire, check Settings → Modules — the dependent module may be disabled.

Three common causes for wrong report totals:

1. Department filter active — many reports inherit the Department Switcher. Switch to "All departments" and re-run.

2. Date-range mismatch — financial reports default to current fiscal year. If you expected last year's data, change the date range.

3. Draft records excluded — most reports show only finalised records by default. Drafts and cancelled records have a separate toggle.

If totals are off by a specific number that doesn't reconcile easily, raise a support ticket with the report URL, the expected total, and 1-2 example records that you believe should be included.

Easedesk's median page load is under 1 second on broadband. Slow loads are usually one of: a very large list view (> 5,000 rows), poor network on your end, a heavy report running in the background, or an ongoing incident on our side.

Quick fixes: apply filters to narrow the list view (date range, status, department), close other Easedesk tabs (each tab keeps a websocket open), and check status.easedesk.com for live incidents.

If the slowness is specific to a single report or page, raise a support ticket — we can profile the query and optimise.

Easedesk is fully responsive, but some workflows are easier on a desktop — long forms with many fields (employee onboarding, BOM creation, GST return preparation) and large list views.

On mobile, use search and filters aggressively to keep lists short. The bottom-sticky action bar shows the most-used buttons; tap the kebab menu (•••) for less-used actions.

If the mobile UI breaks (zoom-stuck or unreadable text), rotate the device, force-close the browser, and re-open. Easedesk does not yet have a native mobile app — the web app is the canonical experience.

If none of the above resolves your issue, use these escalation paths in order:

1. AI Assistant (fastest) — click the violet brain icon in the navbar. It has context about your tenant data, can read your settings, and can walk you through diagnostics conversationally.

2. In-app support chat — click the help button at the bottom-right. Median response time is under 4 hours during Indian business hours.

3. Email support@easedesk.com — for issues that need long descriptions, screenshots, or attachments. We respond within 1 business day.

Always include: your workspace slug (the bit after /t/ in the URL), the specific error message, the exact steps to reproduce, and which browser + OS you're using.