Syncing Your Accounting Data with DualEntry

Overview

Slash’s integration with DualEntry allows your finance team to send current Slash activity into the same ERP where you manage your books. After you connect, you can review and categorize Slash transactions, apply the right accounting fields, and sync them to DualEntry from your Slash Accounting workflow.

Depending on your accounting setup, synced data can include transaction details, GL or account codes, departments, classes, locations, subsidiaries, vendor or merchant details, cardholder and memo information, and receipts or supporting details where available.

Slash does not replace DualEntry. Instead, Slash connects to DualEntry so spend and money movement from Slash can be mapped to the right accounting values, and posted into your ledger.

Before you begin

Before connecting DualEntry, make sure you have:

• An active DualEntry account
• Admin or Owner permissions in your Slash account
• Permission to authorize integrations in DualEntry
• Your DualEntry chart of accounts and accounting dimensions, such as departments, classes, locations, or subsidiaries, configured the way your finance team wants to use them

How to connect DualEntry to Slash

Step 1: Open Integrations or Accounting

From your Slash dashboard, go to Settings → Integrations and choose DualEntry. If you’re setting up accounting for the first time, you may also be prompted to choose your ERP from the Accounting page.

Step 2: Authorize the connection

Start the DualEntry connection flow and sign in to your DualEntry account when prompted. Authorize Slash to connect with DualEntry so Slash can use your accounting setup for categorization and sync.

Step 3: Confirm mappings and sync settings

Review the account mappings and sync preferences before turning on the integration. Mappings tell Slash how your Slash accounts and transaction fields should correspond to your DualEntry ledger and dimensions.

If you manage multiple entities or subsidiaries, confirm that each Slash account maps to the correct DualEntry entity or accounting structure before syncing transactions.

How to sync transactions from Slash to DualEntry

Step 1: Go to Accounting

Open Accounting from the sidebar in your Slash dashboard. Transactions are organized by review status, such as In Review, Ready to Sync, Synced, and Archived.

Step 2: Review and categorize transactions

In the “In Review” tab, assign the accounting values your finance team needs before posting the transaction to DualEntry. Depending on your setup, these may include a GL account, department, class, location, subsidiary, vendor or merchant, memo, or other dimensions.

Slash accounting mappings and automations can pre-fill fields for future transactions based on rules you set up, such as merchant, card, card group, merchant category, or virtual account. It’s best to review your pre-filled values before syncing.

Step 3: Mark transactions as Ready to Sync

Once a transaction has the correct accounting fields, move it to Ready to Sync. You can review transactions individually or select multiple transactions and update them in bulk.

Step 4: Sync to DualEntry

From the Ready to Sync tab, use the sync action to send the reviewed transactions to DualEntry. Successfully synced transactions move to the Synced tab.

If a sync fails, open the error details, update any missing or invalid accounting fields, and retry the sync.

What data can sync to DualEntry

The exact fields available depend on your Slash account, your DualEntry setup, and the accounting dimensions your business uses. Common synced details include:

• Transaction details: Amount, date, merchant, description, and other transaction context.
• GL or account codes: The account each transaction should post to in your ledger.
• Departments, classes, locations, and subsidiaries: Dimensions that help your team report by function, business line, location, or entity.
• Vendor or merchant details: Details that help match Slash activity to vendor records and reporting in DualEntry.
• Cardholder and memo information: Additional context for who made the purchase and why.
• Receipts and supporting details: Attachments or receipt information where available.

Best practices

• Confirm your DualEntry chart of accounts and dimensions are set up before connecting the integration.
• Review account mappings before syncing historical or high-volume transaction data.
• Use accounting mappings in Slash to reduce repetitive categorization work.
• Attach receipts and supporting documents before syncing when your accounting team needs them for close or audit support.
• Review failed sync messages instead of retrying repeatedly; the error usually points to a missing, inactive, or invalid accounting value.

Troubleshooting

If transactions aren’t syncing to DualEntry correctly:

• Confirm the DualEntry integration is still connected and authorized.
• Check that the transaction has all required accounting fields before syncing.
• Make sure the selected accounts, dimensions, vendors, or entities are still active in DualEntry.
• If you use multiple entities or subsidiaries, verify that the transaction is mapped to the correct entity.
• Open the sync error details in Slash, update the transaction or mapping, and retry.

Need more help?

If you can’t connect DualEntry, don’t see the accounting fields you expect, or continue to run into sync errors after updating the transaction, contact Slash Support using the in-app chat in your Slash dashboard.