Libraries tagged by UBL2.1
ubl21dian/torresoftware
13185 Downloads
Core for electronic invoicing pre-validation - DIAN UBL 2.1
lopezsoft/ubl21dian
1781 Downloads
Core for electronic invoicing pre-validation - DIAN UBL 2.1
darvis/ubl-peppol
2347 Downloads
Generates UBL 2.1 invoices and credit notes that pass PEPPOL BIS Billing 3.0 and EN 16931 validation, with Dutch and Belgian rules, VIES and company registration checks. Works in plain PHP; the Laravel integration is optional.
cambodia/e-invoice-sdk
1064 Downloads
CamInv (Cambodia E-Invoicing) SDK for Laravel β OAuth, UBL 2.1 XML generation, document submission, webhooks, and member management
stenfrank/ubl21dian
14000 Downloads
Core for electronic invoicing pre-validation - DIAN UBL 2.1
gtcrais/hr-einvoicing
134 Downloads
Croatian e-invoices (Fiskalizacija 2.0) for Laravel: UBL 2.1 documents under the HR CIUS 2025, sent through Moj-eRaΔun or ePoslovanje
pnscripts/pn-invoice
187 Downloads
PN Scripts Invoice: framework-agnostic PHP library to generate and validate EN 16931 e-invoices in UBL 2.1 and UN/CEFACT CII D16B syntax.
intragile/einvoicing-rules-xrechnung
39 Downloads
The KoSIT XRechnung 2.6.0 validation rules compiled to PHP arrays, the scenario table of the KoSIT validator configuration 2026-08-31 and the UBL 2.1 and CII D16B schemas it uses, for intragile/php-einvoicing.
soenac/api-dian
1025 Downloads
API Electronic Invoicing Pre-Validation UBL 2.1.
danielgp/efactura
26 Downloads
eFactura scripts to produce and read XML files containing official selling details to help out business data exchange and authorities oversight
stenfrank/soap-dian
296 Downloads
Web Service consumption of the DIAN SOAP UBL 2.1
meita/zatca-engine
48 Downloads
Framework-agnostic ZATCA Phase 2 engine for generating UBL 2.1 e-invoices (XML, hashing, signing, QR, chaining).
henry-ht/ubl21dian
110 Downloads
Core for electronic invoicing pre-validation - DIAN UBL 2.1
factpulse/sdk
84 Downloads
REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## π― Main Features ### π Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search) ### β Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) ### βοΈ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification ### π Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### π Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments) ### π‘ AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user ### ποΈ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro ### β³ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete ## π Authentication All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token? #### π Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended** for integration in your applications and CI/CD workflows. **Prerequisites:** Having set a password on your account **For users registered via email/password:** - You already have a password, use it directly **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password" }' ``` **Optional `client_uid` parameter:** To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password", "client_uid": "550e8400-e29b-41d4-a716-446655440000" }' ``` The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client **Response:** ```json { "access": "eyJ0eXAiOiJKV1QiLCJhbGc...", // Access token (validity: 30 min) "refresh": "eyJ0eXAiOiJKV1QiLCJhbGc..." // Refresh token (validity: 7 days) } ``` **Advantages:** - β Full automation (CI/CD, scripts) - β Programmatic token management - β Refresh token support for automatic access renewal - β Easy integration in any language/tool #### π₯οΈ Method 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable for quick tests or occasional use via the graphical interface. **How it works:** - Log in to the dashboard - Use the "Generate Test Token" or "Generate Production Token" buttons - Works for **all** users (OAuth and email/password), without requiring a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:** - β Quick for API testing - β No password required - β Simple visual interface **Disadvantages:** - β Requires manual action - β No refresh token - β Less suited for automation ### π Full Documentation For more information on authentication and API usage: https://factpulse.fr/documentation-api/
dcorreah/ubl21dian
260 Downloads
Core for electronic invoicing pre-validation - DIAN UBL 2.1