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

CONQVA Quantity valuation

The UN/EDIFACT message a contractor uses to submit progress, the quantities of work completed, to the client or its representative.

Sent by
Contractor or subcontractor
Received by
Client's representative or main contractor
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CONQVA message?

CONQVA is the UN/EDIFACT quantity valuation message. The directory describes it as typically used by a contractor to submit progress details to a client or its representative. It is also used for parts of the project contracted out to other parties, where subcontractors report to the main contractor.

Progress is reported as quantities completed for each contract item. The client's representative checks the quantities, sometimes supported by measurements sent with CONWQD, and the agreed values lead to the payment valuation (CONPVA).

How the EDIFACT CONQVA message worksDiagram of the UN/EDIFACT CONQVA Quantity valuation message. Contractor or subcontractor sends it to client's representative or main contractor. It usually follows CONEST. It is usually followed by CONPVA. 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 SG2 loop with NAD (Name and address). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT CONQVA message worksQuantity valuation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCONESTEstablishment ofcontractCONQVASENDERContractor orsubcontractorRECEIVERClient's representativeor main contractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCONPVAPayment valuation2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CONQVAUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9NADName and address+ 5 conditional groups, starting with:RFFDOCCTABIIBlue 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 CONQVA. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CONQVA message worksDiagram of the UN/EDIFACT CONQVA Quantity valuation message. Contractor or subcontractor sends it to client's representative or main contractor. It usually follows CONEST. It is usually followed by CONPVA. 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 SG2 loop with NAD (Name and address). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT CONQVAmessage worksQuantity valuation: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCONESTEstablishment of contractCONQVASENDERContractor orsubcontractorRECEIVERClient'srepresentativeor maincontractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCONPVAPayment valuation2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CONQVA (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9NADName and address+ 5 conditional groups, starting with:RFFDOCCTABIIBlue 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 CONQVA.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CONQVA, 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 CONQVA 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

  • Reporting monthly progress on contract items
  • Reporting subcontractor progress to the main contractor
  • Supporting interim payment applications

Where it fits in the message flow

Usually follows CONEST Establishment of contract
This message CONQVA Quantity valuation
Usually followed by CONPVA Payment valuation

Structure

Mandatory segments in CONQVA (directory D.21A)

In UN/EDIFACT directory D.21A, the CONQVA message has 29 segment positions arranged in 9 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
  • SG2 (NAD)
  • UNT

Practical example

CONQVA in practice

At the end of each month, a contractor sends the client's quantity surveyor a CONQVA with the cumulative quantities completed for each contract item. The surveyor checks a sample against site measurements, agrees the quantities and prepares the payment valuation.

Implementation

Implementation considerations for CONQVA

  • Report cumulative quantities against contract item references.
  • Support disputed quantities with measurement details.
  • Align reporting periods with the payment cycle.
  • Separate variations from original contract items.

How ECOM helps

Automate CONQVA with ECOM

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

Solution

Financial Document Automation

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

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

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 CONQVA?

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

Request a Demo Contact us