What this guide covers
This guide provides solutions for the most common QuickBooks integration
problems. Use this as a reference when you encounter sync errors,
connection issues, or unexpected behavior.
The QuickBooks page is at Settings > Marketplace > QuickBooks
Online > Manage integration. From there, View log opens the sync
log, and the sync errors page is at
/settings/marketplace/quickbooks/manage/errors. Whenever a sync error is
open, the QuickBooks page shows a banner with a View sync errors link
to that page. It reads "A QuickBooks payment may be counted twice" when a
possible duplicate payment is waiting for your answer.
Connection issues
Cause: Only owners and admins can connect QuickBooks.
Fix: Ask an owner or admin to connect it. Other team members see
Ask owner/admin on the Marketplace page.
"Access denied" during authorization
Cause: Your QuickBooks account does not have admin permissions.
Fix: Sign in with a QuickBooks admin account or ask your QuickBooks
admin to authorize the connection.
QuickBooks asks you to reconnect
Cause: Your QuickBooks sign-in stopped working. JobsiteOn renews it
every hour, and QuickBooks refused the renewal, for example because
someone disconnected JobsiteOn inside QuickBooks. Nothing syncs until you
sign in again.
Fix: Open the QuickBooks page. A red banner reads "Reconnect
QuickBooks to start syncing again." Click Reconnect QuickBooks and sign
in to the same QuickBooks company. Your sync settings and synced records
stay as they are. After you reconnect, JobsiteOn sends the contacts,
pricebook items and invoices that never reached QuickBooks, and the
payments recorded, refunded or deleted while syncing was stopped. Edits
made in the meantime to contacts and invoices that are already in
QuickBooks go out the next time you change them.
Screenshot: The QuickBooks page showing the red "Reconnect QuickBooks to start syncing again" banner with a Reconnect QuickBooks button.
QuickBooks shows "QuickBooks sync is paused"
Cause: JobsiteOn's nightly connection check failed for your
QuickBooks company, for example because QuickBooks rejected the saved
sign-in, so it paused syncing instead of sending changes that would fail.
A network hiccup, a timeout or a QuickBooks outage doesn't cause this.
Those are noted and syncing keeps going.
Fix: On the QuickBooks page, click Try again. JobsiteOn checks the
connection again and starts a sync as soon as the check passes. If it
still fails, click Reconnect QuickBooks. JobsiteOn also rechecks paused
connections every night and turns syncing back on by itself once the check
passes. Either way, payments recorded, refunded or deleted while syncing
was paused go to QuickBooks once it's back on, if their invoice is already
there. Try again runs a full Sync now, which also sends records
that never reached QuickBooks.
"Your last sync finished with problems"
Cause: One step of a Sync now run didn't finish, for example
because QuickBooks was slow to answer. Syncing stays on. A single failed
step never pauses the connection.
Fix: Click View sync errors on the QuickBooks page to see which
step failed, then click Sync now to run it again. The message goes away after the next Sync
now in which every step finishes, or when you reconnect QuickBooks. The
regular two-minute sends and the daily check don't clear it. If a
scheduled check was bringing in QuickBooks payments at the moment you
clicked Sync now, Sync now leaves the payment step and the check for
other QuickBooks changes to it. That isn't a failure, but it doesn't
clear the message either, so click Sync now again a little later.
Sync failures
Invoices are not appearing in QuickBooks
- Check that Invoices is turned on under Sync settings on the
QuickBooks page.
- Check the sync log for a failure on that invoice.
- Click Sync now. It resends invoices that never reached QuickBooks,
except drafts and cancelled invoices. A draft goes again the next time
you save it.
- If the log shows a problem with the invoice's customer, check that the
customer is active in QuickBooks.
Cause: When JobsiteOn sent the contact, QuickBooks had no customer with
the same email address or with the display name JobsiteOn gives it (such
as "Acme Roofing (Dana Lee)"), so JobsiteOn added a new customer.
Fix: Use the same email address in both systems so future contacts
match. The contact stays linked to the customer JobsiteOn added, so
contact support before you merge the two customers in QuickBooks.
Payment not syncing back to JobsiteOn
- Verify the payment in QuickBooks is applied to an invoice that came
from JobsiteOn. Payments on invoices created only in QuickBooks don't
come in.
- Check that Payments sync is turned on for QuickBooks.
- A payment comes in only up to what the JobsiteOn invoice still has
open. If JobsiteOn already shows the invoice paid in full, it isn't
brought in, which is right when it's the same payment as one recorded
in JobsiteOn. When that JobsiteOn payment hasn't been sent to
QuickBooks, JobsiteOn asks you instead (see "A QuickBooks payment may
already be recorded in JobsiteOn" below). Otherwise JobsiteOn brings
the QuickBooks payment in, up to what's owed, once the invoice has
money owed again. If it still hasn't come in by then, open the payment
in QuickBooks and save it again, and JobsiteOn reads it again.
- On an invoice JobsiteOn took over because QuickBooks already had its
number, a QuickBooks payment created before JobsiteOn took the invoice
over doesn't come in. Only later ones do. See "Invoice taken over by
number" in
Sync Invoices with QuickBooks.
- Give it a few minutes. QuickBooks usually tells JobsiteOn about a new
payment right away. If JobsiteOn couldn't apply it, it keeps trying for
more than a day, and the daily check catches anything missed. A change
it gave up on shows as an Inbound row on the Dead letter queue
tab of the sync errors page. Click Retry there to start its tries
over.
- Click Sync now if you need it immediately.
A payment recorded in JobsiteOn isn't in QuickBooks
- Check that Payments sync is turned on for QuickBooks.
- JobsiteOn sends a payment when it was recorded while Payments sync
was on, when JobsiteOn itself added its invoice to QuickBooks after
Payments sync last started, or when you chose Different payments
for it on a possible duplicate. There's one more case for an invoice
JobsiteOn added during the previous time Payments sync was on. Any
other payment, such as one recorded before you first connected, or
while Payments sync was off or QuickBooks was disconnected, isn't sent,
and the sync errors show "Payments recorded before Payments sync was
turned on were not sent to QuickBooks." You can record that payment in
QuickBooks yourself, for the same amount on the same invoice. If the
JobsiteOn invoice still shows money owed, JobsiteOn brings it in and
shows "A payment imported from QuickBooks may already be recorded in
JobsiteOn." If the invoice already shows paid in full, JobsiteOn
doesn't bring it in and shows "A payment recorded in QuickBooks may
already be recorded in JobsiteOn." instead. Either way, click Same
payment on that error and pick your JobsiteOn payment, so each
system counts it once and later refunds reach QuickBooks. See "Which payments go to QuickBooks" and "Possible
duplicate payment" in
Sync Invoices with QuickBooks.
- The invoice has to be in QuickBooks. JobsiteOn sends it first when
Invoices sync is on. With invoice sync off, the payment waits until
the invoice reaches QuickBooks.
- Online payments go over once they clear. A payment under dispute
waits until the dispute is decided.
- If QuickBooks sync was paused or needed reconnecting when the payment
was recorded, it goes over once syncing is back on, or when you click
Sync now.
- Check the sync log for an error on that payment, then click
Sync now.
A payment from JobsiteOn shows as a credit in QuickBooks
Cause: The QuickBooks invoice had less open than the payment. JobsiteOn
records the whole payment in QuickBooks, applies only what the invoice has
open there, and leaves the rest as a credit for the customer. This usually
happens because JobsiteOn doesn't send tax and QuickBooks worked out a
lower total, or because the payment had already been entered in
QuickBooks by hand. It can also happen after you choose Different
payments on a possible duplicate, when the QuickBooks payment had
already paid that part of the invoice there. The sync errors show "A
payment recorded in JobsiteOn was more than the invoice had open in
QuickBooks." Its hint points to a lower invoice total in QuickBooks,
unless JobsiteOn sent the payment because you chose Different
payments. Then the hint says so and that the credit is expected when
the customer paid twice.
Fix: Check the invoice and its payments in QuickBooks. If you chose
Different payments, the customer paid twice: refund the credit in
QuickBooks or apply it to another invoice for that customer, and don't
raise the invoice total to use it up. If the payment had also been
entered by hand, void or delete that one, not the one JobsiteOn sent.
JobsiteOn's payment is already in QuickBooks, so there's nothing to
answer on the sync errors page for it. If the QuickBooks invoice should
match JobsiteOn, correct it there. Then apply the customer's credit to
the invoice. JobsiteOn keeps credit you apply by hand when it later
updates the payment. To avoid this, record each payment in one place.
JobsiteOn never links a payment already entered in QuickBooks to its own
just because the amounts match, not even on an invoice it took over by
number. See
"Invoice taken over by number" in
Sync Invoices with QuickBooks.
A payment counts twice
Cause: The same payment was recorded in JobsiteOn and entered by hand
in QuickBooks. JobsiteOn never decides on its own that two payments are
the same because they have the same amount or date.
- JobsiteOn hadn't sent its payment: when the amounts match, the sync
errors show a possible duplicate warning, and the QuickBooks page shows
a banner. If JobsiteOn brought in the payment entered in QuickBooks, it
counts twice in JobsiteOn until you answer ("A payment imported from
QuickBooks may already be recorded in JobsiteOn."). If the JobsiteOn
invoice already showed paid in full, JobsiteOn didn't bring it in, but
QuickBooks would count the money twice if JobsiteOn sent its payment
too ("A payment recorded in QuickBooks may already be recorded in
JobsiteOn.").
Fix: Click Same payment on that error, as described in the next
section.
- JobsiteOn had sent its payment: both payments are in QuickBooks,
and no possible duplicate warning shows. When the QuickBooks invoice
still had enough open, JobsiteOn's payment was applied to it in full.
Otherwise part or all of it was left as a customer credit, with the sync
error "A payment recorded in JobsiteOn was more than the invoice had
open in QuickBooks." The payment entered in QuickBooks can also come
into JobsiteOn whenever the JobsiteOn invoice has money owed. This also
happens when JobsiteOn sends its payment before you answer a possible
duplicate warning, which then resolves itself.
Fix: JobsiteOn's payment is already in QuickBooks, so the fix is in
QuickBooks, not on the sync errors page. Void or delete the payment you
entered by hand, not the one JobsiteOn sent. The one JobsiteOn sent has a memo that
starts with "Recorded in JobsiteOn". If JobsiteOn brought the other
payment in, it takes it off the invoice too. If part or all of
JobsiteOn's payment was left as a customer credit, apply that credit to
the invoice in QuickBooks, because voiding the other payment doesn't do
that. Then check that the invoice shows the same amount owed in both
systems.
A QuickBooks payment may already be recorded in JobsiteOn
Cause: A QuickBooks payment landed on an invoice that also has a
JobsiteOn payment for exactly the same amount that JobsiteOn never sent
to QuickBooks, such as one held back because of when it was recorded,
one waiting to go, one QuickBooks turned down, or one whose send
QuickBooks never confirmed. JobsiteOn doesn't match payments by amount on
its own, so it doesn't know whether they're one payment recorded in both
places or two different payments, such as two equal installments. The
QuickBooks page shows the banner "A QuickBooks payment may be counted
twice", and the sync errors show one of these:
- "A payment imported from QuickBooks may already be recorded in
JobsiteOn." JobsiteOn brought the QuickBooks payment in, and until you
decide, it counts both.
- "A payment recorded in QuickBooks may already be recorded in
JobsiteOn." The JobsiteOn invoice already showed paid in full, so
JobsiteOn didn't bring the QuickBooks payment in. If JobsiteOn sent its
own payment too, QuickBooks would count the money twice.
The error names both payments and shows once for each QuickBooks payment
and invoice. It shows only when the JobsiteOn payment has cleared. A
partly refunded JobsiteOn payment matches on its original amount or on
what's left after the refund, and one refunded in full never matches.
Fix: On the sync errors page, the error has two buttons instead of
Mark Resolved:
- Same payment, if they're one payment: pick your JobsiteOn payment in
the Match the QuickBooks payment window, then click Link
payments. JobsiteOn reads the QuickBooks payment in QuickBooks, links
it to your payment and removes the copy it brought in, if there is one,
so JobsiteOn and QuickBooks each count the payment once. After that,
JobsiteOn handles refunds of your payment like those of any payment it
sent to QuickBooks. If the QuickBooks payment also pays other invoices
or leaves a credit, JobsiteOn can't link it: it shows a message and
changes nothing. Change the payment in QuickBooks so it pays only this
invoice and click Same payment again, or choose Different
payments.
- Different payments, if they're two payments. JobsiteOn sends the
JobsiteOn payments the warning names to QuickBooks too. If it brought
the QuickBooks payment in, confirm with Keep both, and the copy
stays in JobsiteOn. If it didn't, confirm with Different payments,
and the QuickBooks payment stays out of JobsiteOn while the invoice
shows paid in full. One that another open possible duplicate on the
same invoice also names waits until that warning is answered or
resolves itself. A message names the payments JobsiteOn is sending.
The error resolves itself if the QuickBooks payment is voided, deleted or
taken off the invoice in QuickBooks, or if the JobsiteOn payment is
refunded in full or reaches QuickBooks first. See "Possible duplicate
payment" in
Sync Invoices with QuickBooks.
Sync errors about payments JobsiteOn sends
- "Payments recorded before Payments sync was turned on were not sent to
QuickBooks." JobsiteOn doesn't send a payment recorded before you
first connected, or while Payments sync was off or QuickBooks was
disconnected, apart from the exceptions under "Which payments go to
QuickBooks" in
Sync Invoices with QuickBooks,
such as a payment on an invoice JobsiteOn itself added to QuickBooks
after Payments sync last started, or one you chose Different
payments for. That way a payment you already entered in QuickBooks
isn't recorded twice. Later changes to those payments, such as refunds,
aren't sent either. If one of those payments is missing in QuickBooks,
you can record it there for the same amount on the same invoice. If the
JobsiteOn invoice still shows money owed, JobsiteOn brings it in and
flags it as a possible duplicate: click Same payment (see the
section above). If the JobsiteOn invoice already shows paid in full,
JobsiteOn doesn't bring it in, but still flags it as a possible
duplicate, and Same payment links the two the same way. If Payments
sync starts again later and more payments are left out, JobsiteOn marks
this error resolved and shows a new one.
- "A payment change was not sent because QuickBooks applies part of
that payment to other invoices." Someone applied part of the payment
to other invoices in QuickBooks, and a change such as a partial refund
would leave the payment smaller than what it applies there. JobsiteOn
changes nothing in QuickBooks. Lower what the payment applies to other
invoices to the amount the error names, then click Sync now.
- "A payment JobsiteOn started to send may be in QuickBooks." QuickBooks
didn't confirm an earlier send of the payment, and the payment was then
deleted, refunded or returned in JobsiteOn, whether or not its invoice
was cancelled since. JobsiteOn usually finds such
a send in QuickBooks and voids it by itself. It shows this error only
when it can't look it up. In QuickBooks, look for a payment whose memo
ends with the code the error names, such as
[jsp:...], and void it if
you find one.
A refund in JobsiteOn didn't change QuickBooks
Cause: JobsiteOn doesn't add refunds to QuickBooks. It only changes
the QuickBooks payment, and when you refund part or all of a payment on an
invoice that was paid in full, JobsiteOn keeps the invoice settled, so the
QuickBooks payment stays as it is and the invoice stays paid there too.
The sync errors show "A refund recorded in JobsiteOn was not sent to
QuickBooks."
Fix: Record the refund in QuickBooks yourself, for example as a refund
receipt. Don't void or delete the payment in QuickBooks instead: JobsiteOn
still counts it toward the settled invoice, so it shows a sync error
saying the payment was voided or deleted in QuickBooks (for example, "A
payment recorded in JobsiteOn was voided in QuickBooks.") and doesn't send
the payment again. A
refund on an invoice that was only partly paid is different: the balance
opens again in JobsiteOn, and JobsiteOn lowers or voids the QuickBooks
payment to match. If part of that payment was applied to other invoices
in QuickBooks, see "A payment change was not sent because QuickBooks
applies part of that payment to other invoices." above.
A payment voided, deleted or changed in QuickBooks still shows in JobsiteOn
- Recorded in QuickBooks: a void or delete takes it off the invoice
within a few minutes and the invoice opens back up, and a new amount or
invoice comes into JobsiteOn the same way. Click Sync now if it
hasn't happened yet. A delete older than 30 days can't be caught this
way.
- Sent from JobsiteOn: JobsiteOn keeps it and shows a sync error,
because it can't tell whether the money came in. If it did, record the
payment again in QuickBooks. If it didn't, contact support to correct
the payment in JobsiteOn.
- Sent from JobsiteOn and changed in QuickBooks: if someone lowers
the payment in QuickBooks, moves it to another invoice, or leaves it
unapplied as a customer credit, JobsiteOn keeps its amount and shows the
sync error "A payment recorded in JobsiteOn was changed in QuickBooks."
If the payment is right in JobsiteOn, apply it to the invoice again in
QuickBooks. If QuickBooks is right, contact support to correct the
payment in JobsiteOn.
Sync errors about payment changes from QuickBooks
A check here is a Sync now or a scheduled backup check.
- "Some payments deleted in QuickBooks may still count in JobsiteOn."
1,000 or more payments changed in QuickBooks in the dates the error
names, and one check lists at most 1,000. JobsiteOn still read every
payment that exists in QuickBooks, but a payment deleted in that time
comes off in JobsiteOn only if QuickBooks sent its delete notice. If you
deleted payments in QuickBooks then, check that their invoices show the
same amount owed in both systems. When some deletes in those dates also
couldn't be applied, JobsiteOn first reads the same dates again on up
to 2 more checks, and shows this error once, when it moves on.
- "Some payment changes from QuickBooks could not be applied in
JobsiteOn." JobsiteOn tried some payment changes again on later
checks and then moved on. It tries a payment that still exists in
QuickBooks again on each check and usually gives up on it after 3 tries
in a row. When 1,000 or more payments changed in QuickBooks, one check
can try it twice. A delete of a payment in QuickBooks that couldn't be
applied is given up after 3 checks in a row. If a change goes through on
a later try, no error shows. The error names the QuickBooks payments JobsiteOn
gave up on, up to 10 of them, plus how many more. Check that their
invoices show the same amount owed in both systems. Saving a payment
again in QuickBooks sends its change again. Contact support if this
keeps happening.
A customer or item added in QuickBooks isn't in JobsiteOn
- Check that Customers (or Products & services) sync is turned
on for QuickBooks.
- Inactive customers and items aren't brought in, and neither are
QuickBooks category or bundle items.
- It may have been linked to an existing record instead: a customer with
the same email address or the same first and last name as one
unlinked contact, or an item with the same SKU or name as one unlinked
pricebook item.
- Click Sync now to check QuickBooks right away.
Cause: The record was also edited in JobsiteOn, and the JobsiteOn
edit is newer. The most recent edit wins, so JobsiteOn keeps its version.
A contact's newer version then goes to QuickBooks. A pricebook item's
doesn't, because JobsiteOn doesn't send later item edits.
- A field left blank in QuickBooks never erases a value in JobsiteOn.
- A company name changed in QuickBooks doesn't move the contact to a
different company.
- An edit to another field of the customer in QuickBooks doesn't replace
an address you changed in JobsiteOn. There's one exception, mostly for
contacts last synced by an older version of JobsiteOn. See "Address
changes" in
Sync Contacts with QuickBooks.
- Edits to synced invoices in QuickBooks don't change the JobsiteOn
invoice.
Fix: Make the change in JobsiteOn, or edit it again in QuickBooks.
A pricebook change didn't reach QuickBooks
Cause: JobsiteOn sends a pricebook item to QuickBooks only while it
isn't there yet, when you connect, reconnect or click Sync now. Edits to an item
that's already in QuickBooks, including archiving it, aren't sent.
Services and parts you create with New item are kept apart from the
main pricebook list and don't go to QuickBooks.
Fix: Make the same change in QuickBooks. It then comes back into
JobsiteOn.
Animation: Opening the sync errors page, switching to the Dead letter queue tab, and clicking Retry on a failed invoice that then goes through.
Data issues
Invoice totals do not match
Cause: JobsiteOn doesn't send tax. QuickBooks works out the tax on each
invoice from its own tax settings.
Fix: Compare the line items and the tax on both invoices. Make sure
the customer's tax settings in QuickBooks match the tax rates you charge
in JobsiteOn. When the QuickBooks invoice totals less, a JobsiteOn payment
for the full amount leaves the difference as a customer credit in
QuickBooks (see "A payment from JobsiteOn shows as a credit in QuickBooks"
above).
Item names are cut short in QuickBooks
Cause: QuickBooks allows 100 characters in an item name. JobsiteOn
sends the first 97 characters plus "..." and keeps the full name in
JobsiteOn.
Fix: Shorten the item name if you want the full name in QuickBooks.
Pricebook items have the wrong type in QuickBooks
Cause: The types don't line up one to one. JobsiteOn sends services
as Service items and every other type (labor, materials, parts,
equipment, fees, bundles) as NonInventory items. There's no setting to change this.
Fix: Change the item type in QuickBooks if you need a different one.
Sync is slow
Cause: JobsiteOn sends about 100 changes every two minutes, and at
most 2,000 existing contacts, items and invoices of each kind per
Sync now, connect or reconnect.
Fix: This is normal during the first sync or after bulk changes. For
large lists, click Sync now again once the first batch is in
QuickBooks.
Sync log shows "Rate limit exceeded" errors
Cause: QuickBooks limits how many requests an app can make each
minute.
Fix: JobsiteOn stays under that limit and retries changes that run
into it. If a change still fails, it moves to the Dead letter queue
tab of the sync errors page. Click Retry there.
Contact support@jobsiteon.com if:
- Errors persist after following the troubleshooting steps above.
- The sync log shows errors you do not recognize.
- Data is missing or corrupted after a sync.
Include the error timestamp, entity type, and sync log details in your
support request.
Tip: Before contacting support, check the QuickBooks page for a
banner. If it shows Reconnect QuickBooks or Try again, use that
first.
Related articles