Square + Go Fig

PaymentsAccounting

Integrate Square payment, POS, and location data with Go Fig for unified retail and financial analytics.

Square is the operating system for a lot of multi-location retail, food, and service businesses: in-person POS, online checkout, inventory, timecards, and cash drawer all in one place. The challenge for finance is that Square's reporting is per-location and per-channel, while the business lives in the consolidation. Go Fig pulls Square at the transaction and payment grain, preserves location and device and channel as dimensions, and joins to the accounting ledger so deposit reconciliation, per-location margin, and same-store sales become first-class views in the Financial Intelligence Graph. Refunds and disputes are tracked through their lifecycle, cash versus card is preserved at the tender grain, and multi-currency locations land in a consistent base currency for roll-up. Celeste can answer per-location and cross-location questions (which store is running the best labor-to-sales ratio this month) without the operator rebuilding the cut in Square Dashboard.

Connect Square See All Integrations

Key facts

Auth: Square OAuth, per-merchant
Grain: Transaction, payment, tender
Locations: Multi-location, multi-device
Tender tracking: Cash vs card preserved
Sync cadence: Webhook-driven, near real time

SOC 2 Type II · All integrations

What you can do with Square data in Go Fig

Multi-location sales and margin

Compare location-level sales, cost of goods, and labor side by side with a shared chart of accounts and same-store math applied consistently.

Deposit reconciliation

Match Square bank deposits back to the underlying transactions and fees, automating a weekly manual task for multi-location operators.

Cash vs card and tip handling

Track tender-level sales, cash drawer variances, and tip distribution through payroll with the full transaction trail intact.

Data available from Square

Go Fig extracts and normalizes the following data from your Square account:

Transactions

Payments

Tenders (cash, card, gift)

Refunds

Disputes

Orders

Line items

Inventory counts

Customers

Locations

Employees

Timecards

How to connect Square

Authorize Square via OAuth

From the Go Fig connector page, click Connect Square. You are redirected to Square to sign in with the merchant account that owns the locations you want synced. For multi-entity operators, repeat this step per merchant account; each lands in its own partition.

Select locations in scope

Square merchants often have locations that are no longer operating or that belong to a different legal entity. Pick the exact locations to sync. Device-level attribution (register, mobile reader, online checkout) is preserved automatically so channel analysis works without extra setup.

Map item categories to GL accounts

Square's catalog categories rarely match your chart of accounts one-for-one. Go Fig suggests a mapping from category to revenue GL, with overrides for items that should book to a different account (gift card liability, service revenue, retail COGS). Once mapped, per-transaction revenue journals are generated automatically.

Wire deposit reconciliation to the bank connector

Connect your bank (Plaid or direct) and Go Fig matches Square deposit batches to bank-posted credits. Fees and chargebacks are reconciled to the underlying payments, so the weekly reconciliation that used to take hours runs as a standing flow.

Authentication: Square OAuth with merchant-level consent. Read-only scopes are requested for Payments, Orders, Items, Inventory, Customers, Employees, Timecards, and Locations. For multi-entity operators (separate merchant accounts per legal entity), each account is authorized independently so entity boundaries are preserved in the graph.

Common Questions About Square Integration

Does Go Fig support multi-location Square operators?

Yes, this is one of the most common Square use cases. Locations are preserved as a dimension on every transaction, so per-location P&L, same-store sales, labor-to-sales ratio, and margin-by-format roll up cleanly. Operators with separate merchant accounts per legal entity can connect each one; each partition has its own deposit schedule and its own GL mapping.

How is cash versus card tracked?

Tender grain. Every payment carries the tender type (cash, credit, debit, gift card, other) as a native attribute. That means cash-drawer reconciliation, card-processing-fee economics, and gift-card liability tracking are all possible without leaving the graph. Cash variances at close are visible by location and by employee when the POS is configured to assign drawers.

Are refunds and disputes handled?

Yes. Refunds are ingested as their own records linked to the original payment with reason codes and partial-refund amounts preserved. Disputes are tracked through the Square dispute lifecycle (evidence requested, won, lost) and the funds impact is posted at the right time. Chargeback fees appear in the fees feed so payout reconciliation never has unexplained deltas.

Does Go Fig support Square Appointments, Invoices, and Online?

Yes, all Square product lines route through the same Payments and Orders objects once authorized. Appointments revenue is attributed to the service category, Invoices revenue carries the invoice object through to reconciliation, and Online checkout transactions are tagged as an online channel so in-person versus online can be compared as a dimension.

How are timecards and labor data used?

Timecards are ingested at the shift grain with employee, location, and role preserved. Joined to the Payments feed at the same location and hour, this produces labor-to-sales ratio, a key operating metric for retail and food service. Joined to payroll, you get fully loaded labor cost against sales, which is the number most multi-location CFOs want on the weekly flash.