...
Expected Behavior | Description | ||
Transaction line: Department,Class,Transaction type are sourced from the Vendor fields
| This behavior is expected when the following fields are populated in the Vendor record:
| ||
Transaction vendor lookup | Current look up uses the vendor’s Tax ID, Bank account number, IBAN, BBAN and Vendor Name in this order. | ||
Vendor bill creation when vendor is not found | If INFlow preference: CREATE VENDOR IF NOT FOUND is FALSE then an error is returned. If TRUE then the vendor is created. Refer to the Appendix section 4.9 Conversion Mapping for the list of vendor fields and the data sources.
| ||
Vendor bill creation when Total amount is not equal to the related purchase order total amount. | If the following INFlow preferences are configured:
then a new expense line is added to the converted vendor bill when the Total Amount of the vendor bill is not equal to the purchase order.
| ||
E-documents where the transaction date is in a closed period. | The bill is converted using the first date of the next open period. | ||
Inbound E-Document: Date in NetSuite Override Bill transaction date defined in the XML. | To change the transaction date for e-documents that are waiting to be converted into NetSuite vendor bills, go to the portlet described in section 3.1.2 Manually convert bills. Edit the Inbound E-document record. Enter a date in the Date in NetSuite field. Save the E-document. This date will be used instead of the date from the XML.
| ||
Inbound E-Document: PO Number in NetSuite Override Bill transaction reference PO number defined in the XML. | If set, the value is used as PO Number reference when looking for related purchase orders, instead of the PO Number sourced from the XML file. | ||
Inbound E-Document: Reference Number in NetSuite
Override Bill transaction Number defined in the XML. | If set, the value is set as the document number on converted transactions instead of the value on Reference Number sourced from the XML file. |
Bill Conversion based on the expected receipt date
| Expand | ||
|---|---|---|
| ||
This feature was first introduced in INFlow V2.6.0 |
| Note |
|---|
Dependency:
This feature is available only if your INFlow conversion setup uses the Inherit PO lines feature. |
On a purchase order that is expected to be partially billed, check the [STA] Match based on expected receipt date field.
...
Once the INFlow server receives and converts a bill with reference to a purchase order where [STA] Match based on expected receipt date = T; (Field ID: custbody_sta_inflow_match_exp_receipt)
The related purchase order lines where the vendor bill date is within the same month of the expected receipt date will be added to the vendor bill lines.
The basis of the bill date compared with the expected receipt date of the PO is the scanned date (tran date in the XML).
The complete quantity of the purchase order line will be billed.