What you can fix from the Accounting page:

What to fix in LMN, then retry

What to fix in QuickBooks, or reconnect

If any edits or changes are made to the LMN invoice after it has been Synced to QuickBooks Online, you will need to delete that invoice from QuickBooks and Resync the updated version.

To Resync, open an invoice in LMN. Click on More, then click on Resync to QuickBooks

No. QuickBooks Online only.

No. Each LMN account connects to one QuickBooks company. If your Intuit login has several companies, pick the right one when you connect. To switch companies, disconnect first, then connect the other company and complete setup again.

No. You sync invoices and payments manually– automatic sync is coming in Phase II.

No. This creates the record once. Finish the invoice in LMN before you sync it. If a change is made to the LMN invoice after it is synced to QB, we advise you to delete the invoice in QB and resync from LMN.

No. The customer, tax, and class import during setup is a one-time pull so you can map. It is not a live two-way sync.

Any QuickBooks Online plan can connect. Class mapping requires Plus or Advanced.

No. LMN takes the class from each line's cost code and adds it to that line. If QuickBooks assigns one class to each transaction, your invoices still sync, but they won't have a class.

To get classes on synced invoices, go to Settings → Account and settings → Advanced → Categories in QuickBooks. Under Track classes, set Assign classes to One to each row in transaction.

The processing fee line item will only sync to QuickBooks if the payment is already captured on the LMN invoice before you sync and the invoice total updated (current behavior in LMN).

Yes-if Custom Transaction numbers are turned On in QuickBooks. LMN cannot change that setting — Accounting settings only shows whether it is On or Off. If it's Off, QuickBooks assigns its own number and the two will not match.

Yes, if you create and send invoices from LMN. That's how your LMN number becomes the QuickBooks number. Turn it on in QuickBooks, then set your next LMN invoice number above the highest number already in QuickBooks.

Leave it Off only if you regularly create invoices in QuickBooks as well, or you have a long QuickBooks sequence you don't want LMN numbers to use. If you leave it Off, the numbers will not match. If left Off, the LMN invoice number will still appear in QuickBooks but in the “Message on Statement” box on the invoice.

Change the LMN invoice number to one that isn't already in QuickBooks, then retry the sync. Finish the invoice in LMN before you sync, and avoid creating the same number sequence in both systems.

You can, but we don't recommend it on the same number sequence. Two systems assigning the same numbers is what causes duplicate errors. Create and send in LMN, then sync to QuickBooks.

A QuickBooks customer is the client. A sub-customer is a job under that client. The choice is saved on the LMN job, and later invoices for that job go the same way.

Invoices must be approved, and $0 invoices do not sync.

Payments can sync once they are recorded in LMN, including ACH still marked Pending. Card payments are usually paid right away. If the payment is applied to an invoice, that invoice must already be in QuickBooks.

Yes. ACH payments can sync while they're still Pending — you do not need to wait until the status is Success. If the payment is on an invoice, sync that invoice first.

If the ACH payment later fails, QuickBooks is not updated. Use your reject email and adjust the payment in QuickBooks.

Yes. If the LMN payment has no invoice attached, it syncs to QuickBooks as an unapplied payment on the customer.

Full deposit accounting i.e. posting to a liability account and transferring to revenue when the work is billed.

Timesheets and vendor bills do not sync, and switching to the new QuickBooks Online integration turns off the old sync tool for your account. Here's how to handle each one.

Timesheets: LMN never sent payroll codes or overtime to QuickBooks Online timesheets, so pay was always calculated outside the timesheet. Use LMN's payroll reports (the payroll PDF or the Excel payroll report) or the ADP or Paychex export to get hours into your payroll provider. Labor job costing stays in LMN.

Vendor bills: Enter bills directly in QuickBooks so they appear in accounts payable and on your profit and loss. If you job cost materials and subcontractors in LMN, keep entering those bills in LMN with their job allocations as well.

If syncing timesheets or vendor bills is a must-have for your business, tell Support. We want to hear it, and we can switch you back to your previous sync if it isn't working for you.

If you already sync with the old QuickBooks Sync Tool, the new integration is turned on with your QuickBooks connection and links in place.

Only if your account is in the beta. When the new integration is turned on for your account, it replaces the old QuickBooks Sync Tool, and your connection and links carry over. If your account isn't in the beta, your existing sync stays exactly as it is.

When the new QuickBooks Online integration is turned on, Export is replaced by Sync to QuickBooks, and the old QuickBooks Sync Tool is turned off. You no longer queue invoices and then publish them from the Sync Tool. Sync to QuickBooks sends the invoice straight to QuickBooks Online.

Approving an invoice doesn't send it to QuickBooks. Invoices don't sync automatically yet, so once an invoice is approved, sync it one of two ways:

The QB Status shows Syncing while it processes and Synced once the invoice is in QuickBooks Online, which can take up to 30 seconds. If it shows Sync Error, click it to see what went wrong and fix it.

Payments work the same way: on the Payments page, select the payment, click Update Status, then click Sync to QuickBooks.

For step-by-step screenshots, see New QBO: Syncing Invoices & Payments.

Partly. LMN can send invoices to a project that already exists in QuickBooks, because underneath it's a sub-customer. LMN can't create projects, doesn't label them as projects, and in the new integration doesn't send labor or material costs to them.

Create the project in QuickBooks first. Then link the LMN job to it under QuickBooks Settings → Linking → Sub-customers, or choose Sub-customer for that job on the Accounting page when it first syncs. The client has to be linked under Customers before this works. All later invoices for that job go to the project.

No. The sub-customer picker reads live from QuickBooks every time it opens, so the new project shows up right away. The customer import only runs once during setup, so new projects don't become LMN jobsites.

Setup turns every active sub-customer, including projects, into a jobsite under the matching LMN customer. It doesn't create LMN jobs, and it doesn't link any job to a project. Linking is a separate step.

No. "Create new sub-customer" makes a regular sub-customer, never a project. Intuit's standard API doesn't let apps mark a record as a project; only a separate premium Intuit API can create projects, and LMN doesn't use it.

Yes, inside QuickBooks, on Plus or Advanced plans only. Intuit's rules: the sub-customer must be active, sit directly under a top-level customer, have no sub-customers of its own, and have "Bill parent customer" checked. LMN creates sub-customers with that box unchecked, so they'll need to check it first. Watch out for these:

You can find a full list of guidelines for troubleshooting errors here

If the new QuickBooks integration has been turned on and you’d like it turned off, please contact Granum support via chat or email at lmn-support@granum.com.

unbillable-field and unbillable-overhead are LMN's default cost codes, tied to punch-in tasks rather than invoice work. unbillable-field covers tasks like drive time, loading materials, or clean-up, while unbillable-overhead covers non-billable office or administrative costs. Mapping each to a QuickBooks service item determines which income account those costs are recorded against when timesheets sync to QuickBooks. If you aren't sending timesheets to QuickBooks Online, you can leave these two cost codes unmapped.