Skip to main content

Technical Features August 2026​

Connectors​

France e-Invoicing​

Invoice lifecycle flows (buyer side)​

As a buyer's platform (PA-R) under the France e-Invoicing mandate, the system now supports additional invoice lifecycle status messages to give buyers and sellers clearer visibility into an invoice's status at every processing stage.

When a buyer disputes an invoice due to missing documentation, the system automatically sends a "Suspendue" (Suspended, code 208) status to notify the seller, and upon the seller resolving the issue with supplementary information, the platform processes the "Complétée" (Completed, code 209) status to lift the suspension and update the buyer's invoice.

Invoice lifecycle flows (seller side)​

As a seller's platform (PA-S), the system now supports a full set of inbound and outbound invoice lifecycle status messages - including "Rejetée à l'émission" (code 213), "Mise à disposition" (code 203), "Suspendue" (code 208), "Complétée" (code 209), "Rejetée" (code 213), and "Prise en charge" (code 204) - providing sellers with transparent, real-time tracking of their invoices throughout the regulatory process.

Lifecycle status visibility and audit​

Several platform improvements now enhance visibility and traceability by automatically sending a "Prise en charge" (code 204) status upon invoice opening or processing, logging clear rejection reasons for "Rejected" (code 213) statuses in the Activities tab, and storing CDAR feedback files from the PPF to maintain a complete audit trail.

Payment lifecycle compliance​

Two improvements strengthen compliance with French regulatory lifecycle rules by updating operation endpoints for invoice status changes to the latest API version and tightening the conditions for sending the "Encaissée" (code 212) status to the PPF only when VAT is legally due.

France e-Reporting (F10)​

The F10 e-Reporting pipeline for VAT transaction reporting to the French public portal has been strengthened through atomic database persistence (no partial or duplicate records are created), enhanced multi-level duplicate detection, stored PPF feedback acknowledgements for auditability, and automated Liquibase database schema migrations.

France CTC - Schematron compliance update​

The validation rules for French CTC invoice formats (Factur-X, UBL, CII, and CDAR) have been updated to FNFE schematron version 1.4.0, which becomes mandatory for outgoing invoices starting 1 September 2026 to ensure full regulatory compliance and reduce the risk of rejection by the PPF or trading partners.

Peppol connector - VAT declaration compliance​

Businesses that activate the Peppol connector without VAT declaration to the PPF (Option 1) now correctly receive mandatory regulatory notifications, with the platform automatically sending required "Refused" and "Rejected" CDAR status messages to the PPF to fulfill regulatory obligations regardless of the selected option.

G2B invoice reception​

The platform can now receive invoices issued by French public entities (Government-to-Business flows) pushed by Chorus Pro. This covers invoices in both UBL and Factur-X formats, and the platform will automatically acknowledge successful receipt or report a rejection to Chorus Pro if the invoice fails technical validation - ensuring full traceability and compliance with the AFNOR interoperability framework.

AFNOR API​

Partner lifecycle status processing​

By using the AFNOR API, partners can now directly submit invoice lifecycle status messages - including CDAR 210 "Refusée" (Refused), CDAR 207 "En litige" (Disputed), and CDAR 205 "Approuvée" (Approved) - to enable a richer and more automated invoice approval workflow.

Directory & flow enhancements​

The AFNOR API has been upgraded to version 1.3 to align with the latest AFNOR specification, introducing Directory Service and Flow Service enrichments, business instruction flags, an expanded flow type taxonomy, and increased identifier lengths.

Webhook management​

Partners using the AFNOR API can now subscribe to, list, and unsubscribe from webhooks (POST/GET/DELETE /webhooks) to receive real-time, event-driven push notifications secured in v1.3 with HMAC-SHA-256 server-side signing and timestamp headers.

Corrections & enhancements​

The AFNOR API has been improved for a better developer and partner experience through a reorganized documentation structure grouping endpoints into AFNOR Flow API (Flow, Webhook, Supervisor) and AFNOR Directory API (Directory Line, Routing Code, Siren, Siret), clear structured error responses with an InvoiceLCAccessDenied reason code for unauthorized role status submissions, and support for downloading Converted Factur-X versions of submitted invoices.

Document conversion​

Enhanced payment means mapping​

To ensure full compliance with Peppol BIS3 and EFFF specifications, the mapping for Payment Means has been refined to correctly capture the descriptive text for payment methods (BT-82) and map it to the appropriate attributes within the UBL XML output, ensuring human-readable payment instructions are properly displayed in generated documents.

Improved CII and Factur-X schema compliance​

The serialization logic for CII and Factur-X documents has been updated to strictly adhere to XSD sequence requirements - specifically correcting the positions of Monetary Summation fields (Rounding Amount BT-114 and Charge Total) and the Header Settlement field (Bank Assigned Creditor Identifier BT-90) - ensuring generated files pass all official validation checks and comply with French and European e-invoicing standards.

UBL allowance and charge compliance​

To align with modern Peppol BIS 3.0 and EN16931 standards and ensure smoother document transmission across the Peppol network, the system no longer includes the legacy listID attribute for allowance and charge reason codes in UBL documents.

French CTC extended profile support​

To prevent French tax authority (CTC) validation consistency errors for users of the French EXTENDED-CTC-FR profile, Banqup automatically populates line-level VAT exemption reasons by mapping document-level exemption reasons or codes directly to the corresponding invoice lines.

UBL credit note reconciliation​

Outbound UBL Credit Notes have been updated to include detailed document-level allowance and charge information (BG-20 and BG-21), ensuring XML visibility, compliance with strict EN16931 validation rules, and accurate reconciliation of VAT taxable amounts.

Inbound CTC profile recognition​

The inbound document processor now recognizes a broader range of French CTC Profile IDs (B4, S4, M4, S5, and S6) and correctly identifies the business process as goods, services, or mixed during conversion to Banqup's internal format.

VAT point date support (BT-8)​

Banqup now supports the VAT point date code (BT-8) across UBL, CII, and Factur-X formats, correctly extracting the code from incoming electronic files and automatically inserting the corresponding regulatory code into generated XML when a VAT chargeable method is selected to ensure compliance with semantic e-invoicing rules.

Flux 1 BASE profile compliance​

To ensure seamless integration and regulatory compliance with French e-invoicing requirements when submitting to platforms like Chorus Pro, Banqup now supports a strictly enforced "Flux 1 BASE" profile for outbound invoices and credit notes, which includes strict data filtering, standardized identifiers, precise date formatting, refined tax and totals mapping, and automatic profile identification.

Enhanced UBL compliance for payment identifiers​

To ensure compliance with the EN16931 standard and Peppol syntax rules and prevent validation errors in Continuous Transaction Control (CTC) and Peppol delivery channels, payment account details in UBL invoices and credit notes have been refined by removing the schemeID attribute from the Payment Account Identifier field (BT-84) per rule UBL-CR-654 and correctly mapping the Payment Service Provider Identifier (BT-86) to the Financial Institution Branch ID.

Precise payment data extraction and conversion​

To ensure digital representations of invoices remain faithful to source data, payment information conversion between JSON and Factur-X/CII formats has been improved by preserving payment means descriptive text (BT-82) and updating the document extractor to stop injecting default "Credit Transfer" codes when source data lacks specific payment method information.

Enhanced line item identification for e-Invoicing compliance​

To ensure full compliance with international e-invoicing standards - including EN 16931, PEPPOL, and BR-21 - and prevent technical rejections, the generation of line item identifiers (BT-126) during document conversion has been refined to ensure every invoice line contains a valid ID.

When converting documents to Factur-X (CII) or UBL (Invoice & Credit Note) formats, the system now populates the Line ID using an externalLineId from metadata if provided, or automatically assigns a 1-based sequential index based on item order if no identifier exists.

This improvement guarantees that all generated XML files satisfy mandatory XSD and Schematron validation rules, ensuring seamless document exchange across all supported profiles, including BASIC, EN 16931, and EXTENDED.

Improved french supplier identification​

To ensure data consistency and prevent validation mismatches, data extraction for French suppliers has been enhanced: the 9-digit SIREN is automatically identified and extracted from provided 14-digit SIRET codes to populate the Supplier Legal Organization ID (BT-30) during JSON conversion across all standard electronic invoicing formats, including Factur-X, CII, and UBL.

Document processor​

Lifecycle message payload revision​

To improve consistency and data clarity for downstream subscribers, lifecycle message payloads have been standardized with enhanced routing context (channel), guaranteed event ordering (orderGroup), a new FileProcessingFailed event type, updated field names (documentNumber and documentCategory), detailed extraction metadata (extractionEngine), and streamlined payloads for refused and disputed documents.

Injecting a sample document number into XML and PDF preview​

To ensure a smoother experience and compliance with the French electronic invoicing reform, the Document Creator now automatically generates and injects a sample document number during the validation and conversion phase using configured numbering series or supplier prefixes (for self-billed documents), preventing validation rules (such as BR-FR-01) from blocking document creation before a formal number is officially assigned.

Document processing & OCR​

Currency detection for purchase invoices​

To reduce manual corrections and automate data entry, the OCR engine now uses a smarter currency identification logic that applies the extracted currency, derives the local currency from the supplier's country if no currency is found, or defaults to EUR as a final fallback.

Improved validation handling and data preservation​

To ensure no data is lost during ingestion and to allow manual review, documents with invalid data patterns or failed checksums now move rejected field values to the rawData field rather than discarding them, while technical integrations update the validation error code to document.field.invalid and trigger a validation_failed lifecycle message for structured Peppol documents to support CDAR rejection handling.

Enhanced processing events and error tracking​

To improve visibility into the document lifecycle, new automated notifications have been introduced for document status changes. A space event is emitted whenever a file is reprocessed, and a specific "com.unifiedpost.btx.documents.lifecycle.v1.FileProcessingFailed" lifecycle message is emitted if a document's attachment fails during conversion.

Draft PDF safeguards for compliance​

To ensure document integrity and regulatory compliance, a safety mechanism has been introduced that marks draft PDFs with a draft=true metadata flag, which the document pipeline mandatorily checks to prevent draft documents from being accidentally embedded into official electronic files or used for FacturX generation.

Reconciliation and payments​

Enhanced automatic payment method assignment​

To reduce manual corrections and speed up purchase invoice processing, Banqup now intelligently prioritizes the correct payment method by following a hierarchy that applies high-confidence OCR extraction first, uses the supplier's default Business Partner payment method as a second priority, and falls back to "Other" if no default is set.

Improved payment actions for migrated documents​

To improve the consistency and accuracy of managing imported legacy records, the logic for "Migrated" documents has been updated so that payment status actions appear contextually, state transitions function accurately, and the "Resolve" action is tuned to exclude non-applicable migrated documents.