Integrations

How BizBooks Pro connects to your bank, your payment processor and your filing service — and why your accounting records still never leave your computer.

Overview

BizBooks Pro is desktop accounting software, which leads people to assume that everything has to be typed in by hand. It doesn't. Transactions arrive from your bank on their own, customers pay invoices by card, contractor filings are transmitted electronically, and your entire QuickBooks history can be carried across in one pass.

What makes this different from cloud accounting is direction. Outside data flows in. Your general ledger does not flow out.

Where to find these: Every connection described on this page is set up from Settings inside BizBooks Pro. None of them require a separate purchase or an add-on subscription.

How Connections Work

Understanding the mechanics helps when you are deciding what you are comfortable connecting.

Your installation initiates every request. BizBooks Pro reaches out to fetch data. Nothing outside your network initiates a connection to your machine, and no port needs to be opened on your router.
Credentials are handled by the provider. When you link a bank, you sign in on your bank's own secure screen. Those credentials are never typed into BizBooks Pro, never stored by us, and never transmitted through our systems.
Only transaction data comes back. What returns is the activity itself — dates, amounts, descriptions, balances — which is written directly into the PostgreSQL database on your computer.
Your books stay put. Journal entries, financial statements, customer records and invoices live in that local database. There is no synchronized copy of your ledger on a vendor's server.

What's Available Today

The following are shipping features in the current version. Anything not listed here is not yet available — see What's Coming.

Bank & Card Feeds

Link checking accounts, savings accounts and business credit cards so transactions download automatically. Smart matching proposes a category and the offsetting account for each one, turning data entry into review.

Detailed setup instructions, matching rules and troubleshooting are covered in Bank & Statement Import.

If your institution isn't supported: use statement import instead. It is a fully supported permanent workflow, not a fallback — see Statement Import below.

Stripe & PayPal Payments

Attach a pay-now option to your invoices so customers can settle by card or through PayPal. The accounting is handled for you: the payment is recorded against the invoice, the processor's fee is booked to an expense account, and the net deposit matches what actually hits your bank.

That fee split is the part most small businesses get wrong when processing payments outside their accounting system — revenue ends up recorded net of fees, which understates both income and expenses on your P&L.

Setup: ⚙️ Company Settings → 💳 Payment Gateway → Add Gateway. Enter your API keys from your Stripe or PayPal account, choose the deposit account and the fee expense account, then use Test Connection to confirm before going live.

Test mode first: Both processors provide test credentials. Run a test transaction end to end and confirm the entries land where you expect before switching to live keys.

1099 Electronic Filing

BizBooks Pro already knows what you paid each contractor over the year. The 1099 tool assembles the forms from that data and transmits them electronically through our filing partner, so you are not re-keying totals into a separate tax product every January.

Review the amounts on screen before anything is submitted. Contractor details come from your vendor records, so keeping tax IDs and addresses current during the year makes filing season considerably shorter.

QuickBooks Migration

Bring your chart of accounts, customers, vendors, employees and transaction history across from QuickBooks Desktop or QuickBooks Online. The importer suggests how each field should map and lets you correct it before a single record is written.

Social Security numbers are deliberately excluded. QuickBooks Desktop export files are plain text and frequently get emailed around during a migration. BizBooks Pro does not read the SSN column from those files — enter them yourself from the Employees screen afterward, where they are stored encrypted.

Statement Import

For institutions you would rather not link directly, or that aren't supported, import the statement file instead. CSV, Excel and PDF are all handled — and PDF statements are genuinely parsed into transactions rather than simply attached as a document.

Plenty of customers use this method permanently by preference, keeping no live connection to their bank at all.

Payroll Register Import

Keep running payroll wherever you run it today. Export the payroll register from Gusto, ADP or any provider that produces one, then import it so gross wages, employee withholdings and employer taxes post to the correct accounts.

Worth being precise about: this is an import of your payroll results, not a live two-way connection to a payroll provider. Direct payroll sync is on the roadmap but is not available yet.

Shopify

Connect a Shopify store and its orders, refunds and payouts are recorded in your books automatically. Setup starts on Shopify's side: install BizBooks Pro from the Shopify App Store and approve the connection there, choosing the store you want to link. Shopify then shows you a short connection code.

Back in BizBooks Pro, go to ⚙️ Company Settings → 🔌 Integrations, click Connect on the Shopify card, and enter that code. That is the whole handshake — you are never asked to type your store address, and you only approve the connection once. The code lasts 72 hours; if it runs out, open the app again from your Shopify admin and a fresh one is issued.

Choose your accounts first

Before anything can be recorded you must tell BizBooks Pro where Shopify activity should post. Click Accounts on the connected card. We suggest accounts from your existing chart, but nothing is applied until you confirm — getting this wrong would misstate your revenue quietly rather than throwing an error, so it is worth thirty seconds of attention.

Product sales and shipping charged to customers — income accounts
Sales tax collected — a liability account, never income
Shopify processing fees — an expense account
Clearing account and the bank account payouts land in — see below

Why there is a clearing account

A Shopify payout is a single deposit covering many orders, minus the fees Shopify kept. If your books recorded both the orders and the deposit, your revenue would be counted twice. So orders post into a clearing account, and the payout moves that money into your bank:

On each order: the clearing account is debited for the full amount the customer paid, split across sales, shipping and sales tax.
On each payout: your bank is debited for what actually arrived, the fees are expensed, and the clearing account is credited for the total.

Once everything has settled, the clearing account returns to zero. That makes its balance a useful health check: if it is not zero after payouts have cleared, something needs looking at.

Refunds

Refunds and partial refunds are recorded as their own entries, reversing sales and returning the sales tax to the liability account. They also pass through the clearing account, because Shopify recovers the money out of a later payout rather than taking it from your bank directly.

When does it sync? Automatically shortly after you open BizBooks Pro, and every fifteen minutes while it is running. Orders that arrive while your computer is switched off are held safely and recorded next time you open the app. You can also press ↻ Sync now on the Shopify card at any time.

Orders that are not recorded

If an order contains something BizBooks Pro cannot fully account for, it refuses to record it rather than guessing. A skipped order is a question you can answer; a wrong journal entry is a corrupted ledger. Common reasons:

Sales tax was collected but no sales tax account is mapped
The order is in a currency other than your books' currency
The order includes a tip, duty or adjustment with no account mapped for it
The amounts do not add up to what the customer paid — usually a gift card or store credit

Anything skipped appears on the Shopify card with the reason, and can be retried once you have fixed the cause. Check this occasionally: silently missing orders are the one thing that would make your books quietly wrong.

Duplicate deliveries are handled. Shopify often sends more than one notification for the same order. BizBooks Pro records each order exactly once, so your revenue is never doubled — including when a batch of held orders arrives together after your computer has been off.

Square

Status: built and tested; switches on in Settings once our listing is approved on the Square App Marketplace. Nothing to install on your side when it does.

Connect a Square account and every completed sale, refund and payout is written into your books. Setup is an ordinary Square sign-in: in ⚙️ Company Settings → 🔌 Integrations, click Connect on the Square card, approve BizBooks Pro in the Square window that opens, then come back and click Finish connecting.

Where each part of a sale goes

Click Accounts on the connected card. Beyond the usual sales, tax and fee accounts, Square asks for two that Shopify does not, because a Square seller takes money in ways Square never pays out:

Cash on hand — cash sales debit this account directly. They never touch the clearing account, since no payout will ever arrive to empty it.
Payments taken outside Square — for "Other" tenders (a cheque, a third-party terminal). Optional; a sale using one is held until you choose where that money landed.
Tips collected — a tip belongs to your staff, so it is kept out of sales. Map a liability account, or an income account if tips are yours.
Service charges — an income account if you keep them, a liability if they are passed on.

An order paid partly by card and partly by cash is split across both accounts on one entry.

Payouts and fees

Square reports the processing fee on each payout, so the fee is expensed exactly — no estimate. The payout entry debits your bank for the net deposit, debits fees, and credits the clearing account for the gross. A payout where refunds exceeded sales runs the other way and is recorded as money leaving the bank.

Refunds

When you refund by item in Square, the return carries its own tax figure and the entry reverses sales and tax exactly. A refund of the whole sale is reversed in the sale's own proportions. A partial refund entered as a bare amount cannot be split between revenue and tax honestly, so it posts to a refunds and allowances account if you have mapped one, and is held for you otherwise. Refunds handed back in cash credit cash on hand, not clearing.

What is not recorded, and why

Open or cancelled orders — nothing has been collected yet; the completed order arrives later.
Sales in a currency other than your books' currency.
A tip, service charge, cash or "Other" tender with no account mapped for it.
A payout that arrives without its breakdown — retried, because the fee would otherwise be unknown.

Everything held appears under Skipped on the Square card with the reason, and can be retried after you fix the cause.

WooCommerce

Status: built and tested; connects once BizBooks Pro for WooCommerce is approved in the WordPress.org plugin directory.

Install the plugin on your WordPress site and activate it. Its settings page (WooCommerce → BizBooks Pro) shows a ten-character connection code. In BizBooks Pro, open ⚙️ Company Settings → 🔌 Integrations, click Connect on the WooCommerce card and enter the code. Your store address is never typed anywhere and no BizBooks Pro login is stored in WordPress.

From then on the plugin sends each order the moment it is paid, again if its status changes, and each refund when it is issued. Orders that arrive while your computer is off are held by our connection service for up to 30 days and recorded the next time BizBooks Pro starts.

Why the accounts are set up by payment method

WooCommerce is a storefront; it never holds your money. Stripe, PayPal, WooPayments or whichever gateway you use collects it and pays you out on its own schedule, net of its own fees — and WooCommerce does not know what those fees were. So the mapping asks one question per gateway your store uses: where does money from this method land?

Card gateways (Stripe, PayPal, WooPayments, Square) — a clearing account. When the gateway's payout appears on your bank feed, record it against that account with the fee split out, and it returns to zero.
Cash on delivery, cheque, bank transfer — your bank or cash account directly. The money is yours the moment you mark the order paid.
Default — an account such as Undeposited Funds for any gateway you have not listed. Without a default, an order from an unmapped gateway is held rather than guessed.

Product sales, shipping charged, extra fee lines and tax each go to their own account; coupons can be shown as a separate discount line or netted into sales.

Refunds

A refund credits the same gateway account the sale debited. Refunds issued by line item reverse goods, shipping and tax exactly. A full refund entered as one amount is reversed in the order's own proportions. A partial refund entered as one amount is posted to a refunds and allowances account if you have mapped one, and held for you otherwise — refunding by line item in WooCommerce avoids the question.

Reinstalling or moving computers

Reinstalling the plugin, or connecting from a new computer, never duplicates anything already recorded. Request a new code from the plugin's settings page and connect again.

Clio

Status: built and tested; switches on once our listing is approved in the Clio App Directory. Requires the Law Firm edition.

Connect Clio and every bill you issue, and every payment Clio records against it, is written into your books. In ⚙️ Company Settings → 🔌 Integrations, click Connect on the Clio card, sign in to Clio in the window that opens, then click Finish connecting.

How a bill posts

When a bill is issued (not while it is a draft), receivables are debited for the total and the parts are kept apart the way your accountant and your bar expect: legal fee income, disbursements recovered from clients, tax on services as a liability, interest if charged, and a courtesy discount shown separately or netted into fees. If the bill's parts do not add up to its total — a credit applied at issue, say — it is held with both figures rather than recorded wrong.

Payments

A payment from the client's own funds debits your operating bank account and clears the receivable, dated when Clio recorded it. Several payments against one bill are each recorded once, even if Clio notifies you about the bill several times.

Trust money is never posted automatically. When a bill is paid out of the client's trust funds, the correct record is two entries plus the client trust ledger plus the state-bar client notice. BizBooks Pro's Trust screen produces all of that together under the same-client check; a connector writing only the ledger half would leave your three-way trust reconciliation broken. So a trust-applied payment appears under Skipped with the amount and client, and you apply it from Trust → Transfer to Operating. The mapping also refuses to let a trust account be chosen as the operating account.

Clients and matters

Before a bill posts, its client is matched to your customer list by email, then name. An exact match is linked; an unambiguous new client is created; anything doubtful is queued under Contacts on the Clio card for you to confirm — the bill still posts, and is attached once you answer. The bill's matter is linked to a BizBooks Pro matter, created from Clio's matter number if you have not set it up here, so a per-matter profit report is an ordinary filtered report. A bill spanning several matters is recorded but left untagged rather than credited to the wrong one.

Stripe Revenue & Payouts

Status: built and tested; switches on in Settings once our Stripe partner listing is approved.

This is not the Stripe card option on your invoices (that is set up under Payment Gateway Settings and records itself). This connector records everything else your business takes through Stripe — website checkout, subscriptions, a storefront that runs Stripe — and the payouts that settle it. Connect it from ⚙️ Company Settings → 🔌 Integrations: click Connect on the Stripe Revenue card, approve read-only access in the Stripe window, then Finish connecting.

How it posts

Each charge debits a Stripe clearing account for the gross and credits sales. If the charge belongs to a Stripe invoice, or came through Checkout with Stripe Tax, the tax portion is credited to your sales tax liability instead of revenue. A plain charge carries no tax information, so it is recorded entirely as sales — if you charge tax on plain payments, tell us and we will show you the invoice path.
Each refund reverses the sale (and its share of tax) and credits clearing, one entry per refund, so a second partial refund never repeats the first.
Each payout debits your bank for the net deposit, expenses the fees exactly as Stripe's balance transactions report them, and credits clearing for the gross. When everything has settled, clearing returns to zero.

Invoice payments are never counted twice. When a customer pays a BizBooks Pro invoice by card, the payment gateway already records the payment, the fee and the deposit. That same charge also reaches this connector, which recognises it and leaves it alone. You will not see those on the Skipped list — there is nothing to fix.

Not recorded, and why

Authorised-but-uncaptured, pending or failed charges — no money has moved.
Charges in a currency other than your books' currency.
A charge with tax on its invoice when no tax account is mapped.
A payout that arrives without its balance transactions — retried, because the fee would be unknown.

Zapier & Make

Status: Zapier is live now, by invitation. The app works in full — it is simply not listed in Zapier's public directory yet, so you open it with the link below rather than by searching for it. Make is built and still awaiting its directory review.

Connect BizBooks Pro to thousands of other applications without code. Nothing is typed into BizBooks Pro itself, and revoking the key in BizBooks Pro stops the tool the same minute.

Setting up Zapier

Open the BizBooks Pro app on Zapier. Click this invitation link while signed in to your Zapier account. This is a one-off step that makes BizBooks Pro appear in your Zap editor; without it, searching for us returns nothing.
Create an API key. In BizBooks Pro open ⚙️ Company Settings → 🔑 API keys and create a key — read for triggers, write if you also want actions. Copy it straight away; it is shown once and starts bb_live_.
Build your Zap. Add BizBooks Pro as the trigger or action, and paste the key when it asks you to connect an account. A good connection shows your key's name and its permissions, like Zapier (read,write).

Make follows the same shape — create a key, add the BizBooks Pro module — once its directory review is through.

Triggers

New invoice · Invoice paid · Payment received · New customer · New vendor · New bill. Each delivers the record as it exists in your books — invoice number, customer, amounts, status, dates.

Actions

Create customer · Create vendor · Create invoice (with line items) · Create bill (with line items), plus Find action result to read the outcome of any of them.

Timing is the one thing to understand. Your books live on your computer, not in a cloud, so a trigger fires and an action runs when BizBooks Pro is open — typically under a minute if it is open now, otherwise the next time you open it. An action step does not wait: it returns a command id and queued straight away, and you use Find Action Result afterwards to read what was created. A queued action stays waiting for up to 14 days, so an action raised on Friday still runs on Monday. Triggers work the other way round — they are raised by the work you do in your books, so they only occur while you are using BizBooks Pro anyway.

What an action may do

Exactly what the key allows. A read-only key can drive triggers and searches but every create is refused; a write key can create the records above and nothing else. The same allow-list that governs direct API calls governs actions from Zapier and Make — there is no back door.

Live Exchange Rates

Invoice in any of fifteen major currencies with the rate fetched automatically for the transaction date. A built-in converter is available for quick checks, and your base-currency reporting is reconciled underneath so the financial statements stay correct.

Security & Privacy

A few specifics worth stating plainly:

Card details never touch our software. Payment entry uses the processor's own secure fields, which is what keeps you out of PCI scope.
Bank credentials are never held by us. Authentication happens on your bank's own screen through the connection provider.
Sensitive stored fields are encrypted using a key unique to your installation, generated on first run and never shared.
Your ledger is not uploaded. Connections bring data in; they do not send your accounting records out.

Further detail is in Bank Connection Security.

What's Coming

These are being built and are not available today. We list them so you know where we are headed, not to imply they exist.

Industry connections — Buildertrend and Procore for construction, dotloop for brokerages, Donorbox for non-profits.

Square, WooCommerce, Clio, Stripe Revenue, Zapier and Make are finished and documented above; each switches on when its marketplace listing is approved. The public API and webhooks are live today — see the developer reference.

Requesting an Integration

Our build order comes from customer requests. If the tool you depend on isn't listed, submit it through the form on the Integrations page and it goes into the prioritization list. A person reads every submission.

Troubleshooting

A bank connection stopped importing

Banks periodically require you to re-authenticate, particularly after a password change or a security update on their end. Reconnect the account from the bank feed screen; historical transactions already imported are unaffected.

Test Connection fails on a payment gateway

Confirm you are using the correct key pair for the mode you selected — test keys with test mode, live keys with live mode. A test key checked into live mode is the most common cause. Also verify the key was copied whole, with no trailing space.

Payments succeed but the fee isn't recorded

The fee expense account must be selected in your gateway configuration. If it was left blank, set it in ⚙️ Company Settings → 💳 Payment Gateway; transactions recorded after that will split correctly.

An imported statement produced duplicate transactions

This usually means the same date range was imported twice, or the account has both a live feed and a manual import covering the same period. Review the affected date range and delete the duplicate batch — then pick one method per account going forward.

Still stuck? Reach us through Contact with the name of the connection and roughly when it stopped working. That is usually enough to identify the cause on the first reply.