Customers, vendors and owners

These pages hold who the money moves between: customers who owe you, vendors you owe, and officers and owners of the business itself.

Why they are worth keeping tidy

Every customer-level number depends on the customer list being one record per customer.

Duplicates are the usual problem, and they arrive honestly — the same business entered slightly differently by two people, or synced twice from two systems. The effect is not obvious: revenue splits across two records, so your largest customer looks like two medium ones, and customer concentration reads as safer than it is.

Records can be merged, which keeps the history rather than discarding it.

The same applies to vendors, where duplicates hide the opposite risk: the same bill paid twice under two spellings. See duplicate payments.

Parent customers

A customer can be recorded as belonging to a parent — useful where one client has several sites, properties or subsidiaries.

This matters for concentration more than for billing. Four separate accounts that are all the same property management company are one relationship, and losing it loses all four.

Officers and owners

Who owns and directs the business, which is what a lender, an insurer or an accountant will ask for and what nobody can find when they do.

It also matters for keeping the owner's own money visible. Draws and distributions are not business expenses, and recording them against a person rather than a category is what keeps them out of your cost figures.

The habit

Review the customer list once a quarter for duplicates and for names that have changed. Ten minutes, and it is the input every customer-level figure in the platform is built on.

Last reviewed 2026-07-29

Customers, vendors and owners — Omnyra Wiki | Omnyra