Share via

POPEnterMatchInvoiceType

  • Article

Description

An eConnect transaction type that describes a purchase order invoice.

XML nodes

Remarks

You can only use the taPopEnterMatchSerialInsert and taPopEnterMatchLotInsert nodes when the purchase order is a drop-ship or drop-ship blanket type for the associated taPopEnterMatchInvLine node.

Header taxes The calculation that eConnect uses to validate the header tax amount differ between a purchase invoice and a purchase order. To complete your transaction, you must supply the header TAXAMNT value required by a purchase invoice document.

When eConnect validates the amount of the <taPopEnterMatchInvHdr> TAXAMNT element, it totals the value from each of the purchase invoice's line tax amounts. The validation calculation does not include freight or miscellaneous tax amounts. If the header TAXAMNT value is not equal to the line tax amounts, eConnect returns a validation error.

The following example uses a simplified version of a POPEnterMatchInvoiceType schema object to illustrate the related elements:

Header.TAXAMNT= 25 (Line.TAXAMNT of 25)
Header.FRTAMNT= 30
Header.MISCAMNT= 23
Header.UsingHeaderLevelTaxes = 0
Line.TAXAMNT= 25
LineTaxInsert.TAXAMNT= 25
LineTaxInsert.FRTTXAMT= 30
LineTaxInsert.MSCTXAMT= 23

**AutoInvoice   **The AutoInvoice element of the <taPopEnterMatchInvLine> XML node allows you to automatically invoice against a purchase order. AutoInvoice is a boolean element with a value of either 0 or 1. If AutoInvoice is set to 1, the AUTOCOST element of the <taPopEnterMatchInvLine> XML node must also be set to 1. Setting AUTOCOST to 0 is not valid. The AUTOCOST element allows you to base cost on the purchase order.

Warning: The AutoInvoice settings applies to a specific purchase order and not the vendor. If you set AutoInvoice to 1, eConnect automatically invoices shipments that are received against the purchase order number that is specified for the transaction.

MultiLine You use the <taPopEnterMatchInvToShpMultiLine> XML node when you need to manually enter/match a transaction that has one item that spans multiple shipments. The <taPopEnterMatchInvToShpMultiLine> XML node allows the line to be passed to the <taPopEnterMatchInvLine> node with the first shipment to match against. Use the <taPopEnterMatchInvToShpMultiLine> XML node to allow other shipments to be added to the line that it matches. If you use multiple <taPopEnterMatchInvToShpMultiLine> XML nodes, the totals for the transaction must be immediately passed to the <taPopEnterMatchInvLine> XML node.

Document structure

<eConnect>
    <POPEnterMatchInvoiceType>
        <eConnectProcessInfo />
        <taRequesterTrxDisabler_Items>
            <taRequesterTrxDisabler />
        </taRequesterTrxDisabler_Items>
        <taUpdateCreateItemRcd />
        <taUpdateCreateVendorRcd />
        <taCreateVendorAddress_Items>
            <taCreateVendorAddress />
        </taCreateVendorAddress_Items>
        <taPopRcptLineTaxInsert_Items>
            <taPopRcptLineTaxInsert />
        </taPopRcptLineTaxInsert_Items>
        <taPopDistribution_Items>
            <taPopDistribution />
        </taPopDistribution_Items>
        <taAnalyticsDistribution_Items>
            <taAnalyticsDistribution>
        </taAnalyticsDistribution_Items>
        <taPopEnterMatchLotInsert_Items>
            <taPopEnterMatchLotInsert>
        </taPopEnterMatchLotInsert_Items>
        <taPopEnterMatchSerialInsert_Items>
            <taPopEnterMatchSerialInsert>
        </taPopEnterMatchSerialInsert_Items>
        <taPopEnterMatchInvLine_Items>
            <taPopEnterMatchInvLine />
        </taPopEnterMatchInvLine_Items>
        <taPopEnterMatchInvToShpMultiLine_Items>
            <taPopEnterMatchInvToShpMultiLine>
        </taPopEnterMatchInvToShpMultiLine_Items>
        <taPopEnterMatchInvHdr />
        <taMdaUpdate_Items>
            <taMdaUpdate />
        </taMdaUpdate_Items>
    </POPEnterMatchInvoiceType>
</eConnect>

See also