# How to use a Righthand with Square

Build a Square payment-to-order review with payment IDs, location context, status, tips, refunds, and owner-approved reconciliation rules.

By Righthand Team · 2026-10-10

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-square

## Keep payment and order evidence distinct

Righthand can help prepare a Square payment-to-order review for one approved location or account. The useful output matches payment records to order references and identifies unresolved status or amount questions. An approved payment is not the same recorded state as a completed payment, and payment completion does not establish fulfillment.

Square's [Payment object](https://developer.squareup.com/reference/square/objects/Payment) separates payment identity, status, location_id, order_id, amount_money, tip_money, total_money, and refunded_money. Preserve those fields and their currency units. A comparison that mixes the base amount with a total including tips can create a false discrepancy.

## Define location and source scope

Give the seller account, location, reporting interval, payment source, and approved order ledger. For an illustrative daily-close worksheet, compare selected completed and unresolved payments with the day's order references, using the bookkeeper's treatment of tips and refunds.

Inspect Square's exposed tools through [integrations](/integrations). If payment or order reads are absent, use an approved export or scoped browser review. Do not assume native capture, cancellation, refund, or order-update capability from the provider reference.

## A complete illustrative brief

> At 9 AM America/Los_Angeles after the selected business day, review the approved Square payment extract and order ledger for the named location. Return a private worksheet with payment ID, location, order reference, status, currency, base amount, tip, total, refunded amount, and matching result where supplied. Keep unresolved payments separate from completed payments. Do not capture, cancel, refund, or edit orders. Deliver to me for bookkeeper review and reconcile counts and source amount units.

The example is illustrative. The bookkeeper decides what belongs in sales, tips, adjustments, and settlement reporting. The assistant should not substitute its own accounting policy.

## Define the expected result

An example row could say: “Completed payment matched to order; ledger excludes tips while payment total includes them; comparison requires the approved rule.” Another can show an approved payment whose completion evidence is absent, leaving the owner's next action unresolved.

A receipt URL, when available, can be useful evidence, but it does not prove that a product was delivered. Keep fulfillment status in its separate source. Do not choose a customer relationship from a name match alone.

## Reconcile changes before remedies

Refresh payment and order records before proposing a refund or capture. Another operator may have already taken action. Match payment IDs and preserve separate refund references so a partial refund does not become an apparent duplicate full reversal.

Permissions, location filters, and incomplete pagination can limit the worksheet. State missing coverage. If a supported financial action is later authorized, retrieve its resulting record independently and reconcile the related order separately.

Use [Righthand's connection guide](https://docs.righthand.ai/guides/add-a-connection) for narrow access and reviewed actions. Check [plans](/pricing) for recurring close preparation.