Coresuite 8.55 - Changelog

Introduction

We are pleased to announce the release of Coresuite version 8.55. Below is a brief overview of the key updates introduced in this version.

For a full list of changes and enhancements, please refer to our Release Notes.

Important: 

If you have not yet upgraded to Coresuite versions 7.90 through 8.20, please be aware that you will need to update the full Coresuite add-on due to significant changes and performance improvements introduced in version 7.90. This update is crucial to ensure compatibility with version 8.35 and future releases.

Coresuite Add-On Installation Folder Change

As we announced in Coresuite 8.30 - changelog, there are key changes to the Coresuite add-on installation process with Coresuite 8.35.
For more details about the change, please see the article Important Notice: Coresuite Add-On Installation Folder Change.

ZUGFeRD Implementation

For more details about the whole ZUGFeRD implementation in Coresuite-related products, please see the article Implementation of ZUGFeRD in Coresuite Designer.

Major Changes Delivered in Coresuite 8.55

Designer: ZUGFeRD Configuration

In Coresuite Designer 8.55, all ZUGFeRD settings have moved to their own tab. You can find it here: Administration --> Add-Ons --> Coresuite --> Coresuite Designer --> Configuration --> tab "ZUGFeRD"

Designer: ZUGFeRD - Support for XRechnung Profile

We added support for the ZUGFeRD XRechnung Profile. This profile follows the KosIT electronic invoicing standard.

There is a new ZUGFeRD profile setting at company level in the Designer configuration. There is also a business partner UDF that lets you choose a specific profile for each business partner.

If a profile is set on the business partner, it overrides the company-level setting.

- XRechnung - creates a KosIT-compatible PDF/A file with an attached XML file
- Extended - creates a ZugFerd 2.x PDF/A file with an attached XML file. This profile is made for medium and large businesses, but we recommend it for SAP Business One, because it covers more fields and options
- Comfort - uses the EN 16931 profile and creates a basic ZugFerd 2.x PDF/A file with an attached XML file. This profile is made for small and medium businesses (SMBs).

ZugFerd and XRechnung use almost the same XML structure. However, some fields are optional in one format but required in the other, and the formatting rules can differ. Because of this, it is important to choose the correct profile for each customer. If you choose the wrong profile, the file may be rejected by validation tools for the other format.

Coresuite Designer: PDF/A Generation on AP Documents: Credit Notes, Invoices and Down Payments

Coresuite Designer can now create PDF/A files for AP Credit Notes, AP Invoices and AP Down Payments.

This feature was already available for Sales (AR) documents. Now AP documents can meet the same archiving and compliance standards, which helps with long-term storage and legal requirements.

Coresuite Designer: BT-72, BT-73 and BT-74 Prioritization

These three fields follow this priority order for BT-72 (ActDelDate), BT-73 (BillingStartDate) and BT-74 (BillingEndDate):

BT-72 - Delivery Date Determination:
If the document is based on a delivery note, we use the delivery note's date as the actual delivery date.

BT-73 - ActualDeliverySupplyChainEvent - Service Date Determination
The Service Date is chosen using this order of priority:
Priority 1: Use the ShipDate from the delivery note, if the invoice is based on a delivery note
Priority 2: Use the DocDueDate from the delivery note, if the invoice is based on a delivery note
Priority 3: Use the ActDelDate from the invoice, if the invoice is not based on a delivery note
Priority 4: Use the DocDueDate from the invoice, if the invoice is not based on a delivery note

If you want to use a custom field for these dates, you can follow these steps:

1. Go to the Zugferd Settings table SWA_LD_ZUGFERDSET from Tools > User-Defined Windows
2. Set UseCustomDeliveryDates to 'Y'
3. Go to the Zugferd Mapping table SWA_LD_ZUGFERDMAP
4. At the bottom, you will find the entries Header.Custom.ActualDeliveryDate, Header.Custom.BillingStartDate and Header.Custom.BillingEndDate. Update the Datasource and Field columns to point to the data you want to use. No further changes are needed. In our example, we selected the Row Datasource for demo purposes, but the fields already come filled in with RowBaseDocument:

Coresuite Designer: BT-49 - Determination of Buyer Electronic Address to Which a Business Document Should be Delivered

BT-49 defines the electronic address where a business document should be delivered. Because of how the ElectonicAddressSchemeIdentifier enum is defined in the ZugFerd library, we check whether a VatStruct is defined in the business partner's master data.

If this value exists, we generate the electronic address using the identifier from the VAT Structure field and the Participant ID.
If this value does not exist, we generate the address using the Shipping GLN instead. This is because PEPPOL identifiers are different in every country, and international companies often have different entities in each country.

Note: If the VAT Structure does not match any value of the ElectonicAddressSchemeIdentifier, the system will automatically use the GLN approach instead.
 

Coresuite Designer: BT-X-145 - Improvement of Delivery Terms Code

Added a new mapping table SWA_LD_ZUGFERDDT that should be filled with the desired mapping types for each Shipping Type.
The values are the ones from UNTDID 4053 + INCOTERMS List:

Coresuite Designer: ZUGFeRD - PaymentMeans Determination

The Payment Means is defined as BT-81 in the mapping table SWA_LD_ZUGFERDMAP or SWA_LD_ZUGFERDMAP90.

The value comes from a UDF named U_SWA_LD_ZUGFERD_PMTCODE on the OPYM table. 
Each Payment Method has to be set up with the desired code as specified by the customer. The default value is e.g. 30:

Coresuite Designer: BT-30 - Legal Registration Number Support

We added support for BT-30 (Seller's legal registration identifier). This adds the company's registration number to the ZUGFeRD XML file, using the correct identifier scheme for each country.

Each country uses a different identification scheme (schemeID). We built a mapping table that automatically selects the correct schemeID based on the country of the seller. If the country is not found in this table, the system uses the GLN scheme (0088) by default.

In addition, if an Alias Name is defined under Company Details > General, it will now also be included in the XML as TradingBusinessName (BT-28).

For example, for a German company with registration number "HRA3320" and an Alias Name of "OEC", the XML output will look like this:

<ram:SpecifiedLegalOrganization>
  <ram:ID schemeID="0204">HRA3320</ram:ID>
  <ram:TradingBusinessName>OEC</ram:TradingBusinessName>
</ram:SpecifiedLegalOrganization>

The table below shows the schemeID used for each supported country. If a country is not listed, the GLN scheme is used instead.

Coresuite Designer: ZUGFeRD - Correct Label for the Manager Field in the Company Info Note

The company info note in the ZUGFeRD XML file previously showed the label "Führungskraft" ("Manager"), even though the value next to it came from the "Geschäftsführer" ("Managing Director") field in the company settings.

This label comes from the PrintHeadr column in the OADM table (company settings). The SAP Business One label for this field ("Führungskraft") does not correctly describe its content: the value is actually the Geschäftsführer (OADM.Manager) value.

We updated the label so that the company info note now shows "Geschäftsführer" instead of "Führungskraft". The XML now looks like this:

<ram:IncludedNote>
  <ram:Content>Geschäftsführer: John Doe, Jane Doe; Firmensitz: Musterstadt; Musterfirma GmbH, Musterstraße 1, 12345 Musterstadt</ram:Content>
  <ram:SubjectCode>REG</ram:SubjectCode>
</ram:IncludedNote>

Coresuite Designer: ZUGFeRD - BT-56 / BT-58 - Buyer Contact Name and E-Mail Mapping

The ZUGFeRD library currently does not support the BuyerAgentTradeParty node, which is needed to output BT-X-418 (Invoice recipient e-mail address).

As a temporary solution, we added two new mapping fields to the ZUGFeRD Mapping table (SWA_LD_ZUGFERDMAP), pointing to the Buyer's contact name and e-mail address instead:

- Header.BuyerContactName - maps to DocumentContactPerson.Name - outputs as BT-56
- Header.BuyerContactEmail - maps to DocumentContactPerson.E_MailL - outputs as BT-58

Both fields are output under BuyerTradeParty > DefinedTradeContact in the XML:

<ram:BuyerTradeParty>
  ...
  <ram:DefinedTradeContact>
    <ram:PersonName>Alexandra Deuber</ram:PersonName>
    <ram:EmailURIUniversalCommunication>
      <ram:URIID>alexandra.deuber@microchips.sap.com</ram:URIID>
    </ram:EmailURIUniversalCommunication>
  </ram:DefinedTradeContact>
  ...
</ram:BuyerTradeParty>

The same approach can be used on the Seller side (BT-41 / BT-43) if needed.

If this mapping is not wanted, it can be turned off by clearing the Datasource and Field columns for these two rows in the ZUGFeRD Mapping table.