Approve Every New Customer Before the First Order

A sales rep at a mid-size maker closes a promising lead at a trade show. By Tuesday the prospect is in the customer master with a credit limit the rep picked, a payment term the rep guessed, and a bank account the prospect sent over email. The first order ships Wednesday. The first invoice is raised at month-end. Sixty days later the invoice is still unpaid, the prospect's parent company is in restructuring, and the credit analyst did not even know this customer existed until collections began calling. This is not a rare story. Ungoverned onboarding is one of the most common sources of bad debt that mid-size Japanese manufacturers carry, and a single un-vetted customer can wipe out a quarter of margin.

The root cause is not a careless rep. The root cause is a customer master that anyone in sales can write to, paired with an order and billing flow that trusts whatever credit limit and bank account the master holds. Fixing it does not mean adding another standalone tool. It means moving onboarding into the same core business system that already runs your approvals, so that a new customer is not authorized to be added, shipped to, or invoiced until sales and a credit or finance check have both cleared it. The approval gate is built and live today; the automatic push of that cleared status into the downstream quote, order, and billing records is on the roadmap.

Why an Open Customer Master Quietly Builds Bad Debt

A customer master looks like a harmless contact list. In reality it is one of the most sensitive records in any ERP, because every line in it is a potential revenue commitment and a potential collection risk. When the master is open to sales, three categories of loss follow.

The first is credit risk that walks in the front door. A rep under pressure to hit quota has every incentive to set a generous credit limit and an aggressive payment term. Without a credit check against the prospect's financials, payment history, and industry risk, the company is effectively lending money to a stranger. Uncontrolled trade credit is how mid-size manufacturers end up carrying receivables that never convert to cash.

The second is fraud and identity risk. A prospect might have a valid registration number and a polished website and still be a shell set up to receive goods and disappear, a related party of an employee, or an entity already on an internal blacklist. Onboarding that prospect without a finance or compliance review imports risk that you only discover after goods have shipped and the invoice has gone quiet. In industries with lot control, the exposure extends to warranty and recall risk downstream.

The third is silent drift and weak governance. Even honest customers change. They change ownership, they change bank accounts, they merge. When onboarding is a free-for-all, those changes also become a free-for-all, and a customer record that started clean slowly accumulates unverified edits. Internal-control frameworks, from J-SOX to the broader Committee of Sponsoring Organizations guidance, converge on the same answer: changes to the customer master must be authorized, reviewed, and logged. An open master is none of those things.

The Control That Actually Stops the Risk

The fix is a gate. A new customer cannot enter the customer master until a defined set of approvals has cleared. Sales confirms the commercial relationship, the intended products, and the negotiated terms. Credit or finance confirms the prospect's financial health and sets the credit limit. Compliance or legal can be added for higher-risk industries. None of them can sign for the others, and the customer does not exist in the master until the required approvers have said yes.

This is not a hypothetical design. The workflow engine inside a modern core business system runs this approval as a first-class flow. A new-customer request opens with the prospect's legal name, registration number, intended payment terms, requested credit limit, bank details, and the sales owner. The moment it is submitted, the approval tasks route to the right roles. Sales leadership confirms the commercial terms. Credit or finance pulls the prospect's financials and checks them against company policy. Each works in their own queue. The customer is blocked until the required clearances complete.

The reason routing matters is that the gate survives reorganizations. Approvals route to the role, the position, or the department rather than to a named person, so when someone changes jobs the control still routes correctly. For a mid-size manufacturer growing into formal internal control, this is one of the highest-value controls you can build, because customer master changes are exactly where revenue risk and governance gaps tend to hide.

What the Approval Captures, and Why That Record Matters

When the last approver signs, the system does not just flip a status. It freezes a snapshot of exactly what was approved: the prospect's name at the moment of approval, the credit limit finance set, the payment terms sales negotiated, the bank account that was vetted. That snapshot is the audit trail. If anyone later edits the credit limit or the bank account, the change is its own new request, layered on top of the original record.

This is the record an auditor wants to see during a J-SOX review or an internal-control walkthrough. The question they always ask is whether a new customer was properly authorized before any revenue was committed or any invoice was raised. With a frozen approval snapshot tied to the customer record, the answer is yes, and you can prove it in seconds rather than reconstructing an email thread from a shared drive. The same snapshot protects the company in a dispute, showing exactly who agreed to what and when.

A Scenario: The Precision Parts Maker in Aichi

Consider a precision parts manufacturer in Aichi, about 280 staff, supplying components to industrial machinery makers across Japan. Their sales team opens roughly 150 new customer accounts a year, a mix of trading companies, end users, and contract manufacturers. Before they gated onboarding, a sales rep could add a customer in the afternoon, set a credit limit by feel, and ship the first order the same week. Credit and finance found out at month-end, if at all, usually because an invoice had already aged past terms.

In the new flow, the sales rep opens a new-customer request in the same core business system they already use for quotes, orders, and expense reimbursement. They attach the prospect's registration certificate, the draft trade agreement, and the bank account form, and they enter the intended payment terms and the requested credit limit. The request routes to the right approvers. Sales leadership confirms the commercial relationship. The credit analyst pulls the prospect's financials, checks trade references, and sets the actual credit limit against policy. If the prospect is in a higher-risk category, compliance signs off too. Each reviewer works in their own queue, on their own schedule. The total elapsed time is a few business days, not a few weeks, because the reviews run together rather than in a fixed sequence.

When the last reviewer clears, the customer is approved, and that cleared status is confirmed inside the workflow. The gate is the control that must run first: a new customer is not authorized until sales and credit have both signed off, and the frozen snapshot proves who agreed to what. The automatic push of that cleared status into the quote, order, and billing modules, so that those downstream records cannot be opened against an un-cleared customer, is on the roadmap. Today the cleared status lives inside the workflow, and the customer master is created or updated through the normal ERP flow once the gate has done its work. The control that prevents un-vetted customers is the part you already get; the last inch of downstream automation is a roadmap item with clear scope.

Over the first year, the company catches several prospects that would have been problems. One is a thinly capitalized shell whose financials fail the credit check before any goods move. Another turns out to be a related party of a departing employee, flagged by compliance during onboarding. A third has a payment history that warrants a lower credit limit than the rep requested. None ever ship on open terms until the risk is understood and priced. The cost of running the control is the few hours each reviewer spends per customer, a fraction of what a single bad receivable would cost.

What Is Built Today, and What Is on the Roadmap

Being precise about the boundary matters more than overselling. What is built today is the approval gate itself: the new-customer request, the routing to sales leadership and credit or finance, the requirement that the named reviewers clear before the request advances, the frozen snapshot of what was approved, and the audit trail tying it back to the customer record. That control is live now, and it is the part that actually stops un-vetted customers from transacting. A customer cannot be cleared as approved until the gate has done its work.

What is on the roadmap, and not yet built, is the automatic creation of the customer master record on approval. Today, once the approval clears, the customer is confirmed as cleared inside the workflow, and the master record is created or updated through the normal ERP flow by the team that owns the master. The fully automatic push, where approval completion directly creates the new customer in the master with no manual step, is coming. The honest way to say it: the approval control is live today, and the automatic customer-master creation is on the roadmap. The control that prevents the bad debt is the part you already get.

This honesty is worth pausing on. A surprising number of tools sell onboarding software that promises full automation and then quietly depends on a spreadsheet and an email to finish the job. The cleaner story is that the gate is real and enforced now, and the last inch of automation is a roadmap item with a clear scope. For a buyer evaluating tools, that clarity is more useful than a slide that promises everything is automatic.

Frequently Asked Questions

Will this slow down every new sale?

No, because the approval gate runs only on new customers and on material changes to existing ones, not on every repeat order. Once a customer is in the master and cleared, quoting and ordering against it is fast. The gate sits in front of the revenue commitment for a new account, not in front of every transaction. The reviewers also work in parallel, so the elapsed time is the slowest reviewer, not the sum.

What happens when a reviewer is traveling or out of office?

The workflow engine supports safe delegation, so an approver can hand their queue to a deputy for the days they are away. For higher-risk items, the system can require that the original approver re-confirm after they return, so delegation never becomes a quiet way to bypass the gate. The control survives vacations and business trips, which is exactly when paper approvals tend to break.

How do we handle a prospect who needs to order immediately?

Urgency is real, and a rigid gate that ignores it will get routed around. The practical answer is that the gate runs on business-day deadlines, so each reviewer has a defined window rather than an open-ended one. If a prospect genuinely cannot wait, the request can be escalated, but the clearances are still required before the customer is cleared. The goal is to make the right way the fast way.

Does this replace our credit team?

No. The control exists because sales and credit each see something the other does not. The workflow routes the work to the right people and enforces that they clear. It does not do the credit analysis. What it removes is the manual chasing and the gaps where a customer slipped in because nobody was sure whose turn it was.

Key Takeaway

The customer master is a revenue commitment, and an open master is an un-governed revenue commitment. The control that closes it is an approval gate: sales and a credit or finance check must clear before a new customer enters the master, receives a shipment, or is invoiced. That gate is built and live today. The automatic creation of the customer master record on approval is on the roadmap. The bad-debt-prevention part, which is the part that matters, you already get.

Get Started With Kikan System

If you have ever discovered a customer in your master that nobody in credit remembers approving, look at Kikan System. The workflow engine runs the new-customer approval, routes it to sales and credit or finance, and freezes a snapshot of what was cleared. The approval gate is built and live today; the automatic push of that cleared status into the downstream quote, order, and billing records is on the roadmap. Start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.