Vista Watch: early access

Altura Innovation Technology Partners

Square to NetSuite reconciliation

Square payout reconciliation to NetSuite

A channel guide for retail and omnichannel brands whose Square deposits net processing fees and refunds that NetSuite never sees.

The method

How do you reconcile Square payouts to NetSuite?

Square payout reconciliation to NetSuite matches each Square payout to the sales, processing fees, refunds, disputes, and instant-transfer fees behind the deposit, across every location that shares the account. The method decomposes the payout before posting, so finance reviews exceptions instead of reverse-engineering the net deposit.

Key takeaways

  • Start from the Square payout report, not the net amount that lands in the bank.
  • Square nets a processing fee on every sale before it deposits, so gross sales never equal the payout.
  • Refunds, disputes, and instant-transfer fees each move money on their own timeline.
  • When one Square account spans multiple locations, split activity by location before posting.

01 · The pattern

Why does a Square payout not match NetSuite?

A Square deposit is net of processing fees, refunds, disputes, and any instant-transfer fee, and it batches sales by Square's payout schedule rather than by NetSuite's accounting events. When one account rings up several locations, a single payout can blend their activity together. NetSuite holds each sale, refund, and fee as a separate record, so the net deposit rarely equals a clean sum of NetSuite sales.

  • Processing fees are deducted per transaction before the payout batches.
  • Instant transfers charge an extra fee for same-day access to funds.
  • Refunds and disputes can settle in a later payout than the original sale.
  • Multi-location accounts fold several stores' activity into one deposit.

02 · The pattern

Which Square payout lines need NetSuite treatment?

Each category in the payout report needs a NetSuite destination or an exception reason. The goal is to preserve enough Square detail that NetSuite carries accurate revenue, fee, refund, and location treatment instead of a lump-sum deposit.

Square detailNetSuite treatmentReview gate
Card sales and tipsSales order, invoice, or cash application pathConfirm the sale maps to the right NetSuite location and channel.
Processing and instant-transfer feesFee expense or configured clearing treatmentIsolate both fee types from gross sales.
Refunds and disputesRefund, credit, or exception pathTie the refund to the original sale and check payout timing.
Multi-location activityLocation-specific postingSplit blended payouts by location before posting.

03 · The pattern

How does Altura make Square reconciliation close-ready?

Altura designs the reconciliation around source detail, location split, and exception ownership. The workflow matches Square payout lines to NetSuite activity, isolates fee types, separates location activity, and holds unresolved items for review. Vista Recon turns that method into a repeatable NetSuite reconciliation path.

  • Normalize the Square payout report before matching it to NetSuite.
  • Separate processing fees and instant-transfer fees from gross sales.
  • Split multi-location payouts to the correct NetSuite location.
  • Keep unresolved refunds and disputes visible by owner and reason.

Shared vocabulary

What terms matter on this page?

These definitions keep the method precise and extractable for answer engines, while giving finance a shared vocabulary for source files, NetSuite treatment, and review gates.

Square payout

A batched deposit from Square that includes card sales net of processing fees, refunds, and any instant-transfer fee.

Instant transfer fee

The additional fee Square charges to move a payout to the bank the same day instead of on the standard schedule.

Location split

Separating a single Square payout into the individual store or location activity it combined, so NetSuite posts each to the right location.

Where it goes next

When the pattern becomes an operating decision

This pattern sits between the settlement library, productized reconciliation, and the service paths that explain why the mismatch keeps recurring.

If this reconciliation pattern is caused by connector behavior, the operating decision belongs with a Celigo NetSuite integration partner. If the issue comes from a stalled implementation or brittle partner handoff, compare it with NetSuite HealthCheck and recovery. If the same pattern recurs every close, evaluate Vista Recon against the full NetSuite payout reconciliation.

Authorship

Who wrote this guide?

Written by Dave Charland, Founder, Altura Innovation. Last updated 2026-07-04.

FAQ

Frequently asked questions

Need this payout source to tie to NetSuite?

Tell us where the source file, NetSuite record, and close process stop agreeing, and we will help scope the safest Vista Recon path.