Manaz Afzal Book a consultation

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.

Findings from the review
IDFindingEvidenceRisk if left
F1Deposits are posted to income on the day they are receivedQuickBooks Online: income on booking dates with no stage invoiceProfit in a quiet month is overstated
F2Stage invoices are issued for the full stage, ignoring the deposit already heldJobber invoice total equals the stage, not the balance after the depositCustomers are asked for money already paid
F3Refunds are recorded as a spend, not a credit memo against the jobBank spend with no link to the Jobber jobCustomer balances and job profit are wrong
F4No tie-out of the deposits figure to open Jobber jobsNo deposits liability, or an unused account at $0Nobody can say what is still held
F5Two tax rates are in use, but only one was considered in the current flowJob list: standard and a reduced rate on some workThe application of a deposit can leave a rounding remainder

Approach

  1. Write the postings

    One rule for a deposit, a stage, a change order, a refund and a cancellation.

  2. Set the accounts and the keys

    A deposits liability, and an idempotency key on every Jobber payment and invoice id.

  3. Build the event flow

    Jobber events write the matching QuickBooks Online entries, including applications.

  4. Tie out what is already held

    Open deposits are loaded, then checked every week.

Current state and future state

Money movement, current and future

Current state

Jobber depositTaken on booking
QuickBooks OnlinePosted to income
Stage invoiceFull stage billed
RefundUnlinked spend

Future state

Jobber depositPayment event
LiabilityUnearned deposits
Stage invoiceDeposit applied
RefundCredit memo

Future-state modules

JobberPayments and invoicesMake or ZapierEvent, map, postQBO liabilityDeposits heldQBO invoicesStages and applicationsWeekly tie-outJobber vs liability

How it is built

Module-level build
  1. Module APosting rules

    A deposit, each stage, a change order, a refund and a cancellation each have one written posting.

  2. Module BAccounts

    A deposits liability, income by stage, and a fees account only where the signed terms allow a retained fee.

  3. Module CEvent flow

    Jobber payment and invoice events write the matching QuickBooks Online entries, including the application of the deposit.

  4. Module DOpening load

    Open jobs with a deposit already taken are loaded and tied out before go-live.

  5. Module EWeekly tie-out

    The deposits liability is agreed to Jobber, and exceptions are listed with an owner.

Field mapping

Event mapping, Jobber to QuickBooks Online
Jobber eventKey fieldsQuickBooks Online actionIdempotency key
Deposit payment recordedJob id, payment id, amount, taxDebit bank, credit deposits liabilitypayment id
Stage invoice sentInvoice id, job id, amount, tax codeCreate invoice; apply outstanding deposit up to the invoice totalinvoice id
Invoice payment (non-deposit)Payment id, invoice idReceive payment on the invoicepayment id
Refund or cancellationRefund id, job id, amount, reasonCredit memo; refund payment; retain a fee only if the terms say sorefund id
Change order approvedChange id, new contract valueAdjust remaining stages; do not touch a deposit already appliedchange id

Worked exhibits

Worked figures for one job (USD, ex tax)
Contract value$48,000four stages
Deposit held$12,00025% on booking
First stage invoice$12,000deposit applied in full
Cash in from the deposit$12,000not taken as income on day one
EventJobberQuickBooks OnlineLiabilityIncome
Deposit $12,000 receivedPayment on the jobDebit bank, credit deposits liability$12,000$0
Stage 1 invoice $12,000Invoice sentInvoice $12,000, deposit applied$0$12,000
Stage 2 invoice $12,000Invoice sentInvoice $12,000, no deposit left$0$12,000
The two systems after the deposit is applied
Jobber · job J-4418
CustomerKitchen renovation, one site
Contract$48,000
Deposit$12,000 received
Stage 1$12,000 invoiced
Deposit appliedYes, $12,000
Balance due$36,000
QuickBooks Online · invoice 10421
Invoice total$12,000
Deposit applied$12,000
Amount due$0.00
Deposits liability$0.00 for this job
Income this month$12,000
Weekly tie-out, one Friday
Jobber deposits open$186,400
QuickBooks Online liability$186,400
Difference$0.00after two held items
Held items2named, with an owner

Exceptions and runbook

Exception runbook
CaseRuleWho actsCheck
Deposit larger than the first stageApply what is needed, leave the rest on the liabilityFlow, then finance if a remainder sits more than 30 daysLiability equals the unused deposit
Cancelled job after a depositRefund through a credit memo; retain a fee only if the signed terms say soFinance, using the runbookJobber refund equals the QuickBooks Online payment
Part refundReduce the liability first, then income if the deposit was already appliedFinanceBoth systems show the same remaining credit
Tax rounding remainder under $0.05Write to a rounding account, listed on the weekly tie-outFlowTie-out still agrees
Event replayedThe payment or invoice id is the key; a second posting is refusedOperations, only if the first posting is proven missingNo duplicate payment or invoice

How to read the exhibits

  1. The worked job shows the deposit staying off income until it is applied to a stage invoice.
  2. The two app windows should tell the same story: $12,000 applied, nothing still due on stage 1.
  3. The weekly tie-out is the ongoing check: Jobber open deposits equal the QuickBooks Online liability.

Test plan

PASS / FAIL checks on scripted jobs
IDCheckMethodPASS whenFAIL when
T1Deposit held, not taken to incomeBook a test job, take 25%Liability equals the deposit; income is $0Income moves on the payment date
T2Application to stage 1Issue the first stage invoiceInvoice due is $0; liability for the job is $0The customer is asked for the deposit again
T3Deposit larger than stage 1$12,000 deposit, $8,000 stage$4,000 remains on the liabilityThe remainder is taken to income
T4Cancellation and refundCancel after the deposit, before a stageCredit memo and refund match the rule in the termsA spend is posted with no credit memo
T5Replay safetySend the same payment event twiceOne QuickBooks Online payment onlyA second payment is created
T6Weekly tie-outRun the Friday check on the test setDifference $0.00, or every difference namedAn unexplained difference
T7Both tax ratesRepeat T1 and T2 at each rateApplications and totals agree at both ratesA remainder that is not in the rounding rule

Scope

AreaIncluded
DiscoveryOpen jobs with deposits, current postings, and the signed deposit terms, with written findings
Posting rulesWritten rules for deposits, stages, refunds, cancellations and fees
Event flowJobber payments and invoices writing the matching QuickBooks Online entries, with idempotent keys
Opening loadDeposits already held on open jobs, tied out job by job
Weekly tie-outDeposits liability agreed to Jobber, with an exceptions list
Test planScripted jobs for each tax rate and each edge case
Handover and supportSOPs, a recorded walkthrough, 14 days of fixes, and an optional monthly hour block
Not includedChanging the deposit percentage in the sales process, or historical recoding of closed jobs

Rollout, handover and monthly support

MilestoneDeliverableTimingShare of fee
M1 Discovery and rulesFindings, written postings and the account mapWeek 125%
M2 Flow and testsLive in a copy, scripted cases passedWeeks 2 to 335%
M3 Opening tie-outOpen deposits loaded and agreedWeek 425%
M4 HandoverSOPs, weekly checklist, 14 days of fixesWeek 515%
Handover and monthly support

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.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation