| EDI business document Invoice |  |
| The business document Invoice describes the invoicing and payment of goods and includes the following EDI messages: INV Invoice RAD Remittance Advice The Invoice (INV) message results from the Invoicing procedure in the Invoicing package. The Central Invoicing package contains invoices that can be sent to a business partner electronically. The Invoice (INV) message can be received in the Accounts Payable module of the Financials package. The Remittance Advice (RAD) message is received during the Electronic Bank Statements procedure in the Cash Management module of the Financials package. A remittance advice contains information that is sent to the selling company by the purchasing company about the transactions being settled by a payment. Both the invoicing procedure and the electronic bank statements (EBS) procedure include a large number of steps. This business document does not discuss all of these steps, but only the ones that relate to the generation and processing of the Invoice (INV) and Remittance Advice (RAD) messages. Invoice (INV) To generate the Invoice (INV) message, carry out the following steps in the invoicing procedure: After invoicing data is released to Invoicing, create a billing request in the Billing Requests (cisli2100m000) session. Use the Compose/Print/Post Invoices (cisli2200m000) session to process the billing request, which includes composing the invoice for the released data and printing the original invoice. You can also use the Print Invoices (cisli2400m000) session to print the invoice. Printing the original invoice prepares the Invoice (INV) for EDI transmission. Remittance Advice (RAD) To generate and process the Remittance Advice (RAD) message, complete the following steps in the electronic bank statements procedure: Use the Remittance Advice Messages (Receipts) (tfcmg5101s000) session to view the Remittance Advice Messages (RAM), and add or change messages with the Converted status, if necessary. Use the Match Electronic Bank Statements (tfcmg5212m000) session to match the converted Remittance Advice Messages (RAD) automatically against the open invoices/items. The matched remittance advice is then matched to the received EBS for reconciling the open entries. Importing bank statements and matching total receipts against relevant open items can save considerable time when processing bank transactions and reconciling accounts. Invoice (INV) After you ship the goods to the customer, which is the purchasing company, and after you transfer the order to central invoicing and create a billing request, use the Compose/Print/Post Invoices (cisli2200m000) session or the Print Invoices (cisli2400m000) session to prepare the Invoice (INV) for EDI transmission. If the Generate Outgoing Message before Connection check box is selected in the Networks (ecedi0120s000) session, use the Direct Network Communication (ecedi7205m000) session to generate the outgoing message and to provide a report showing the generated messages. If you do not use the option to generate outgoing messages before connection in the Networks (ecedi0120s000) session, you can use the Generate EDI Messages (ecedi7201m000) session to create the ASCII files for outgoing messages. External EDI messages are placed in the appl_from subdirectory specified for the network and the translation software retrieves the messages. Internal EDI messages need not be translated and are stored in the appl_comm subdirectory, which is used for outgoing and incoming messages. To receive the Invoice (INV) message from a supplier, which is the selling company, use the Direct Network Communication (ecedi7205m000) session. A purchase invoice is created and two reports are generated. The Remarks in Copied Messages report shows the invoice number(s) generated, along with some pertinent remarks. The Incoming EDI Purchase Invoice report lists the invoiced quantity and amounts at the line level and the tax amounts by tax code ID, if applicable. If goods are received before the Invoice (INV) message is received, automatic invoice matching occurs. If the invoice message arrives before the order is received, the purchase invoice remains unmatched and can be manually matched when the goods are received. The invoice matching can occur either at the invoice header or at the invoice line depending on the data received in the incoming purchase invoice message: Invoice Matching at the Invoice Header To perform invoice matching at the header, the Automatic Matching check box must be selected in the ACP Parameters (tfacp0100s000) session. If the received message includes a valid customer purchase order number in the invoice header and no invoice order line information, the entire order is matched for all order lines for which goods have been received. If the tolerance is not met, the entire purchase invoice remains unmatched. Invoice Matching at the Invoice Line If the received message includes order line information, each invoice line is matched to the included customer order lines for which goods have been received. The invoice lines for which the ordered goods have not yet been received remain unmatched. You can view the received invoice data in the Match/Approve Purchase Invoices (tfacp2507m000) session. Remittance Advice (RAD) To receive the Remittance Advice (RAD) message from your customer (pay-by business partner), use the Direct Network Communication (ecedi7205m000) session. This session retrieves the RAD message from the appl_to directory, after the ASCII file is placed on the directory by translation software. After the Remittance Advice (RAD) message is received, a remittance advice message (receipt) is created along with the Remarks in Copied Messages report. This report shows the document number(s) generated and some pertinent remarks. You can use the Remittance Advice (tfcmg5501m000) session to view the received information, based on which you can take further action. Related topics An overview of EDI business documents The invoicing procedure Electronic Bank Statements An overview of BEMIS |