[IMP] accounting/l10n_ar: liquidity product direct sales
Link to GDrive images folder: https://drive.google.com/drive/folders/1qWtbGewR3LxDKs21QpMEPhCKEovVyoKx?usp=drive_link closes odoo/documentation#8009 Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Co-authored-by: XPL <xpl@odoo.com>
This commit is contained in:
parent
7e30d6f7da
commit
094924d5ff
@ -948,6 +948,73 @@ the corresponding layout and fiscal stamps stated in the :ref:`Invoice printed r
|
|||||||
.. seealso::
|
.. seealso::
|
||||||
:doc:`Client account creation <../../websites/ecommerce/checkout_payment_shipping/checkout>`
|
:doc:`Client account creation <../../websites/ecommerce/checkout_payment_shipping/checkout>`
|
||||||
|
|
||||||
|
Liquidity product direct sales
|
||||||
|
------------------------------
|
||||||
|
|
||||||
|
Liquidity product direct sales are used for sales involving third parties. For such
|
||||||
|
sales, the seller and the proprietary company of the goods can each register their corresponding
|
||||||
|
sales and purchases.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
:ref:`Install <general/install>` the *Argentinian Electronic Invoicing* module (`l10n_ar_edi`) to
|
||||||
|
use this feature.
|
||||||
|
|
||||||
|
Configuration
|
||||||
|
~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Purchase journal
|
||||||
|
****************
|
||||||
|
|
||||||
|
A purchase journal is needed to generate an electronic vendor bill with a document type *Liquidity
|
||||||
|
Product*. This journal needs to be synchronized with the AFIP as it will be used to generate the
|
||||||
|
liquidity product electronic document.
|
||||||
|
|
||||||
|
To modify the existing purchase journal or create a new one, navigate to :menuselection:`Accounting
|
||||||
|
--> Configuration --> Journals`. Then, select the existing purchase journal or click the
|
||||||
|
:guilabel:`New` button, and fill in the following required information:
|
||||||
|
|
||||||
|
- :guilabel:`Type`: select :guilabel:`Purchase`.
|
||||||
|
- :guilabel:`Use Documents`: check this field to to be able select the electronic document type.
|
||||||
|
- :guilabel:`Is AFIP POS`: check this field to be able to generate electronic documents.
|
||||||
|
- :guilabel:`AFIP POS System`: select :guilabel:`Electronic Invoice - Web Service` from the
|
||||||
|
drop-down menu in order to send the electronic document to AFIP via web service.
|
||||||
|
- :guilabel:`AFIP POS Number`: is the number configured in the AFIP to identify the operations
|
||||||
|
related to this AFIP POS.
|
||||||
|
- :guilabel:`AFIP POS Address`: is the field related to the commercial address registered for the
|
||||||
|
POS, which is usually the same address as the company. For example, if a company has multiple
|
||||||
|
stores (fiscal locations) then the AFIP will require the company to have one AFIP POS per
|
||||||
|
location. This location will be printed in the invoice report.
|
||||||
|
|
||||||
|
.. image:: argentina/l10n-ar-purchase-journal.png
|
||||||
|
:align: center
|
||||||
|
:alt: l10n_ar Purchase Journal Configuration.
|
||||||
|
|
||||||
|
Sales journal
|
||||||
|
*************
|
||||||
|
|
||||||
|
A sales journal is needed to register the invoice when a product is sold to a third party that will
|
||||||
|
then sell the same product. This journal will not be synced with AFIP as the invoice will not be
|
||||||
|
electronic.
|
||||||
|
|
||||||
|
To modify the existing sales journal or create a new one, navigate to
|
||||||
|
:menuselection:`Accounting --> Configuration --> Journals`. Then, selecting the sales journal or
|
||||||
|
click the :guilabel:`New` button, and fill in the following required information:
|
||||||
|
|
||||||
|
- :guilabel:`Type`: select :guilabel:`Sales`.
|
||||||
|
- :guilabel:`Use Documents`: check this field on the journal to select the electronic document type
|
||||||
|
(in this case the electronic invoice).
|
||||||
|
|
||||||
|
.. image:: argentina/l10n-ar-sales-journal.png
|
||||||
|
:align: center
|
||||||
|
:alt: l10n_ar Sales Journal Configuration.
|
||||||
|
|
||||||
|
Invoicing flow
|
||||||
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Once the configurations are all set, the *Liquidity Product Vendor Bill* will be generated by the
|
||||||
|
company that is selling the product on behalf of another party. For example, a distributor of a
|
||||||
|
specific product.
|
||||||
|
|
||||||
Reports
|
Reports
|
||||||
=======
|
=======
|
||||||
|
|
||||||
@ -965,11 +1032,10 @@ VAT reports
|
|||||||
Sales VAT book
|
Sales VAT book
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
In this report, all the sales are recorded, which are taken as the basis for the accounting records
|
This report records all the sales, which are taken as the basis for the accounting records
|
||||||
to determine the VAT (Tax Debit).
|
to determine the VAT (Tax Debit). The :guilabel:`Sales VAT` book report can be exported as a `.zip`
|
||||||
|
file using the :guilabel:`VAT BOOK (ZIP)` button at the top left, containing `.txt` files to upload
|
||||||
The :guilabel:`Sales VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK (ZIP)`
|
to the AFIP portal.
|
||||||
button in the top left, which contains `.txt` files to upload in the AFIP portal.
|
|
||||||
|
|
||||||
.. image:: argentina/sales-vat-book.png
|
.. image:: argentina/sales-vat-book.png
|
||||||
:align: center
|
:align: center
|
||||||
@ -978,8 +1044,9 @@ button in the top left, which contains `.txt` files to upload in the AFIP portal
|
|||||||
Purchases VAT book
|
Purchases VAT book
|
||||||
~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK
|
The :guilabel:`Purchases VAT` book report can be exported as a `.zip` file using the
|
||||||
(ZIP)` button in the top left, which contains `.txt` files to upload in the AFIP portal.
|
:guilabel:`VAT BOOK (ZIP)` button at the top left, which contains `.txt` files to upload to the AFIP
|
||||||
|
portal.
|
||||||
|
|
||||||
.. image:: argentina/purchases-vat-book.png
|
.. image:: argentina/purchases-vat-book.png
|
||||||
:align: center
|
:align: center
|
||||||
@ -988,7 +1055,7 @@ The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file :guil
|
|||||||
VAT summary
|
VAT summary
|
||||||
~~~~~~~~~~~
|
~~~~~~~~~~~
|
||||||
|
|
||||||
Pivot table designed to check the monthly VAT totals. This report is for internal usage, it is not
|
Pivot table designed to check the monthly VAT totals. This report is for internal use and is not
|
||||||
sent to the AFIP.
|
sent to the AFIP.
|
||||||
|
|
||||||
.. image:: argentina/vat-summary.png
|
.. image:: argentina/vat-summary.png
|
||||||
@ -1002,7 +1069,7 @@ IIBB - Sales by jurisdiction
|
|||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the
|
Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the
|
||||||
corresponding taxes to pay, therefore it is not sent to the AFIP.
|
corresponding taxes to pay; and therefore, it is not sent to the AFIP.
|
||||||
|
|
||||||
.. image:: argentina/iibb-sales-jurisdiction.png
|
.. image:: argentina/iibb-sales-jurisdiction.png
|
||||||
:align: center
|
:align: center
|
||||||
@ -1012,7 +1079,7 @@ IIBB - Purchases by jurisdiction
|
|||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the
|
Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the
|
||||||
corresponding taxes to pay, therefore it is not sent to the AFIP.
|
corresponding taxes to pay; and therefore, it is not sent to the AFIP.
|
||||||
|
|
||||||
.. image:: argentina/iibb-purchases-jurisdiction.png
|
.. image:: argentina/iibb-purchases-jurisdiction.png
|
||||||
:align: center
|
:align: center
|
||||||
|
Binary file not shown.
After Width: | Height: | Size: 28 KiB |
Binary file not shown.
After Width: | Height: | Size: 21 KiB |
Loading…
Reference in New Issue
Block a user