All integrations

Square

Connects · Payments & subscriptions

Fiona connects to Square and syncs it automatically.

What happens today

Paste a Square access token and Fiona pulls every completed sale, splitting it into what you earned, the processing fee, sales tax held for the state, and tips held for your staff — so your income is what you earned rather than what was banked.

Why it matters to your books

Square nets its fee out of the deposit and mixes tips into it. Book that deposit as revenue and you overstate income by money you owe your staff, understate it by the fee, and the tip liability appears nowhere at all. No amount of careful statement reading fixes it — the bank line simply doesn't contain the split.

What syncs

How to set it up

  1. Square Developer dashboard → your application → Credentials
  2. Copy the production access token (PAYMENTS_READ is all it needs)
  3. Paste it into Connect → Square

Questions people actually ask

Why do tips need their own account?

Because they aren't your money. A tip is collected from the customer and owed to staff, so it belongs on the balance sheet as a liability until it's paid out. Counted as revenue it inflates your income and hides what you owe — and it's the most common misstatement in restaurant books.

Can't you just read my bank deposits instead?

The deposit is one number: sales plus tips minus the fee. Nothing in that number says how it was made up, so food-cost percentage and tip liability are both unanswerable from the bank alone.

Does Fiona need permission to move money in Square?

No. The token needs read access to payments and nothing else. Fiona never holds, moves or refunds money.

All product names, logos and brands are property of their respective owners. Naming them here describes what Fiona reads or connects to — it does not imply any affiliation with, sponsorship by, or endorsement from them.