AXAP by Argentis - Argentis. Run your business. Better.

Release 25.03.21

eferreyra — Fri, 21 Mar 2025 13:15:42 +0000

Release 25.03.21 eferreyra Fri, 21/03/2025 - 10:15

Release 25.03.21

Release Notes - Version 25.03.21

Updated Avatax API to v25.3.0

Cumulative fixes for reported issues.

Customer code alternative field

Added a new feature to enable sending alternative Customer Code values for documents.

The customer code field for the document reported to Avatax defines if an exemption rule or certificate matches the transaction.

Some scenarios requires sending specific Customer Code values for a document, that can differ from the customer code in SAP. One comon case are sales documents from eCommerce portals, that uses a single Business Partner code in SAP, but have different customer code in the eCommerce and may have an exemption certificate for this alternative customer code.

The new feature gives the option to configure a field from the marketing document in SAP, evaluate if has a value, and send this value as the customer code for the Avatax transaction.

This is the setting. When enabled, if the document field has value, that value will be sent as the customer code. If it's empty, the default customer code field will be sent instead.

Release 25.01.30

eferreyra — Thu, 30 Jan 2025 14:30:06 +0000

Release 25.01.30 eferreyra Thu, 30/01/2025 - 11:30

Release 25.01.30

Release Notes - Version 25.01.30

Updated Avatax API to v25.1.0

Cumulative fixes for reported issues.

Adjusted behavior for Down Payments applied balance when calculating using external tax mode and service layer.

Added a new configuration behavior setting due to differences with the SAP SDK on HANA and SQL, to support both scenarios.

New settings are in the Behavior tab.

The default setting will be having enabled a double update when setting Down Payment values on an Invoice Draft. However in some environments only one update works, and using double update gets the down payment amount changed. You can adjust this based on your environment tests.

Release 25.01.07

eferreyra — Tue, 07 Jan 2025 18:02:55 +0000

Release 25.01.07 eferreyra Tue, 07/01/2025 - 15:02

Release 25.01.07

Release Notes - Version 25.01.07

Cumulative fixes for reported issues.

Upgraded components to most up-to-date versions.

Adjusted behavior for Down Payments applied balance when calculating using external tax mode.

Release 24.12.23

eferreyra — Mon, 23 Dec 2024 12:15:38 +0000

Release 24.12.23 eferreyra Mon, 23/12/2024 - 09:15

Release 24.12.23

Release Notes - Version 24.12.23

Cumulative fixes for reported issues.

Updated Avalara API to v24.12.0

Release 24.10.30

eferreyra — Wed, 30 Oct 2024 12:25:09 +0000

Release 24.10.30 eferreyra Wed, 30/10/2024 - 09:25

Release 24.10.30

Release Notes - Version 24.10.30

Cumulative fixes for reported issues.

Additional logic to handle Unbalanced Transaction issues when calculating external tax on Invoices.
Added support to process draft documents with serial, batch and bin location assignments using Document Generation Wizard, AES and WebUI.
Adjusted tax calculation behavior for documents using foreign currency, in all tax modes, to ensure reporting values are similar to SAP values.
Added support to handle Credit Memo copied from Return Request document.
Updated component libraries.

Release 24.09.25

eferreyra — Mon, 23 Sep 2024 16:26:54 +0000

Release 24.09.25 eferreyra Mon, 23/09/2024 - 13:26

Release 24.09.25

Release Notes - Version 24.09.25

Cumulative fixes for reported issues.

Filtering for Document Generation Wizard, custom filters using Not and numeric values, to filter for example documents without tax calculated.
Document Generation Wizard. Processing Credit Memos from drafts and post the created document to Avalara.

Release version complatible with SAP SDK 10.00.260 SP 2408

Release 24.08.22

eferreyra — Thu, 22 Aug 2024 19:53:51 +0000

Release 24.08.22 eferreyra Thu, 22/08/2024 - 16:53

Release 24.08.22

Release Note - Version 24.08.22

Upgraded Avatax API to v24.8.0

Fix and support for external tax calculation on Returns based on A/R Credit Memos.

Cumulative fixes.

Release 24.07.29

eferreyra — Mon, 29 Jul 2024 12:39:14 +0000

Release 24.07.29 eferreyra Mon, 29/07/2024 - 09:39

Release 24.07.29

Release Note - Version 24.07.29

Adding support to calculate Retail Delivery Fee for Minnesota state.

Added support to handle the "Unbalanced Transaction" status on draft invoices with applied downpayments when calculating taxes, using SAP Service Layer.

Adding AES versions for compatibility support for old SAP versions (SAP 10 FP 2208 or lower and SAP 9.3).

Cumulative fixes.

Release 24.06.27

eferreyra — Thu, 27 Jun 2024 14:00:15 +0000

Release 24.06.27 eferreyra Thu, 27/06/2024 - 11:00

Release 24.06.27

Release Note - Version 24.06.27

Adding support to calculate Retail Delivery Fee for Minnesota state.

Consolidating features for Retail Delivery Fee and support calculation for multiple states.

Upgrade to SAP Business One SDK 10 (10.00.250) FP 2405

Avatax SDK updated to 24.6.1

Cumulative fixes.

Retail Delivery Fee

eferreyra — Thu, 27 Jun 2024 13:20:48 +0000

Retail Delivery Fee eferreyra Thu, 27/06/2024 - 10:20

Retail Delivery Fee

Overview

Since July 2022 the state of Colorado started applying a Retail Delivery Fee for some transactions.

Starting on July 1st 2024 the state of Minnesota is also imposing a Retail Delivery Fee.

Please check the previous links and updated information on the Avalara Knowledge Center or with your Avalara account manager.

In order to support this, the Avatax for BusinessOne solution is adjusting the configuration to support multiple states. The behavior and calculation logic will remain the same: the approach is to add a non-inventory item in the transaction, with a specific OF400000 taxcode.

Avatax identifies this tax code and will calculate the fee if applies using that item.

Calculating Retail Delivery Fee in SAP BussinesOne

The fee is calculated by the Avatax engine. Avatax for SAP B1 sends the transaction information to Avaltax and then handles the response.

In order to have the Retail Delivery Fee calculated, you need to include a new line item in the sales document, with the provided Avatax TaxCode (OF400000), and a valid Ship-To address set for this line. If the fee applies, Avatax will calculate and return the expected fee as the calculated tax for this line.

Define a new item in your Item Master Data, like this, and set the indicated Avatax Tax Code.

Then you can include the item on the sales document, and get the tax calculated including the fee, like in this example with a ship-to Colorado.

Features to calculate Retail Delivery Fee in SAP BusinessOne

With the previous steps you can get the Retail Delivery Fee included and calculated in the document, but you still need to manually add the Colorado Fee line item manually in the document.

To enhance this and provide automatization capabilities you can use the following features, configurable from the add-on settings:

There are 4 (four) Retail Delivery Fee Modes available:

Inactive
Prompt Message
UDF Check
Automatic – Always

Enabled States

To use the Retail Delivery Fee features you must check en enable the desired supported US states using the checkboxes.

Mode Inactive

This is the default mode. Here the application won't perfom any actions, and you need to manually include the Retail Delivery Fee item when required.

For the automated modes, the application will check the document at the moment of calculation. If the document is of type Items, and the document ship-to state or any line ship-to state is one the applicable US states, then it will consider the Retail Delivery Fee applies, and will follow the mode logic, as explained below.

The automatization consists in adding the Retail Delivery Fee item to the document, and calculate the taxes.

Prompt Message

For automated modes, you need to select the Colorado Fee Item defined before in the Item Master Data.

In this mode, the application will prompt you with a confirmation message to include the Retail Delivery Fee, like this.

If confirmed, then the item will be added and the tax calculated.

This mode will only work for manual calculations. It doesn’t apply to Document Generation Wizard process or Event Service process, as there is no prompt during the bulk processing.

UDF Check

This mode works by evaluating a configurable UDF at the document header level, and add the Retail Delivery Fee Item if the UDF value is Y.

To use this mode, you need to complete the Retail Delivery Fee Fee UDF name at the settings, in this sample called U_TEST.

At the calculation moment, if the UDF value is Y, then the Colorado Fee Item will be automatically included in the document and in the tax calculation. The UDF value can only by Y, using Yes or other values will not be considered, but you can set any description to the UDF field.

Automatic

On this mode, the Retail Deliveryu Fee Item will always be included in the document if the previous requirements are met: having a enabled US state Ship-To address in the Item-Type document.

No prompts or evaluation will be made, and the fee item will be added to the document and included in the tax calculation.

This mode works for manual calculations, event service calculations and document generation wizard processes.

WebUI

The same features will be also released for the webUI, even for tax calculation jobs and for document generation.

Like all other configuration settings, the WebUI is totally independent from the Avatax add-on configuration.

The Prompt Message method is not available as no prompt will be shown during bulk processes.