How it works
In integrations, the data model is the contract between your code and the data. It decides what an invoice is, which fields it has, how line items, taxes and currencies are represented, and how it links to a customer and its payments. A good shared model keeps platform-specific detail available while making the common case identical across sources.
Example
In one model an invoice links to its customer, its lines, its tax lines and the payments that settle it, so a collections tool can ask one question across every ledger.
In integrations
The Unify Graph is the shared data model under every Unify Int product: companies, accounts, ledgers, invoices, bills, payments, customers, suppliers, products, SKUs, inventory, orders, listings and campaigns. Finance and product data sit in the same model, so a SKU can link to the revenue it posted. The data model shapes everything downstream: your database, your API, your UI. Picking one that already reflects finance and commerce realities, such as multi-currency and variants, saves rework later.