Skip to main content
Dash.fi’s accounting integration pushes card transaction activity directly into your accounting or ERP platform. When a card transaction clears, it appears in a review queue where your team confirms the expense category, GL code, vendor, and memo. Once reviewed, Dash.fi batches and syncs the transactions directly to your accounting platform — no manual data entry required. The connection is OAuth-based, so your accounting credentials never touch Dash.fi directly.

Supported platforms

PlatformStatus
QuickBooks OnlineAvailable
QuickBooks DesktopAvailable
XeroAvailable
NetSuiteAvailable
Sage IntacctComing soon

How the sync works

The Accounting section in Dash.fi has four areas:
  • Card Transactions — the main review and sync queue. Every cleared card charge appears here for categorisation before it syncs to your GL.
  • Categories — maps Dash.fi spend categories to GL codes in your accounting platform. AI-powered suggestions accelerate initial setup.
  • Account Map — maps your Dash.fi credit card account to the corresponding GL account in your accounting platform. This must be completed before any transactions can sync.
  • Payments — a view of your Dash.fi bill payments.

Transaction lifecycle

Each transaction moves through three states:
Pending → Ready → Synced
  • Pending — transaction has cleared and is waiting to be reviewed
  • Ready — reviewed and approved for sync; will be picked up in the next batch (typically within the hour)
  • Synced — pushed to your accounting platform and posted to the GL
Transactions can be edited right up until the sync batch picks them up. Once synced, the accounting platform record is the source of truth.

Card Transactions tabs

Accounting → Card Transactions has three tabs:
  • Ready to sync — transactions you’ve reviewed and queued for the next sync batch.
  • Needs review — transactions whose last sync attempt failed. Each one needs action before it can sync. The count next to the tab label shows how many are waiting.
  • History — everything that’s already synced, with sync timestamps.

Vendor sync status icons

The vendor column on the Card Transactions table shows an icon next to the vendor name. It reflects the state of that vendor in your accounting platform:
IconMeaningWhat to do
Green plusDash.fi will create a new vendor in your accounting platform on the next sync.Nothing — Dash.fi handles it.
Spinning loaderThe vendor is syncing. The transaction syncs on the next run once the vendor exists.Wait for the next sync cycle.
Red warning triangleDash.fi couldn’t create the vendor in your accounting platform, usually due to a name conflict.Open the vendor and link it to an existing record — see Map to your accounting platform.
No iconThe vendor is already linked and ready to use.Nothing.

Clearing the Needs review queue

When an expense fails to sync, its Status pill shows Sync failed with a tooltip explaining the reason. The most common cause is a Vendor creation failed error. To clear it:
  1. Go to Accounting → Card Transactions → Needs review
  2. Open a transaction in the list
  3. Follow the action in the tooltip — usually, link the vendor to an existing record in your accounting platform
  4. Re-open the transaction and mark it ready to sync
Once you link the vendor, the Sync failed tooltip updates to confirm the connection and prompts you to mark the expense ready again. The next sync batch picks up the transaction and moves it from Needs review to History.

What accounting automation handles

Beyond the basic sync, Dash.fi’s accounting automation reduces the manual work of closing the books each month:
  • AI merchant mapping — Dash.fi learns from your category decisions and automatically suggests the right GL code and category for recurring vendors. Over time, most transactions are pre-categorised and require only a quick review.
  • Dedicated accountant view — users with the Accountant or Bookkeeper role have a focused view of the sync queue, with batch review tools for processing large transaction volumes efficiently.
  • Vendor mapping — each vendor in Dash.fi can be mapped to the corresponding vendor record in your accounting platform, ensuring bill payments post to the right payee in your GL.
  • Multi-entity support — if your accounting platform supports multiple subsidiaries or entities (for example, NetSuite OneWorld), you can map different Dash.fi accounts or card groups to different entities.
  • Bill pay sync — payments processed through Dash.fi Bill Pay are visible in the Payments tab and sync to your platform alongside card transactions.

Get connected

Choose your platform for step-by-step setup instructions.

QuickBooks Online

Connect QuickBooks Online

QuickBooks Desktop

Connect QuickBooks Desktop

Xero

Connect Xero

NetSuite

Connect NetSuite