How it works
An ERP combines a general ledger with operational modules: procurement, sales orders, inventory, fulfillment, projects and often manufacturing. Transactions in one module post to the others, so a received purchase order updates stock and creates a liability. Mid-market and enterprise ERPs add multi-entity books, dimensions such as departments and classes, approval workflows and heavy customization.
Example
A distributor runs NetSuite with three subsidiaries. A sales order in the US entity reserves stock, ships, invoices the customer and posts revenue, all inside the ERP.
In integrations
ERPs are where integrations get hard: custom fields, custom records, subsidiaries and approvals vary by customer. The Unify ERP API is designed for NetSuite, Sage Intacct, Microsoft Dynamics 365, Acumatica, SAP and Oracle, with subsidiaries, dimensions and approval states in the model. Status per platform is listed on each integration page. ERP coverage is often what decides whether a software company can move upmarket. Prospects running NetSuite or Sage Intacct expect integrations to handle their entities, custom fields and approvals, not just the basics.