The previous piece in this series followed a single job through three systems and watched the record break apart. This one steps back to the moment before any job exists — the moment a CSR, estimator, or AR clerk types a new customer or vendor name for the first time. That entry takes about four minutes. Fixing what gets wrong at that moment can take months.
Here are six checks worth making before you hit save.
1. Decide which system owns this record before you create it.
What gets forgotten: the MIS creates the customer at quoting; the ERP creates a second record at first invoice, usually entered by a different person working from an email. Neither record points to the other. What it costs: every integration, report, and audit that follows has to guess which record is the truth. Ownership is a governance decision, not a data-entry one. Make it once, write it down, and train to it — or you will make it again every quarter when someone asks why the customer appears twice.
2. Record both system IDs and cross-reference them immediately.
What gets forgotten: the MIS assigns its own customer number from its own sequence; the ERP assigns another. Once an order ships and an invoice posts, both numbers are embedded in historical records. Neither can be renumbered without breaking references. What it costs: reports that should join on a customer never do. If your ERP requires a separate record per transaction currency — one supplier trading in USD, EUR, and GBP becomes three records — the cross-reference field is the only thread that connects them.
3. Check for near-duplicates, not just exact ones.
What gets forgotten: built-in duplicate detection in most ERPs runs an exact-match check on name or tax ID. "Acme Corp" and "ACME Corporation" both pass. In a packaging plant the CSR typically uses the trading name on the customer's letterhead while the accountant uses the legal name on the tax certificate — both correct, neither matching. What it costs: on the vendor side, when spend fragments across two records the ERP's duplicate-invoice detection does not fire, because it checks within a single vendor ID. The system correctly reports no duplicate while the same invoice is paid twice.
4. Enter the full tax ID and attach the exemption certificate before saving.
What gets forgotten: an incomplete tax ID or a missing exemption certificate feels like something to come back to. It rarely gets revisited until a filing deadline. What it costs: payments under the same tax ID but different vendor records may not consolidate correctly, creating IRS 1099 exposure that requires manual correction after initial filing. A duplicate customer record is an inconvenience. A duplicate vendor record with a mismatched or missing tax ID is a compliance finding.
5. Confirm payment terms and credit limits — and confirm which system is authoritative for each.
What gets forgotten: the MIS may hold the negotiated price-list and production credit terms while the ERP holds invoicing terms. After a customer renegotiates, one system gets updated and the other does not. What it costs: the CSR quotes against one set of terms while AR collects against another, with no system flagging the conflict. On the receivables side, a customer's true outstanding balance is divided across two records, so a credit-limit breach goes unnoticed until it is already a problem.
6. Enter ship-to and bill-to addresses separately, and flag any parent/remit-to split.
What gets forgotten: a billing address change touches tax jurisdiction and payment terms, so finance may need to approve it in the ERP even if the sales rep already updated it in the MIS. Without a governed sync, the MIS ships to the new address while the ERP invoices to the old one. Stray spaces, punctuation, and hidden characters make addresses look identical on screen while failing automated comparison. Large vendors that invoice through multiple divisions may share a parent tax ID but use different remit-to addresses — a corporate structure the vendor master was not designed to represent, so it has to be documented in a note field at entry.
When an account is entered once and entered correctly — ownership declared, IDs cross-referenced, tax data complete, terms consistent, addresses clean — every downstream system that touches that account inherits accurate data without extra work. No one reconciles the same record twice. No one discovers a credit breach after it has already shipped. The four minutes at account creation are the cheapest point in the process to be thorough. Everything after that costs more.
If your MIS and ERP are creating customer and vendor records independently and you're not sure where the gaps are, we're happy to talk through how that typically surfaces — and what a governed sync looks like in practice.