What does Clover connect to on its own?
Clover offers a REST API that lets other software read a merchant’s orders, payments and inventory. Access runs over HTTPS with OAuth 2.0, so a merchant has to authorize each app, and each location is authorized separately. Other connections, including accounting and CRM, generally come from apps in Clover’s App Market or from developers who build on that API. What each app covers differs, so read its listing before you rely on it.
What Clover does well is run the point of sale, card payments and inventory in one system, with its own reports and transaction exports. For one location with simple sales, an accounting app plus a periodic check may be enough.
If you run Clover in the shop and Shopify online, you are really asking how to combine two sales streams into one set of books. Shopify to QuickBooks Online or Xero, and Shopify to HubSpot, are self-serve connections in Pandaflow. The Clover side is set up on request.
The gaps owners hit (books, CRM, reporting)
Clover reports sales. Your bank shows a deposit. The two numbers differ every day, and a sync that posts only sales will never match the bank line.
| Clover data | Where it should land | Why the bank deposit differs |
|---|---|---|
| Gross card sales | Sales income, posted to a clearing account (Undeposited Funds in QuickBooks Online) | The deposit is net of fees, refunds and chargebacks |
| Processing fees | Merchant fees expense | Netted from the payout or billed separately, depending on the processing agreement |
| Refunds | Reduction of sales or a refunds account, dated when issued | Often a different day than the original sale |
| Chargebacks | Chargeback or disputes account, plus any fee | Arrive as deposit reversals, sometimes weeks later |
| Tips on card payments | Tips payable (liability) until paid to staff | Included in the deposit but not revenue |
| Sales tax | Sales tax payable, split by location and rate | Included in the deposit but not revenue |
| Gift card sales and redemptions | Gift card liability, released to revenue on redemption | Sale produces a deposit; redemption produces none |
| Cash sales | Sales income and cash or bank deposit account | No processor deposit at all |
| Customers | HubSpot or Salesforce contacts | Not a financial entry; the match is by email or phone |
The manual fix is a clearing account. In QuickBooks Online, post daily card sales to Undeposited Funds, then match each bank deposit against it. In Xero, use a clearing account the same way. Without this step, the bank feed shows deposits that match no entry.
Summaries per day reconcile cleanly only when the batch cutoff lines up with the calendar day. Per-transaction entries need grouping to reach a single deposit. Pick one approach and check it on a week that includes a refund, a tip-heavy day and a gift-card sale.
This is an illustrative setup, not a customer story. A café has one day of $1,000 in card sales, $100 in card tips, a $50 refund and a $30 fee netted from the payout. The deposit is $1,020, which looks like more than the sales report. Posted correctly, sales income is $1,000, refunds reduce it by $50, tips payable gets $100, merchant fees take $30, and the clearing account shows the $1,020 that matches the bank.
Which Clover connections does Pandaflow set up on request?
Clover syncs in Pandaflow are set up on request. They are not a self-serve connector today, so there is no button to press. Here is what gets set up, in order:
- Books first: Clover to QuickBooks Online, and Clover to Xero.
- Then CRM: Clover to HubSpot, and Clover to Salesforce.
What posts to the books:
- Sales by day or by transaction, depending on how your books are kept.
- Sales tax by location and rate.
- Tips to a liability account.
- Gift cards as a liability, released on redemption.
- Fees and refunds on their own lines.
- Entries grouped to each bank deposit through the clearing account.
Pandaflow’s AI agent maps the data, posts the entries and repairs the sync when an app changes. You can see pricing for Pandaflow: it is free to start, with plans at Lite $79, Silver $299 and Gold $499 a month, and it can be deployed in Pandaflow’s cloud or yours.
For CRM, customers captured at the register do not reach HubSpot or Salesforce on their own. The match is usually by email or phone, which is also how duplicates appear when the same person orders online.
How does Clover setup with Pandaflow work?
- Request setup.
- Short call about what you sell and how your books are kept: locations, tax setup, tips, gift cards and the chart of accounts.
- Pandaflow builds the sync and tests it on real records.
- Go live.
- The agent keeps it running.
Bring these to the call:
- A recent processor deposit statement, so the fee treatment is clear.
- A list of locations with their tax rates.
- The account names already used for fees, tips and gift cards.
Once it runs, you should see entries in QuickBooks or Xero grouped to match each bank deposit, with fees, refunds, tips and tax on their own lines. If an app changes, the agent repairs the sync.
What can go wrong?
- A batch cutoff across midnight. Sales after closing can land in the next day’s deposit. Agree the cutoff time on the call and check the first deposit.
- A location added later. A new location has its own merchant account and needs its own tax setup and class or location tag. Tell us before you open it.
- A gift card redeemed at another location. The liability has to clear against the right location. Check the first redemption across sites.
- A fee schedule that changes. If your processing terms change, the fee line needs updating. Re-check one deposit after any change.