A new nominal code is added. A project changes. A supplier record is updated.
For finance teams, small changes like these can quickly turn into repeat admin across multiple systems. Your accounting package may be up to date, but your ExpenseIn coding lists still need to catch up.
That’s why we’re introducing two-way data sync for supported accounting integrations.
Admins can now sync selected reference data from their connected accounting package into ExpenseIn, helping expense and invoice coding stay aligned with the finance structure already in place.
Depending on the integration, this can include:
Categories
Projects
Departments
Tax rates
Suppliers
That means teams can code expenses and invoices using the right accounts, tracking categories, BI codes, nominal codes, suppliers, vendors, tax codes, or other system-specific records, without finance having to rebuild the same lists by hand.
Every accounting package uses its own terminology. What one system calls nominal codes, another might call GL accounts, ledger accounts, BI codes, dimensions, tracking categories, classes, or locations.
ExpenseIn reflects that language in the sync settings, so admins see the terms that match their connected accounting package.
Two-way sync is available for supported integrations, including:
The sync is optional and configurable by dataset, so admins can choose which reference data to bring into ExpenseIn.
Where supported, admins can also filter what comes through before syncing. That might mean filtering by account type, code, name, classification, category, ledger type, subsidiary, location, or other integration-specific fields.
So instead of pulling through every available record, finance teams can keep ExpenseIn focused on the data their teams actually need.
Two-way sync supports your existing ExpenseIn setup. It doesn’t replace it.
Manual configuration remains available, which is useful where finance teams need to split categories, apply policy rules, or shape reporting in a way that works for their organisation.
Existing ExpenseIn data that does not exist in the accounting package will not be deleted as part of the sync.
Reference data sync helps finance teams reduce duplicate admin and keep coding data closer to the accounting system.
That means:
Fewer manual list updates across systems
More accurate coding options for employees and approvers
Cleaner expense and invoice data before posting
Better alignment between ExpenseIn and your accounting package
“We didn’t want this to be just another import. It was important that admins could choose the right data, use the terminology from their accounting system, and still keep control of how ExpenseIn is configured.”
To see how ExpenseIn works with your accounting setup, speak to our team or book a demo.
Business accounting can often be complex and time-consuming. Hence, we’re exploring the main benefits of integrating your expense management software with your accounting system.
