Work snippet
Jobber deposits, stage payments and refunds into QuickBooks Online
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Renovation jobs here start with a quarter of the price paid upfront through Jobber, then stage claims. Make or Zapier records that deposit in QuickBooks Online as money held for the customer, offsets it on the first stage claim, and handles a cancellation through a credit memo, keeping a fee only where the signed terms allow it.
The problemDeposits taken in Jobber land in QuickBooks as income, and refunds leave balances wrong.
What changesDeposits sit as a liability, apply to the right stage invoice, and refunds follow the signed terms.
- Area
- Deposits and progress billing
- Tools
- Jobber · QuickBooks Online · Make or Zapier
- Typical scope
- US$1,800-3,200
- Timeline
- About 5 weeks · fixed milestones
The problem
Upfront money was being counted as sales the day it landed, which flattered busy months, and refunds afterwards left customer balances out of step.
- Income is recognised before any work is done
- Stage invoices are issued in full even though a deposit is already held
- Refunds are written off or left as credits that never clear
- Nobody can tie a deposits account to the jobs that are still open
What discovery would examine
A review of open jobs with deposits, the current QuickBooks Online chart, and a month of Jobber payments for a renovation company that takes a 25% deposit and bills in stages.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Deposits are posted to income on the day they are received | QuickBooks Online: income on booking dates with no stage invoice | Profit in a quiet month is overstated |
| F2 | Stage invoices are issued for the full stage, ignoring the deposit already held | Jobber invoice total equals the stage, not the balance after the deposit | Customers are asked for money already paid |
| F3 | Refunds are recorded as a spend, not a credit memo against the job | Bank spend with no link to the Jobber job | Customer balances and job profit are wrong |
| F4 | No tie-out of the deposits figure to open Jobber jobs | No deposits liability, or an unused account at $0 | Nobody can say what is still held |
| F5 | Two tax rates are in use, but only one was considered in the current flow | Job list: standard and a reduced rate on some work | The application of a deposit can leave a rounding remainder |
Approach
- Write the postings
One rule for a deposit, a stage, a change order, a refund and a cancellation.
- Set the accounts and the keys
A deposits liability, and an idempotency key on every Jobber payment and invoice id.
- Build the event flow
Jobber events write the matching QuickBooks Online entries, including applications.
- Tie out what is already held
Open deposits are loaded, then checked every week.
Current state and future state
Current state
Future state
Future-state modules
How it is built
- Module APosting rules
A deposit, each stage, a change order, a refund and a cancellation each have one written posting.
- Module BAccounts
A deposits liability, income by stage, and a fees account only where the signed terms allow a retained fee.
- Module CEvent flow
Jobber payment and invoice events write the matching QuickBooks Online entries, including the application of the deposit.
- Module DOpening load
Open jobs with a deposit already taken are loaded and tied out before go-live.
- Module EWeekly tie-out
The deposits liability is agreed to Jobber, and exceptions are listed with an owner.
Field mapping
| Jobber event | Key fields | QuickBooks Online action | Idempotency key |
|---|---|---|---|
| Deposit payment recorded | Job id, payment id, amount, tax | Debit bank, credit deposits liability | payment id |
| Stage invoice sent | Invoice id, job id, amount, tax code | Create invoice; apply outstanding deposit up to the invoice total | invoice id |
| Invoice payment (non-deposit) | Payment id, invoice id | Receive payment on the invoice | payment id |
| Refund or cancellation | Refund id, job id, amount, reason | Credit memo; refund payment; retain a fee only if the terms say so | refund id |
| Change order approved | Change id, new contract value | Adjust remaining stages; do not touch a deposit already applied | change id |
Worked exhibits
| Event | Jobber | QuickBooks Online | Liability | Income |
|---|---|---|---|---|
| Deposit $12,000 received | Payment on the job | Debit bank, credit deposits liability | $12,000 | $0 |
| Stage 1 invoice $12,000 | Invoice sent | Invoice $12,000, deposit applied | $0 | $12,000 |
| Stage 2 invoice $12,000 | Invoice sent | Invoice $12,000, no deposit left | $0 | $12,000 |
Exceptions and runbook
| Case | Rule | Who acts | Check |
|---|---|---|---|
| Deposit larger than the first stage | Apply what is needed, leave the rest on the liability | Flow, then finance if a remainder sits more than 30 days | Liability equals the unused deposit |
| Cancelled job after a deposit | Refund through a credit memo; retain a fee only if the signed terms say so | Finance, using the runbook | Jobber refund equals the QuickBooks Online payment |
| Part refund | Reduce the liability first, then income if the deposit was already applied | Finance | Both systems show the same remaining credit |
| Tax rounding remainder under $0.05 | Write to a rounding account, listed on the weekly tie-out | Flow | Tie-out still agrees |
| Event replayed | The payment or invoice id is the key; a second posting is refused | Operations, only if the first posting is proven missing | No duplicate payment or invoice |
How to read the exhibits
- The worked job shows the deposit staying off income until it is applied to a stage invoice.
- The two app windows should tell the same story: $12,000 applied, nothing still due on stage 1.
- The weekly tie-out is the ongoing check: Jobber open deposits equal the QuickBooks Online liability.
Test plan
| ID | Check | Method | PASS when | FAIL when |
|---|---|---|---|---|
| T1 | Deposit held, not taken to income | Book a test job, take 25% | Liability equals the deposit; income is $0 | Income moves on the payment date |
| T2 | Application to stage 1 | Issue the first stage invoice | Invoice due is $0; liability for the job is $0 | The customer is asked for the deposit again |
| T3 | Deposit larger than stage 1 | $12,000 deposit, $8,000 stage | $4,000 remains on the liability | The remainder is taken to income |
| T4 | Cancellation and refund | Cancel after the deposit, before a stage | Credit memo and refund match the rule in the terms | A spend is posted with no credit memo |
| T5 | Replay safety | Send the same payment event twice | One QuickBooks Online payment only | A second payment is created |
| T6 | Weekly tie-out | Run the Friday check on the test set | Difference $0.00, or every difference named | An unexplained difference |
| T7 | Both tax rates | Repeat T1 and T2 at each rate | Applications and totals agree at both rates | A remainder that is not in the rounding rule |
Scope
| Area | Included |
|---|---|
| Discovery | Open jobs with deposits, current postings, and the signed deposit terms, with written findings |
| Posting rules | Written rules for deposits, stages, refunds, cancellations and fees |
| Event flow | Jobber payments and invoices writing the matching QuickBooks Online entries, with idempotent keys |
| Opening load | Deposits already held on open jobs, tied out job by job |
| Weekly tie-out | Deposits liability agreed to Jobber, with an exceptions list |
| Test plan | Scripted jobs for each tax rate and each edge case |
| Handover and support | SOPs, a recorded walkthrough, 14 days of fixes, and an optional monthly hour block |
| Not included | Changing the deposit percentage in the sales process, or historical recoding of closed jobs |
Rollout, handover and monthly support
| Milestone | Deliverable | Timing | Share of fee |
|---|---|---|---|
| M1 Discovery and rules | Findings, written postings and the account map | Week 1 | 25% |
| M2 Flow and tests | Live in a copy, scripted cases passed | Weeks 2 to 3 | 35% |
| M3 Opening tie-out | Open deposits loaded and agreed | Week 4 | 25% |
| M4 Handover | SOPs, weekly checklist, 14 days of fixes | Week 5 | 15% |
Handover
- Written operating procedures for the happy path and each exception in the runbook
- A recorded walkthrough of the architecture, the queue and how to replay an item
- A credentials and ownership list, with every connection in your name
- Fourteen days of fixes after go-live, for defects in the agreed scope
Monthly support
A set block of hours each month, at US$35 per hour, agreed in writing before it starts. Typical use of the block: the Friday tie-out, refund cases, and any change to stage percentages or tax rates
- Review of the exception queue and the weekly digest
- Small mapping or rule changes, agreed before they are made
- A short written note on what was done and what is still open
Typical scope for this kind of project: US$1,800-3,200
About 5 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing, to watch the flows, handle changes and work the exception queue.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.