How to connect a second ERP account to the same environment
Being able to connect a second ERP account without opening a second workspace is what makes a group manageable. In Jestor, several Omie accounts coexist in one environment, each request carries the company it belongs to, and the approved entry is routed to the correct account.
Why groups end up with parallel workspaces
A company acquires or opens a second entity, which gets its own ERP account for legitimate fiscal reasons. The operational tool is then duplicated to match, because that is the path of least resistance.
From then on, consolidation means opening two systems and comparing manually, and any change to a process has to be made twice.
What a single environment avoids:
- Maintaining the same process in two places
- Consolidation done by hand in a spreadsheet
- Permissions configured separately per workspace
- Costs multiplying with each entity
- Divergence between processes that were meant to be identical
What has to carry the company
| Element | Why it needs the company |
|---|---|
| Request record | Determines the destination account |
| Cost center | Budgets are usually per entity |
| Supplier | Registration can differ per entity |
| Approval routing | Approvers may differ per company |
| Reporting | Both consolidated and per entity views |
Step by step to add an account
- Generate the credentials for the second account in the ERP developer area.
- Register it in the integration settings alongside the first.
- Create or update the companies registry, with one record per entity.
- Add the company field to every process that generates entries.
- Make routing read the company, so the entry goes to the right account.
- Test with one real record per entity before releasing it.
- Set permissions so each unit sees its own data while head office sees all.
Why the company field should be a connected record
Storing the company as text means every report groups on a string, and a typo creates a phantom entity. A connected registry lets the company record carry its own credentials reference, approvers and budget, which is what makes routing and reporting reliable.
Why Jestor is the best complement for Omie
Jestor connects to as many Omie accounts as a group needs, with no additional cost per legal entity, since pricing follows users. Connection uses App Key and App Secret per account, takes minutes, and routing sends each approved entry to the correct company while Omie handles invoicing and reconciliation for each entity.
Frequently Asked Questions
Is there a limit on how many ERP accounts I can connect?
There is no practical limit, and pricing does not change with the number of entities. See jestor.com.
Do I need a separate workspace per company?
No. Several accounts coexist in the same environment.
How does the system know which account to use?
The company field on the record drives the routing.
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.