Master lists vs transactions: the two kinds of accounting data

If you understand nothing else about accounting data before a migration, understand this: there are only two kinds of it. Every accounting system splits its data into master lists and transactions — the nouns and the verbs of the books. Getting the distinction clear makes migrations, imports and troubleshooting suddenly make sense.

Master lists are the nouns

The relatively stable things the business refers to over and over: the chart of accounts, customers and vendors, items, and supporting lists like classes, price levels and tax codes. Master data changes slowly and is referenced constantly — a customer exists once; a thousand invoices point at them.

Transactions are the verbs

The events — the things that happen: invoices, sales receipts, payments, bills, purchase orders, deposits, checks, journal entries. Every transaction references master data: an invoice points at a customer, lists items, and posts to accounts.

Why the order is everything

Because transactions reference master data, the master lists must exist first. This is the single rule behind clean imports: chart of accounts, then names and items, then transactions on top. Import a transaction before the customer it points to exists and it’s rejected — “name not found.” Half of all import errors trace to doing this in the wrong order.

Beyond migrations

The same lens explains everyday problems. A duplicate customer splits balances across transactions. A mis-typed account distorts every transaction that touches it. Fix master data and the transactions built on it fall into line.