What this is
What is a customer master data and terms setup record?
What is a customer master data and terms setup record?
It is the record that turns an agreed customer relationship into usable data: codes, credit limit, payment terms, currency and tax treatment, delivery addresses and windows, and any requirement the customer specifically accepted above the standard offer. It is completed by master data with commercial sign-off, not either function alone.
What triggers a new or updated setup?
The Setup Type field names five: a new customer, a terms change on an existing one, an additional site, a reactivation after dormancy, and the scheduled annual review. Each carries the same commercial and operational checks regardless of how minor the trigger looks.
Why does the template separate 'requirements carried into the system' from the commercial fields?
Commercial data (credit, terms, tax) usually gets entered correctly because it blocks an order if wrong. Requirements such as shelf life, labelling or packaging do not block anything by default, so the template forces a deliberate check rather than letting them ride on the commercial entry alone.
Scope
When is a customer master data and terms setup required?
This record sets up and maintains a customer's terms once they exist. Using it to run the wider onboarding, or to review requirements clause by clause, produces a record that neither purpose is served well by.
Use this template when
- A new customer has been won and their commercial and operational terms need to go live
- An existing customer's terms are changing: credit limit, payment terms, currency or tax treatment
- An additional site is being added under an existing customer relationship
- A dormant customer is being reactivated and their master data needs re-verifying, not assumed still correct
- The scheduled annual review of the customer's data is due
Do not use it for
- Customer Onboarding Record, the broader onboarding checklist that takes a new customer from won to able to receive product, of which this master data setup is one input.
- Carrier Onboarding and Qualification, which qualifies a haulier or courier, not a customer, before they carry anything.
- Customer Specific Requirement Review, which assesses whether the site can actually meet a requirement in detail; this record assumes that assessment is done and records the outcome as a flag, not a re-assessment.
- Customer Register, the register entry itself; this record is one of the things the register points to, not the register.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.7.5 requirements does this satisfy?
ISO 9001 cl.7.5 sets the documented information requirement this record satisfies, but the sharper obligation, resolving what was agreed before commitment, sits in the requirements-review and operational-control clauses below.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.2.2 | Determine the requirements specified by the customer, including delivery and post-delivery activities | Header |
| ISO 9001 cl.8.2.3 | Review requirements before committing to supply, and resolve any difference from what was previously expressed, such as in a tender | Commercial data |
| ISO 9001 cl.8.2.3 | Confirm the organisation has the capability to meet the requirements it is committing to | Operational data |
| ISO 9001 cl.8.5.1 | Control production and service provision, including the labelling, traceability and packaging requirements to be met | Requirements carried into the system |
| ISO 9001 cl.7.5.3 | Ensure documented information is available, suitable for use, and adequately protected | Outcome |
| ISO 9001 cl.5.3 | Assign responsibility and authority for ensuring customer requirements are met and maintained | Outcome |
| ISO 9001 cl.7.5.1 | Determine the documented information the quality management system requires, including customer records | Header |
What it does not cover
- Customer Onboarding Record, the wider checklist this master data setup is one input into, not a substitute for.
- Carrier Onboarding and Qualification, which qualifies the haulier, a separate party with separate obligations.
- Customer Specific Requirement Review, the detailed technical assessment of whether a requirement can be met, which this record assumes has already happened.
- Customer Register, the register entry this record is linked from, not a replacement for it.
- Load Tender Record, which documents the tender itself; this record is downstream and should reflect what the tender settled, not repeat its detail.
Global
Customer Master Data and Terms Setup requirements by country
ISO 9001 itself is not jurisdiction-specific, but tax treatment, the commercial field this record sets, sits on tax law that varies by where the customer and supplying site are.
VAT Act 1994 (UK); EU VAT Directive 2006/112/EC
Tax Treatment Correct must reflect the actual VAT position, including reverse charge and zero-rating for qualifying exports, not a default rate copied from a similar customer.
A wrong tax treatment set at customer level propagates onto every invoice against that customer until someone notices, usually via an HMRC or auditor query.
State economic nexus statutes following South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018)
Whether a sale creates a sales tax collection obligation depends on the customer's state and the seller's activity there, not one national rule.
Getting a customer's state tax status wrong at setup means either under-collecting tax owed, or applying tax that should not apply, across every order until corrected.
ISO 9001:2015 clauses 8.2.3 and 7.5
A certification audit sampling customer records looks for evidence that requirements differing from a tender were actually resolved before supply began.
Complete commercial fields with no trace of a tender-to-record reconciliation is a plausible minor nonconformity, not a pass by default.
How to complete it
How to complete a customer master data and terms setup, step by step
The fields are mostly yes or no, easy to tick optimistically. The judgement calls below separate a record reflecting the actual agreement from one reflecting what was convenient to enter.
Work from the actual tender document or signed contract, checking each accepted requirement off against a field, rather than recalling what was agreed. Anything agreed with no obvious field still needs to go somewhere, even as a note pending a template change.
If the same person who entered the data also ticks Second Person Reviewed, the field records that entry happened twice, not that it was checked. The reviewer should be someone who did not do the original entry.
A terms change is the trigger most likely to get a partial update, touching only the field that changed and leaving the rest stale. Re-confirm the commercial and operational sections at every trigger, not just the field it was about.
This field is where the record tests itself: a requirement entered correctly in master data that despatch cannot see when loading the vehicle has still failed the customer, whatever the rest of the record shows.
What auditors find
Most common customer master data and terms setup findings
These recur because the fields that fail have no downstream check forcing a correction, unlike a wrong credit limit, which usually blocks an order and gets noticed quickly.
| Finding | Clause | What fixes it |
|---|---|---|
| A requirement accepted in the tender has no corresponding field entered anywhere in the record. | ISO 9001 cl.8.2.3 | Reconcile against the tender or contract line by line before marking Setup Complete. |
| A terms change edits only the changed field, leaving the rest of the commercial section unverified. | ISO 9001 cl.7.5.3 | Re-confirm every field in Commercial and Operational data at each trigger, not only the one raised. |
| Second Person Reviewed is marked Yes by the person who entered the original data. | ISO 9001 cl.5.3 | Name a different reviewer, and record who it was. |
| Special instructions are recorded in master data but do not appear on what despatch actually uses. | ISO 9001 cl.8.5.1 | Confirm the despatch-facing output surfaces the field before marking it satisfied. |
| Data Review Due is set arbitrarily far out, or left to default, rather than a fixed interval. | ISO 9001 cl.7.5.3 | Set the date to a defined interval from setup, typically twelve months, and enforce it. |
| Certification or labelling requirements are flagged met without a linked specification version. | ISO 9001 cl.8.5.1 | Do not mark satisfied until Specification Version Linked is actually populated. |
Case in point
Case in point: the pallet label nobody entered
A customer's contract renewal added a requirement, agreed in the final commercial call, that every pallet carry a secondary barcode label for their own warehouse system. Commercial closed the renewal; master data updated the credit terms and delivery windows that changed at the same time, and the record was marked complete.
The label requirement was never entered, because nobody on the commercial side told master data it existed, and the checklist had no field prompting a reconciliation against the renewal. It surfaced three weeks later as a complaint about pallets rejected at goods-in, by which time it had shipped on every order in between.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- LOG-050
- Archetype
- Record
- Record ID
- CMD-2026-000
- Scoring
- Set up correctly first time
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.7.5
- Links
- Links Customer Register and Requirement Review
- Tags
- Customer, Master data
- Sections
- 5
- Fields
- 50
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 5
Header
13 fieldsRecord ID*
Auto sequence. Format CMD-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Customer Name*
Customer Code
Setup Type*
Requested By*
Entered By*
Second Person Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Accepted In A Tender, Entered Nowhere
A requirement agreed during a tender and never entered into the system is a requirement that will be missed on the first order and every order afterwards.
Commercial data
6 fieldsLegal Entity Correct*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Billing Address Correct*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Credit Limit Applied*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Payment Terms Applied*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Currency Correct*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Tax Treatment Correct*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Operational data
6 fieldsDelivery Addresses Loaded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Delivery Windows Loaded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Minimum Order Quantity Set*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Lead Time Set*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Booking Requirement Flagged*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Carrier Or Collection Method Set*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Requirements carried into the system
6 fieldsMinimum Remaining Life Enforced*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Labelling Requirements Recorded Against The Product*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Certification Requirements Flagged*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Specification Version Linked*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Packaging Configuration Recorded*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Special Instructions Visible To Despatch*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
19 fieldsSetup Complete*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Requirements Visible To Operations*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Onboarding ID
Links to LOG-049 Checklist ID
Requirement Review ID
Links to QUA-112 Review ID
Customer Register ID
Links to FDN-021 Register ID
Data Review Due*
Items Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Master Data*
Signature*
Commercial*
Second Signature*
LOG-050 · record IDs look like CMD-2026-000 · Links Customer Register and Requirement Review
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is short. What slips is reconciling against the tender, the independence of the second review, and whether a flagged requirement reaches the person loading the vehicle.
Holds the customer master data record against the register, tracks Data Review Due, and links each requirement flag through to the despatch output that has to surface it.
Carries the detailed requirement assessment this record only flags, keeping the two records' IDs cross-referenced rather than duplicating the analysis.
Tracks tax treatment and legal entity fields against the jurisdictions they actually touch, and flags a review overdue against the fixed interval.
Watches for Setup Complete marked Yes with an open action, or a Data Review Due date quietly passed, and raises it rather than letting it carry forward.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Customer Master Data and Terms Setup definitions and key terms
- Master data
- The core, relatively stable data about a customer, item or site that other transactions reference rather than re-enter, such as codes, credit terms and addresses.
- Credit limit
- The maximum outstanding balance a customer is permitted before further orders are held, set on commercial risk assessment rather than requested volume.
- Minimum order quantity
- The smallest quantity a customer may order, set to keep small orders economically viable to pick, pack and deliver.
- Booking requirement
- A condition that a delivery must be booked into a time slot before it arrives, common at large retail distribution centres, and a field that has to reach the transport plan.
- Minimum remaining life
- The minimum proportion of a product's shelf life that must remain at delivery for a customer to accept it, enforced by the order system rather than the driver's judgement.
FAQ
Frequently asked questions about customer master data and terms setup
Does every terms change need a brand new record, or an update to the existing one?+
An update to the existing record, since this is a maintained customer record rather than an event log. What changes is the Setup Type selected and which sections get re-verified, not the record's identity.
Who should complete Second Person Reviewed?+
Someone other than whoever entered the data. The field is an independent check; the same person confirming their own entry provides none, whatever the tick says.
What is the difference between this and the Customer Onboarding Record?+
The onboarding record is the broader checklist from won customer to able to receive product. This template sets up the master data and terms, and is also used alone for terms changes that are not a full onboarding.
What if operations needs a requirement now, but it is not verified into master data yet?+
Flag it as an interim manual instruction to despatch and raise an action to complete the master data properly, rather than marking the field Yes on an intention to enter it later.
How does this connect to the Customer Specific Requirement Review?+
That review does the detailed technical assessment of whether a requirement can genuinely be met. This record assumes that has happened and carries the outcome forward as an operational flag, cross-referenced by ID.
What happens if the annual review finds nothing has changed?+
It still resets Data Review Due and records that the check happened. A confirmed 'nothing changed' is more useful than a review that never occurred.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Customer and Carrier Onboarding
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Customer Register
Holds every customer you supply, with their specifications, audit requirements and complaint history reference
Load Tender Record
Records a load offered to a carrier, the rate agreed and whether it was accepted or refused
Customer Onboarding Record
Takes a new customer from won to able to receive product, covering credit, terms, specifications, delivery constraints, labelling requirements and system setup
Carrier Onboarding and Qualification
Qualifies a new haulier or courier before they carry anything, covering operator licence, insurance, vehicle standards, temperature capability, driver vetting and the service levels agreed
Customer Specific Requirement Review
Reviews requirements a customer imposes beyond the standard specification, and whether the site can meet them
More in Customer and Carrier Setup
Customer Onboarding Record
Takes a new customer from won to able to receive product, covering credit, terms, specifications, delivery constraints, labelling requirements and system setup
Carrier Onboarding and Qualification
Qualifies a new haulier or courier before they carry anything, covering operator licence, insurance, vehicle standards, temperature capability, driver vetting and the service levels agreed
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 8.2.2 and 8.2.3, Requirements for products and services
- ISO 9001:2015 clause 7.5, Documented information
- ISO 9001:2015 clause 8.5.1, Control of production and service provision
- South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.