This XML invoice support has the following restrictions for how the invoices are processed:

1. All invoices in one message must be from the same supplier and supplier site.

2. Custom code conversions must be defined as part of trading partner setup.

3. Tax groups are not supported.

4. Invoices in one message are limited to one organization.

5. Oracle supports the following XML element structure:

   <PROCESS_INVOICE>

   INVHEADER (invoice header)

   INVCHARGE (freight/miscellaneous charge line)

   INVLINE (item line)

   INVTAX within INVLINE (This tax line will have the same LINE_GROUP_NUMBER as the Item line)

   INVTAX (tax line(s)) (This tax line will not have a LINE_GROUP_NUMBER because it will be prorated across all taxable Item lines in this invoice.)

   </PROCESS_INVOICE>

   The following are examples of document structures that are not supported:

   • INVTAX and INVCHARGE within INVHEADER

   • INVTAX within INVCHARGE

   • INVCHARGE within INVLINE

6. The map does not support tax on tax. See Tax on XML Invoices.

7. The map does not support invoices matched to blanket purchase orders.