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

CONPVA Payment valuation

The UN/EDIFACT message used between a contractor and the client's representative to approve the value of, and payment for, work completed in a period.

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

What is the EDIFACT CONPVA message?

CONPVA is the UN/EDIFACT payment valuation message. The directory describes it as typically used between a contractor and the client's representative during the approval of the value of, and payment for, work completed in a given period.

The valuation applies contract rates to the agreed quantities, adds variations and adjustments and deducts retention and previous payments to reach the amount due. Exchanging it electronically keeps both parties' figures aligned before an invoice is issued. The agreed valuation is the basis for the contractor's invoice for the period.

How the EDIFACT CONPVA message worksDiagram of the UN/EDIFACT CONPVA Payment valuation message. Contractor or client's representative sends it to client's representative or contractor. It usually follows CONQVA. It is usually followed by 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 SG2 loop with NAD (Name and address), UNS (Section control) and UNS (Section control). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT CONPVA message worksPayment valuation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCONQVAQuantity valuationCONPVASENDERContractor or client'srepresentativeRECEIVERClient's representativeor contractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CONPVAUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9NADName and addressUNSSection controlUNSSection control+ 9 conditional groups, starting with:RFFDOCCTACUXINDBIITAXBlue 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 CONPVA. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CONPVA message worksDiagram of the UN/EDIFACT CONPVA Payment valuation message. Contractor or client's representative sends it to client's representative or contractor. It usually follows CONQVA. It is usually followed by 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 SG2 loop with NAD (Name and address), UNS (Section control) and UNS (Section control). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT CONPVAmessage worksPayment valuation: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCONQVAQuantity valuationCONPVASENDERContractor orclient'srepresentativeRECEIVERClient'srepresentativeor contractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CONPVA (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9NADName and addressUNSSection controlUNSSection control+ 9 conditional groups, starting with:RFFDOCCTACUXINDBIITAXBlue 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 CONPVA.Your trading partner's implementation guide adds itsown requirements.

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

  • Agreeing the amount due for a period's work
  • Applying retention and previous payments
  • Supporting interim and final payments

Where it fits in the message flow

Usually follows CONQVA Quantity valuation
This message CONPVA Payment valuation
Usually followed by INVOIC Invoice

Structure

Mandatory segments in CONPVA (directory D.21A)

In UN/EDIFACT directory D.21A, the CONPVA message has 96 segment positions arranged in 34 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)
  • UNS
  • UNS
  • UNT

Practical example

CONPVA in practice

After agreeing a month's quantities, the client's quantity surveyor sends the contractor a CONPVA valuing the work at contract rates, adding two approved variations, deducting five percent retention and the previous payments. The contractor accepts the valuation and invoices the amount due.

Implementation

Implementation considerations for CONPVA

  • Use the contract rates from the established contract.
  • Show retention and previous payments explicitly.
  • Keep variations traceable to their approvals.
  • Reconcile valuations with invoices and payments.

How ECOM helps

Automate CONPVA 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

Procure-to-Pay Automation

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

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

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

Request a Demo Contact us