Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

VendorWhen Bill Not Found *

Field name

Description

FlowAP Template

Select the FlowAP template that will be used for converting bills and bill credits for this subsidiary.

The FlowAP Template record is responsible for mapping the XML elements into NetSuite fields.

Limitation

Vendor Specific Preferences

If set, the vendor-specific preferences will supersede the same FlowAP Preference that is included in the selected Vendor-specific preferences saved search.

The selected saved search type must be Vendor.

All vendors returned by the search will use FlowAP preferences defined in the vendor record instead of the Staria FlowAP subsidiary setup.

Tip

Best Practice: Create separate Vendor searches per subsidiary and associate the searches to the correct Subsidiary Setup record. This ensures that the query for these preferences only include the appropriate subsidiary thereby speeding up the process.

Default Vendor Expense Item

Select a default expense item to be set on a vendor record when it is created.

If “USE EXPENSE ITEMS INSTEAD OF ACCOUNTS FOR EXPENSE LINES” is TRUE, then, this will be the default item. The Subsidiary of the item selected in this preference will be the default when creating a Vendor Record.

If you define a default expense item on the Vendor Record, then it will be the priority instead of what you have selected in this preference.

For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

Enable Cross-Subsidiary Vendor

This configuration option is used to restrict conversion vendor search and creation to specific subsidiaries.

Select the associated subsidiaries for the Vendor records that will be searched or created during the FlowAP conversion process.

Recommended field selections for each use cases:

  1. The FlowAP conversion must search only for vendors with the same subsidiary as the e-document. Vendors for this subsidiary are not shared to other subsidiaries.

    • Select only the same subsidiary that is selected in the Staria FlowAP Subsidiary Setup : Subsidiary field.

  2. The FlowAP conversion must search for vendors within any active subsidiary in the NetSuite instance. The vendors are shared across all subsidiaries.

    • Select all subsidiaries in the list.

  3. The FlowAP conversion must search for vendors in some subsidiaries.

    • Select specific subsidiaries in the list.

Expand
titleRelated deprecated preferences

These preferences effectively replace the INFLOW: Create separate vendors for different subsidiaries and Use Web service ID format preferences.

Auto Create Vendor

Note

This was renamed from “CREATE VENDOR IF NOT FOUND”

Check this box if you want a new vendor to be created for a direct bill in case it is not found in the system.

 

Vendor look-up uses Tax ID, Bank account number, IBAN, BBAN, and Vendor Name in this order.

Vendor: Bank Details

Do Not Create New Vendor Bank Details If Do Not Match Existing

If vendor bank details in the incoming file do not match the already existing bank details, the default FlowAP behavior is to create a new set of bank details and mark them as Primary, so they are by default selected in the next payment.

Check this box if you want the new bank details to NOT be created and the bill to be flagged

Default Domestic Payment Template ID*

Enter the internal ID of the default template for domestic payments for the vendor which is used when creating Entity Bank Payments record

Default Foreign Payment Template ID*

Enter the internal ID of the default template for foreign payments for the vendor which is used when creating Entity Bank Payments record

Transaction Header

Warning

The FlowAP conversion only supports UBL 2.1 Invoice XML schema. The UBL 2.1 (Universal Business Language) standard provides a set of predefined codes for the InvoiceTypeCode element, which specifies the type of invoice being issued. The following are supported InvoiceTypeCode values:

  • 380 - Commercial invoice: The most common type of invoice used for general business transactions.

  • 381 - Credit note: Used to correct or cancel a previously issued invoice.

Vendor

Vendor Specific Preferences

If set, the vendor-specific preferences will supersede the same FlowAP Preference that is included in the selected Vendor-specific preferences saved search.

The selected saved search type must be Vendor.

All vendors returned by the search will use FlowAP preferences defined in the vendor record instead of the Staria FlowAP subsidiary setup.

Tip

Best Practice: Create separate Vendor searches per subsidiary and associate the searches to the correct Subsidiary Setup record. This ensures that the query for these preferences only include the appropriate subsidiary thereby speeding up the process.

Warning

Saved search Criteria subtab > “Use Expression” = T is not supported.

Default Vendor Expense Item

Select a default expense item to be set on a vendor record when it is created.

If “USE EXPENSE ITEMS INSTEAD OF ACCOUNTS FOR EXPENSE LINES” is TRUE, then, this will be the default item. The Subsidiary of the item selected in this preference will be the default when creating a Vendor Record.

If you define a default expense item on the Vendor Record, then it will be the priority instead of what you have selected in this preference.

For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

Enable Cross-Subsidiary Vendor

This configuration option is used to restrict conversion vendor search and creation to specific subsidiaries.

Select the associated subsidiaries for the Vendor records that will be searched or created during the FlowAP conversion process.

Recommended field selections for each use cases:

  1. The FlowAP conversion must search only for vendors with the same subsidiary as the e-document. Vendors for this subsidiary are not shared to other subsidiaries.

    • Select only the same subsidiary that is selected in the Staria FlowAP Subsidiary Setup : Subsidiary field.

  2. The FlowAP conversion must search for vendors within any active subsidiary in the NetSuite instance. The vendors are shared across all subsidiaries.

    • Select all subsidiaries in the list.

  3. The FlowAP conversion must search for vendors in some subsidiaries.

    • Select specific subsidiaries in the list.

Expand
titleRelated deprecated preferences

These preferences effectively replace the INFLOW: Create separate vendors for different subsidiaries and Use Web service ID format preferences.

Auto Create Vendor

Note

This was renamed from “CREATE VENDOR IF NOT FOUND”

Check this box if you want a new vendor to be created for a direct bill in case it is not found in the system.

 

Vendor look-up uses Tax ID, Bank account number, IBAN, BBAN, and Vendor Name in this order.

Vendor: Bank Details

Anchor
INFpref-vbankdetails
INFpref-vbankdetails

Do Not Create New Vendor Bank Details If Do Not Match Existing

If vendor bank details in the incoming file do not match the already existing bank details, the default FlowAP behavior is to create a new set of bank details and mark them as Primary, so they are by default selected in the next payment.

Check this box if you want the new bank details to NOT be created and the bill to be flagged

Default Domestic Payment Template ID*

Enter the internal ID of the default template for domestic payments for the vendor which is used when creating Entity Bank Payments record

Default Foreign Payment Template ID*

Enter the internal ID of the default template for foreign payments for the vendor which is used when creating Entity Bank Payments record

Transaction Header

Anchor
INFpref-tranheadersetup
INFpref-tranheadersetup

When Bill# Not Found *

Anchor
Flowsetup-whenbillnotfound
Flowsetup-whenbillnotfound

Select the preferred behavior of the script when the Bill# in the e-document does not match any vendor bills in NetSuite:

Option 1: Create Direct Vendor Bill/Credit (FlowAP conversion will create a stand-alone bill credit if a matching vendor bill is not found.)
Option 2: Report Error (The FlowAP conversion will not create a bill credit, an error audit trail will be logged against the FlowAP Document).

Info

Vendor-level preference [STA] No Direct Credit supersedes this setup When Bill # Not Found Preference.

If this Vendor-level preference is enabled, no stand-alone vendor credit can be created at all.

When PO# Not Found *

Anchor
Flowsetup-whenPOnotfound
Flowsetup-whenPOnotfound

Select the preferred behavior of the script when the Bill# PO# in the inbound file is not found e-document does not match any purchase order in NetSuite:

Option 1: Create

a

Direct Vendor Bill/Credit (FlowAP conversion will create a stand-alone bill if a matching purchase order is not found.)
Option 2: Report Error (

the bill will not be created but it will enter the error queue).

The FlowAP conversion will not create a bill, an error audit trail will be logged against the FlowAP Document).

Info

Vendor-level preferences [STA] No Direct Bill supersedes this setup When PO# Not Found

*

Select the preferred behavior of the script when the PO# in the inbound file is not found in NetSuite:

  • Create a Direct Vendor Bill

  • Report Error (the bill will not be created but it will enter the error queue)

    Preference.

    If these Vendor-level preference is enabled, no stand alone vendor bill can be created at all.

    Default Bill Location

    Select a default bill location

    Transaction Lines

    Inherit PO Lines

    Anchor
    INFpref-inheritpolines
    INFpref-inheritpolines

    If this is checked, purchase order lines will be inherited during vendor bill and vendor credit creation. The vendor bill/vendor credit total amount will still be adjusted however based on the inbound e-document/XML's total amount

    Inherit PO Lines : Default to 0 Quantity and Amount

    Check this box on top of the Inherit PO Lines preference if you want the inherited lines from PO to have 0 quantity and and 0 amount. The total balance of the Purchase Order will be posted in the Inherit PO Lines: Variance Account.

    Transaction Lines: Expense Items

    If a customer decides to use only items (which are typically service items) instead of accounts on purchase transactions, then fill up the field values under the Expense Items tab

    Post Single Bill Line: Use Payable Amount (NO TAX)

    If checked and the Vendor's Post Single Bill Line is checked, FlowAP will use the payable amount from XML instead of tax exclusive amount

    • Tax Rate is set to 0

    • Tax Amount is always calculated by the conversion script but since the tax rate is set to zero, then the calculated tax amount will be zero.

    Create Unidentified Items as Expense

    Handling of bills linked to POs: check this box if you want the item numbers not found in NetSuite to be created as expense lines on the Bill

    Info

    Related feature: https://staria.atlassian.net/wiki/pages/resumedraft.action?draftId=838729768 : Inherit PO line is not compatible with this preference. Inherit PO Lines is simulating billing the PO normally via the NetSuite user interface. In effect, PO Lines are inherited from the bill, disregarding the lines on the XML.

     

    Only the XML total amount is considered.

    • If XML's total amount is less than the PO billable amount, amount is adjusted on the bill to be created.

    • If XML total amount is equal to the PO billable amount then no change is made.

    • If XML total amount is greater then the PO billable amount then an error is thrown.

    Use Expense Items Instead of accounts for Expense Lines

    Check this box if you use default items rather than expense accounts to post your expenses. If this feature is enabled, you should then:

    • Select a default item on every Vendor

    define default items for bill posting under the Expense Items tab in FlowAP Subsidiary Setup

    Post Unidentified Items As Default Expense Items

    Check this box if you want the item numbers not found in NetSuite to be created as default items on the Bill.

     

    If the item specified in the XML does not have a matching item in the LINKED PO, the Default item will be used instead.

    Expense Item

    Select a default expense item, which will be used in case there is no bill created for a vendor yet (no last posting) or in case there is no default vendor expense item defined.

     

    If “POST UNIDENTIFIED ITEMS AS DEFAULT ITEMS ON LINKED BILLS“ is TRUE; then the item defined in this preference will be used as the default.

    For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

    Default Accounts: Vendor

    Vendor Expense Account *

    Select a default expense account to be set on a vendor record when it is created

    For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

    Default Accounts: Transaction

    Bill Expense Account (Preference)*

    Select which expense account should be set on the direct vendor bill:

    • Vendor's default expense account; or

    • Based on the last posting

    For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

    Expense Account *

    Select a default expense account, which will be used in case there is no bill created for a vendor yet (no last posting) or in case there is no default vendor expense account defined.

    For more information regarding this field and how it is used when determining the correct expense account/item during conversion, please refer to the following: [Link]

    Discount Account

    Select an account to be used for discount posting. If no account is selected, the default vendor expense account will be used.

    Charge Account

    Select an account to be used for additional charge (markup) posting. If no account is selected, the default vendor expense account will be used.

    Rounding Difference Account

    Select an account to be used for rounding difference posting. If no account is selected, the default vendor expense account will be used.

    Inherit PO Lines: Variance Account

    Select an account that will be used to recognize the variance between the purchase order and vendor bill. This will allow purchase orders to be created when the total amount of the bill is greater than or less than the total amount of the purchase order.

    If this preference is empty:

    • and the purchase order's billable amount exceeds the e-document's bill amount, no additional line will be added but the exceeding amount will be deducted starting from the last line of the bill.

    • If the e-document's bill amount exceeds the purchase order billable amount, conversion error is returned.

    Tax Codes

    Tax Code Table

    Contains an array of Tax Code Object
    TaxCodeObject should have the following:
    {
    taxrate : tax percentage rate
    countrytype: Domestic, EU, or Import
    itemtype: Service, Goods, or NA (Note: Use NA for Expense Lines)
    taxcode: tax code internal id
    }
    Format:
    [TaxCodeObject , TaxCodeObject ]

    If the Tax Code table is not needed for the subsidiary, input “[]” to disable the tax code table.

    Expand
    titleExamples
    Code Block
    languagejson
    [
      {
        "taxrate": "18.00%",
        "countrytype": "Domestic",
        "itemtype": "Goods",
        "taxcode": "27"
      },
      {
        "taxrate": "18.00%",
        "countrytype": "Domestic",
        "itemtype": "NA",
        "taxcode": "27"
      },
      {
        "taxrate": "5.00%",
        "countrytype": "EU",
        "itemtype": "Service",
        "taxcode": "26"
      },
      {
        "taxrate": "0.00%",
        "countrytype": "EU",
        "itemtype": "Goods",
        "taxcode": "21"
      },
      {
        "taxrate": "0.00%",
        "countrytype": "EU",
        "itemtype": "NA",
        "taxcode": "21"
      },
      {
        "taxrate": "21.00%",
        "countrytype": "Import",
        "itemtype": "Service",
        "taxcode": "81"
      },
      {
        "taxrate": "60.00%",
        "countrytype": "Import",
        "itemtype": "Goods",
        "taxcode": "80"
      },
      {
        "taxrate": "60.00%",
        "countrytype": "Import",
        "itemtype": "NA",
        "taxcode": "80"
      }
    ]

    https://staria.atlassian.net/wiki/spaces/SIS/pages/1316683781/Hierarchy+Used+by+FlowAP+Conversion+When+Selecting+Tax+Codes+on+Vendor+Bill+Lines#Understanding-the-Tax-Code-Lookup-Table

    Limitation

    Warning
    • Nexus using Tax Groups is not supported.

    Inherit PO Lines : Variance Tax Code

    Select a default tax code to be used when a new line is inserted to record the variance between the PO and the Vendor Bill.

    ...

    1. If you choose Single Reminder, then define the Email Reminder Days value below.

    2. If you choose Scheduled Daily Reminders, then complete the following steps to define the reminder email schedule

      1. Go to Customization > Workflow > Workflows > click Edit next to [STA] Approval Flow.

      2. Click the Pending Approval state.

      3. Click [STA] WA INFlow Send Approval Email action, under the Scheduled section.

      4. Make a copy of this custom action and set the original action to Inactive a. (NOTE: in the new bundle version this custom action will be inactive by default).

      5. Set up the values under the action Schedule section of your newly created custom action.

    ...

    Field name

    Description

    Flow AP Portal Preferences

    FlowAP Portal List Search - AP Transactions

    Select the saved search that will define the fields displayed in the AP Transactions list view. The default selection is [STA] INFlow Portal Main Search.

    The columns of the search will also define the fields that can be used to sort the list using the “Sort By” dropdown field.

    Note

    When creating a custom saved search, the following fields must be included in the result columns:

    • [STA] FlowAP Document {custbody_sta_flowap_document}

    • [STA] FlowAP PDF {custbody_sta_flowap_pdf} field

    FlowAP Portal List Search - Purchase Orders

    Select the saved search that will define the fields displayed in the Purchase Order list view. The default selection is [STA] INFlow Portal Main Search.

    The columns of the search will also define the fields that can be used to sort the list using the “Sort By” dropdown field.

    Vendor Bill/Credit Form Configuration

    Select the INFlow Portal Form Configuration Record for the AP transaction detailed view. This custom record is used to customize the fields displayed in the INFlow portal transaction view. Please contact support@staria.com for more information or if you need the INFlow portal fields customized.

    The default selection is [STA] Default Vendor Bill/Credit Form Configuration.

    Purchase Order Form Configuration

    Select the INFlow Portal Form Configuration Record for the Purchase order detailed view. This custom record is used to customize the fields displayed in the INFlow portal transaction view. Please contact support@staria.com for more information or if you need the INFlow portal fields customized.

    The default selection is [STA] Default Vendor Bill/Credit Form Configuration.

    ...

    Field name

    Description

    Handling of Transaction Dates

    Move Transaction Dates When (Conversion)

    Select when the transition date will be moved to a different date other than what was indicated in the e-document during conversion:

    • Period is Closed - when this option is selected, the Date (id: trandate) field will be updated only when the original date falls on an accounting period that is already closed.

    • Period is Locked - when this option is selected, the Date (id: trandate) field will be updated when the original date falls on an accounting period where A/P is already locked or the accounting period is already closed. This is the default value when creating a new preference record.

    • Never - the date will not be changed regardless.

    Note

    This preference checks the transaction: accounting period.

    This is not always the same as the calendar month of the transaction date.

    Related troubleshooting article: Understanding the Date-Period Mismatch Conversion Behavior

    Move Transaction Dates When (Approval)

    Select when the transition date will be moved to a different date other than what was indicated in the e-document during approval:

    • Period is Closed - when this option is selected, the Date (id: trandate) field will be updated only when the original date falls on an accounting period that is already closed.

    • Period is Locked - when this option is selected, the Date (id: trandate) field will be updated when the original date falls on an accounting period where A/P is already locked or the accounting period is already closed. This is the default value when creating a new preference record.

    • Never - the date will not be changed regardless.

    Note

    This preference checks the transaction: accounting period.

    This is not always the same as the calendar month of the transaction date.

    Related troubleshooting article: Understanding the Date-Period Mismatch Conversion Behavior

    Move Transaction Date To

    Select the Date (id: trandate) on which it will be updated:

    • First Day of Current Period (default) - the transaction date field will be updated with the first day of the current accounting period.

    • First Day of Earliest Open Period - the transaction date field will be updated with the first day of the first open accounting period. The earliest open period is:

      • when Move Transaction Date When = Period is Closed, the earliest accounting period that is not yet closed. This is the default value when creating a new FlowAP subsidiary setup record.

      • when Move Transaction Date When = Period is A/P Locked, the earliest accounting period where the A/P locked is not yet completed.

    Accruals

    Transaction Date Fields for Accruals

    Input the internal ID of the transaction date field to be used as a filter in the FlowAP Accruals search (i.e. ON OR BEFORE <datefield>).
    For join fields, use the syntax recordtype.fieldid
    If blank, the default would be accountingperiod.endate.

    AP Accrual Account - Net Amount

    Select an accruals account to post unapproved bill balances at the end of the month.

    ...