Technical Features September 2026

Connectors

---

AFNOR API - lifecycle status (CDAR)

• The CDAR 209 'Complete' (Approuvée Complète) lifecycle status is now delivered from the seller's platform (PA-S) to the buyer's platform (PA-R) to confirm the full resolution of a disputed invoice.

• Error acknowledgements returned by the AFNOR API for rejected CDAR submissions are now more precise, including specific reason codes like InvoiceLCAccessDenied and InvoiceLCStatusError to help integrators easily diagnose failures.

AFNOR API v1.3.0

• The AFNOR Flow Search API v1.3.0 now simultaneously supports both cursor-based pagination and the existing date-based updatedAfter approach.

• The AFNOR API and its documentation align with the v1.3.0 specification, including updates to search endpoints, enum values, parameter defaults, required fields, and Schematron 1.4.0 validation to improve consistency and clarity for integrators.

• The webhook configuration API has been updated in line with the AFNOR v1.3.0 specification, adding new fields and validations to refine how webhooks are created, retrieved, and deleted.

France e-Invoicing

• For invoices sent to buyers not registered on an e-invoicing platform (PA), the system now automatically submits a mandatory "Deposée" status (code 200, "Customer Without Platform") to the PPF national directory to ensure regulatory compliance and traceability.

• Lifecycle status 213 events for sent or received CDAR 213 documents are now recorded in the Activities tab under the Connector section to give users a consolidated view of all CDAR lifecycle activity.

• Key events related to the Peppol connector and national directory registration are now recorded in the connector's activity log, giving platform operators full visibility and improving traceability and auditability for French PDPs managing connector lifecycles.

Peppol document delivery

• The document sending and redelivery flow for Peppol and email connectors has been improved for reliability and correctness by formalizing the Send and Finalize payload contract, resolving FR Flow 10 compliance issues, streamlining the French send pipeline, and correcting recipient routing.

• Users can now update the participant ID and trigger reprocessing for documents stuck in delivery due to an incorrect Peppol address, without needing to recreate the document from scratch.

Schematron validation

• Peppol validation error messages now include the precise field path where a rule violation was detected, making it significantly easier to identify and correct the offending data.

Improved Peppol lifecycle visibility

Monitoring your Peppol network status is now more transparent with clear event messages when connectors are enabled/disabled or when specific identifiers are successfully published/unpublished.

List of the messages:

Subcategory	Action / Case	Trigger	Display Message / Format
peppol_extension_lifecycle_succeeded	CONNECTOR_ENABLED	Activation completes successfully (async Pub/Sub or sync REST).	Peppol connector was enabled for this space. Published identifiers: [publishedIds]
peppol_extension_lifecycle_succeeded	CONNECTOR_DISABLED	Deactivation completes successfully.	Peppol connector was disabled for this space. Unpublished identifiers: [unpublishedIds]
peppol_extension_lifecycle_succeeded	IDS_PUBLISHED	Configure call publishes identifiers to the Peppol network.	Peppol identifier(s) were published to the Peppol network: {publishedIds}.
peppol_extension_lifecycle_succeeded	IDS_UNPUBLISHED	Configure call publishes no identifiers but successfully unpublishes one or more identifiers.	Peppol identifier(s) were unpublished from the Peppol network: {unpublishedIds}.
peppol_extension_lifecycle_succeeded	SEND_ONLY_ENABLED	sendOnly changes from false to true via configure.	Peppol connector Send Only mode was enabled. The space will send documents but not receive via Peppol.
peppol_extension_lifecycle_succeeded	SEND_ONLY_DISABLED	sendOnly changes from true to false.	Peppol connector Send Only mode was disabled. The space will now both send and receive documents via Peppol.
peppol_extension_lifecycle_succeeded	WITHOUT_VAT_DECLARATION_ENABLED	pdpEnabled changed to false (opts out of National Directory participation).	Peppol connector configured to operate without VAT declaration.
peppol_extension_lifecycle_succeeded	WITHOUT_VAT_DECLARATION_DISABLED	pdpEnabled changed back to true (opts back into National Directory participation).	Peppol connector VAT declaration requirement was enabled.
peppol_extension_lifecycle_succeeded	Fallback (General Update)	Any succeeded event not explicitly listed above	Peppol connector has been updated successfully.
peppol_extension_lifecycle_failed	ID_PUBLISH_ERROR	Identifier fails to register in SMP/NatDir during activation or configuration.	Peppol identifier {identifier} failed to publish to the Peppol network.
peppol_extension_lifecycle_failed	ID_UNPUBLISH_ERROR	Identifier fails to deregister from SMP/NatDir during deactivation or configuration.	Peppol identifier {identifier} failed to unpublish from the Peppol network.
peppol_extension_lifecycle_failed	Terminal Activation Failure (No action field)	Async Pub/Sub activation flow fails with a business error and all retries are exhausted.	Failed to update Peppol connector.

Document conversion

---

Improved validation for non-EU and international invoices

Banqup has enhanced its e-invoice validation logic with a smart fallback system that automatically maps non-EU seller identifiers (BT-29), tax registration fields (BT-32), and standard fallback identifiers for missing OCR data to prevent validation errors and streamline international invoice processing.

Robust Factur-X data extraction

The document conversion engine has been refined to better handle non-standard Factur-X invoices by automatically managing minor inconsistencies, such as sanitizing numeric fields by trimming spaces to prevent data extraction errors.

Improved validation for mismatched file types

The platform's enhanced file content validation against its declared format now returns a 422 Unprocessable Entity status titled "Invalid document content" instead of a generic internal error when a file's content does not match its declared format.

Improved seller contact data mapping

To ensure EN16931 compliance and data accuracy, the bidirectional mapping for the Seller Contact Point (BT-41) has been enhanced to fully preserve and intelligently merge the supplier's contact name using the metadata.supplier.partyContactName field during UBL, CII, and Factur-X document conversions.

Product data - Tax Simulator app

---

The Tax Simulator operates as a stateless, visual client layer over the Banqup Tax Service REST API, enabling real-time validation of tax engine logic without custom integration code.

Architecture and execution flow

• Frontend serialization: Client-side inputs are mapped to a structured JSON payload and transmitted via HTTP POST to the Banqup Tax Service core endpoint.
• Engine processing: Executes out-of-the-box tax determination matrices across EU, UK, CH, and NO jurisdictions using global reference data.
• Audit and debugging: Provides a Developer View exposing unparsed Request/Response JSON payloads alongside complete rule evaluation logs.

Input payload mapping

• Primary parameters:
  • Invoice directional flags: AR (Accounts Receivable) or AP (Accounts Payable).
  • Temporal markers: Tax point date (defaults to runtime ISO timestamp if omitted).
  • Geographic indicators: ISO country codes for Seller, Buyer, Ship-From, and Ship-To locations.
  • Product classifications: System tax product identifiers or standard commodity codes (e.g., HSN).
• Extended contextual traits (modals):
  • Establishment context: Primary jurisdiction overrides and subdivision locations.
  • Tax registration arrays: Tax ID numbers, registration types (e.g., TTID, MTID), and issuing territories.
  • Regime flags: Boolean toggles for Electronic Interface status, Small Enterprise (SME) exemptions, and One Stop Shop (OSS) applicability.

Fallback mechanics and output resolution

• Omitted non-required attributes trigger pre-configured default resolution logic within the engine.
• Output includes system decision codes (e.g., MEM044) documenting triggered rules, applied fallbacks, and parameter warnings.
• Returned data schema:
  • Classification: DOMESTIC, INTRA_EU, EXPORT, IMPORT, or OUT_OF_SCOPE.
  • Determination Results: Legal place of supply, rate category (STANDARD_RATE, REDUCED_RATE, ZERO_RATE), numeric rate percentage, and reverse charge boolean flag.
  • Financial Breakdown: Taxable basis, invoice tax, payable tax, deductible tax, and the standardized system tax code string.

Payments

---

Improved payer address validation

To improve SEPA and foreign currency payment success rates, Banqup now always includes the payer's city and country in payment requests - even if a full street address is unavailable. This prevents rejections caused by missing address data, especially for non-EEA (European Economic Area) SEPA transactions.

Banqup card ATM withdrawal billing

Banqup Card billing logic now automatically categorizes ATM withdrawals by location - separating EEA and International transactions - to ensure accurate fee application per your service agreement.

SEPA Direct Debit initiation tracking

To ensure that billing records accurately reflect all payment activities, we have enhanced the tracking of SEPA Direct Debit (SDD) collections. The system now captures a billing event as soon as a Direct Debit initiation is successfully planned. This update ensures that the initiation phase of a payment is correctly recorded in the system.

Reconciliation

---

Enhanced reconciliation matching

Auto-reconciliation now compares (next to a literal match) also normalised payment references (ignoring special characters and letter casing) to improve matching accuracy:

• Identifies document numbers embedded inside longer text strings.
• Suggests matches for exact payment amounts within a 4 calendar days window to account for bank delays.
• Automatically confirms exact dates paired with references over 6 characters long.
• Triggers proposed matches for 4–6 character references, while ignoring references of 3 characters or fewer to prevent false positives.

Advanced fuzzy name matching

To better handle card payments and transactions where supplier names vary, we have implemented an intelligent fuzzy name matching algorithm. This feature allows the system to link bank movements to documents even when the names aren't identical.

The algorithm performs the following:

• It automatically ignores common legal suffixes and prefixes such as "BV", "NV", "SA", "SRL", or "GmbH" during the comparison process.
• The system calculates a similarity score. High-confidence matches (e.g., "K B C SRL" vs "KBC") are automatically linked, while medium-confidence matches are presented as proposals if the amount and date are within acceptable ranges.
• This logic specifically solves issues where card transaction descriptions (like "MASTERCARD * AMAZON.BE") need to be matched against official supplier names (like "AMAZON EU SARL").

Connection-based reconciliation

We have introduced a new CONNECTION_EXACT rule to provide high-confidence matching for recurring business partners. This rule prioritizes matches where both the transaction amount is exact and the counterparty's connection details (such as a known IBAN) match the information stored on the document. This ensures that payments to verified suppliers are reconciled instantly and accurately.

Document Processor

---

Chorus Pro (G2B) integration

Automated Chorus Pro (G2B) invoice processing

Automated handling for Chorus Pro (G2B) invoice TAR archives has been introduced to automatically extract, convert, track, and route individual XML invoices to the Peppol Connector and the buyer's Purchases folder with enhanced error handling.

Automated government partner creation for Chorus Pro invoices

When receiving a Chorus Pro G2B XML invoice, Banqup now automatically identifies and registers the supplier as a "Government" business partner if they do not already exist, integrating partner registration into the document processing pipeline.

Document finalize and delivery

Smart compliance and connector management

Banqup now features a fully redesigned document finalization and delivery pipeline with three integrated services:

• The new Compliance Service - automatically evaluates each document's transaction context - sender/recipient country, invoice classification, and live Peppol/PPF registry lookups - to determine which connectors can deliver it, in which format, and under which regulatory constraints.
• The Finalize Action - replaces the legacy finalize operation with a dialog-driven flow that runs a live compliance check upfront, pre-selects the best connector, and surfaces warnings before any document is sent.
• The Delivery Service - acts as the single orchestration entry point - managing concurrency, handling participant ID changes, and dispatching to the correct connector (Peppol, KSeF, Email) with full delivery status tracking.

Document management and actions

Draft PDF safeguards for electronic files

Banqup now includes a specific "draft" marker in the metadata of temporary PDF representations to prevent them from being accidentally used for FacturX generation or embedded into other electronic files.

Automated tasks for pending actions

The system now automatically generates a task in the user's Todo list when a file enters the AWAITING_USER_ACTION status and removes it once the necessary action is taken and the document transitions to a different status.

Data extraction and OCR

Automated approval for OCR documents

Enhanced automation logic for OCR-processed documents now correctly applies trusted supplier settings to extracted invoices and enables space-level auto-approval for purchase receipts.

Improved line-level discount extraction

Data extraction has been improved to accurately handle discounts applied at the invoice line level by converting negative values into a compliant format - a positive unit price with a negative quantity - ensuring that document totals, VAT, and discounts are calculated perfectly without manual adjustments.

Disabling the "Human-in-the-loop" (HITL) manual verification step

Due to the increased accuracy of the automated OCR engine, the document extraction workflow has been optimized by disabling the "Human-in-the-loop" (HITL) manual verification step to provide faster processing times.