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

CREEXT Extended credit advice

The UN/EDIFACT message a bank uses to advise a credit to an account together with extended details of the business transactions settled.

Sent by
Account-servicing bank
Received by
Account owner
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CREEXT message?

CREEXT is the UN/EDIFACT extended credit advice. Like CREADV, it is sent by the account-servicing financial institution to tell the account owner that its account has been or will be credited for a specified amount on a given date in settlement of referenced transactions. The extended version can also carry the detailed commercial information the payer supplied, such as the invoices being paid.

That remittance detail lets the beneficiary apply a single credit across many invoices automatically, which is especially useful when a payer settles many invoices with one transfer.

How the EDIFACT CREEXT message worksDiagram of the UN/EDIFACT CREEXT Extended credit advice message. Account-servicing bank sends it to account owner. It usually starts the exchange. 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 MOA (Monetary amount). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT CREEXT message worksExtended credit advice: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCREEXTSENDERAccount-servicingbankRECEIVERAccount ownerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CREEXTUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 4MOAMonetary amount+ 8 conditional groups, starting with:RFFFIINADINPGEIFCAPRCAUTBlue 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 CREEXT. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CREEXT message worksDiagram of the UN/EDIFACT CREEXT Extended credit advice message. Account-servicing bank sends it to account owner. It usually starts the exchange. 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 MOA (Monetary amount). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT CREEXTmessage worksExtended credit advice: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCREEXTSENDERAccount-servicing bankRECEIVERAccount ownerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CREEXT (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 4MOAMonetary amount+ 8 conditional groups, starting with:RFFFIINADINPGEIFCAPRCAUTBlue 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 CREEXT.Your trading partner's implementation guide adds itsown requirements.

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

  • Advising credits that settle several invoices
  • Passing the payer's remittance information to the beneficiary
  • Supporting automatic cash application

Where it fits in the message flow

This message CREEXT Extended credit advice

No other message routinely comes directly before or after CREEXT; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in CREEXT (directory D.21A)

In UN/EDIFACT directory D.21A, the CREEXT message has 64 segment positions arranged in 18 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 (MOA)
  • UNT

Practical example

CREEXT in practice

A retailer pays a supplier for 60 invoices in one transfer and includes the invoice list in its extended payment order. The supplier's bank receives the funds and sends the supplier a CREEXT with the credit amount and the full invoice list. The supplier's accounts receivable system clears all 60 invoices without manual research.

Implementation

Implementation considerations for CREEXT

  • Confirm that payer remittance details are passed through end to end.
  • Map the detail lines to open items in accounts receivable.
  • Reconcile the total with the credited amount.
  • Agree with the bank when CREEXT is sent instead of CREADV.

How ECOM helps

Automate CREEXT with ECOM

Solution

Financial Document Automation

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

Industry

Financial Services

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

Solution

Order-to-Cash Automation

Automate the flow from purchase order to payment across every customer channel.

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

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

Request a Demo Contact us