LMN sync with QuickBooks Desktop fails on permissions and wage items
LMN users syncing into QuickBooks Desktop hit permission errors and payroll wage-item mismatches; the accepted fix covers roles and wage-item mapping.
Landscape contractors running LMN alongside QuickBooks Desktop are hitting two linked failures. The sync either stops on a permissions error before any data moves, or time entries arrive while payroll refuses to post. LMN’s published FAQ for the Desktop integration carries the accepted resolution for both symptoms, and it splits the blame between user roles and wage-item mapping.
Two failure points in the sync
Both failures trace back to the same bridge, the one that carries LMN Time into the company file. On one side sits a QuickBooks user whose role may not cover everything the sync touches. On the other sits the mapping that ties each LMN wage item to a matching wage item in QuickBooks. Break either link and the sync stops.
Checking permissions inside QuickBooks
The first check happens inside the company file. Sign in as the QuickBooks admin, open the Company menu, and choose Users, then Set Up Users and Roles. Select the account that runs the sync and click View Permissions. The permission list shows exactly what that account may touch.
If payroll is missing from that list, the role is the problem. Close the Permissions window, select the user again, and choose Edit. Pick a role from the Available Roles list, add it, and confirm with OK. An account that syncs time and payroll needs a role that covers both. Only the admin can change roles, so have that password ready before you start.
If Windows is the real blocker
Sometimes the QuickBooks permissions come back clean and the sync still fails. That points to the layer underneath: the Windows account. QuickBooks roles govern what a user may do inside the file, but the sync itself runs under a Windows sign-in on that machine. That sign-in needs its own rights to the company file and the folder holding it.
The two systems are separate, which is why a correct role list can coexist with a blocked sync. Test it by signing in to Windows with an administrator account and rerunning the sync. If it completes, either grant the original Windows account access to the file’s location or keep the sync on the admin profile.
The order that saves time
Sequence matters here. Check roles before touching any wage-item mapping, because a payroll-blocked account fails even when the mapping is correct. Once roles pass, fix the mapping in LMN first and the employee records second. Reversing that order tends to produce the same error twice, once for the missing role and once for the unassigned item. That reads like a failed fix when it is really a second cause.
Wage items must line up for payroll to post
Permissions open the door; wage items decide whether payroll actually flows. The documentation names three causes for payroll failures, and the first is familiar: the QuickBooks user lacks payroll rights. That points back to the role steps above. The second is a gap in the mapping, where an LMN wage item is not linked to any QuickBooks wage item at all. The third is the sneakiest: the link exists, but the employee in QuickBooks never had that wage item assigned.
The second and third causes are fixed from both ends. In LMN, open the sync setup for LMN Time and map every wage item to its QuickBooks counterpart. Then in QuickBooks, open the employee record, go to the Payroll Info tab, and add the matching wage item for that person. Until both ends agree, time can cross over while payroll stays broken.
Verifying the fix afterward
After the changes, rerun the sync and spot-check one employee. The wage item should appear in that employee’s payroll info, and a time entry pushed from LMN should post without a permissions prompt. Run a small batch first rather than a full payroll push; a single week of entries exposes any remaining mapping gap quickly.
If the sync runs but one person still fails, that record is where to look. The item is either unassigned there or mapped to a different QuickBooks wage item than the one LMN sends. The rest of the file is healthy at that point, so the correction is local and quick.