Direct electronic sales invoicing

Electronic invoice solutions must include vendor inbox to customer inbox. Both parties must use the same software or standard format to exchange electronic messages. Alternatively, they can both use a third-party service provider.

Reliable audit trails for paper and electronic invoices are required for authenticity of origin, integrity of content, and legibility of invoices.

Mexico specifics

Comprobante Fiscal Digital por Internet (CFDI) is a required format for electronic invoicing in Mexico. CFDI is set by the Mexico Servicio de Administración Tributaria (SAT). It is designed to improve integrity,security, reliability, and ease of invoicing. CFDI requires these components:

  • The commodity code must be updated for the items that are used in orders or billing. The commodity code is also referred to as Mexico product code or SAT code.
  • The UUID is a unique electronic number used by CFDI and CFD that represents the electronic invoice in Mexico. It is provided by the SAT authority.

How Infor meets the requirement

In Mexico, few clients are required to publish the addenda record. The addenda can be anything, including the purchase order or bill of lading.

To ensure that the customer PO and bill of lading are included in the invoice BOD, verify that the invoice is created from customer order entry. Localization integration works only if the invoices are created with lines in FSM.

On successful release of the Billing Invoice, the batch jobs must be run successfully to update to Subsystem Update. Now the Invoice is moved to Receivables, which triggers the FSM_ION_SyncInvoice_Outbound BOD to Infor LSP. A corresponding record is created for the invoice that is generated in Infor LSP.

On successful triggering, the corresponding invoice record in Infor LSP is created by the FSM_ION_SyncInvoice_Outbound BOD.

The required changes to the BOD FSM_ION_SyncInvoice_Outbound are made so that this requirement is available in Infor FSM application and Infor LSP.

Specify the Payment Form and USO-CFDI with a hyphen in the BillingInvoice.LetterOfCredit field. The valid values for Payment Form are from 01 to 99 and USO-CFDI is three characters. If 10-G01 is specified, 10 represents the payment mechanism and is included in the Invoiceheader/Paymentmethodcode xpath. G01 represents the SAT UseCode and is included in the InvoiceHeader/UserArea/Property/NameValue('lcl.MX.SATUseCode') xpath.

See BODs for the BOD to use to generate the vendor payment file.

See Triggering the SyncInvoice BOD for electronic sales invoicing.

To set up Infor LSP for integration, you must define default codes, contact masters, and payment methods. Exports are not currently supported for Infor LSP integration.

See Infor Localization Services Platform User Guide.