Expensify
DualEntry's chart of accounts flows into Expensify as categories and tags. Approved expenses and company card spend flow back as vendor bills and direct expenses.
Overview
Most teams can't close until expense reports arrive, and then someone re-keys them into the ledger. The Expensify integration with DualEntry removes that step. Expensify, Inc. (Nasdaq: EXFY) built a direct, two-way integration with DualEntry so that expenses land in the ledger already coded to the right accounts and departments, with no CSV exports in between.
Setup starts from your chart of accounts. DualEntry's chart of accounts syncs into Expensify as categories, your DualEntry classifications appear in Expensify as tags, and tax rates sync as well where they are available. That means the people submitting expenses in Expensify are choosing from the same accounts and dimensions your accountants use in DualEntry, so coding happens once, at the point of submission.
Data then flows back the other way. Out-of-pocket expenses post to DualEntry as vendor bills, and company card spend posts as direct expenses to the appropriate accounts. Reimbursements and card transactions stay automatically synchronized between the two platforms, so the ledger reflects what has actually been approved and paid without anyone re-entering it.
Expensify provides expense, travel, and corporate card management for 15 million users globally. The integration is available now; implementation details and setup instructions are in Expensify's integration documentation.
Chart of accounts (synced to Expensify as categories)
Classifications (synced to Expensify as tags)
Tax rates (where available)
Out-of-pocket expenses (posted to DualEntry as vendor bills)
Company card spend (posted to DualEntry as direct expenses)
Reimbursements
Card transactions
Data synced
The integration syncs the following data types:
- DualEntry's chart of accounts syncs into Expensify as expense categories, so submitters code spend against the same accounts finance uses in the ledger.
- DualEntry classifications appear in Expensify as tags, so department and other dimensional coding is captured when the expense is submitted.
- Tax rates sync to Expensify as well, where they are available in DualEntry.
- This is the setup that lets expenses arrive in DualEntry already coded, so it should be in place before expenses start flowing back.
- Employee out-of-pocket expenses submitted in Expensify post to DualEntry as vendor bills.
- Each bill carries the category and tag chosen in Expensify, which map back to the DualEntry account and classification, so no re-keying is needed.
- Reimbursements stay automatically synchronized between the two platforms once the bill is in DualEntry.
- Company card spend tracked in Expensify posts to DualEntry as direct expenses against the appropriate accounts.
- Card transactions remain automatically synchronized between Expensify and DualEntry, so the ledger reflects card activity without a manual export.
- Because card spend is coded with DualEntry's categories and tags at the point of submission, it lands in the right account and department.
Key Features
- Chart of accounts synced as categories
DualEntry's chart of accounts flows into Expensify as expense categories, so submitters code spend against the accounts finance actually uses. - Classifications as tags
DualEntry classifications appear in Expensify as tags, so department and other dimensional coding is captured at submission rather than added afterwards. - Tax rates included
Where tax rates are available in DualEntry, they sync to Expensify as well. - Out-of-pocket expenses become vendor bills
Approved employee expenses post to DualEntry as vendor bills, ready for the accounts payable workflow. - Company card spend becomes direct expenses
Card transactions post to DualEntry as direct expenses against the appropriate accounts. - Reimbursements and card transactions stay in sync
Once connected, reimbursements and card activity remain automatically synchronized between the two platforms. - Built and maintained by Expensify
This is a native integration developed by Expensify. Setup instructions live in Expensify's integration documentation.
FAQ
No. This is a native, direct integration built and maintained by Expensify, Inc. (Nasdaq: EXFY). There is no third-party connector platform or middleware sitting between Expensify and DualEntry.
Setup instructions and implementation details are published in Expensify's integration documentation.
Most teams can't close until expense reports arrive, and then someone re-keys them into the ledger. With this integration, expenses land in DualEntry already coded to the right account and department, so that step disappears.
DualEntry's chart of accounts and classifications are the categories and tags people pick in Expensify, so coding happens once, at submission, and finance stops exporting CSVs between the two tools.
Both ways. DualEntry sends its chart of accounts to Expensify as categories, its classifications as tags, and tax rates where available.
Expensify sends expenses back: out-of-pocket expenses post to DualEntry as vendor bills, and company card spend posts as direct expenses to the appropriate accounts. Reimbursements and card transactions stay automatically synchronized after that.
It depends on how the expense was paid. Out-of-pocket expenses that an employee needs to be reimbursed for arrive as vendor bills, ready for your accounts payable workflow.
Spend on a company card arrives as a direct expense against the account it was coded to in Expensify, since there is nothing to reimburse.
An Expensify account and a DualEntry organization. The integration is available now and is included with DualEntry.
Connection and setup are done from the Expensify side; follow the steps in Expensify's integration documentation, and make sure your DualEntry chart of accounts and classifications are in the shape you want before syncing, since those become the categories and tags your team will code against.
.avif)