JobsiteOn

Sync Invoices with QuickBooks

How invoices sync from JobsiteOn to QuickBooks Online and how payments, refunds and voids sync both ways, including which fields map and how to handle errors.

Ethan Rivera
Written by Ethan RiveraUpdated over a week ago31 min readBeginner

What this guide covers

This guide explains how invoices sync from JobsiteOn to QuickBooks Online and how payments sync both ways. You will learn which invoice fields map to QuickBooks, when the sync triggers, and how to resolve common sync errors.

Before you begin

How invoice sync works

Invoice sync is one-directional: JobsiteOn pushes invoices to QuickBooks. Invoices created in QuickBooks are not pulled into JobsiteOn.

Editing a synced invoice in QuickBooks doesn't change it in JobsiteOn. JobsiteOn stays the source for invoice details, so your next edit in JobsiteOn replaces the QuickBooks version. Payments recorded in QuickBooks still update the invoice balance in JobsiteOn.

JobsiteOn does watch for two QuickBooks changes and tells you about them on the sync errors page:

JobsiteOn field QuickBooks field
Invoice Number Doc Number
Customer Customer Ref
Issue Date Invoice Date
Due Date Due Date
Due Date Terms (see below)
Line Items Line Items
Discount Discount Line
Job site Shipping address
Tax Not sent (QuickBooks calculates it)
Total N/A (calculated)
Status N/A (calculated)

The customer on the QuickBooks invoice is the job's customer contact. If that contact isn't in QuickBooks yet, JobsiteOn sends it first.

The job's property goes to QuickBooks as the invoice's shipping address. QuickBooks automated sales tax charges tax by that address, so field work is taxed where the job is, not at your office address.

The invoice's terms in QuickBooks follow its dates. When the due date is the issue date, or 15, 30, 45, 60 or 90 days after it, the QuickBooks invoice shows the matching term, such as Due on receipt or Net 30. JobsiteOn uses your QuickBooks term with those days. If QuickBooks has none, JobsiteOn adds one named like Net 45. Any other due date goes across as the date alone, so the terms never disagree with the due date. Changing the due date in JobsiteOn updates both in QuickBooks.

Screenshot: A JobsiteOn invoice detail page with an annotation showing which fields map to QuickBooks and a "Synced" badge in the corner.

When invoices sync

Payment sync

Payments sync both ways when Payments sync is turned on for QuickBooks: payments recorded in JobsiteOn go to QuickBooks, and payments recorded in QuickBooks come into JobsiteOn.

JobsiteOn treats a JobsiteOn payment and a QuickBooks payment as the same payment when JobsiteOn sent it to QuickBooks itself (its QuickBooks memo starts with "Recorded in JobsiteOn"), the two are already linked, you chose Same payment for them on the sync errors page, or they plainly match, with no other payment they could be (see "Payment already in QuickBooks" and "Possible duplicate payment" below). When it isn't that clear, JobsiteOn asks you.

From JobsiteOn to QuickBooks

When you record a payment in JobsiteOn, or a customer pays online, JobsiteOn adds the payment in QuickBooks and applies it to the same invoice, so the payment shows on the invoice there too. The payment keeps its date, amount, and reference or check number. If the invoice isn't in QuickBooks yet, JobsiteOn sends the invoice first (when Invoices sync is on).

From QuickBooks to JobsiteOn

When a payment is recorded in QuickBooks against a synced invoice, it comes into JobsiteOn and updates the invoice balance, up to what the JobsiteOn invoice still has open. A credit memo applied to a synced invoice in QuickBooks comes in the same way. If that payment or credit is later voided or deleted in QuickBooks, JobsiteOn takes it off the invoice, and the invoice opens back up with its balance due. Other payments on the invoice aren't touched. On an invoice JobsiteOn took over by number, QuickBooks payments created before it took the invoice over don't come in (see "Invoice taken over by number" above). If the invoice also has a JobsiteOn payment for the same amount that JobsiteOn hasn't sent, see "Possible duplicate payment" below.

For payments first recorded in QuickBooks, later changes to the payment method, reference or check number, memo, and payment date update the same payment in JobsiteOn, even when the amount stays the same. Clearing the reference clears it in JobsiteOn too. Clearing the memo replaces it with a note that the payment came from QuickBooks. If an unapplied credit was matched to your invoice by customer, amount and date, its matching explanation stays in the note when the memo changes. These changes don't create another payment.

JobsiteOn usually hears about these changes within a few minutes. If it misses one, Sync now usually catches it. A delete older than 30 days can't be caught.

When a QuickBooks payment applies more than the JobsiteOn invoice has open, for example because the invoice already shows paid in JobsiteOn, JobsiteOn brings in only what fits, or nothing, and notes the rest. Once the invoice has money owed again, JobsiteOn rechecks that invoice's payments in QuickBooks and brings in what now fits, up to what's owed. The recheck runs right after you answer a possible duplicate, and within a few minutes when the invoice opens up in another way, such as when a payment JobsiteOn brought in from QuickBooks is voided or deleted there. Each backup check and Sync now also rechecks up to 25 invoices that have such a payment and money owed. If a QuickBooks payment still hasn't come in once the JobsiteOn invoice shows money owed, open it in QuickBooks and save it again, and JobsiteOn reads it again. A payment created before JobsiteOn took its invoice over by number stays out.

Note: A payment JobsiteOn sent to QuickBooks is never copied back into JobsiteOn as a second payment. If someone voids or deletes it inside QuickBooks, JobsiteOn keeps it and shows a sync error, so you can decide which side is right. The same goes for lowering it in QuickBooks, moving it to another invoice, or leaving it unapplied as a customer credit: JobsiteOn keeps its amount and shows the sync error "A payment recorded in JobsiteOn was changed in QuickBooks." A QuickBooks payment you linked with Same payment is handled the same way.

Payment recorded in QuickBooks without an invoice

Sometimes a customer's payment is recorded in QuickBooks without picking the invoice it pays, so QuickBooks keeps it as a credit for the customer. JobsiteOn matches it to your invoice on its own when all of this is true:

If there is such a JobsiteOn payment, the QuickBooks payment may be the same money entered twice, so JobsiteOn doesn't put it on another invoice. The sync errors page names the JobsiteOn payment's invoice and asks you to check it in QuickBooks. If that invoice already shows the payment with the memo "Recorded in JobsiteOn", the payment without an invoice is a second copy: void or delete it. If it doesn't, apply the payment to that invoice and JobsiteOn won't send a second copy. When JobsiteOn sends its own payment and finds this one, it applies it itself (see "Payment already in QuickBooks") and the question goes away.

JobsiteOn then marks the invoice paid and applies the payment to the same invoice in QuickBooks, so both show it paid. If QuickBooks shows less open on that invoice than the payment (usually sales tax), JobsiteOn still marks the invoice paid but leaves the payment unapplied in QuickBooks, and the sync errors page asks you to apply it there.

If the payment matches more than one open invoice, JobsiteOn doesn't guess. The sync errors page lists the invoices it could pay. Apply the payment to the right invoice in QuickBooks and JobsiteOn marks that invoice paid on the next sync. A payment you later apply to a different invoice in QuickBooks moves to that invoice in JobsiteOn too.

Possible duplicate payment

Say a payment comes in from QuickBooks on an invoice that also has a JobsiteOn payment for exactly the same amount that JobsiteOn hasn't sent to QuickBooks: 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 guess whether they're one payment recorded in both places or two different payments, such as two equal installments. It shows a warning on the sync errors page and asks you.

The other way around works too: if the same payment is already in QuickBooks when JobsiteOn sends its own (same customer, exactly the same amount on that invoice, dated from 14 days before to 7 days after JobsiteOn's payment), JobsiteOn links to it instead of adding a second payment in QuickBooks (see "Payment already in QuickBooks").

When the match is plain, JobsiteOn answers Same payment for you within a few minutes: the invoice has exactly one such JobsiteOn payment, it was never refunded, it is dated at most 3 days from the QuickBooks payment, and the QuickBooks payment pays only this invoice. The warning then shows as resolved with "Matched automatically". Equal installments recorded further apart still wait for your answer. While the warning is open, the QuickBooks page shows the banner "A QuickBooks payment may be counted twice" with a View sync errors link.

The warning has two buttons instead of Mark Resolved:

Right after either answer, JobsiteOn rechecks the invoice's payments in QuickBooks and brings in any that now fit, such as one it left out while the invoice counted the same money twice.

The warning also resolves itself, with no button to click, when:

When the warning names more than one JobsiteOn payment, it resolves itself only once none of them is still a match.

If the warning no longer applies when you click Same payment or Different payments, for example because JobsiteOn already took the QuickBooks payment off the invoice after a void in QuickBooks, JobsiteOn says so, doesn't change any payment and updates the list.

Animation: An invoice being created in JobsiteOn, syncing to QuickBooks with a progress animation, and then a payment recorded in QuickBooks pulling back into JobsiteOn.

Common sync errors

Invoice total mismatch

JobsiteOn doesn't send tax. QuickBooks works out the tax on the invoice from its own settings and the job site address, so the totals differ when those settings don't match the tax you charge in JobsiteOn. Line item rounding, or a line changed in QuickBooks, can also make them differ.

After each send, and whenever QuickBooks reports a change to the invoice, JobsiteOn compares the two totals. When they differ you see the sync error "An invoice has a different total in QuickBooks." with both amounts, once per difference. Make the totals match: add the tax or line to the JobsiteOn invoice, or correct the invoice in QuickBooks. When the QuickBooks invoice totals less, a payment for the full JobsiteOn amount leaves the difference as a customer credit in QuickBooks (see "More than the QuickBooks invoice has open" above); when it totals more, the difference stays open in QuickBooks.

Invoice voided or deleted in QuickBooks

If someone voids or deletes an invoice in QuickBooks (or removes every line) while it's still open in JobsiteOn, you see the sync error "An invoice was voided or deleted in QuickBooks but is still open in JobsiteOn." JobsiteOn stops sending changes to that invoice so it doesn't undo what was done in QuickBooks.

If the invoice is already cancelled or deleted in JobsiteOn, resolving the warning only clears the warning. It doesn't send the invoice to QuickBooks.

Books closed in QuickBooks

QuickBooks refuses changes dated on or before the closing date set in QuickBooks. JobsiteOn reads that date from QuickBooks and doesn't send an invoice or payment dated on or before it. You see the sync error "QuickBooks books are closed through" the date, "so JobsiteOn didn't send this change." Give the record a date after the closing date in JobsiteOn, or ask your QuickBooks admin to move the closing date, then click Retry. JobsiteOn checks the closing date again before it holds a change back, so a date your admin just moved doesn't block anything.

If QuickBooks refuses a change for its closing date anyway, you see "QuickBooks books are closed for this date, so QuickBooks refused the change." The fix is the same. Neither is retried on its own.

Customer is inactive in QuickBooks

QuickBooks doesn't delete customers. It makes them inactive. If an invoice for an inactive customer fails, make the customer active again in QuickBooks, then click Retry on the failed invoice in the Dead letter queue tab of the sync errors page, or save the invoice again in JobsiteOn.

Duplicate invoice number

JobsiteOn takes over a QuickBooks invoice with the same number only when it's for the same customer and date and isn't linked to another JobsiteOn invoice. It then replaces its details, and payments already on it in QuickBooks don't come into JobsiteOn (see "Invoice taken over by number" above). Any other invoice with that number is left alone and JobsiteOn adds its own. If your QuickBooks company needs unique numbers, you see "QuickBooks already has another transaction with this number." Change the number in JobsiteOn, or the other invoice's number in QuickBooks, then retry.

QuickBooks numbers invoices itself

If Custom transaction numbers is off in QuickBooks, QuickBooks gives invoices its own numbers. JobsiteOn's invoices keep their JobsiteOn numbers, but invoices made in QuickBooks can then get numbers JobsiteOn also uses. JobsiteOn shows the sync warning "QuickBooks numbers invoices itself in this company." In QuickBooks, open Settings > Account and settings > Sales and turn on Custom transaction numbers. JobsiteOn closes the warning when it sees the change.

Tip: Use the sync log to monitor invoice sync status. Check it weekly to catch errors early before they affect your accounting.

Open the record in QuickBooks

In the record's Details panel, choose View in QuickBooks to open its synced copy in a new tab. Sign in to the connected QuickBooks company if asked. The link appears once the record has synced and its connection is still present. It stays hidden in a JobsiteOn sandbox workspace.

Synced payments also have a link in the invoice Details panel, labelled with the payment amount. Opening a link does not record or send a payment.

Did this answer your question?

Related Articles