+1 480 485 7373
Microsoft Teams
What moves, and in which direction
Reimbursable and card spend are two different postings
The mistake we see most often is posting every expense report the same way. Out-of-pocket spend creates a debt to the employee that you must pay back. So it belongs on a payable, either an employee ledger entry or a vendor set up for that person. The card issuer has already paid for corporate card spend. So it belongs against the card's liability account, which clears when you pay the card statement.
Mixing the two makes employees look owed for money they spent on the company card. Or card balances never agree with the issuer's statement. Expensify marks each expense as reimbursable or not, and the integration should route each one to its own posting pattern.
Tax needs a decision too. US sales tax paid on expenses is normally not recoverable, so it simply becomes part of the cost. However, companies with use tax duties or operations abroad may want tax split out. Settle this before mapping categories, because it changes the shape of every journal line.
Ways to connect Expensify and Business Central
Scheduled export and import
Expensify exports approved reports in a template you define, and a journal import or configuration package brings them into Business Central.
- ✓No code and nothing to host
- ✓Someone must run it each pay cycle
- ✓A good test of the mapping before automating
Connector app
Connector apps from several vendors sync reports and reference data between the two systems on a schedule.
- ✓Check whether it posts journals, purchase invoices or both
- ✓Confirm dimension support before buying
- ✓A subscription on top of both products
API integration
Code or an integration platform reads approved reports from Expensify's API and posts them through Business Central's APIs, with your rules in between.
- ✓Handles splits across projects and entities
- ✓Needs monitoring and a named owner
- ✓Worth it mainly at higher volumes or with several companies
Mapping decisions to settle first
Category to account
Each Expensify category points at one G/L account. Fewer categories mean fewer miscodes, so we often trim the list before syncing.
Tags to dimensions
Department and project tags must match dimension values exactly, including blocked or closed ones, or posting fails.
People to payees
Decide whether staff are Business Central employees or vendors, since that shapes how you pay and report reimbursement.
Entity and currency
In a group of companies, route each report to the right company and decide whether foreign spend posts in its original currency.
From approved report to paid employee
- 1
Approve in Expensify
Managers and finance approve against policy there, so Business Central receives only final numbers.
- 2
Post in a reviewed batch
Approved reports arrive together and one person checks them before posting, grouped by pay cycle.
- 3
Pay the reimbursement
Either a Business Central payment run pays employees, or Expensify reimburses them and you record the payment against the payable.
- 4
Clear the card account
When you pay the card statement, the payment clears the liability account. Any gap points to a missing or duplicated transaction.
Expensify integration questions from finance teams
Does Expensify connect directly to Business Central?
Check Expensify's current integration list, because its direct connections change over time and can differ by plan. Where no direct connection suits you, export templates, a connector app or an API integration fill the gap. We compare the options against how you want expenses posted rather than starting from a tool.
Should expenses post as purchase invoices or journal lines?
Journal lines are simpler, while purchase invoices give one document per report that is easier to trace and attach receipts to. Companies that pay reimbursements through Business Central payment runs often prefer invoices against an employee vendor. Whichever you choose, apply it consistently so month-end review follows one pattern.
How are client projects handled?
Project tags in Expensify can map to Business Central projects. Billable expenses then reach the project, ready to invoice to the client. That needs the project and task structure agreed with project managers first. Non-billable costs can still carry a project dimension for internal reporting.
More Business Central Expensify integration questions
What happens when someone codes an expense to a closed project?
The posting fails in Business Central, which is the correct outcome, because blocked dimension values should not accept new costs. The fix is keeping the tag list in Expensify current, which is why reference data should flow from Business Central on a schedule. Failed reports go to a named person to correct and resend.
Is an integration worth it at low volumes?
Often not, because a company with a modest number of reports can import a monthly export file with little effort. Integration pays off when reports are frequent, spread across projects or entities, or when rekeying has already caused errors. The scoping call is where we weigh that honestly with you.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.