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

STATAC Statement of account

The UN/EDIFACT message a seller or its agent sends a buyer with the status of an account at a point in time, as a reconciliation aid.

Sent by
Seller or its agent
Received by
Buyer or its agent
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT STATAC message?

STATAC is the UN/EDIFACT statement of account. The directory defines it as a communication from a seller, or its agent, to a buyer, or its agent, giving information about the status of an account at a specific point in time. It is used as an aid to reconciliation and can also serve as a reminder of payments due.

A statement lists open invoices, credit notes and payments received, with balances and due dates. Buyers compare it with their own payables ledger to find invoices they never received, payments the seller has not applied and differences that need resolving.

How the EDIFACT STATAC message worksDiagram of the UN/EDIFACT STATAC Statement of account message. Seller or its agent sends it to buyer or its agent. It usually starts the exchange. It is usually followed by REMADV and REQDOC. 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), body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG3 loop with DOC (Document/message details) and MOA (Monetary amount) and end of message: UNS (Section control) and MOA (Monetary amount). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT STATAC message worksStatement of account: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSTATACSENDERSeller or its agentRECEIVERBuyer or its agentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYREMADVRemittance adviceREQDOCRequest for document2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage STATACUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 99NADName and addressMandatory group SG3 · repeatsmany timesDOCDocument/message detailsMOAMonetary amount+ 1 conditional group, starting with:CTAEND OF MESSAGEUNSSection controlMOAMonetary amountBlue 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 STATAC. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT STATAC message worksDiagram of the UN/EDIFACT STATAC Statement of account message. Seller or its agent sends it to buyer or its agent. It usually starts the exchange. It is usually followed by REMADV and REQDOC. 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), body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG3 loop with DOC (Document/message details) and MOA (Monetary amount) and end of message: UNS (Section control) and MOA (Monetary amount). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT STATACmessage worksStatement of account: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSTATACSENDERSeller or itsagentRECEIVERBuyer or itsagentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYREMADVRemittance adviceREQDOCRequest for document2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message STATAC (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 99NADName and addressMandatory group SG3 · repeatsmany timesDOCDocument/message detailsMOAMonetary amount+ 1 conditional group, starting with:CTAEND OF MESSAGEUNSSection controlMOAMonetary amountBlue 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 STATAC.Your trading partner's implementation guide adds itsown requirements.

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

  • Sending periodic account statements to customers
  • Reconciling receivables and payables
  • Reminding customers of overdue items

Where it fits in the message flow

This message STATAC Statement of account
Usually followed by REMADV Remittance adviceREQDOC Request for document

Structure

Mandatory segments in STATAC (directory D.21A)

In UN/EDIFACT directory D.21A, the STATAC message has 16 segment positions arranged in 3 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
  • SG1 (NAD)
  • SG3 (DOC)
  • UNS
  • MOA
  • UNT

Practical example

STATAC in practice

A packaging supplier sends a retailer a STATAC at each month end listing open invoices, credit notes and unapplied payments. The retailer's payables system matches it with its ledger and finds two invoices it never received. It requests copies with REQDOC and schedules payment of the overdue items.

Implementation

Implementation considerations for STATAC

  • Reference documents exactly as originally issued.
  • Agree the statement frequency and cut-off date.
  • Reconcile differences promptly in both directions.
  • Distinguish reminders from routine statements.

How ECOM helps

Automate STATAC with ECOM

Solution

Financial Document Automation

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

Solution

Order-to-Cash Automation

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

Industry

Wholesale Distribution

Customer orders, supplier purchasing, catalogs and drop-ship for distributors.

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

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

Request a Demo Contact us