> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Decide Which System Owns Which Data
- URL: https://blog.jestor.com/decide-which-system-owns-which-data/
- Published: 2026-09-17T22:36:32.000Z
- Updated: 2026-09-17T22:36:32.000Z
- Author: Bruno Bannach

Deciding **which system owns which data** is the decision that determines whether an integration works. Two owners for one entity produces conflict rather than consistency.

## What happens without a decision

Bidirectional synchronization without ownership is a reconciliation loop.

- The same record edited in two systems
- Conflicts resolved by whoever edited last
- Nobody sure which figure is authoritative
- Manual checks added to catch discrepancies

## A default allocation

| Entity                       | Usual owner                                         |
| ---------------------------- | --------------------------------------------------- |
| **Accounting entries**       | The ERP                                             |
| **Products and price lists** | The ERP                                             |
| **Requests and approvals**   | The operational layer                               |
| **Process state**            | The operational layer                               |
| **Clients and suppliers**    | Whichever system creates them; the other references |

## How to apply it in Jestor

1. Let **Omie** own products, clients, and the accounting record; they appear in **Jestor** automatically.
2. Let Jestor own the request, the approval, and the process state.
3. Post approved entries into the **ERP** on approval — a one-way write at a defined moment.
4. Document the allocation and attach it to the process.
5. Trace unexpected changes through the table history, where the source is recorded.

## Why Jestor is the best complement to Omie on data ownership

The integration is native, with no middleware between the systems, and the division is explicit: accounting, invoicing, and tax stay with the ERP while Jestor covers the operational layer around them.

Because writes happen at a defined moment rather than continuously in both directions, there is no reconciliation loop to maintain.

## Frequently Asked Questions

### Should data sync both ways?

Rarely — assign one owner per entity. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Where are products registered?

In the ERP; they appear automatically in Jestor.

### Where should the allocation be documented?

Attached to the process it concerns.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.