JobTread QuickBooks integration: setup and sync fixes

The official JobTread QuickBooks Online integration page lists customers and locations mapped to customers; jobs to customers/projects or classes; invoices and invoice payments; vendors, vendor bills and bill payments; expenses; and cost codes mapped to products/services. It also lists users mapped to employees, time entries to time activities, customer credits/refunds, vendor credits/refunds, and attachments/files.

That list is not a promise that every object moves identically or in both directions. Verify direction, supported edits, required fields, eligibility, and attachment behavior for the records you actually use. Approval, finalization, and sync settings can vary. Use the current interface and support guidance rather than following an assumed sequence of clicks.

Confirm the intended QuickBooks Online company, authorized connection owner, and people allowed to change mappings. Write down which system creates customers, invoices, payments, vendors, and bills. Note any other connected apps that might create the same transactions. Choose a quiet test window and protect closed accounting periods.

With your bookkeeper, review active accounts, tax treatment, opening balances, outstanding invoices, unpaid bills, and existing duplicates. Keep a dated record of settings and test results. Use the JobTread setup checklist for broader readiness; connecting accounting should follow those decisions, not substitute for them.

Compare existing customers, locations, jobs, and vendors across both systems. Names alone are weak evidence: one homeowner may have several properties, and one commercial customer may have several projects. Inspect record IDs, addresses, parent relationships, and transaction history before deciding whether two entries represent the same thing.

Record confirmed matches in a working log. Resolve ambiguous matches through the supported linking process or support, not a bulk import. For a remodeler, distinguish the homeowner from the kitchen project; for a landscaper, distinguish the property manager from each site. Neither example establishes a universal customer structure.

Trace each test cost code to its QBO product/service, then review that item’s income and expense accounts with the bookkeeper. A correct display name does not prove correct accounting. Check inactive items, similarly named products, and whether the intended item fits the transaction. There is no universal chart of accounts or tax treatment suitable for every contractor.

Confirm how jobs will be represented using the supported customer/project or class mapping. Then verify the account selected for customer payments and the accounts used for vendor payments or expenses. Ask whether receipts should pass through an undeposited-funds workflow or another approved account. Document the choice instead of guessing from a default.

Use an approved test approach with your bookkeeper; do not create pretend live revenue just to exercise the connection. Choose one eligible job with simple, understood lines. Check the customer, job mapping, cost codes, quantities, tax treatment, dates, and total before allowing its invoice to transfer.

Inspect the destination invoice and record its ID. Process one legitimate customer payment through the agreed entry point, then verify its invoice allocation, amount, date, and receiving account in both systems. Separately test a vendor bill with a known vendor, reference, cost allocation, and amount. Confirm the destination bill before considering payment.

An HVAC service invoice and a roofing material bill exercise different sides of the workflow. Test both rather than assuming a successful customer invoice proves vendor bills work. Add credits, time entries, or attachments later when those workflows matter, checking each record’s current support and requirements first.

Compare invoice lines, tax, gross total, balance due, and payment allocation. Compare vendor bill lines, reference, total, job allocation, and unpaid balance. Check the chosen date range and accounting reports with the bookkeeper. Explain every difference before calling the test complete; a success indicator alone is not reconciliation.

Receiving a customer payment reduces an invoice balance. Matching the later bank-feed deposit connects bank activity to accounting already recorded. Not every deposit is new income: it may combine receipts or represent another transaction. Do not independently mark payments in both systems or add a deposit as income without checking what exists.

Expand by a small group of jobs, with a named reviewer and scheduled checks. Keep unrelated automation paused until the baseline reconciles. The JobTread AI and automations guide can help frame later workflow work without treating automation as an accounting fix.

Pause affected records, not necessarily every workflow. These are possible causes, not diagnoses. Never use blind retries or destructive merge, delete, or repost actions to make an error disappear.

Preserve the audit trail. Inspect existing IDs, fix the underlying cause, and retry once only if appropriate. Posted entries, tax corrections, and closed-period changes belong with the bookkeeper. If the outcome is uncertain, stop and escalate rather than sending the same transaction again.

Prepare a sanitized packet with the affected record type, source and destination IDs, timestamps and time zone, exact error text, expected result, actual result, and steps already taken. Include redacted screenshots of relevant mappings and a short reconciliation showing the difference. State whether a destination transaction already exists.

Exclude passwords, access tokens, bank details, and unnecessary customer or employee information. Use official support channels for technical investigation. Return to the JobTread guide for the wider workflow, or consider a Jobwalk if ownership is unclear. You can book a conversation about the process without sharing credentials.