> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leara.se/llms.txt
> Use this file to discover all available pages before exploring further.

# Leara data model and master of record for each data type

> Learn which system owns each type of data in a Leara setup: accounting and invoices in your ERP, while stock, product data, and orders live in Leara.

Leara's data model defines which system is the master of record for each type of data. Knowing this helps you decide where to make changes and what to expect when systems sync.

## Master of record

| Data | Master |
| - | - |
| Accounting, invoice numbers, payment status | Your business system (ERP), for example Fortnox |
| Operational stock balance | Leara |
| Product data (variants, groups, attributes, images) | Leara |
| Orders (aggregated across channels) | Leara |

## What this means in practice

* **Invoices and accounting stay in your ERP.** Leara creates the invoice in the business system, which handles bookkeeping.
* **Stock is managed in Leara.** Leara keeps the operational balance, including reservations and available-to-sell, and mirrors it to connected channels.
* **Product data is richer in Leara.** Fields your business system often lacks, such as variants, product groups, attributes, images, and prices including VAT, live in Leara and reach your e-commerce.
* **One order book.** Orders from all channels are collected in Leara and can be picked from a warehouse or a store.

<Tip>
  Make product and stock changes in Leara, not directly in your webshop or ERP. Changes made elsewhere can be overwritten when Leara mirrors its data back.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.