EDIFACT message guide · Finance
ENTREC Accounting entries
The UN/EDIFACT message used to exchange accounting entries for accounting, audit, cost accounting, consolidation and analysis.
- Sent by
- Enterprise, service provider or accountant
- Received by
- Accounting system, auditor or parent company
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT ENTREC message?
ENTREC is the UN/EDIFACT accounting entries message. The directory defines it as a message used to exchange accounting entries between an enterprise and whoever may use them for accounting, auditing, cost accounting, consolidation, financial analysis and similar purposes.
Entries are the individual journal postings, with dates, accounts, amounts and references. Organizations use ENTREC to post entries from one system into another, such as from a payroll provider into the general ledger, or to give auditors transaction-level data. Entries must balance per batch.
How to read this diagram: the top row shows who sends ENTREC, 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 ENTREC 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.
When it is used
- Posting entries from an outsourced service into the ledger
- Giving auditors transaction-level accounting data
- Transferring intercompany entries
Where it fits in the message flow
Structure
Mandatory segments in ENTREC (directory D.21A)
In UN/EDIFACT directory D.21A, the ENTREC message has 48 segment positions arranged in 13 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)
- SG4 (DTM)
- UNS
- SG12 (QTY)
- UNT
Practical example
ENTREC in practice
A company outsources payroll. After each payroll run, the provider sends an ENTREC with the journal entries for salaries, taxes and social contributions by cost center. The company's accounting system posts the entries automatically and reconciles them with the bank payments.
Implementation
Implementation considerations for ENTREC
- Use account numbers from the agreed chart of accounts.
- Ensure that each batch of entries balances.
- Include references back to source documents.
- Prevent duplicate posting of resent batches.
How ECOM helps
Automate ENTREC with ECOM
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
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
Need help with ENTREC?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.