Connections

Connecting a processor is the single highest-value thing a new account does — revenue, customers and refunds all start flowing without you typing anything. DeskOps never asks for your processor password; the connection is OAuth, so you log in on Stripe's or Square's own page.

QuickBooks imports history once, then disconnects; it does not keep syncing. After Intuit approval, review “See what will come over” before anything is written: payments, sales, existing matches, customers, expenses, supplier payments and unpaid bills. Unpaid invoices stay in QuickBooks; the preview shows what is owed on each.

Supplier payments become expenses on their payment dates, with QuickBooks categories. Unpaid balances become Bills; partial payments keep the expense and remaining bill separate. Bank matches are counted once. Choose Bring it in, or cancel and disconnect. Completion disconnects QuickBooks and sends a notification. Undo is available for seven days in Recent imports.

An Intuit “create a company” wizard means that login has no QuickBooks Online company yet; complete that step at Intuit. Connecting another accounting system warns you first to avoid double-counting.

Xero is a one-time import, not a live connection. The import reads one fixed history window of customers, the payments received on invoices, and expenses; the invoices themselves are not imported. Payments and expenses go through the same duplicate checks as Stripe and the bank, so the same money is counted once. When the history is in, DeskOps removes its local tokens and disconnects this business from Xero automatically; if the remote disconnect needs a retry, Settings says so. A Xero connection still needed by another connected business is kept for that business; the import can be undone for seven days from Recent imports. A large Xero book may stop at a saved page: Settings then says Continue import, and continuing resumes from that page without inserting the earlier rows again.

Bank connection goes through Plaid, and DeskOps asks you to confirm by email before Plaid opens. Your bank credentials are entered on Plaid's screen and never reach DeskOps — we only ever hold a token.

Two connections carry the product: the bank, through Plaid, so every dollar in and out is real; and Stripe, so an invoice can actually be paid online and paid out to you. The rest are importers — useful, never required. Square brings in sales and customers, read-only (invoicing runs through Stripe). QuickBooks brings history in once — expenses, customers, invoices and payments — then disconnects. Xero does the same with expenses, customers and the payments received on invoices. Google Ads brings campaign spend, clicks, leads and conversions to the Ads page and is included in DeskOps through Ad Integrations. Meta Ads connects from Settings with the read-only ads_read permission; it reads ad accounts and campaign reporting and never edits campaigns. Google Business Profile brings in profile figures and review totals. For other systems, bring history through the universal CSV importer. Historical imports still count; they do not make those systems available as connections.

No. DeskOps only reads Square: it brings in your payments, customers, locations, the sales tax on each order and any chargeback (dispute) on your payments, and it never creates, sends, changes, cancels or refunds anything in your Square account — not an invoice, not a refund, not a subscription. That holds even if you connected Square before September 15, 2026, when DeskOps asked Square for wider permission: that permission is never used. To void a Square invoice, refund a Square payment or stop a Square subscription, do it in Square; a refund you give there comes into DeskOps with the next sync. A Square connection made before DeskOps began reading chargebacks picks them up after you next reconnect it in Settings; nothing else changes until then, and you are never forced to reconnect. Invoices you send from DeskOps go out with a Stripe Pay link, or as check-or-cash invoices.

Stripe, Square and the bank sync every hour, and Stripe payments on your invoices and new bank transactions also arrive on their own within about a minute of happening. Google Ads and Google Business Profile sync once a week, on Monday mornings — ad platforms report a day in arrears anyway. Your main bank's balance refreshes daily; any other bank's balance refreshes weekly. Sync (Sync now on a phone) runs those live connections on the spot. QuickBooks and Xero are different: each imports history once, then disconnects and never runs on a schedule.

DeskOps marks an invoice paid only after Stripe confirms the payment, so a Stripe outage can delay a payment showing up but can never make an invoice look paid when it is not. While Stripe is having trouble, a card payment may not go through or may be slow to appear, and the invoice stays unpaid. When Stripe is back, payments it confirmed in the meantime arrive on their own, and the hourly sync catches up anything missed. If a payment looks late, open Connections → Stripe, check the last-synced time and tap Sync.

A first live connection pulls 365 days of history in the background. On a heavy history that takes several minutes and the KPI cards fill in as rows land — nothing is broken, it is still working. If a live connection has not synced in more than about two days, the advisor says so before quoting you any figure rather than quietly using stale numbers. QuickBooks and Xero instead have their own one-time import rows in Settings; a partial Xero import says Continue import and resumes from its saved page.

Disconnecting revokes the token at the provider where the provider supports it. Data that already synced stays — disconnecting stops future syncing, it does not erase your history.

A connection that has synced for a full day and brought in no customers and no payments says so on its own row: "Nothing has come in from Stripe yet." That is normal for a brand-new account with no payments in it. If you already take payments there, it usually means a different account was connected — a test account, an old one, or one that belongs to another business. Disconnect it from the row's menu and connect the account you actually get paid in; since nothing came in from it, there is nothing of its to lose. The line goes away the moment the first record arrives.

Tokens expire on the provider's schedule, and some providers drop a connection when a password changes or an admin revokes an app. Reconnecting is a full re-authorisation and it picks up where the sync left off rather than starting the 365-day pull over. When Stripe is the one that broke, customers can't pay your invoices by card or bank until you reconnect: the line at the top of DeskOps says "Stripe needs reconnecting; you can still send invoices for check or cash", and an open invoice's pay page asks the customer to contact you to pay.

DeskOps holds a revocable token, never a credential. That is also why disconnecting is instant and why we can never "look up" your bank login for you.

Connect the Google account that manages your profile. With only one profile on a new connection, DeskOps selects it automatically. With more than one profile, choose the exact profile and Use this profile. Check its address and Google Maps link when names repeat; Google may omit a service-area business’s street address. Changing profiles replaces the old figures; DeskOps never substitutes another profile.

Choose From/Through dates. Calls count call-button taps, not completed calls. Reviews/rating are the latest saved snapshot with its own date. Partial periods show reported subtotals; missing readings stay unavailable, while reported zeros stay zero. Last complete sync marks a full update.

On a phone, open the connection’s options → Sync now. If Google is busy, retry after the displayed wait; saved figures are kept. Disconnect stops updates but keeps saved figures readable; reconnect before changing profiles.