Frequently Asked Questions / Anveo EDI Connect / Sending Invoice Lists

Sending Invoice Lists

When you are communicating with big companies in the food business you might need to send invoice lists to them. In this article we will describe the basics for the NAV and the exporting mapping.

You can use the sales invoice export mapping template as a starting point for the NAV mapping and expand it for the invoice list, but you can also start from scratch and build the mapping line by line. When the mapping is finished, it will create an EDI Invoice List Document which contains the numbers of other EDI Invoice Documents in its Document Lines.

If you use the sales invoice export mapping template, there’s a mapping line for the sales invoice header and an EDI Document for the sales invoice indented below. In an empty mapping, you should now create these two lines with its filters. For the invoice list you need to insert a mapping line between these two and set the following minimum properties:

  • Table: EDI Document
  • Filter: Document Type=CONST(Invoice List), Bill-to Customer No. = Sales Invoice Header.Bill-to Customer No.

After that, indent the EDI Document line below the line for the invoice list and add the fields you want to transfer to the Anveo EDI tables. The next step is to create the EDI Invoice List Document Lines. As usual you can create them no matter where. For this tutorial they will be created at the Document Summary Lines because you can transfer the total invoice amount to the document line. In the data item link for the invoice list document lines you link to the EDI Invoice List Document and add the filter “Type”=CONST(EDI Document).
You need to transfer the No., Version No. and Document Type from the EDI Invoice Document to the Document Line No., Linked Version No. and Document Type because the primary key of the table EDI Document is made of this three fields and you could use the same number for different document types. In most cases the no. is sequential so this information would be enough to identify the record. Another reason is that the Version No. and the Document Type are needed for the lookup of the field “No.” in the EDI Document Line.
In order for the user to display which invoice was transferred to the EDI Document, the number of the sales invoice header is put to the invoice list line description and the aforementioned total invoice amount from the Document Summary Line to the field “Line Amount”.

If you want to specify a post processing for the exporting mapping, it has to be specified on the EDI Invoice List Document and not on the Invoice Document. This way you pass the invoice list document to your export mapping.

Thus the EDI Invoice List Document is the first table in the export mapping. Indented below are the Document Lines of this document and finally, indented below again there’s another EDI Document table, with the No., Document Type and Version No. from the document lines, in order to loop over all invoice documents that are listed in this Invoice List. Below you can see this structure in an EDIFACT export mapping:

Anveo EDI table structure for invoice lists

If you need to export the total invoice list amount you can use the invoice list document lines where the total amount for every invoice is stored in the field “Line Amount”.