Customers and commercial defaults: building a dependable sales relationship

Customer master data supplies reusable commercial information: identity, addresses, contacts, currency, payment terms and financial settings. Groups segment customers, while sales types classify the way business is conducted. Good defaults reduce repetitive entry, but they do not replace checking the transaction.

In DNA, customer selection supplies information to sales documents. The customer selector sends the search to the customer service and displays identifying details such as code and contact information, helping distinguish similar names. Search results must still be checked against the intended customer. A third-party payer is a special customer role used for split receivables, not simply another contact at the same customer.

Why the customer's identity matters

A familiar contact is not always the party legally responsible for the purchase. A project manager may request equipment for one company while another company issues the purchase order. A branch may receive the goods while head office receives the invoice.

The customer record needs to support the actual commercial relationship. Identity, delivery details, billing details, contacts, and payment responsibility should be understandable together. Similar names are not sufficient evidence that two records represent the same party.

A practical example

Two branches share a similar trading name but have different billing addresses. Selecting the first search result can send an invoice to the wrong payer. Compare the code, contact details and address, then verify currency and terms on the quotation or order.

The error affects more than the printed address. It can fragment balances, complicate collection, and make later analysis of the customer's business unreliable. Consistent master data prevents those downstream problems.

Defaults support the agreement

DNA uses customer settings to provide a starting point for sales documents. Payment terms and currency establish the usual commercial context. Groups and sales types help organise customers and activity for business purposes.

A default should be distinguished from a negotiated exception. A customer normally paying after 30 days might agree to an advance for a special order. The specific transaction should reflect the accepted terms rather than assume that the usual arrangement covers every situation.

Changing a default also does not automatically rewrite historical agreements. The business needs to distinguish a new preference for future transactions from a correction to an existing document.

Groups, contacts, and third-party payers

Customer groups describe a business classification, such as a market segment. Contacts describe people who communicate for the account. A third-party payer describes a separate payment responsibility under a supported split arrangement. These are different relationships and should remain distinguishable.

A well-maintained customer record lets sales, warehouse staff, and finance understand who is buying, who receives the supply, who receives the bill, and what commercial defaults usually apply. That clarity supports both efficient processing and reliable customer service.