Invoice object

1. SKIPINVOICE - Skips the sending of the document if both of the following conditions are true:
   • The document has not been sent out before.
   • The new status is not listed in the IVSEND control.
2. SKIPINVIOCEUPDATE - Skips the sending of the document when updated but the status is not changed.
3. SETSTATUSIFACE - Sets the value of the STATUSIFACE field to 0 (false) for all status values except those listed in the IVSEND control.
4. CHECKSTATUS – Sends only the invoice header data if the status changes and the new status is not in the IVSEND control. (In this case the full document was previously sent and this is sending only the status change notification).

The inbound processing creates and updates INVOICECOST lines only if one of the following conditions is met:

• The invoice line does not reference a purchase order line.
• The corresponding purchase order line does not have a distribution.
• The purchase order line does not reference a storeroom.

In all other cases, the inbound processing ignores INVOICECOST information when creating or updating the invoice.

If the inbound message provides INVOICETERMS, the inbound processing deletes the old terms and adds the new ones.

Users can optionally specify a price variance in the PRICEVAR field on each invoice line, if invoice matching is done in the external system and price variances determined in the external system are sent to create variance transactions to update work orders and storerooms. In order to process these variances, a value must exist for OWNERSYSID in the inbound invoice, and it cannot be the same as the value of MAXVARS.MXSYSID.

Users can optionally specify a price variance in the PRICEVAR field on each invoice line, if invoice matching is done in the external system and price variances determined in the external system are sent to create variance transactions to update work orders and storerooms. In order to process these variances, a value must exist for OWNERSYSID in the inbound invoice, and it cannot be the same as the value of MAXVARS.MXSYSID.

The IVMATCH collaboration switch requires the following values:

• OWNER1SYSID value is always “THISMX”.
• OWNER2SYSID value is the value of INVOICE.OWNERSYSID.

If the evaluation is false, line level invoice variances are ignored in the invoice processing.

The following are the typical scenarios for using the invoice interface:

• Invoice Matching in the system (AP Outbound): Invoices received from third parties, either electronically or manually, are processed by the system; that is, they are matched against receipts, if applicable, and then approved. Alternately, payment schedules created in the system will result in approved invoices being created based on the schedule. These approved invoices result in a payment advice being sent to an external AP system. The process of matching also results in accounting entries being posted to the general ledger.
• Invoice Matching in external system (Variances Inbound): The system does not do the invoicing, but accepts matched invoices from external systems and applies any variances back to the respective work orders, storerooms, and so on. The accounting entries related to the accounts payable and/or variances must be recorded in the external system; they will not be sent out.

The primary intent of this interface is to provide the system with any variance information necessary for updating the work order costs.