Skip to main content
📢 Looking to add e-invoicing support for France? We've partnered with Ecosio to extend coverage there. This is an upgrade to your current e-invoicing subscription — contact your Account Manager to get started.

Release 2.22.0

General information

Version 2.22.0 was released on 7th August 2026 and introduces multi-invoice PDF splitting, French e-invoicing lifecycle notifications, Business-to-Government (B2G) e-invoicing for France, and AP Payments enhancements and bug fixes. Below you can find more information related to the changes introduced in the new version. We will update your live account automatically and the sandbox account can be updated from the customer's end at any given time.

Note: French e-invoicing is available for new, selected Ecosio-connected configurations at this time. If you're interested in enabling French e-invoicing for your account, please reach out to your Account Manager. 

Enhancements

PDF multi-invoice splitting

ZoneCapture introduces manual PDF splitting, enabling users to upload a single PDF containing multiple invoices and split it into individual Bills to Process.

A new "Manual Split" checkbox on the Manual Upload page allows users to indicate their PDF contains multiple invoices. After clicking Process, the user is routed to a visual PDF Splitter where they can mark where each invoice starts. On submission, the PDF is split client-side and each segment is created as a separate Bill to Process, sent to OCR, and appears in the Incoming queue. Please check this article for more information: How to Split a Multi-Invoice PDF in ZoneCapture.

France e-invoicing — lifecycle notifications

ZoneCapture expands French e-invoicing support with full lifecycle notification handling, enabling compliance with the French e-invoicing mandate's status reporting requirements.

  • Inbound application responses: When a sent e-invoice receives an application response (e.g. 202 — Received by Platform, 203 — Made Available, 213 — Rejected), ZoneCapture creates an E-Invoicing Notification record linked to the original invoice, keeping lifecycle statuses out of the AP queue.
  • Receive Refused notification: When a buyer refuses a sent e-invoice (FR:210), the refusal status and reason are displayed in the Failed E-invoices section of the ZoneCapture portlet and on the E-Invoicing Sending Notification Summary record.
  • Send Refused notification: When a user rejects an incoming vendor bill or Bill to Process record, ZoneCapture sends a Refused (210) ApplicationResponse to Ecosio. An E-Invoice Application Response Send Log record is created for audit purposes, and any delivery failures are reflected in NetSuite with error details.
  • Option to skip refusal notification: When rejecting a Bill to Process record, a checkbox (checked by default) controls whether the refusal is reported to the French tax authority. Unchecking it changes the button label to "Reject in NetSuite Only."
  • Payment Received notification - daily sync: A new Map/Reduce script syncs Payment Received (FR:212) notifications to Ecosio daily for fully paid French domestic invoices. A dedicated saved search surfaces any failed notifications for AR managers.

France e-invoicing — B2G support

ZoneCapture now supports sending e-invoices to French government recipients via Chorus Pro through Ecosio.

  • A new "ZC E-invoice B2G Flow" checkbox on the Customer record triggers the B2G template when the recipient is a government entity.
  • Two new fields on ZC Subsidiary Setup — B2G Chorus Pro Endpoint ID and Endpoint Scheme — allow configuration of the subsidiary's Chorus Pro registration details.

Support outbound e-invoices with billable expenses

Invoices containing billable expenses can now be sent as e-invoices via Ecosio. Quantity defaults to 1, price defaults to the line amount (positive), and the item name is sourced from the line description or a configurable default item on the Subsidiary Setup.

Zone AP Payments Improvements

  • (SC-5187) Auto-populate Pay To bank account: When a Vendor has exactly one active Beneficiary Bank Account and no AP Primary Beneficiary Bank Account is set, ZoneCapture will automatically populate the Pay To field on the Vendor Bill, reducing manual effort during bill entry.
  • (SC-5214) Prevent deletion of AP Payment batch records: To ensure data integrity between NetSuite and Transfermate, as well as prevent unforeseen issues caused by data deletion, AP Payment Batch records can no longer be deleted once registered with TransferMate. Users should reject the batch instead of deleting it, preventing flow-breaking scenarios where a duplicate batch cannot be authorized.
  • (SC-5231) Saved search for Beneficiary Bank Account errors: A new bundled saved search displays all Beneficiary Bank Account records that failed validation, showing the API error, bank country, account number type, and other key fields for efficient troubleshooting.
  • (SC-5237) Extend Rejected Payments saved search: The ZC AP Rejected Payments saved search now includes a Rejection Reason column and covers AP Payments with a Cancelled status in addition to Rejected, with a Status column to differentiate between the two.

Bug fixes

SC-4949: Outbound e-invoice fails due to negative quantity on certain item account types

Outbound e-invoices containing items with Income Account types of Fixed Assets, Other Expense, or Other Current Asset were failing validation due to negative quantity and amount values in the XML. This has been resolved for both Basware and Ecosio providers.

SC-5104: 3-Way Matching "Quantity not allowed for this item" popup with Description Type Items

When processing a vendor bill linked to a Purchase Order containing a Description Type item line, clicking the 3-Way Matching Submit button triggered an unexpected "Quantity not allowed for this item" popup. The popup no longer appears — description-type item lines are handled correctly during 3-Way Matching submission.

SC-5188: [AP Payment] Special characters in beneficiary name causing creation failure

When vendor names contained non-ASCII characters (e.g. Polish diacritics, German umlauts), beneficiary creation with TransferMate failed silently. The system now applies transliteration — mapping non-ASCII characters to their closest ASCII equivalents — before sending data to the TransferMate API.

SC-5272: [AP Payment] Bill status not updating after TransferMate payment cancellation

When TransferMate returned a Cancelled payment status, the AP Payment record was updated correctly but the associated NetSuite Bill Payment was not voided, leaving the bill in an incorrect paid state. The system now voids the Bill Payment and reopens the bill to Open status, and displays a warning banner on the bill record.

Was this article helpful?