New Features and Enhancements in Accounting Summer 2026

The following new features have been introduced in the Summer 2026 release of Accounting.

If you are upgrading from a previous version, see Upgrading to Accounting Summer 2026. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.

If you are upgrading from a version earlier than Spring 2026, check the documentation for previous releases for upgrade details.

Dependencies on Other Certinia Packages

Accounting Summer 2026 requires the following Certinia packages to be installed in this order:

  1. Foundations Summer 2026
  2. Reporting Spring 2020

You must install these packages before installing or upgrading to Accounting Summer 2026.

Allow override Product GLA in Payable Invoices and Payable Credit Notes

You can now override the default product general ledger account (GLA) directly on payable invoices (PIN) and payable credit notes (PCR). After enabling the new Override Product GLA for PIN and PCR custom setting, you can populate the Override Product GLA and Override Product Local GLA fields on both documents, replacing the previous need for manual data preparation and month-end adjustment journals to correct posting.

To keep your data accurate, new validation rules enforce that you can only use a local GLA when the custom setting is enabled, prevent both the override product GLA and the override local GLA from being populated at the same time, and confirm that any override local GLA matches the local chart of accounts (COA) for both the owner and destination companies. Clear error messages appear if a mismatch occurs or if the owner company has no local COA.

This ensures accurate financial posting at the source, reduces reliance on downstream corrections, and gives you confidence that overrides comply with your local accounting structure.

Creating Prepaid Expense Journals

We have introduced a new Lightning tab that streamlined the prepaid expenses journal creation process, removing unnecessary steps and allowing you to easily review and edit your journal proposals before you generate the prepaid expenses journals.

The new process begins with a blank proposal to which you can add the prepaid expense lines and specify the journal criteria. You can then review the proposal before generating your prepaid expense journals.

You can create up to 200 journals at a time using this page.

As part of this change we have added a new field set, Expense Lines Dynamic Fields, to the Payable Invoice Expense Line Items object, that allows you to select the columns that are displayed on the new Add Expense Lines window.

Note:

The existing Prepaid Expenses page is no longer supported and will be deprecated in a future release. We recommend that you use the new Prepaid Expenses Lightning Page.

For more information, see Creating Prepaid Expenses Journals.

Meeting Poland VAT Reporting Requirements with Updated Compliance Support

We've introduced new capabilities to help you meet the latest Electronic Invoicing requirements in Poland, ensuring your org remains compliant with the National E-Invoicing System (KSeF). These updates automate the exchange of invoice data and ensure every document carries the mandatory legal identifiers aligning with the Poland VAT Reporting mandate.

To enable this, we've expanded our Avalara mappings to help you stay compliant with the Poland VAT Reporting mandate. This update ensures your accounting documents communicate correctly with Avalara for accurate tax filling.

To support this integration, the following fields mappings are now mapped from sales invoices, sales credit notes, payable invoices, and payable credit notes to Avalara:

  • Unique Document Code
  • Unique Document Code Type
  • Unique Document Code Country

The Unique Document Code and Unique Document Code Type fields are now available on the Sales Invoice, Sales Credit Note, Payable Invoice, and Payable Credit Note objects. Once the accounting document is issued and approved by Poland's National E-Invoicing System, these fields are populated via Storecove with the assigned KSeF ID.

To maintain alignment with Storecove's seamless integration, the Electronic Invoice receiving flow has been migrated to their new received-documents webhook. This migration is purely backend-focused; the data captured from received documents and the information displayed on the resulting payable invoices and payable credit notes remain unchanged.

To help you activate the values required for these identifiers, we've added the Electronic Invoicing Localization feature on the Feature Console. For Poland, this feature adds the required values to the Unique Document Code Type picklist and cross-references the Avalara VAT Reporting Integration feature for customers who use Avalara VAT Reporting.

For more information, see Enabling Electronic Invoicing Localization.

Note:

This enhancement is also documented in Foundations Summer 2026. New Features and Enhancements in Foundations Summer 2026

Classify Tax Codes for Storecove E-Invoicing with a New Tax Category Field

You can now record the tax category for each tax code that you use when generating electronic invoices and credit notes through Storecove. The new E-Invoicing Tax Category picklist field has been added to the Tax Code object and defaults to standard, with additional values available for you to add as your e-invoicing requirements expand.

This enables you to prepare your tax codes for upcoming country-specific e-invoicing mandates by capturing the exact tax category that the e-invoicing provider expects, in one consistent location.

For more information, see Tax Code and Rate Fields.

 

Supporting the French Electronic Invoicing Mandate

We've extended the integration of Accounting with Storecove for French Electronic Invoicing (e-invoicing), supporting French companies in sending and receiving invoices in compliance with French legislation. This leverages the Storecove connection for seamless, secure and authenticated e-invoice exchange.

This release introduces the following:

  • A new E-Invoicing Document Entity Type field on Account records to set the default document entity type for e-invoices sent from or received by an account. Supported values are Invoice/B2B, Invoice/B2G, and Simplified invoice/ticket/B2C.
  • A new Invoice/B2G value for the Document Entity Type field on sales invoices and sales credit notes, supporting business-to-government e-invoicing.
  • New send-side field mappings for additional party roles required by French e-invoicing: BuyerAgent, PayerParty, PayeeParty, InvoiceeParty, InvoicerParty, FrCadreDeFacturation, InvoiceTypeCode, and CreditNoteTypeCode. PublicIdentifier mappings are also available for all party roles.
  • New receive-side field mappings for BuyerAgent and InvoiceeParty on payable invoices and payable credit notes. PublicIdentifier mappings are also available for all party roles on the receive side.
  • New line-level field mappings for AdditionalItemProperties, including name code, value quantity, and value quantity unit code, on both send and receive sides.

To set up French electronic invoicing, see Setting Up French Electronic Invoicing.

Supporting the French Electronic Invoicing Mandate

Expand French Electronic Invoice Support with Additional Party Roles

You can now include and receive the full set of party roles required by the French electronic invoicing reform when exchanging invoices through Storecove. Six new party fields — BuyerAgentParty, PayerParty, SalesAgentParty, InvoiceeParty, InvoicerParty, and PayeeParty — are now available on outbound electronic invoices and can be populated using custom field mappings. When receiving electronic invoices, Certinia captures these same party roles automatically, along with full address, contact, and identifier details for the delivery party, which were previously captured by name only.

This enables French companies to exchange electronic invoices that carry all the party information required by the French mandate, and to retain that data faithfully in Accounting when receiving invoices from trading partners.

For more information, see Field Mappings for Sales Invoice to Electronic Invoice and Field Mappings for Sales Credit Note to Electronic Invoice.

 

Supporting the French Electronic Invoicing Mandate

Specify Reason Codes and Tax Exemption Details on Allowance and Charge Lines for Electronic Invoicing

You can now specify a coded reason, a tax exemption reason, and a tax exemption reason code on allowance and charge lines when sending electronic invoices, and map those same details from inbound electronic invoices to your payable invoices and payable credit notes. Three new fields — AllowanceCharges.ReasonCode, AllowanceCharges.TaxExemptionReason, and AllowanceCharges.TaxExemptionReasonCode — are now available for mapping in the Electronic Invoicing field mapping UI, alongside the existing free-text AllowanceCharges.Reason field.

This enables you to include structured compliance data on allowance and charge lines, helping you meet regulatory requirements such as Peppol BIS UNCL5189 and the French electronic invoicing mandate (FR-FE).

For more information, see Field Mappings for Sales Invoice to Electronic Invoice, Field Mappings for Sales Credit Note to Electronic Invoice, Field Mappings for Electronic Invoice to Payable Invoice, and Field Mappings for Electronic Invoice to Payable Credit Note.

Supporting the French Electronic Invoicing Mandate

Map Allowance-Charge Reason Codes and Tax Exemption Details on Outbound Electronic Invoices

Map Additional AllowanceCharge Fields on Outbound Sales Invoices and Sales Credit Notes for French E-Invoicing

You can now map allowance-charge reason codes and tax-exemption details on outbound sales invoices and sales credit notes sent as electronic invoices. The Reason Code, Tax Exemption Reason, and Tax Exemption Reason Code source fields are now available in the outbound mapping for the AllowanceCharge object, alongside the existing Reason field.

This enables you to send French e-invoices that carry the additional allowance-charge metadata required by the FR-FE and Peppol BIS profiles, so your outbound sales invoices and sales credit notes meet French compliance requirements without custom development.

For more information, see Field Mappings for Sales Invoice to Electronic Invoice and Field Mappings for Sales Credit Note to Electronic Invoice.

Supporting the French Electronic Invoicing Mandate

Map Additional Note Fields on Sales and Payable Documents for Electronic Invoicing

You can now map up to three invoice-level notes on outbound sales invoices and sales credit notes, and on inbound payable invoices and payable credit notes, and up to three line-level notes on line items for electronic invoicing. The Field Mapping UI for e-invoicing now exposes Notes[0], Notes[1], and Notes[2] at both header and line level, alongside the existing singular Note field at header level.

This enables you to send and receive richer contextual information on electronic invoices, helping you meet regulatory requirements such as those defined by the French e-invoicing mandate.

For more information, see Field Mappings for Sales Invoice to Electronic Invoice, Field Mappings for Sales Credit Note to Electronic Invoice, Field Mappings for Electronic Invoice to Payable Invoice, and Field Mappings for Electronic Invoice to Payable Credit Note.

Automate Accounting with Invocable Actions

You can now use invocable actions to automate document processing in Accounting using Salesforce Flow Builder. The following invocable actions have been added in this release:

  • Find
  • Post Documents
  • Discard Documents
  • Cancel Documents
  • Reverse Documents

You can use Find, Post Documents and Discard Documents to find, post and discard the following document types:

  • Cash Entry
  • Journal
  • Payable Credit Note
  • Payable Invoice
  • Sales Credit Note
  • Sales Invoice

Cancel Documents can be used for Cash Entries and Journals.

Reverse Documents can only be used for Journals.

Note:

When using Cancel Documents or Reverse Documents you cannot currently set the date and period of the canceling or reversing document. The following defaults are applied:

  • Cancel Documents uses the same date and period as the original cash entry or journal.
  • Reverse Documents use the following period and the first day of that period.

For more information, see the Technical Reference Pack.

Supporting the French Electronic Invoicing Mandate

Send Payment Received Notifications for French Sales Invoices and Sales Credit Notes

You can now notify the French tax authority when a paid French B2B sales invoice or sales credit note has been collected, completing the document lifecycle through to its final Encaissée state. The new Send Payment Received Notification quick action on sales invoices and sales credit notes sends the payment received notification through Storecove to the Public Billing Portal (PPF), and the new Payment Notification Sent checkbox prevents the notification from being sent more than once.

This helps your French B2B sales invoices and sales credit notes reach the Encaissée status in the DGFiP records, keeping your organization compliant with French e-invoicing regulations.

For more information, see Sending Sales Invoices as Electronic Invoices and Sending Sales Credit Notes as Electronic Invoices.

 

Release Content

We want to help you find all of the information and resources that you need to use our products effectively.

Certinia Academy

If you want to learn more about the new features in this release, see the FM Cloud - Summer 2026 Release Highlights Certinia Academy module. This module will guide you through the new features in Financial Management Cloud.

Fixes

Fixes are listed on the Known Issues page of the Certinia Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of Accounting, see the relevant section of the Known Issues page.