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 · Finance

JUPREQ Justified payment request

The UN/EDIFACT message an accounts payable service sends to a payment service to request payments, with the details that justify them.

Sent by
Accounts payable service or equivalent
Received by
Payment service or equivalent
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT JUPREQ message?

JUPREQ is the UN/EDIFACT justified payment request. The directory defines it as a message an accounts payable service, or equivalent, sends to a payment service, or equivalent, to request payment of a sum to one or several creditors. It can carry all the details required for auditability to justify the requested payments.

The message suits organizations where the department that approves invoices is separate from the one that pays them, as in many public administrations. The payment service can check each request against its supporting details before releasing funds.

How the EDIFACT JUPREQ message worksDiagram of the UN/EDIFACT JUPREQ Justified payment request message. Accounts payable service or equivalent sends it to payment service or equivalent. It usually follows INVOIC. It is usually followed by PAYMUL. 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). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT JUPREQ message worksJustified payment request: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSINVOICInvoiceJUPREQSENDERAccounts payableservice or equivalentRECEIVERPayment service orequivalentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPAYMULMultiple payment order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage JUPREQUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 99NADName and address+ 2 conditional groups, starting with:RFFDOCBlue 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 JUPREQ. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT JUPREQ message worksDiagram of the UN/EDIFACT JUPREQ Justified payment request message. Accounts payable service or equivalent sends it to payment service or equivalent. It usually follows INVOIC. It is usually followed by PAYMUL. 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). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT JUPREQmessage worksJustified payment request: who sends it, whereit fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSINVOICInvoiceJUPREQSENDERAccountspayable serviceor equivalentRECEIVERPaymentservice orequivalentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPAYMULMultiple payment order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message JUPREQ (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 99NADName and address+ 2 conditional groups, starting with:RFFDOCBlue 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 JUPREQ.Your trading partner's implementation guide adds itsown requirements.

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

  • Requesting payments from a separate payment service
  • Providing audit details for each payment
  • Paying several creditors from one request

Where it fits in the message flow

Usually follows INVOIC Invoice
This message JUPREQ Justified payment request
Usually followed by PAYMUL Multiple payment order

Structure

Mandatory segments in JUPREQ (directory D.21A)

In UN/EDIFACT directory D.21A, the JUPREQ message has 67 segment positions arranged in 16 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

JUPREQ in practice

A government ministry's accounts payable unit approves supplier invoices and sends the treasury a JUPREQ for each payment batch, listing the creditors, amounts, approved invoices and budget lines. The treasury checks the justification, executes the payments through its bank and records them for audit.

Implementation

Implementation considerations for JUPREQ

  • Include the supporting details auditors require.
  • Keep request references traceable to invoices and budget lines.
  • Reconcile payments executed with requests sent.
  • Agree controls between the requesting and paying services.

How ECOM helps

Automate JUPREQ with ECOM

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.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

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

Related messages

Related finance messages

All 37 finance messages

Need help with JUPREQ?

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

Request a Demo Contact us