New customer setup across four tools, and how to automate it

To set up a new customer across four tools without typing it four times, make one system the source of truth and agree on what a complete customer record contains. Then let an automation create the matching records in your other tools, while a person approves credit, reviews tax certificates and decides possible duplicates. If the CRM is your source, the customer is entered once there and the automation creates it in the other three.

Why setup takes so long, and what it costs later

A new customer may need to exist in four places: the CRM where the deal was won, the ERP where orders are entered, the accounting system that sends invoices (if it’s separate from the ERP) and a shipping or support tool. Each wants the details in its own format, and each gets typed separately.

The typing is the visible cost. The larger costs show up later:

• An invoice goes to the buyer instead of accounts payable, and sits unpaid.
• A customer is charged sales tax it shouldn’t pay, or a sale goes untaxed with no certificate on file.
• The first order waits because the customer exists in the CRM but not yet in the ERP.
• The same company ends up in a system twice, under two slightly different names.
• Terms go out before anyone approved credit.

Pick a source of truth, and an owner for each field

Choose one system where a customer is created and approved first. The CRM is a natural choice, because that’s where the deal is won. Treat the customer as approved once sales and finance sign off. The other systems copy from it, and changes happen there first. With the CRM as the source, the automation creates records in the ERP, the accounting system and the shipping tool. That’s three tools, not four, because the fourth is where the customer started.

One system creates the customer, but each field still needs one owner. Let sales own names, contacts and the account owner. Let finance own terms, credit limit and tax status, even if those live in the ERP. Changes then flow one way: a new credit limit set in the ERP shows up in the CRM for reference, and nobody retypes it. If you run Microsoft 365 with QuickBooks or NetSuite, the handoffs worth automating first shows where this one fits among the others.

A setup checklist for each system

In the CRM (the source)

• Legal name, any trade name and the website or email domain
• Buyer, accounts payable contact and receiving contact
• Account owner
• Approval status, with who approved it and when
• The customer’s ID in each of the other systems

In the ERP

• Bill-to address and every ship-to address
• Payment terms and credit limit, exactly as approved
• Tax status, with the certificate on file if the customer claims an exemption
• Price level or contract pricing
• Sales rep, default warehouse and shipping method

In the accounting system, if it’s separate

• The same customer ID and legal name as the ERP
• Where invoices go: the accounts payable email or the customer’s portal
• Whether every invoice needs the customer’s PO number
• Terms and tax settings that match the ERP

In the shipping or support tool

• Ship-to addresses spelled exactly as in the ERP
• Receiving hours, dock notes and a delivery contact
• The customer’s carrier account number, if it pays its own freight

The accounts payable contact matters most later: it’s where every invoice and every overdue reminder will go.

How to prevent duplicates

Check before you create, in every system, not only the source. Clean up the name first (drop “Inc.”, “LLC” and punctuation), then search by name, email domain, phone number and address. Your tools may already help, with different defaults:

• HubSpot uses the company domain name to deduplicate companies, and alerts you if you manually create a company with the same domain as an existing one.
• In Salesforce, the standard account duplicate rule alerts the user on create but still allows the record to be created.
• NetSuite duplicate detection can alert you to possible duplicate customers on fields you choose. A record must match on all of them, and a near-match setting can help catch typos.

Whatever your tools do, send possible duplicates to a person and never merge automatically. Two branches of one company may need separate records, and only someone who knows the account can say. Then store each system’s ID on the source record, so later updates reach the right record.

How to approve credit and terms

Decide credit before the first invoice, not after the first late payment:

1. Collect a credit application: the legal name, years in business, bank and trade references and an accounts payable contact.
2. Check it against a written policy: which terms are standard, and who can approve which credit limit.
3. Record the decision with the customer: the limit, the terms, who approved them, the date and a date to review them.
4. Decide what happens before approval: for example, require prepayment or a card for the first order, or hold it.

An automation can assemble the file, check it against your policy and flag anything outside it. Approving credit stays with a person.

Tax certificates on both sides of the river

If you sell from the St. Louis area, new customers may claim an exemption or buy for resale in Missouri or in the Metro East in Illinois. Whether a customer qualifies, and which certificate applies to a sale, is for your tax adviser to decide. Here is what the two states’ official pages say.

Missouri: Form 149

• Form 149, the Sales and Use Tax Exemption Certificate, is completed and signed by the purchaser, who checks the exemption being claimed, such as resale or manufacturing.
• The form cautions that for the seller to accept it in good faith, the seller “must exercise care that the property being sold is exempt.”
• The Department of Revenue’s business registration FAQ says a buyer purchasing goods to resell to a retailer provides the seller with a completed Form 149, and the seller collects it.
• Missouri’s rule on exemption certificates says the seller must obtain and keep a certificate for any exempt sale, or may be held liable for the tax. A certificate on file can cover future sales unless it doesn’t apply to them or the seller can no longer rely on it in good faith, and an unsigned certificate is not valid.

Illinois: Form CRT-61

• Form CRT-61, Certificate of Resale, is a statement signed by the purchaser that the goods are for resale. It can describe a specific purchase or serve as a blanket certificate for purchases from that seller.
• The CRT-61 instructions say it is the seller’s responsibility to verify that the purchaser’s Illinois account ID is valid and active, which you can check with the Verify a Registered Business link at MyTax Illinois.
• The same instructions say the seller keeps the certificate for at least three and a half years, and that blanket certificates should be updated at least once every three years.

For your setup process, a few habits follow:

• Don’t mark a customer exempt in any system until a person has reviewed the certificate.
• Store the certificate on the customer record with its state, type and signature date, plus a renewal date where one applies.
• Record the date you verified an Illinois account ID.
• Agree with your tax adviser what happens to orders while a certificate is missing.

How the automation works

Once the rules are set, an automation can run the setup in seven steps:

1. A customer is approved in the source system.
2. The automation reads the record and checks it against your checklist.
3. It searches the other systems for a possible duplicate.
4. It creates the customer in each of the other tools, in each one’s format.
5. It writes each system’s customer ID back to the source record.
6. It flags gaps for a person: a missing certificate, terms outside policy, a possible duplicate.
7. It logs every run, so you can see what was created where.

A person still approves credit and any terms outside your policy, reviews tax certificates, decides whether a possible duplicate is real and handles anything your team marks for review.

Kestrel’s agent, now in development, is designed to notice a customer approved in your source system, create the matching records in each of your other tools and flag a missing certificate, an out-of-policy term or a possible duplicate for a person. Nothing runs until your team switches it on, and every run is logged. See customer setup automation.

Your setup checklist

• One source system, and one owner for each field
• Legal name, trade name and website or email domain
• Billing address and every ship-to address
• Buyer, accounts payable and receiving contacts
• Payment terms and credit limit, with who approved them and when
• Tax status, with the certificate reviewed and stored (for example Missouri Form 149 or Illinois Form CRT-61, as your tax adviser directs)
• Illinois account ID verified, with the date
• A renewal date for any blanket certificate
• Price level or contract pricing
• Sales rep or account owner
• Shipping method, receiving notes and carrier account number
• A duplicate check in every system
• Each system’s customer ID stored on the source record