# Factur-X / ZUGFeRD 2.2 UN/CEFACT CII E-Invoice Parser & Validator
> Parse and validate UN/CEFACT CrossIndustryInvoice XML files (Factur-X / ZUGFeRD 2.2 EN 16931 profile) into structured JSON.

- **Canonical URL:** https://stanzaapi.com/tools/peppol-validator/standards/factur-x-zugferd-2-2
- **Governing Standard:** Peppol BIS Billing 3.0 / EN 16931 (OpenPeppol AISBL & CEN TC 434)
- **Latency:** <2ms Edge
- **Privacy:** In-memory execution only (zero data stored or logged)

## Technical Overview & Governing Rules
Factur-X and ZUGFeRD 2.2 are identical Franco-German hybrid e-invoice standards utilizing UN/CEFACT CrossIndustryInvoice XML syntax.

Extracts SupplyChainTradeTransaction, ApplicableHeaderTradeAgreement, ApplicableHeaderTradeSettlement, and IncludedSupplyChainTradeLineItem.

Full validation of trade tax breakdowns, payment means (SEPA Credit Transfer 30/58), and SIREN/SIRET French participant identifiers.

## Specification Matrix
| CII XML Node | Field Name | Target JSON Property | Specification |
| --- | --- | --- | --- |
| rsm:ExchangedDocument/ram:ID | Invoice Number | invoice.id | Mandatory string |
| rsm:ExchangedDocument/ram:TypeCode | Document Type Code | invoice.documentType | 380 (Invoice) / 381 (CreditNote) |
| ram:ApplicableTradeTax | Tax Breakdown | invoice.taxSubtotals | UNTDID 5305 Tax Category |
| ram:SpecifiedTradeSettlementHeaderMonetarySummation | Totals | invoice.totals | Line extension, Tax basis, Payable |

## Standard JSON Response Model
```json
{
  "valid": true,
  "syntax": "CII_INVOICE",
  "profile": "PEPPOL_BIS_BILLING_3_0",
  "summary": {
    "status": "COMPLIANT",
    "fatalCount": 0,
    "warningCount": 0
  }
}
```

## Frequently Asked Questions & Edge Cases
### Q: Does this support the French 2026 B2B e-invoicing mandate?
**A:** Yes. Factur-X (CII) and UBL 2.1 are the two primary syntax formats mandated for French B2B electronic invoicing and PDP (Plateforme de Dématérialisation Partenaire) compliance.