VAT sales and purchase books

Tax authorities are required to produce periodic submissions of invoice details for accounts receivable and accounts payable.

Submissions may be required monthly, quarterly, or annually, and are generally in electronic format. The tax authorities can use the information to cross-check data from trading partners and to ensure that the correct taxes are paid.

Argentina specifics

These output files can be extracted from the generated zipped file and must be manually uploaded to the Portal IVA web service. The data that fits the filter criteria for each output must be available to generate the specific output file:

  • Cabecera
  • Ventas CBTE
  • Ventas Alicuotas
  • Compras CBTE
  • Compras Alicuotas
  • Compras Importaciones
  • Credito Fiscal Importacion Servicios

How Infor meets the requirement

Global Document Type is used to identify the type of sale or purchase. In Payables, you must update the PayablesInvoice.GlobalDocumentType field which is published in the SupplierInvoiceHeader/UserArea/Property/NameValue[@name='lcl.SubInvoiceType'] xpath.

In Receivables, the BillingInvoice.GlobalDocumentType for Billing and ReceivableInvoice.GlobalDocumentType for AR is updated. This data is this data will be published in the InvoiceHeader/UserArea/Property/NameValue[@name='lcl.SubInvoiceType'] xpath.

SupplierPartyMaster BOD: If the vendor TaxID and Vendor VATRegistrationID are identical, only VATRegistrationID is published in the BOD with the SchemeName AR:VAT. If they are not identical, VAT Registration ID is published first with schemename AR:VAT. TaxID is published with SchemeName AR:IIBB.

CustomerPartyMaster BOD: If the Customer TaxID and CompanyCustomer VATRegistrationID are identical, only VATID is published in the BOD with the SchemeName AR:VAT. If they are not identical, VAT Registration ID is published first with schemename AR:VAT. TaxID is published with SchemeName AR:IIBB.

SyncSupplierInvoice BOD: Tax Jurisdiction is passed in the BOD. Tax jurisdiction is the state code of the vendor, the field is Vendor.CurrentAddressRel_col_PostalAddress_prd_StateProvince. This field value is passed in the xpath SyncSupplierInvoice/DataArea/SupplierInvoice/SupplierInvoiceLine/Tax/TaxJurisdicationCodes/Code.

The BODs are triggered to Infor Localization Services from the FSM application by doing the transactions like creating a payables invoice and sales invoice. The reports are generated from LSP.

Setup must be done on LSP for the vendors, customers, and tax codes. See Infor Localization Services Platform User Guide.

For the list of required BODs, see BODs.

When the BODs are successfully sent to the Localization System Platform (LSP), the required reports can be generated from LSP.

Localization integration only occurs if you create the invoices with lines for both Payables and Receivables.