0055187: Avalara Connector - trigger Avalara commit based on the creation of simplified invoice

Openbravo Issue Tracking System - Retail Modules
View Issue Details

ID	Project	Category	View Status	Date Submitted	Last Update
0055187	Retail Modules	Events for Client	public	2024-04-12 14:33	2024-04-17 09:51

Reporter	jonae
Assigned To	jonae
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Platform		OS	5	OS Version
Product Version
Target Version		Fixed in Version
Merge Request Status	approved
Review Assigned To
OBNetwork customer	No
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency Pack	No

Summary	0055187: Avalara Connector - trigger Avalara commit based on the creation of simplified invoice
Description	The data to be sent to Avalara will be the same as currently, but the trigger of the transaction commit into Avalara (if the parameter “Commit Openbravo Documents“ is enabled) will be based on the creation of a simplified invoice or an Invoice. Simplified Invoice are created at sales time, if the parameter “Generate Simplified Invoice” is selected. This parameter is located in channel touchpoint type. Invoices are created at sales time, if the seller uses the feature “Issue Invoice”. So the commit will be executed only at sales time and as described below, if the parameter “Commit Openbravo Documents =Y”: an order is created in the POS at checkout we call Avalara to retrieve the sales taxes. After payment, and only in the case when an Invoice “Simplified Invoice” or “Full Invoice” properties are not null, because any of those has been created, we commit that transaction into Avalara We need to take into account that: Openbravo documents will not be committed in Avalara regardless of the “Commit Openbravo Documents” = Yes, if the “Generate Aggregated Invoice” parameter is enabled. This parameter is automatically selected, if the parameter “Generate Simplified Invoice” is not selected. If “Generate Aggregated Invoice” is selected, aggregated invoices are created for all sales/return at cash up. This type of aggregated invoices must not be sent to Avalara in any case. Openbravo will support the import of legacy information import as well as Corners (so such transactions are not committed once again in Avalara) by implementing this new capability in the Avalara connector.
Steps To Reproduce	The data to be sent to Avalara will be the same as currently, but the trigger of the transaction commit into Avalara (if the parameter “Commit Openbravo Documents“ is enabled) will be based on the creation of a simplified invoice or an Invoice. Simplified Invoice are created at sales time, if the parameter “Generate Simplified Invoice” is selected. This parameter is located in channel touchpoint type. Invoices are created at sales time, if the seller uses the feature “Issue Invoice”. So the commit will be executed only at sales time and as described below, if the parameter “Commit Openbravo Documents =Y”: an order is created in the POS at checkout we call Avalara to retrieve the sales taxes. After payment, and only in the case when an Invoice “Simplified Invoice” or “Full Invoice” properties are not null, because any of those has been created, we commit that transaction into Avalara We need to take into account that: Openbravo documents will not be committed in Avalara regardless of the “Commit Openbravo Documents” = Yes, if the “Generate Aggregated Invoice” parameter is enabled. This parameter is automatically selected, if the parameter “Generate Simplified Invoice” is not selected. If “Generate Aggregated Invoice” is selected, aggregated invoices are created for all sales/return at cash up. This type of aggregated invoices must not be sent to Avalara in any case. Openbravo will support the import of legacy information import as well as Corners (so such transactions are not committed once again in Avalara) by implementing this new capability in the Avalara connector.
Proposed Solution
Additional Information
Tags	No tags attached.
Relationships
Attached Files

Issue History
Date Modified	Username	Field	Change
2024-04-12 14:33	jonae	New Issue
2024-04-12 14:33	jonae	Assigned To	=> jonae
2024-04-12 14:33	jonae	OBNetwork customer	=> No
2024-04-12 14:33	jonae	Triggers an Emergency Pack	=> No
2024-04-12 14:36	hgbot	Merge Request Status	=> open
2024-04-12 14:36	hgbot	Note Added: 0163157
2024-04-17 09:51	hgbot	Merge Request Status	open => approved
2024-04-17 09:51	hgbot	Resolution	open => fixed
2024-04-17 09:51	hgbot	Status	new => closed
2024-04-17 09:51	hgbot	Note Added: 0163308
2024-04-17 09:51	hgbot	Note Added: 0163309

Notes