Skip to content
Fire doors, fire stopping & fire risk assessment, one subscription EU hosted
Integrations

What syncs to your accounts, and what does not.

Three flows across four accounting packages, a CRM and Stripe, with a clear boundary. Read this before you connect anything, so you know what will and will not appear in your ledger.

3 min read FinanceOwnersIT

Section 01How to do it

  1. 01

    Connect the account once

    Authorise it from Integrations. Xero, QuickBooks, Sage or FreshBooks for accounting, HubSpot for CRM, Stripe for card payments.

  2. 02

    Paid status reaches your ledger

    When a client pays, the invoice is marked off in your ledger. Nobody reconciles it by hand and nobody forgets.

  3. 03

    Payment details follow it

    The Stripe payment that settled an invoice sits alongside it. That is what finance needs to match one payout against several invoices.

  4. 04

    Client records reach your CRM

    Your CRM and the app agree on who the client is. So the right company owns the right sites, and no duplicate appears at handover.

  5. 05

    Check it once, then stop thinking about it

    Raise a real invoice, pay it, and watch it land. Checking once beats assuming forever.

Section 02What the app actually does here

  • Invoices and payment records are sent to Xero, QuickBooks, Sage or FreshBooks
  • Companies, contacts, deals and deal line items are sent to HubSpot
  • Every write goes one way: we send to your ledger and never read your transactions back
  • We do look up a contact, a tax rate or a ledger account, because an invoice needs something to post against
  • Sending an invoice creates its customer or contact in your ledger if it is not there yet
  • Your client’s PO number goes with the invoice: to Xero as its reference, to FreshBooks as its PO number, and to QuickBooks when you have a custom sales field named PO or Purchase order. Sage does not get it
  • Purchase orders to your suppliers stay in the app. They are not sent to your accounts package
  • A failed send is retried by itself, up to ten times, waiting longer between each try
  • A single invoice can be sent straight away rather than waiting its turn
  • Each connection shows its recent sync activity and how many jobs failed. Fix the cause, and those jobs can be sent again
  • Xero is connected once, then pointed at the organisation, bank account and sales account to post to
  • Only the account owner can connect an account

Section 03What goes wrong

Every one of these has cost somebody real time. They are cheap to avoid and expensive to unwind.

Expecting your full chart of accounts to appear

This is not an accounting package. It sends paid status and payment details, not your ledger structure.

Two systems both creating clients

Decide which side owns a new client record, or you will be removing duplicates for months.

Connecting a test account and forgetting

Test credentials that stay connected send real invoices to nowhere.

Section 04Questions

Q01

Does it cost extra?

No. Every integration is included on every plan — there is no integrations tier.
Q02

Can we sync more than one accounting package?

One accounting connection at a time is the sensible shape. Two ledgers receiving the same paid status is a reconciliation problem, not a feature.
Q03

What about VAT?

Your accounting package stays the authority on tax. Each invoice records the VAT rate it was issued at.
Q04

What if a job keeps failing?

After its retries it is marked failed and counted on that connection’s sync activity. Fix the cause — often reconnecting — then send those jobs again.

Section 05Related

Start today

Guides help. Doing it helps more.

Everything above is checkable inside the trial, on a real building, with nothing held back and no card required.

7-day trial · No card · Cancel anytime