Breaking
No breaking changes.
Compliance
✅ Document output logic
We've updated the document output logic for the following countries:
- Netherlands
- Ireland
- South Africa
- New Zealand
- Macau
- Hong Kong
- Denmark
- Switzerland
Details
Case description | User data | Document output | Email (PDF) | Paper (PDF) | Thermal (Receipt) | Email (Receipt) | |
---|---|---|---|---|---|---|---|
If the order is anonymous | None | Receipt | No | No | Yes | Yes | |
Anonymous with VAT number below threshold | VAT number | Simplified Invoice | No | No | Yes | Yes | |
Anonymous with VAT number above threshold | VAT number | Receipt | No | No | Yes | Yes | |
B2C user with complete billing address with AllowConsumerInvoices : true | First name, Last Name, Address 1, Zip Code, City | Invoice | Yes | No | No | Yes | |
B2C user with complete billing address with AllowConsumerInvoices : false | First name, Last Name, Address 1, Zip Code, City | Receipt | No | No | Yes | Yes | |
B2C user with in-complete billing address AllowConsumerInvoices : true | Error | ||||||
B2C user with in-complete billing address AllowConsumerInvoices : false | Error | ||||||
B2B user with Company name, without VAT number and without billing address | Company name | Receipt | No | No | Yes | Yes | |
B2B user without Company name, with VAT number and without billing address | VAT number | Error | |||||
B2B user with Company name, with VAT number and without billing address and below threshold | Company name, VAT number | Simplified Invoice | No | No | Yes | Yes | |
B2B user with Company name, with VAT number and billing address and below threshold | Company name, VAT number, Address 1, Zip Code, City | Invoice | Yes | No | No | Yes | |
B2B user with Company name, with VAT number and billing address and above threshold | Company name, VAT number | Error |
✅ Removing redundant 0% VAT rate
In case an order contains line discounts or order discounts, no unnecessary 0.00% tax rate line will be displayed in the VAT table on the receipt and invoices for the following countries:
- Netherlands
- United Kingdom
- Ireland
- South Africa
- New Zealand
- Macau
- Hong Kong
- Denmark
- Switzerland
Mind that if the order includes products with zero/exempt VAT rate, the VAT rate of these products is still displayed in the tax rate table.
✅ Individual countries
🇵🇱 Poland
We've changed the logic behind the audit files for Poland and Portigal.
- When setting
Auditing:Provider
to Poland for an OU, an audit file will be generated for that OU. - Setting
Auditing:Provider
to Default for an OU, an audit file will NOT be generated for that OU.
This goes for both E-commerce and stores.
🇵🇹 Portugal
We've changed the logic behind the audit files for Poland and Portigal.
- When setting
Auditing:Provider
to SAFT for an OU, an audit file will be generated for that OU. - Setting
Auditing:Provider
to Default for an OU, an audit file will NOT be generated for that OU.
This goes for both E-commerce and stores.
🇦🇹 Austria
- Certified invoice receipt templates in Austria will from now on only display customer data in case of B2B sales - thus preventing private data from being shared on the receipt for B2C.
- PDF invoices will however still include this customer data.
- The PDF CertifiedInvoice now also includes the following fields:
- RKSV-Beleg (Receipt number)
- RKSV-Datum (Receipt Timestamp)
- RKSV-Kassen-ID (CashRegister Serial Number)
🇩🇪 Germany
Certified invoice receipt templates in Germany will from now on only display customer data in case of B2B sales - thus preventing private data from being shared on the receipt for B2C.
PDF invoices will however still include this customer data.
Properties
🆕 Requirements in SerialNumberConfiguration
The SerialNumberConfiguration
services now include a new Requirement property, allowing you to specify for what kind of flow a serial number must be entered.
Details
The Requirement property can have the following values:
- -1 (None) - a serial number is never required
- 0 (Sales) - for your day to day sales and returns
- 1 (OwnershipChange) - sales and returns + shipments (Interbranch / incoming shipments / RTS)
- 2 (StockMovements) - sales and returns + shipments (Interbranch / incoming shipments / RTS) + Cycle counts and Full stock counts
🆕 ProgramGroup in ListLoyaltyPrograms
The ListLoyaltyPrograms
service now includes the ProgramGroup property to allow for filtering on the loyalty program group ID.
🆕 CountrySubdivisionID in Addresses
The Address objects now allow for specifying a CountrySubdivisionID.
This will allow setting it as an address requirement, which in turn facilitates a correct tax calculation for shipments to specific regions.
Sample
By providing the following subdivision, EVA will enforce the country subdivision to be either Sevilla or Toledo for the address. (In other words: when setting the ShippingAddress for a customer)
{
ID: 123,
PredefinedValues: [ "ES-SE, ES-TO" ],
Visibility: 1 // enum Visible
}
When PredefinedValues is left empty, any country subdivision will do, as long as it’s valid (as listed in GetCountrySubdivisions
).
{
User: {
EmailAddress: 'john.doe@some-domain.com',
ShippingAddress: {
Address1: 'C. Garcilaso de la Vega',
ZipCode: '38005',
City: 'Santa Cruz de Tenerife',
CountryID: "ES",
CountrySubdivision: "ES-CN"
}
}
}
🆕 OU ID in FSC summary Excel
The Excel file containing the Full stock count summary now also includes the OrganizationUnitNumber along with the OrganizationUnit (name).
🆕 CreationTime in Financial Period Data lake
The Financial period Data lake export now includes the CreationTime property for bank deposits. Creation time of a bank deposit is set when the deposit goes into a pending state.
Services
🆕 ProductLimitations and OU sets in PushLoyaltyProgram_Async
You can now set product limitations via the PushLoyaltyProgram_Async
service in two ways.
The service now additionally allows for pushing in loyalty programs for OrganizationUnitSets.
Details
- The service allows for pushing product limitations via the ProductLimitations object on the loyalty program itself;
- The service also allows pushing loyalty program PaymentTypes that can optionally contain their own ProductLimitations (which is restricting to specific ProductIDs, Quantities, etc.)
The former allows for configuring limitations regardless of the payment type, while the latter sets limitations specifically in combination with the payment type connected to a loyalty program.
🆕 AddLoyaltyProgramRequiredCustomField
To make it easy to start verifying customers' eligibility for loyalty programs, EVA now allows for addding custom fields to your loyalty program of type Order and Order line.
Such custom fields will trigger a custom field order requirement.
Details
The following services/properties are now available:
AddLoyaltyProgramRequiredCustomField
- Accepts CustomFieldID
- Accepts LoyaltyProgramID
ListLoyaltyProgramRequiredCustomFields
- Returns the program's connected custom fields
RemoveLoyaltyProgramRequiredCustomField
- Accepts CustomFieldID
- Accepts LoyaltyProgramID
✅ GetAvailableGiftCardConfigurations
Depending on your PaymentMethods:PaymentTypeAvailabilityByOuSetType setting, EVA will now only display gift cards which are available for use in your country.
Details
With the setting on true, then a payment type is only available on the OU set which is specified in the Organization unit settings of the payment type. This influences the availability of a gift card in individual countries as follows:
- When
PaymentMethods:PaymentTypeAvailabilityByOuSetType
= false (thus making use of the legacy filter), EVA shows all the returned giftcards inGetAvailableGiftCardConfigurationsresponse
- When
PaymentMethods:PaymentTypeAvailabilityByOuSetType
= false, and we don’t have any OU/OU set on the giftcard payment configuration, EVA displays them everywhere as seen in theGetAvailableGiftCardConfigurations
response (when checking balance and when going to payments on order) - When
PaymentMethods:PaymentTypeAvailabilityByOuSetType
= true and we have giftcard configurations/giftcard payment types without any OU/OU set, they are not returned in theGetAvailableGiftCardConfigurations
response - When
PaymentMethods:PaymentTypeAvailabilityByOuSetType
= true and we have OU/OU sets configured on giftcard configuration payment types, EVA will display show them in theGetAvailableGiftCardConfigurations
response based on their configuration in the Organization unit settings
🆕 ParseBarcode
We are making a slight change to the ParseBarcode
service in combination with USER type barcodes.
Details
When callled with a USER type barcode (U:123) from the context of an anonymous user, the result will only contain the parsed UserID in the result data.
To prevent unwanted data exposure, it will not include the FullName, nor will EVA check if this ID actually exists in EVA.
🆕 EmailOrderTaxFreeForm
We are introducing a new generic service which will allow for retrieving TaxFreeForms associated with an order to an email address. This way you might send a Global Blue invoice to a customer for example.
The service is called EmailOrderTaxFreeForm
and takes an EmailAddress and OrderID.
Settings
🆕 Authorization for HTTP stencils
We are adding two new settings that will let you set credentials for your HTTP endpoint, which in turn will make for a more secure endpoint for your stencils with the HTTP destination.
Details
The following two settings let you set your credentials:
Email:ExternalTemplateUsername
Email:ExternalTemplatePassword
These two will be combined into a Basic
authorization header with the HTTP request, which is sent to your endpoint in the existing setting Email:ExternalTemplateEndpoint
.
✅ Removal of deprecated AX settings
We are removing several AX-related settings which were planned for deprecation.
Details
Setting | Functionality |
---|---|
AX:BrandName:BeautyAndWellness | FinancialEvents |
AX:BrandName:BeautyAndParfum | FinancialEvents |
AX:BrandName:VVVCard | FinancialEvents |
AX:BrandName:WonderboxNL | FinancialEvents |
AX:BrandName:FashionCheque | FinancialEvents |
AX:BrandName:Love2Shop | FinancialEvents |
AX:BrandName:Illicado | FinancialEvents |
AX:BrandName:IGive | FinancialEvents |
AX:BrandName:Xpon | FinancialEvents |
AX:BrandName:Sparebank | FinancialEvents |
AX:BrandName:Oberthur | FinancialEvents |
AX:BrandName:ProsodieIllicado | FinancialEvents |
AX:BrandName:Netscard | FinancialEvents |
AX:BrandName:XponCard | FinancialEvents |
AX:BrandName:CashComGiftCard | FinancialEvents |
AX:BrandName:ResursBank | FinancialEvents |
AX:BrandName:Breuninger | FinancialEvents |
AX:BrandName:UniversalGiftCard | FinancialEvents |
AX:BrandName:Mapping | FinancialEvents |
Other topics
✅ Date&Time for InvoiceExport Error
We've made some changes to ensure the date and time associated with an InvoiceExport error (as seen in the E-invoices chapter in Admin Suite) will display the actual values corresponding to when the error happened (isntead of when the export happened).
Mind that a front-end change is still required for this as well.
✅ Optional: Shipping restrictions adhere to scripts only
We've made it possible for you to instruct EVA to skip your Country and/or OU shipping restrictions and to adhere to your ShippingRestriction script only.
For this purpose we're adding the property CheckScriptOnly to the ShippingRestriction
CRUD services.
✅ Product requirements on certified templates
While product requirements had already been made visible for non-certified receipt and invoice templates in Core drop 2.0.739, EVA now offers this for certified templates as well.
✅ SerialNumbers
In anticipation of wide-scale use of serial numbers throughout EVA, we've made all relevant back-end processes compatible.
Fixes
- The Maximum value when creating a Replenishment can no longer be below the Minimum value.
- When requesting availability for non-stock products that are flagged as DisableDelivery, EVA now correctly disables delivery availability.
- When requesting availability for non-stock products that are flagged as DisablePickup, EVA now correctly disables pickup availability.
this fixes an issue with incorrect availability of digital giftcards
Deprecations
🚫 Effective
These deprecations are now effective. As of now, these services and/or fields are no longer available in EVA and can no longer be used.
Deprecated
High
- High Lines is deprecated since 2.0.749: This is no longer supported.
- CreateManualTaxExemptionReason.Lines
- High Result.Page.ScriptID is deprecated since 2.0.749: This is no longer supported.
- ListUserRequirementsResponse.Result.Page.ScriptID
- High Result.Page.ShippingMethodID is deprecated since 2.0.749: This is no longer supported.
- ListUserRequirementsResponse.Result.Page.ShippingMethodID
- High Result.Page.SubscriptionID is deprecated since 2.0.749: This is no longer supported.
- ListUserRequirementsResponse.Result.Page.SubscriptionID
- High Result.Page.UserRequirementSetID is deprecated since 2.0.749: This is no longer supported.
- ListUserRequirementsResponse.Result.Page.UserRequirementSetID
- High Result.Page.UserRequirementSetName is deprecated since 2.0.749: This is no longer supported.
- ListUserRequirementsResponse.Result.Page.UserRequirementSetName
For more details on the impact categories, please see When are changes communicated?.
Release dates may vary
The exact date for deploying a Core release to production environments may vary. See How we handle Core releases for more details.