Centralized invoices

Within Maximo® Manage, you can combine payments for purchase orders from different sites within the same organization on a single invoice. However, this consolidation is not available in Oracle E-Business Suite. The invoice integration both in and outbound does not support the function of combining payments.

Structure of invoice line numbers

The invoice line number for an inbound invoice is a concatenation of the number 1, a four digit Oracle invoice line number, and a four‐digit distribution line number.

Vendor pay sites

Both Maximo Manage and Oracle invoices can contain a vendor that differs from the vendor on the corresponding purchase order. In the Oracle E-Business Suite, you must designate a vendor site as a Pay Site if it is used on an invoice.

Invoice matching

Maximo Manage supports four‐way matching of an invoice when the corresponding purchase order contains rotating items or items that require inspection. It supports three‐way matching if the items are non‐rotating and do not require inspection.

Table 1. Invoice matching approval levels
Match approval level Description
3‐way Within the following defined tolerances, the purchase order and invoice are checked for a match:
  • The quantity billed is less than or equal to the quantity ordered on the PO shipment.
  • The invoice price on the PO shipment is less than or equal to the purchase order price on the PO shipment.
Checks that the receipt and invoice information match the quantity tolerances defined:
  • The quantity that is billed on the PO shipment is less than or equal to the quantity received on the PO shipment.
4‐way Same as 3‐way, with the extra criterion that checks that acceptance documents and invoice information match within the following quantity tolerances defined:
  • The quantity that is billed on the purchase order shipment is less than or equal to the quantity received on the purchase order shipment.

Reversal of invoices

In Maximo Manage, when an original invoice contains errors, such as unit cost mistakes, you can replace the original invoice by reversing it. In Oracle E-Business Suite, you can cancel a complete invoice. You can also cancel invoice distributions.

The status of the invoice, the credit memo, or the debit memo that is being reversed must be Approved or Paid.

You must cancel the invoice in the application in which it was created, if the invoice was created in Oracle E-Business Suite, it must be canceled in Oracle E-Business Suite.

Inbound processing of canceled invoices

In Oracle E-Business Suite, you can cancel an invoice at the header level, which cancels the complete invoice. You can also reverse an invoice distribution, which does not cancel the complete invoice.

You can cancel a paid invoice in Oracle E-Business Suite only after the payment is voided, which is transferred to Maximo Manage as a reverse invoice.

In Oracle E-Business Suite, if you cancel an invoice distribution, it is transferred to Maximo Manage as a reverse invoice, or a reverse credit invoice, or a reverse debit invoice. Canceled invoices of type STANDARD are transferred from Oracle E-Business Suite to Maximo Manage as invoices of type REVINVOICE. Canceled invoices of type CREDIT are transferred from Oracle E-Business Suite to Maximo Manage as invoices of type REVCREDIT. Canceled invoices of type DEBIT are transferred from Oracle E-Business Suite to Maximo Manage as invoices of type REVDEBIT.

After the invoice is canceled in Oracle E-Business Suite, the accounting must be re-created to send the canceled invoice back to Maximo Manage.

Outbound processing of reversed invoices

In Maximo Manage, when an original invoice contains errors, such as unit cost mistakes, you can replace the original invoice by reversing it. The replacement for the original invoice contains the updated information. You can reverse an invoice without creating a return transaction.

You can transfer reversed invoices from Maximo Manage to Oracle E-Business Suite as a credit invoice.

Payment updates to invoices that are reversed in Maximo Manage are not imported back from Oracle E-Business Suite to Maximo Manage.

Filter

The integration framework transfers invoices from Maximo Manage to the Oracle E-Business Suite when the status of the invoice matches a status in the APSEND integration control.

The integration framework transfers invoices from the Oracle E-Business Suite to Maximo Manage when the following conditions are met:
  • The value of the Oracle integration control APIN is 1.
  • The invoice is validated. The accounting is created and the receipt is complete.

Integration controls

The invoice integration uses the following Maximo Manage and Oracle integration controls.

Table 2. Invoice integration controls
Control Description System
APIN Send the Oracle E-Business Suite invoice data to Maximo Manage. Oracle E-Business Suite
APLINETYPE Default invoice line type in the Oracle E-Business Suite. Maximo Manage
APSEND Statuses at which invoices are sent from Maximo Manage to the Oracle E-Business Suite. Maximo Manage
GENITEM Dummy identifier for masking the item number. Maximo Manage
GENUSR Dummy identifier for masking user ID in outbound transactions. Maximo Manage
GLCURNCY Default GL currency code in Oracle E-Business Suite. Maximo Manage
GLCURNCYTYPE Type of currency exchange rates. Maximo Manage
INVCSTATUSXREF Translate the Maximo Manage internal and external invoice status, if you are using synonyms. Maximo Manage
INVCTYPEXREF Cross‐reference Maximo Manage and the Oracle E-Business Suite invoice document types. Maximo Manage
ORGXREF Cross‐reference Maximo Manage organization and the Oracle E-Business Suite ledger ID. Maximo Manage
SITEXREF Cross‐reference Maximo Manage site ID and the Oracle E-Business Suite operating unit. Maximo Manage