Upgrading to Accounting Summer 2026

This page describes the changes to make when upgrading to Summer 2026.

See the Upgrade Steps section under each feature for details of any action required. If you don't want to use or upgrade an optional feature, you can skip the upgrade steps for that feature. To perform upgrade steps in your org, you must be assigned administrator permissions.

See the Included in This Feature section under each feature for details of items such as objects, fields, or buttons that have been added in this release.

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

Note:

Where new objects, fields, or buttons have been added for a feature, we recommend that you add them to any relevant page layouts, profiles, and permission sets. For information on how to do this, see the Salesforce Help.

For information on new features and changes to existing features in Summer 2026, see New Features and Enhancements in Accounting Summer 2026.

Allow override Product GLA in Payable Invoices and Payable Credit Notes

Upgrade Steps

To upgrade this feature to Summer 2026, take the following action.

Action Further Information
Enable Override Product GLA (PIN/ PCR) custom setting. This setting must be enabled in Accounting Custom Settings to allow GLA overrides on PIN lines.

Manually update the following field sets on the Payable Invoice Line Item object:

  • Manage Product Lines (Combined)

  • Manage Product Lines (SUT)

  • Manage Product Lines (VAT/ GST)

 Add the new Override Product GLA and Override Product Local GLA fields to these field sets.
Manually update custom permission sets to include Read and Edit access for the new fields. Access to these fields is not automatically included for existing customers. Ensure the following (or your equivalent custom sets) are updated: Accounting - Payable Invoice, Accounting - Payable Invoice - Edit.
Configure the new custom setting: Override Product GLA for PIN and PCR. A new setting has been created specifically for payable documents to distinguish them from Sales Invoices and Sales Credit Notes.

Validations while overriding General Ledger Account in Payable Invoices and Credit Notes

We have introduced new validations to ensure data integrity when overriding General Ledger Accounts in Payable Invoices and Payable Credit Notes. These validations apply when managing lines and ensure that override GLAs align with your Accounting Settings and Chart of Accounts (COA) configurations.

Upgrade Steps

To upgrade this feature to Summer 2026, take the following action.

Action Description Further Information
Enable Local GLAs If you intend to use the "Override Product Local GLA" field, ensure the Allow use of Local GLAs custom setting is enabled in Accounting Settings. For more information, see Accounting Settings
Review Chart of Accounts Verify that owner companies and destination companies have valid Local COAs assigned if local overrides are being used. For more information, see What is a Chart of Accounts?

Included in This Feature

This section details the validation logic added in this release to prevent data entry errors in PIN and PCR documents.

Rule Description Error Condition
Local GLA Setting Validates against Accounting Settings. Throws an error if "Allow use of Local GLAs" is disabled but an override local GLA is populated.
Mutual Exclusivity Ensures only one override type is used. Throws an error if both "Override Product GLA" and "Override Product Local GLA" are populated simultaneously.
Owner Company COA Validates COA existence. Throws an error if an override local GLA is populated but the owner company has no local COA.
Owner Company Match Validates COA alignment. Throws an error if the Override Local GLA does not match the owner company’s local COA.
Destination Company Match Validates cross-company COA. Throws an error if the Destination Company's local COA does not match the Override local GLA.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Payable Invoice Line Item Fields

Payable invoice fields added in Summer 2026.

Object

Field

Description
Payable Invoice Line Item Override Product GLA The corporate GLA to be used for posting, overriding the product's default GLA.
Payable Invoice Line Item Override Product Local GLA The local GLA to be used for posting for multi-company customers.

Payable Credit Note Item Fields

Payable Credit Note fields added in Summer 2026.

Object

Field

Description
Payable Credit Note Line Item Override Product GLA The corporate GLA to be used for posting, overriding the product's default GLA.
Payable Credit Note Line Item Override Product Local GLA The local GLA to be used for posting for multi-company customers.

Permission Sets

Permission Sets Updated in Summer 2026.
Permission Set Description
Accounting - Payable Invoice

We have added the permissions for the fields:

  • Override Product GLA

  • Override Product Local GLA
Accounting - Payable Invoice - Edit

Creating Prepaid Expense Journals

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Lightning Page

Lightning Pages added in Summer 2026
Lightning Page Description Further Information
Prepaid Expenses Lightning Page New Lightning page for creating Prepaid Expense Journal Proposals. Creating Prepaid Expenses Journals

Field Sets

Fields Sets added in Summer 2026
Object Field Set Description Further Information
Payable Invoice Expense Line Item Expense Lines Dynamic Fields Used to define the columns displayed on the Add Expense Lines window when creating prepaid expenses journal proposals. Payable Invoice Expense Line Item Field Sets

Meeting Poland VAT Reporting Requirements with Updated Compliance Support

Upgrade Steps

To upgrade this feature to Summer 2026, take the following action.

Upgrade Steps for Summer 2026
Action Further Information
Update your custom mappings to use the mappings provided by Certinia.  About the Avalara VAT Reporting Mappings
Ensure that your webhooks for receiving are updated to use the new Storecove received-documents. For more information, see the Storecove Help.

Update the following page layouts to display the Unique Document Code and Unique Document Code Type fields:

  • Sales Invoice Layout
  • Sales Credit Note Layout
  • Payable Invoice Layout
  • Payable Credit Note Layout
 For more information, see the Salesforce Help.
Complete the steps for the Electronic Invoicing Localization feature on the Feature Console. Enabling Electronic Invoicing Localization
(Optional) Add the required Reference fields. For more information, see Setting up Electronic Invoicing for Poland.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Fields

Fields Added in Summer 2026
Object Field Description Further Information
SIN, SCN, PIN, PCN Unique Document Code The unique identification number assigned to the accounting document by a country's national e-invoice system. For example, KSeF for Poland. Sales Invoice Fields

Sales Credit Note Fields

Payable Invoice Fields

Payable Credit Note Fields

Unique Document Code Type The type of the Unique Document Code to apply to the accounting document.

Feature Console Features

Feature Console Features Added in Summer 2026
Feature Console Feature Description Further Information
Electronic Invoicing Localization Enables compliance with electronic invoicing requirements for EU countries. Enabling Electronic Invoicing Localization
Feature Console Feature Step Added in Summer 2026
Feature Console Feature Description Further Information
Avalara VAT Reporting Integration (Step 11) Prompts you to configure the Unique Document Code Type picklist values for each tax authority using the Electronic Invoicing Localization feature.

Enabling the Avalara VAT Reporting Integration

Mappings Fields

Avalara VAT Reporting Mappings Fields Added for Summer 2026
Field Description Document type Further Information
UniqueDocumentCode The unique identification number assigned to the accounting document by a country's national e-invoice system. For example, KSeF for Poland. SI, SCN, PI, PCR Avalara VAT Reporting Mappings Table
UniqueDocumentCodeType The type of the Unique Document Code to apply to the accounting document. Values for Poland: KSeF, OFF, BFK, and DI.
UniqueDocumentCodeCountry The country for which the Unique Document Code applies.
Storecove Mapping Fields Added for Summer 2026
Object Storecove Mapping Field Description Level Document Type Further Information
ElectronicInvoicingService.Document document.tax_authority_id Unique Document Code The tax authority ID assigned to the accounting document by a country's national e-invoice system. For example, KSeF for Poland. Header

PIN, PCR

Note:

The Unique Document Code is populated in SIN and SCN once approved by Poland's National E-Invoicing System.

Field Mappings for Electronic Invoice to Payable Invoice

and Field Mappings for Electronic Invoice to Payable Credit Note
Mapping Fields Added at the header and line level in Summer 2026
Sales Invoice and Sales Credit Note
Object Field Description Further Information
ElectronicInvoicingService.Document References[..].DocumentTypeCode The type code of the referenced document. For more information, see Field Mappings for Sales Invoice to Electronic Invoice and Field Mappings for Sales Credit Note to Electronic Invoice
References[..].LineId The line identifier of the referenced document.
References[..].DocumentUuid The UUID of the referenced document.
References[..].DocumentIdSchemeId The scheme ID for the referenced document ID.
References[..].DocumentIdSchemeAgencyId The scheme agency ID for the referenced document ID.
References[..].DocumentIdSchemeVersionId The scheme version ID for the referenced document ID.
References[..].DocumentIdListAgencyId The list agency ID for the referenced document ID.
References[..].DocumentIdListVersionId The list version ID for the referenced document ID.
 
Payable Invoice and Payable Credit Note
Object Field Description Further Information
ElectronicInvoicingService.Document References[..].DocumentTypeCode The type code of the referenced document. For more information, see Field Mappings for Electronic Invoice to Payable Invoice and Field Mappings for Electronic Invoice to Payable Credit Note
References[..].LineId The line identifier of the referenced document.
References[..].DocumentUuid The UUID of the referenced document.
References[..].DocumentIdSchemeId The scheme ID for the referenced document ID.
References[..].DocumentIdSchemeAgencyId The scheme agency ID for the referenced document ID.
References[..].DocumentIdSchemeVersionId The scheme version ID for the referenced document ID.
References[..].DocumentIdListAgencyId The list agency ID for the referenced document ID.
References[..].DocumentIdListVersionId The list version ID for the referenced document ID.
AccountingCustomerParty.CompanyName Customer / buyer party company name.
AccountingCustomerParty.PostalAddress.AddressLine1  
AccountingCustomerParty.PostalAddress.AddressLine2  
AccountingCustomerParty.PostalAddress.CityName  
AccountingCustomerParty.PostalAddress.County  
AccountingCustomerParty.PostalAddress.CountryIdentificationCode Country code (for example, GB).
AccountingCustomerParty.PostalAddress.PostalCode  
AccountingCustomerParty.ContactName The internal party carries a single contact name, so the first and last name on the received document are combined, separated by a space.
AccountingCustomerParty.EmailAddress  
AccountingCustomerParty.Telephone  
AccountingCustomerParty.PublicIdentifiers List of public identifier endpoints (scheme and identifier).

Storecove Mapping Fields Updated for Summer 2026

Previous Storecove

Purchase Invoice Line

New Storecove

Purchase Invoice Line

 Level Document Type Further Information

tax_system

document.invoice.tax_system

 Header PIN, PCR

Field Mappings for Electronic Invoice to Payable Invoice and

Field Mappings for Electronic Invoice to Payable Credit Note

system_generated_primary_image

document.invoice.system_generated_primary_image

invoice_number

document.invoice.invoice_number

document

original

attachments

document.invoice.attachments

issue_date

document.invoice.issue_date

tax_point_date

document.invoice.tax_point_date

due_date

document.invoice.due_date

document_currency_code

document.invoice.document_currency_code

document_totals.rounding

document.invoice.payable_rounding_amount

document_totals.prepaid

document.invoice.prepaid_amount

document_totals.payable

document.invoice.amount_including_tax

document_totals.total

document.invoice.amount_including_tax

allowance_charges

document.invoice.allowance_charges

allowance_charges.amount_excluding_tax

document.invoice.allowance_charges[].amount_excluding_tax

allowance_charges.reason

document.invoice.allowance_charges[].reason

allowance_charges.tax.tax_amount

document.invoice.allowance_charges[].tax.amount

allowance_charges.tax.percentage

document.invoice.allowance_charges[].tax.percentage

allowance_charges.tax.country

document.invoice.allowance_charges[].tax.country

allowance_charges.tax.category

document.invoice.allowance_charges[].tax.category

allowance_charges.tax.type

document.invoice.allowance_charges[].tax.type

source

document.source

sender.party_name

document.invoice.accounting_supplier_party.party.company_name

sender.department

document.invoice.accounting_supplier_party.party.address.department

sender.line1

document.invoice.accounting_supplier_party.party.address.street1

sender.line2

document.invoice.accounting_supplier_party.party.address.street2

sender.zip

document.invoice.accounting_supplier_party.party.address.zip

sender.city

document.invoice.accounting_supplier_party.party.address.city

sender.county

document.invoice.accounting_supplier_party.party.address.county

sender.country

document.invoice.accounting_supplier_party.party.address.country

sender.legal_name

document.invoice.accounting_supplier_party.party.registration_name

sender.building_number

document.invoice.accounting_supplier_party.party.address.building_number

sender.secondary_number

document.invoice.accounting_supplier_party.party.address.secondary_number

sender.neighborhood

document.invoice.accounting_supplier_party.party.address.neighborhood

sender.billing_contact.first_name

document.invoice.accounting_supplier_party.party.contact.first_name

sender.billing_contact.last_name

document.invoice.accounting_supplier_party.party.contact.last_name

sender.billing_contact.email

document.invoice.accounting_supplier_party.party.contact.email

sender.billing_contact.phone

document.invoice.accounting_supplier_party.party.contact.phone

sender.peppol_identifiers.scheme

document.invoice.accounting_supplier_party.public_identifiers[].scheme

sender.peppol_identifiers.identifier

document.invoice.accounting_supplier_party.public_identifiers[].id

sender.identifiers

document.invoice.accounting_supplier_party.public_identifiers

sender.identifiers.scheme

document.invoice.accounting_supplier_party.public_identifiers[].scheme

sender.identifiers.identifier

document.invoice.accounting_supplier_party.public_identifiers[].id

document_type

document.document_type

sub_type

document.invoice.sub_type

period_start

document.invoice.invoice_period (start half)

period_end

document.invoice.invoice_period (end half)

buyer_reference

document.invoice.references[0].documentid (document_type is buyer_reference)

billing_reference

document.invoice.references[0].documentid (document_type is billing_reference)

contract_document_reference

document.invoice.references[0].documentid (document_type is contract_document_reference)

order_reference

document.invoice.references[0].documentid (document_type is purchase_order)

project_reference

document.invoice.references[0].documentid (document_type is project_reference)

payment_means_array

document.invoice.payment_means_array

payment_means_array.type

document.invoice.payment_means_array[].code

payment_means_array.account

document.invoice.payment_means_array[].account

payment_means_array.holder

document.invoice.payment_means_array[].holder

payment_means_array.branch_code

document.invoice.payment_means_array[].branche_code

payment_means_array.payment_id

document.invoice.payment_means_array[].payment_id

payment_means_array.mandate

document.invoice.payment_means_array[].mandate

payment_means_array.network

document.invoice.payment_means_array[].network

accounting_cost

document.invoice.accounting_cost

external_key

document.invoice.external_key

external_user_id

document.invoice.external_user_id

note

document.invoice.note

payment_terms_note

document.invoice.payment_terms.note

tax_subtotals

document.invoice.tax_subtotals

tax_subtotals.amount_excluding_tax

document.invoice.tax_subtotals[].taxable_amount

tax_subtotals.tax.tax_amount

document.invoice.tax_subtotals[].tax_amount

tax_subtotals.tax.category

document.invoice.tax_subtotals[].category

tax_subtotals.tax.percentage

document.invoice.tax_subtotals[].percentage

tax_subtotals.tax.type

document.invoice.tax_subtotals[].type

tax_subtotals.tax.country

document.invoice.tax_subtotals[].country

delivery.actual_date

document.invoice.delivery.actual_delivery_date

delivery.location.city

document.invoice.delivery.delivery_location.address.city

delivery.location.country

document.invoice.delivery.delivery_location.address.country

delivery.location.county

document.invoice.delivery.delivery_location.address.county

delivery.location.department

document.invoice.delivery.delivery_location.address.department

delivery.location.id

document.invoice.delivery.delivery_location.id

delivery.location.line1

document.invoice.delivery.delivery_location.address.street1

delivery.location.line2

document.invoice.delivery.delivery_location.address.street2

delivery.location.scheme_id

document.invoice.delivery.delivery_location.scheme_id

delivery.location.zip

document.invoice.delivery.delivery_location.address.zip

delivery.location.building_number

document.invoice.delivery.delivery_location.address.building_number

delivery.location.secondary_number

document.invoice.delivery.delivery_location.address.secondary_number

delivery.location.neighborhood

document.invoice.delivery.delivery_location.address.neighborhood

delivery.party.name

document.invoice.delivery.delivery_party

invoice.references.documentType

document.invoice.references[].document_type

invoice.references.documentId

document.invoice.references[].document_id

invoice.references.documentDescription

document.invoice.references[].document_description

invoice.references.issueDate

document.invoice.references[].issue_date

invoice.references.documentIdListId

document.invoice.references[].document_id_list_id

price.amount

item_price

 Line

units.quantity

quantity

price.base_quantity

base_quantity

units.unit_code

quantity_unit_code

allowance_charges_array

allowance_charges

allowance_charges_array.amount

allowance_charges[].amount

tax.tax_amount

taxes_duties_fees[0].amount

tax.percentage

taxes_duties_fees[0].percentage

tax.country

taxes_duties_fees[0].country

tax.category

taxes_duties_fees[0].category

tax.type

taxes_duties_fees[0].type

period_start

invoice_period (start half)

period_end

invoice_period (end half)

accounting.Name

accounting.name

references.documentDescription

references[].document_description

references.documentType

references[].document_type

references.documentIdListId

references[].document_id_list_id

references.documentId

references[].document_id

Storecove Mapping Fields Removed for Summer 2026

Storecove

Purchase Invoice Line

 Level Document Type Further Information
sender.peppol_identifiers.superscheme Header PIN, PCR

Field Mappings for Electronic Invoice to Payable Invoiceand

Field Mappings for Electronic Invoice to Payable Credit Note

sender.identifiers.superscheme
sender.identifiers.scheme_numeric
accounting.list Line
Note:

This enhancement is also documented in Foundations Summer 2026. Upgrading to Foundations Summer 2026

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

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Fields

Fields Added in Summer 2026
Object Field Description Further Information
Tax Code E-Invoicing Tax Category The tax category for the tax code. Used when generating electronic invoices and credit notes through Storecove to classify how this tax applies to each invoice line. Defaults to standard. You can update the picklist values for this field. Tax Code and Rate Fields
Note:

This release introduces the E-Invoicing Tax Category field with the single picklist value standard. Add any additional picklist values that your e-invoicing requirements call for as you prepare your tax codes.

The default Storecove e-invoicing mappings currently use the tax category from the Accounting Company. To apply a different tax category per invoice line, update the TaxBreakdown[0].TaxCode, TaxBreakdown[1].TaxCode, and TaxBreakdown[2].TaxCode mappings to use the E-Invoicing Tax Category field on the Tax Code (c2g__TaxCategory__c) instead. In a future release, the default mappings will be updated to use this field automatically. 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

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Fields

Fields Added in Summer 2026
Object Field Description Further Information
Account Extension E-Invoicing Document Entity Type The default document entity type for e-invoices sent from or received by this account. The default value is Invoice/B2B. Values: Invoice/B2B, Invoice/B2G, Simplified invoice/ticket/B2C. Custom Account Fields
Sales Invoice Document Entity Type New value: Invoice/B2G. The type of entities the document is sent from or to. Values: Invoice/B2B, Invoice/B2G, Simplified invoice/ticket/B2C. Default: Inherited from the E-Invoicing Document Entity Type field on the account's Account Extension record. If that field is not set, the default is Invoice/B2B. Sales Invoice Fields
Sales Credit Note Document Entity Type New value: Invoice/B2G. The type of entities the document is sent from or to. Values: Invoice/B2B, Invoice/B2G, Simplified invoice/ticket/B2C. Default: Inherited from the E-Invoicing Document Entity Type field on the account's Account Extension record. If that field is not set, the default is Invoice/B2B. Sales Credit Note Fields

Field Mappings

New field mappings have been added for French e-invoicing. For more information, see:

Supporting the French Electronic Invoicing Mandate

Expand French Electronic Invoice Support with Additional Party Roles

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

Note:

[Optional] To use the new party fields on outbound invoices, configure custom field mappings to populate the BuyerAgentParty, PayerParty, SalesAgentParty, InvoiceeParty, InvoicerParty, and PayeeParty fields on the ElectronicInvoicingService.Document object. For more information, see Field Mappings for Sales Invoice to Electronic Invoice and Field Mappings for Sales Credit Note to Electronic Invoice.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Supporting the French Electronic Invoicing Mandate

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

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

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

Upgrade Steps

No upgrade steps are required to upgrade this feature to Winter 2027.

Supporting the French Electronic Invoicing Mandate

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

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.

Automate Accounting with Invocable Actions

Upgrade Steps

To upgrade this feature to Summer 2026, take the following action.

Upgrade Steps
Action Further Information

Create a custom permission set containing the invocable action Apex classes and assign it to the appropriate users.

Technical Reference Pack

See "Permission Sets" in the Salesforce Help.

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Invocable Actions

Invocable Actions
Invocable Action Apex Class Description Further Information
Find Documents Find Search accounting records by name and returns the matching record ID. The name is the record's Name field value, typically the record number (for example "SIN000123"). Supported document types are journals (c2g__codaJournal__c), sales invoices (c2g__codaInvoice__c), sales credit notes (c2g__codaCreditNote__c), payable invoices (c2g__codaPurchaseInvoice__c), payable credit notes (c2g__codaPurchaseCreditNote__c) and cash entries (c2g__codaCashEntry__c).

Custom Actions

Technical Reference Pack

Post Documents PostDocuments Post accounting documents by ID, creating the corresponding transaction. Only documents with status "In Progress" can be posted; documents in any other status cannot be posted. Supported document types are cash entry (c2g__codaCashEntry__c), journal (c2g__codaJournal__c), sales invoice (c2g__codaInvoice__c), sales credit note (c2g__codaCreditNote__c), payable invoice (c2g__codaPurchaseInvoice__c) and payable credit note (c2g__codaPurchaseCreditNote__c).  
Discard Documents DiscardDocuments Discard accounting documents by ID using the supplied discard reason. Only documents with status "In Progress" can be discarded; documents in any other status cannot be discarded. Supported document types are cash entry (c2g__codaCashEntry__c), journal (c2g__codaJournal__c), sales invoice (c2g__codaInvoice__c), sales credit note (c2g__codaCreditNote__c), payable invoice (c2g__codaPurchaseInvoice__c) and payable credit note (c2g__codaPurchaseCreditNote__c).  
Cancel Documents CancelDocuments Cancel accounting documents by ID, creating the corresponding cancelled document. Only documents with status "Complete" can be cancelled. Supported document types are cash entry (c2g__codaCashEntry__c) and journal (c2g__codaJournal__c).  
Reverse Documents ReverseDocuments Reverse accounting documents by ID, creating the corresponding reverse document. Supported document type is journal (c2g__codaJournal__c).  

Supporting the French Electronic Invoicing Mandate

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

Upgrade Steps

To upgrade this feature to Summer 2026, take the following action.

Upgrade Steps for Summer 2026
Action Further Information
Add the Send Payment Received Notification quick action to the Salesforce Mobile and Lightning Experience Actions section of your Sales Invoice page layouts so that users can trigger the payment received notification from a paid French sales invoice. Sending Sales Invoices as Electronic Invoices
Add the Payment Notification Sent field to your Sales Invoice page layouts and list views if you want to see at a glance which French sales invoices have already had their payment received notification sent. Sales Invoice Fields
Add the Send Payment Received Notification quick action to the Salesforce Mobile and Lightning Experience Actions section of your Sales Credit Note page layouts so that users can trigger the payment received notification from a paid French sales credit note. Sending Sales Credit Notes as Electronic Invoices
Add the Payment Notification Sent field to your Sales Credit Note page layouts and list views if you want to see at a glance which French sales credit notes have already had their payment received notification sent. Sales Credit Note Fields

Included in This Feature

This section details the items that have been added, updated, or deleted in this release.

Fields

Fields Added in Summer 2026
Object Field Description Further Information
Sales Invoice Payment Notification Sent If selected, the payment received notification (Encaissée) has been sent to the French tax authority through Storecove. Used to prevent duplicate notifications. Sales Invoice Fields
Sales Credit Note Payment Notification Sent If selected, the payment received notification (Encaissée) has been sent to the French tax authority through Storecove. Used to prevent duplicate notifications. Sales Credit Note Fields

Buttons

Buttons Added in Summer 2026
Object Button Description Further Information
Sales Invoice Send Payment Received Notification Sends the payment received notification (Encaissée, PPF status 212) to the French tax authority through Storecove for a paid French B2B sales invoice that was previously sent as an electronic invoice. Sales Invoice Fields
Sales Credit Note Send Payment Received Notification Sends the payment received notification (Encaissée, PPF status 212) to the French tax authority through Storecove for a paid French B2B sales credit note that was previously sent as an electronic invoice. Sales Credit Note Fields

Deprecated Elements

The following elements have been deactivated in this release.

Release Content

Upgrade Steps

No upgrade steps are required to upgrade this feature to Summer 2026.