972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Projects and construction

CNTCND Contractual conditions

The UN/EDIFACT message a customer sends to a supplier with the conditions of a negotiated contract, so invoices against it can be processed automatically.

Sent by
Customer
Received by
Supplier and other interested parties
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CNTCND message?

CNTCND is the UN/EDIFACT contractual conditions message. The directory defines it as a message from a customer to a supplier and other interested parties providing the contractual conditions of a previously negotiated contract, to enable automatic processing of invoices for orders made against the contract or for the completion of identified contract stages.

By sharing the agreed prices, payment terms, milestones and conditions in structured form, both sides check invoices against the same terms, which reduces disputes and speeds up payment.

How the EDIFACT CNTCND message worksDiagram of the UN/EDIFACT CNTCND Contractual conditions message. Customer sends it to supplier and other interested parties. It usually starts the exchange. It is usually followed by ORDERS and INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG8 loop with SEQ (Sequence details) and NAD (Name and address). 13 conditional segment groups are listed by their trigger segment.How the EDIFACT CNTCND message worksContractual conditions: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCNTCNDSENDERCustomerRECEIVERSupplier and otherinterested partiesCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDERSPurchase orderINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CNTCNDUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG8 · repeats up to 99SEQSequence detailsNADName and address+ 13 conditional groups, starting with:RFFPRIQTYDOCCUXTAXPYTCTARELALCFORLINBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for CNTCND. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CNTCND message worksDiagram of the UN/EDIFACT CNTCND Contractual conditions message. Customer sends it to supplier and other interested parties. It usually starts the exchange. It is usually followed by ORDERS and INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG8 loop with SEQ (Sequence details) and NAD (Name and address). 13 conditional segment groups are listed by their trigger segment.How the EDIFACT CNTCNDmessage worksContractual conditions: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCNTCNDSENDERCustomerRECEIVERSupplier andother interestedpartiesCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDERSPurchase orderINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CNTCND (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG8 · repeats upto 99SEQSequence detailsNADName and address+ 13 conditional groups, starting with:RFFPRIQTYDOCCUXTAXPYTCTARELALCFORLINBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for CNTCND.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CNTCND, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around CNTCND and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Sharing agreed contract terms after negotiation
  • Defining payment milestones for project work
  • Enabling automatic invoice checks against a contract

Where it fits in the message flow

This message CNTCND Contractual conditions
Usually followed by ORDERS Purchase orderINVOIC Invoice

Structure

Mandatory segments in CNTCND (directory D.21A)

In UN/EDIFACT directory D.21A, the CNTCND message has 141 segment positions arranged in 40 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG8 (SEQ)
  • UNT

Practical example

CNTCND in practice

A utility signs a framework contract with a cable supplier covering prices by cable type, volume discounts and payment terms for two years. It sends the supplier a CNTCND with the contract number and conditions. Orders placed against the contract reference it, and the utility's invoice system checks every invoice against the shared conditions automatically.

Implementation

Implementation considerations for CNTCND

  • Reference the contract number in every order and invoice.
  • Update the conditions when the contract is amended.
  • Agree which party's record of the conditions prevails.
  • Map milestones to the invoices that bill them.

How ECOM helps

Automate CNTCND with ECOM

Solution

Procure-to-Pay Automation

Automate purchasing, receiving and supplier invoicing across EDI, portals and documents.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related projects and construction messages

All 14 projects and construction messages

Need help with CNTCND?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us