Skip to content

Commit 616503e

Browse files
giri-odoovbe-odoo
authored andcommitted
[IMP] accounting/l10n_br: credit usage Avalara integration
To comply with legal requirements—especially consumer protection laws (Lei de Proteção ao Consumidor) — and to ensure full transparency with our users, we provide the following explanation of how credit consumption works in the Avalara integration. closes #13833 X-original-commit: 84a0f6d Signed-off-by: Xavier Platteau (xpl) <[email protected]> Signed-off-by: Audrey Vandromme (auva) <[email protected]> Co-authored-by: Valentino <[email protected]>
1 parent 1a09718 commit 616503e

File tree

1 file changed

+85
-0
lines changed
  • content/applications/finance/fiscal_localizations

1 file changed

+85
-0
lines changed

content/applications/finance/fiscal_localizations/brazil.rst

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,42 @@ how the product will be used.
160160
E-Invoice for goods (NF-e)
161161
~~~~~~~~~~~~~~~~~~~~~~~~~~
162162

163+
.. important::
164+
The :ref:`Avalara integration <localizations/brazil/avatax-account>` works on a credit-based
165+
system, where each interaction with Avalara consumes one credit. Below are the main
166+
credit-consuming operations:
167+
168+
**Sales application**
169+
170+
- Tax calculation on quotations and sales orders.
171+
172+
**Accounting application**
173+
174+
- Tax calculation on invoices.
175+
- Electronic invoice submission (NF-e or NFS-e).
176+
177+
**Occasional operations**: (each step is billed separately)
178+
179+
- :ref:`Correction letter (Carta de Correção) <localizations/brazil/correction-letter>`
180+
- :ref:`Invoice cancellation <localizations/brazil/invoice-cancellation>`
181+
- :ref:`Sales refund via credit note <localizations/brazil/credit-notes>`
182+
- :ref:`Sales complementary invoice via debit note <localizations/brazil/debit-notes>`
183+
- :ref:`Invalidate invoice number range <localizations/brazil/invalidate-invoice-number>`
184+
- Other tax validations.
185+
186+
.. note::
187+
If taxes are calculated in the **Sales** app, and the invoice is later issued in the
188+
**Accounting** app, the calculation happens twice, consuming two credits.
189+
190+
.. example::
191+
| **Sales order confirmed**
192+
| :icon:`fa-arrow-down` 1 credit (tax calculation)
193+
| **Invoice created**
194+
| :icon:`fa-arrow-down` 1 credit (tax calculation)
195+
| **Invoice confirmed and submitted**
196+
| :icon:`fa-arrow-down` 1 credit (tax calculation) + 1 credit (submit invoice)
197+
| **Total: 4 credits**
198+
163199
- :guilabel:`CEST Code`: code for products subject to ICMS tax substitution
164200
- :guilabel:`Mercosul NCM Code`: Mercosur Common Nomenclature Product Code
165201
- :guilabel:`Source of Origin`: origin of the product, which can be foreign or domestic, among other
@@ -182,6 +218,43 @@ E-Invoice for goods (NF-e)
182218
E-Invoice for services (NFS-e)
183219
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
184220

221+
.. important::
222+
The :ref:`Avalara integration <localizations/brazil/avatax-account>` works on a credit-based
223+
system, where each interaction with Avalara consumes 1 credit. Below are the main
224+
credit-consuming operations:
225+
226+
**Sales application**
227+
228+
- Tax calculation on quotations and sales orders.
229+
230+
**Accounting application**
231+
232+
- Tax calculation on invoices.
233+
- Electronic invoice submission (NF-e or NFS-e).
234+
- Invoice status check (1 credit is consumed each time the invoice status is checked).
235+
236+
**Occasional operations**: (each step is billed separately)
237+
238+
- :ref:`Correction letter (Carta de Correção) <localizations/brazil/correction-letter>`
239+
- :ref:`Invoice cancellation <localizations/brazil/invoice-cancellation>`
240+
- :ref:`Sales refund via credit note <localizations/brazil/credit-notes>`
241+
- :ref:`Sales complementary invoice via debit note <localizations/brazil/debit-notes>`
242+
- :ref:`Invalidate invoice number range <localizations/brazil/invalidate-invoice-number>`
243+
- Other tax validations.
244+
245+
.. note::
246+
If taxes are calculated in the **Sales** app, and the invoice is later issued in the
247+
**Accounting** app, the calculation happens twice, consuming two credits.
248+
249+
.. example::
250+
| **Sales order confirmed**
251+
| :icon:`fa-arrow-down` 1 credit (tax calculation)
252+
| **Invoice created**
253+
| :icon:`fa-arrow-down` 1 credit (tax calculation)
254+
| **Invoice confirmed and submitted**
255+
| :icon:`fa-arrow-down` 1 credit (tax calculation) + 1 credit (submit invoice)
256+
| **Total: 4 credits**
257+
185258
- :guilabel:`Mercosul NCM Code`: Mercosur Common Nomenclature Product Code
186259
- :guilabel:`Purpose of Use`: intended purpose of use for this product
187260
- :guilabel:`Service Code Origin`: City Service Code where the provider is registered
@@ -634,6 +707,18 @@ This electronic document can be issued through **Odoo Point of Sale app**.
634707
Its legal validity is guaranteed by the digital signature and by each Brazilian state's SEFAZ
635708
(Secretaria da Fazenda).
636709

710+
.. important::
711+
The :ref:`Avalara integration <localizations/brazil/avatax-account>` operates on a credit-based
712+
system. Each operation that involves communication with Avalara consumes one credit. The following
713+
operations within the **Point of Sale** (POS) application are subject to credit consumption:
714+
715+
- Tax calculation at the time of sale
716+
- Electronic invoice issuance (NFC-e)
717+
718+
.. note::
719+
Each step is billed separately. For example, calculating taxes and issuing an invoice for the
720+
same POS transaction consume two credits.
721+
637722
.. seealso::
638723
:doc:`Point of Sale <../../sales/point_of_sale>`
639724

0 commit comments

Comments
 (0)