Page Comparison

Name

This is a unique name used to identify the FlowAP Document record.

If the file was received from Flow gateway, the name is the same as the XML file name.

Source Documents

XML File Reference

The XML file to be converted.

PDF File Reference

The related PDF file to the XML. This is the scanned document that generated the XML.

Transaction Data

Transaction Type

The NetSuite transaction type that will be created when the FlowAP document is converted.

Reference Number

The reference number included in the FlowAP document. This is the vendor’s reference number for the transaction.

PO/Bill Reference Number

For vendor bills: The purchase order number referenced in the e-document.

For vendor credits: The bill reference number referenced in the e-document.

Subsidiary

The result of the subsidiary lookup that will be the assigned to the transaction upon conversion.

Vendor

The result of the vendor lookup that will be the assigned to the transaction upon conversion.

Transaction Date

he transaction issue date of the e-document.

Preferences Tab

FlowAP Preferences

The list of FlowAP Preferences that were applicable to this document during lookup, parsing, validation, and conversion.

NetSuite Preferences

The list of NetSuite preferences and features that are applicable to this document's processing for FlowAP.

JSON Data file

The JSON data file created FlowAP processing.

The JSON data are netsuite fields and the assign data for each field that will be used for conversion.

Audit Trail - The FlowAP audit trail records script events and details throughout the FlowAP conversion process.

Date Created

Date and time of the event.

Event type

A general description of the script event that was executed.

Details

A detailed description of the script event that was executed.

Transaction type

Selecting the transaction type in the FlowAP document form will override the transaction type parsed from the XML.

Reference Number

This can be overridden at any stage (before Processing or before Conversion).

1. If overridden before processing:

   1. There will be an Audit Trail log which shows the original reference number parsed from the XML:

      Image Added

   2. JSON file will reflect the updated referencenumber:

      Image Added

2. If overridden post-processing, before conversion:

   1. No Audit Trail logs

   2. JSON file will not be updated; it will have the old value before manual override. But the conversion script will still pick up the overridden value from the FlowAP Document field.

PO/Bill Reference Number

This can be overridden at any stage (before Processing or before Conversion)

1. If overridden before processing:

   1. There will be an Audit Trail log which shows the original reference number parsed from the XML:

      Image Added

   2. JSON file will reflect the updated poreferencenumber:

      Image Added

2. If overridden post-processing, before conversion:

   1. No Audit Trail logs

   2. JSON file will not be updated; it will have the old value before manual override. But the conversion script will still pick up the overridden value from the FlowAP Document field.

Subsidiary

This can only be overridden before processing. Subsidiary validation happens in the processing stage. Subsidiary Lookup Criteria

Vendor

This can only be overridden before processing. Vendor validation happens in the processing stage. Vendor related configuration for FlowAP conversion: A Detailed Guide

Transaction Date

This can only be overridden before processing. Transaction date validations are executed on the Processing stage. Date-Period Mismatch Conversion Behavior : A Detailed Guide

1. There will be an Audit Trail log:

   Image Added

2. JSON file will reflect the updated trandate:

   Image Added