Landscaping payment payout reconciliation worksheet

How we work: This guide uses current public documentation and does not claim hands-on testing unless stated. Some links may later become affiliate links, at no added cost to you. Rankings are independent of commissions.

Reconcile a landscaping payment batch from its payout ID, not from the bank date alone. Add the payout’s gross collections, quote deposits, tips, positive adjustments, and dispute reversals. Subtract refunds, dispute debits, processing fees, instant-payout fees, and supported deductions. The result should equal the processor payout, the bank deposit, and the accounting entry after timing differences are resolved.

Download the payment payout reconciliation worksheet. It contains one formula-bearing template row. Copy that row once per payout and replace TEMPLATE-ROW; do not paste card numbers, bank credentials, or customer personal data into it.

This is a desk-researched control, not accounting advice or a report of a company’s books. The Jobber, Housecall Pro, QuickBooks, Stripe, and National Association of Landscape Professionals sources were opened and checked on September 13, 2026. The acceptance checks below are proposed tests, not tests this site performed.

What exactly are you reconciling?

A customer payment and a bank deposit are different events. The landscaping system records which client and invoice were paid. The processor groups available transactions into a payout. The bank receives the net settlement. The accounting system must preserve the invoice payment, deductions, and cash movement without recording the deposit twice.

Use this chain:

invoice or quote deposit → payment transaction → payout ID → bank deposit → ledger deposit or clearing transfer

The payout ID is the control key. Stripe’s current documentation says an automatic payout can include multiple transactions and that its balance transactions can be filtered by payout ID. Those transactions identify charges, refunds, processor fees, and the payout itself. Stripe also says manual payouts do not have the same automatic transaction assignment, so the business is responsible for reconciling them against transaction history.

Do not join records only on a shared date and amount. A card payment may settle after the invoice date, several payments may become one deposit, and a refund or dispute may be deducted from a later payout.

What formula should the worksheet use?

Use signed components with one convention:

expected net payout
= gross invoice payments
+ quote deposits
+ tips
+ positive adjustments
+ dispute reversals
- refunds
- dispute debits
- processing fees
- instant-payout fees
- other documented deductions

Enter deductions as positive amounts in their named columns; the worksheet formula subtracts them. Do not enter the same refund as both a negative collection and a positive refund. Keep each payout in one currency. If a processor settles more than one currency, use separate rows and reconcile each bank amount under the account’s approved foreign-currency method.

The template then calculates three variances:

1. Processor variance: expected net minus processor-reported net.
2. Bank variance: processor-reported net minus bank deposit.
3. Ledger variance: bank deposit minus accounting deposit.

Zero is the target after known timing items are resolved. A nonzero amount is an exception, not an invitation to force a balancing entry.

Which evidence should you collect for each payout?

Build the row from source records, not memory.

Keep the processor report or approved export with the period’s reconciliation evidence. A screenshot of the net payout alone is insufficient because it does not show which invoice payments and deductions produced that amount.

The landscaping job-costing guide explains why invoice and cost identifiers need to survive into estimated-versus- actual reporting. The payout worksheet stays focused on cash settlement; it does not assign processor fees to jobs unless the company’s approved costing policy does so.

Which reconciliation method should you use?

Rank methods by transaction traceability and duplicate protection.

Automation does not remove review. Intuit’s current payout workflow exposes sales, refunds, expenses, and adjustments within a payout, then matches the added payout to the bank deposit. It also warns that a bank deposit entered before the connected payout may need to be undone to avoid duplication.

Have the company’s bookkeeper or accountant approve clearing, fee, refund, dispute, tip, tax, and customer-deposit accounts. The worksheet proves that systems agree; it does not decide when revenue is earned. NALP’s trade coverage notes that landscaping companies can have receivables, work in progress, retention, customer deposits, and prepaid maintenance whose cash timing differs from income-statement timing.

How do Jobber Payments payouts map?

Jobber’s current QuickBooks sync documentation says each payout in paid status is flagged to sync when payout syncing is enabled. It lists payments, quote deposits, instant payouts, tips, fees, refunds, and disputes among the transaction types that can make up the accounting result.

Jobber documents these purpose-specific accounts:

• payment fees go to a Jobber Payments Fees account;
• refunds use Refunds Clearing until the payout containing the deduction syncs; and
• disputed amounts use an Allowance for Disputed Jobber Payments account.

Its guide says a dispute is treated as lost while it is still under investigation, so the deduction can appear before the outcome is final. Keep the dispute ID, status, debit payout, and any later reversal as separate evidence. Do not delete a dispute exception merely because the first payout balanced.

Jobber’s manual reconciliation guide covers accounts without payout sync. It says the bank receives the total payment amount less processing fees, while the Payouts and Transactions reports provide fee totals. This is why recording only the net bank deposit would lose the fee component.

If the Jobber-to-QuickBooks payout sync fails, resolve upstream invoice and payment errors before the payout. Do not also create a manual deposit while an automatic retry can still post the same batch.

How do Housecall Pro payouts map?

Housecall Pro’s Payments Export, updated August 10, 2026, includes job and customer IDs, invoice number, payment date and amount, payment type, exact fee amount, and fee type. Refunds appear as negative payment amounts. For a batch payment covering several jobs, Housecall Pro says the fee amount appears only on the first job so it is not duplicated across every row.

Its Payouts screen separately provides the deposit date, status, gross payment, fees, net payout, job number, and customer. Use the payout detail for the bank join and the export for invoice-level completeness.

Housecall Pro’s QuickBooks reconciliation guide says its integration groups payments, subtracts processing fees, and moves the result from Undeposited Funds to checking. It creates a dedicated payment-processing-fee account. The pass condition is still evidence-based: the grouped accounting transaction must match the expanded Housecall Pro payout and the bank deposit.

Do not combine Jobber and Housecall Pro account names in one “universal” posting recipe. Their published reports demonstrate the same gross-to-net control, but each integration creates and uses its own accounting records.

How should refunds and disputes be handled?

Treat a refund as both a customer event and a payout component. Record its source payment or invoice, refund ID, initiation date, settled deduction, amount, and final status. Then verify that the refund appears once in the customer ledger and once in the correct payout calculation.

Treat a dispute as a lifecycle:

opened → payout debit → evidence or response → won or lost → reversal or final deduction

One dispute can affect more than one reconciliation period. Keep it open until the processor’s final status and every debit, fee, and reversal have been matched. A balanced first payout proves only that the initial deduction was recorded.

Use other_deductions only with a processor transaction ID and explanation. If a recurring difference is really an instant-payout fee, financing repayment, reserve, tax withholding, or currency adjustment, give it a stable account and worksheet field rather than hiding it in “other.”

How do you test the accounting sync?

Run these cases with synthetic records in a vendor-supported test environment when one exists. If the integration has no safe test mode, have the bookkeeper design a controlled live pilot and reversal plan.

Record expected behavior before running a case. Screenshots and exports are evidence of what happened, not proof that the accounting treatment is correct. The reviewer should compare processor components, bank activity, and ledger entries independently.

The software cost calculator can model processor fees as a software cost input. Use reconciled fee totals, not a percentage remembered from a pricing page.

How do you validate saved-payment-method migration?

Do not put primary account numbers, security codes, bank credentials, or encrypted card files in this worksheet. Track only non-sensitive source customer IDs, source payment-method tokens, destination customer IDs, destination tokens, default-method status, migration status, and evidence.

Stripe’s current migration documentation describes a processor-led process for sensitive payment data. It requires a migration request, identifies the customers and payment methods in scope, and returns an old-to-new object mapping after import. It also recommends moving new customers first and designing a process for customers to update card information.

Use this acceptance sequence:

1. Get written confirmation that the source and destination processors support the transfer and name the responsible teams.
2. Count active customers, payment-method tokens, defaults, recurring charges, and excluded method types without exporting card numbers.
3. Freeze or log payment-method changes during the transfer window.
4. Load the returned old-to-new token mapping into the destination through the approved integration path.
5. Reconcile source customer, destination customer, method type, expiration metadata if provided, and default status.
6. Test a synthetic or specifically authorized destination method before scheduling any automatic charge.
7. Route failed, expired, unsupported, or unmapped methods to a secure customer-update request.
8. Keep the old processor available for historical payout, refund, and dispute reconciliation until retention and open-item requirements are met.

A token count match is not enough. A token mapped to the wrong property manager or HOA can charge the wrong payer. Link the acceptance record to the client and billing relationship, not merely a display name. The landscaping CRM migration guide provides the client-property identity controls needed for that review.

What should the daily and month-end review contain?

For each final payout:

• reproduce the net from signed processor components;
• match one processor payout to one bank deposit;
• match the bank amount to one accounting deposit or clearing transfer;
• investigate every nonzero variance;
• keep refunds and disputes open through final status; and
• assign failed payouts, missing transactions, and sync errors to an owner.

At statement close, reconcile the bank, processor clearing, refund clearing, and dispute accounts. Review old unmatched items by payout ID and age. Confirm that no bank-feed item was added as income after an integration had already created the deposit.

The landscaping tech-stack audit template helps identify who owns the processor, bank feed, accounting sync, and exception queue. One person may operate all four in a small company, but the evidence and review steps should remain distinct.

The worksheet is complete when every payout can be rebuilt from source transactions, every bank deposit is matched once, ledger movements preserve the gross-to-net bridge, and open refunds or disputes have owners. A zero bank variance alone is not enough.