Sales transport documentation
A sales delivery form or note includes a description and quantity of the goods delivered and accompanies a shipment of goods. A copy of the delivery note, signed by the customer, is returned to the vendor as proof of delivery.
Sales delivery forms are prenumbered based on chronological order, so that companies can account for all forms and keep track of transactions. A bill of lading can also be electronic.
Transport documents are required as a proof of sale while goods are in transit. These documents must support the legal or cultural requirements that differ by country.
Delivery waybills are documents that support the transfer of goods between different addresses.
Chile specifics
The electronic invoicing process begins with an electronic delivery document, known as Guía de Despacho or bill of lading. The Guía de Despacho is generated and registered with the government as the initial transport event.
Bills of lading are required to be issued when an invoice is not issued at the time of delivery of goods or merchandise. The bills must be numbered and stamped by Servicio de Impuestos Internos. Invoices that are issued later must contain the number of the bill of lading.
How Infor meets the requirement
Shipments that originate from the customer order are sent to LSP and the Chile government. When the approved shipment BOD is received from LSP, the shipment is released in FSM.
Customers must create the customer orders. Localization integration only works if the orders are created with line items in FSM. Release the customer order and run the action to create the shipment record. The shipment must be in the printed state.
When you release the shipment, the FSM_ION_SyncShipment_Outbound BOD is triggered, resulting in these outcomes:
- A Shipment Sent to LSP for approval message is displayed.
- The status of the shipment is Shipped.
- A temporary hold is filed for approval.
You cannot change the details of the shipment. The FSM_ION_ProcessShipment_Inbound BOD is received from LSP and the statuses are displayed in the BOD, such as Registered, Submitted, Failed, or Rejected.
Because of the new ShipmentFolioAuthorizationCode business class, the shipment business class is extended and a new persistent field for each shipment is added. When the FSM_ION_ProcessShipment_Inbound BOD is received from LSP and the status is Registered, the values must be updated in ShipmentFolioAuthorizationCode.
After setting up IDM and releasing the shipment, run the action for released shipments to print the ShipmentFolioAuthorizationCode barcode.
These are the supported formats in FSM–Localization integration:
- CL Delivery Note (Guía de Despacho)
- CL Delivery Note Ledger (Libro de Guías de Despacho Electrónicast)
See Infor Localization Services Platform User Guide.