Skip to main content
Coming soon. The Sage Intacct integration isn’t generally available yet. This page is published ahead of release — if you’d like early access, contact your Dash.fi account manager.
Sage Intacct integration requires Company Admin access in Sage Intacct to complete the connection and configure entity and GL account mappings.

Before you start

You’ll need:
  • Sage Intacct with Web Services access enabled
  • Company Admin access in Sage Intacct
  • Administrator access in Dash.fi

Step 1: Open accounting setup

  1. Log in to Dash.fi and go to Accounting in the left-hand menu.
  2. Select Card Transactions.
  3. If no accounting platform is connected, you’ll see a setup prompt. Click Setup Integration.
  4. You’ll be taken to Settings → Integrations. Select Sage Intacct.

Step 2: Choose your integration mode

Dash.fi offers two modes:
ModeHow it worksBest for
Dash.fi Sync Mode (recommended)Your team codes transactions, attaches receipts, and assigns vendors inside Dash.fi. Reviewed transactions sync to Sage Intacct.Teams who want all spend management in one place
Bank FeedA raw transaction feed is pushed directly into Sage Intacct.Teams who prefer to do all coding in Sage Intacct

Step 3: Connect to Sage Intacct

  1. Click Connect for your chosen mode.
  2. You’ll be redirected to Sage Intacct’s authentication screen. Sign in with your Company Admin credentials.
  3. Approve the integration request.
  4. Dash.fi redirects back to the app and begins the initial sync.
Wait for the initial sync to complete. Dash.fi pulls your chart of accounts, entities, locations, and departments from Sage Intacct.

Step 4: Set up your account map

Once the sync finishes, you’ll be prompted to map your Dash.fi credit card to an account in Sage Intacct. You can create a new account or link to an existing one.

Creating a new account

Fill in the following fields:
FieldNotes
Account nameA clear label, for example Dash.fi Corporate Card
Account numberMust be exactly 5 characters, for example 10000
Bank NameYour card-issuing bank, for example Chase Bank
Bank Account NameUp to 20 characters, for example Dashfi CC
Bank Account NumberYour card or bank account number, up to 44 characters
LocationOptional. Selecting a location filters the available entities below
EntityRequired. The Sage Intacct entity that card transactions should post to

Using an existing account

Select the account from the list, then pick the Entity that transactions should post to.

Journal Type (optional)

After choosing your account, you can specify a Sage Intacct journal type (for example APJ or GJ). If left blank, Sage Intacct uses its default journal. Click Continue. The account status should change to Active.

Step 5: Map expense categories

Go to Accounting → Categories. Map each Dash.fi spend category to the appropriate GL expense account in Sage Intacct. Dash.fi suggests the most likely GL code for each category — review, confirm, or adjust. Mappings apply to all future transactions automatically and can be overridden per transaction. If your Sage Intacct account uses departments or locations as tracking dimensions, you can assign them per transaction in the Card Transactions view.

Step 6: Verify the connection

Return to Accounting → Card Transactions. Cleared transactions should now be visible and ready for review.

Reviewing and syncing transactions

With the integration set up, your workflow for each cleared transaction is:
  1. Review the merchant, amount, category, GL code, vendor, and memo
  2. Assign department and location dimensions if your Sage Intacct setup uses them
  3. Attach a receipt if required
  4. Click Mark as ready — the transaction moves to the sync queue
  5. Dash.fi syncs ready transactions to Sage Intacct in batches, typically within the hour
Transactions can be edited up until the batch picks them up. Once synced, the Sage Intacct record is the source of truth.

Coding transactions with departments and locations

If your Sage Intacct account uses departments and locations as tracking dimensions, the GL code picker on Accounting → Card Transactions expands into a cascading selector:
  1. Pick the GL code for the transaction.
  2. A Department field appears below it — optional.
  3. A Location field appears below that — optional.
A few things to know:
  • Department and location are optional. You can mark a transaction ready without setting either.
  • Locations are scoped to the entity mapped to your Dash.fi card account, so you’ll only see locations that belong to that entity.
  • The entity itself is fixed at connection time — you choose the department and location per transaction, not the entity.

What you need before marking a transaction ready

A transaction can’t be marked ready to sync until it has:
  • A spend category
  • A GL code (Accounting Code)
  • An accounting date
  • A memo
  • A customer — only if the transaction is marked billable
Department and location are not required. If anything’s missing, the Ready control stays disabled and tells you which fields to complete.

FAQ

Sage Intacct uses entities to represent distinct companies or business units in a multi-entity environment. Selecting an entity tells Dash.fi which company’s books card transactions should post to.
Yes. During setup you select the entity that Dash.fi transactions should post to. If you need to post to multiple entities, contact support.
Sage Intacct journals are the mechanism used to record transactions. Common types are AP journals (APJ) and general journals (GJ). If you’re unsure which to use, check with your Sage Intacct administrator. Leaving this blank uses the platform default.
Sage Intacct requires GL account numbers to be exactly 5 characters. Check your Sage Intacct chart of accounts if you’re unsure which number to use.
When you pay your Dash.fi balance, that payment flows into Sage Intacct through your bank account feed. Syncing it through Dash.fi as well would create a duplicate entry. The Payments tab in Dash.fi is for reference only.