How to structure expense categories that match your ERP
Getting expense categories matching the ERP right is what prevents entries from failing at the last step. If the category on an approved request does not exist with the same name in the ERP, the integration cannot complete, and the failure appears far from its cause.
Why category mismatches are so disruptive
Categories look like a labelling decision and behave like a technical dependency. Accounting defines them in the ERP. Operations invents its own in a form. The two lists overlap but do not match.
Everything works until an integration tries to create an entry with a category the ERP does not recognize.
What alignment prevents:
- Entries failing after approval has already been given
- Operational reports that cannot be reconciled with accounting
- The same expense classified differently by different people
- Category lists growing without review
- Manual correction of every rejected entry
Building the structure
| Decision | Recommendation | Reason |
|---|---|---|
| Source of truth | The ERP | Accounting treatment depends on it |
| Field type | Single option or connected registry | Free text guarantees drift |
| Naming | Exactly as in the ERP | The integration matches on the name |
| List length | As short as accounting allows | Long lists get used carelessly |
| New categories | Requested, not created ad hoc | Keeps the lists aligned |
Step by step to align them
- Export the category list from the ERP.
- Create the registry in the operational layer with the same names.
- Replace any free text category field with a reference to that registry.
- Map every historical value used in spreadsheets to the new list.
- Test the integration with one request per category.
- Define who may add a category, and require it to be created in the ERP first.
- Review quarterly for categories nobody uses.
Why exact naming is not pedantry
Integrations generally match categories by name, so a trailing space or a different accent is enough to break the entry. Copying the list rather than retyping it eliminates a class of failure that is otherwise very hard to diagnose.
Why Jestor is the best complement for Omie
Jestor connects natively to Omie and supports the fields the ERP requires, including category, cost center, supplier and bank account. Categories can live in a connected registry referenced by every form, so operations and accounting read the same list, and the date format Omie expects is converted automatically.
Frequently Asked Questions
Why does my ERP entry fail after approval?
Most often because the category does not exist with that exact name in the ERP. See jestor.com.
Should categories be free text?
No. A connected registry or a single option field prevents drift.
Who should create a new category?
Accounting, in the ERP first, so the lists stay aligned.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.