EDIFACT message guide · Finance
TAXCON Tax control
The UN/EDIFACT message used to send summary and control data for taxes or duties applying to a batch of related messages.
- Sent by
- Seller, invoicing party or service provider
- Received by
- Buyer, tax authority or auditor
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT TAXCON message?
TAXCON is the UN/EDIFACT tax control message. The directory defines it as a message for transmitting summary and control data for tax purposes. It summarizes and controls the taxes, such as VAT, or duties that apply to a batch or batches of related messages.
Where invoices are exchanged electronically in large volumes, a control message lets the recipient, or a tax auditor, check that the tax totals of all invoices in a batch add up. Some national e-invoicing rules have required such summary or control lists alongside the invoices.
How to read this diagram: the top row shows who sends TAXCON, 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 TAXCON 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
- Summarizing VAT across a batch of electronic invoices
- Providing control totals for audit
- Meeting summary list requirements for e-invoicing
Where it fits in the message flow
Structure
Mandatory segments in TAXCON (directory D.21A)
In UN/EDIFACT directory D.21A, the TAXCON message has 16 segment positions arranged in 5 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
- SG3 (RFF)
- UNT
Practical example
TAXCON in practice
A supplier sends a retailer 500 electronic invoices a month. At month end it sends a TAXCON listing the invoice numbers with their taxable amounts and VAT by rate, and the totals. The retailer's tax team reconciles the totals with the invoices received and keeps the control message for audits.
Implementation
Implementation considerations for TAXCON
- Check whether national rules require summary or control lists.
- Reconcile control totals with the invoices they cover.
- Archive control messages with the invoices.
- Use the same tax categories and rates as the invoices.
How ECOM helps
Automate TAXCON with ECOM
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Industry
Retail
Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related finance messages
Need help with TAXCON?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.