Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Staria INFlow Version 2.6.0

Enhancements

INFlow Conversion - Inheriting Purchase Order Lines Based On Expected Receipt Dates

  • This new feature will allow INFlow server users to receive partial bills and link them to the referenced purchase order.

  • This feature aims to improve the bill conversion rate for scanned bills that reference:

    • partially received purchase orders

    • purchase orders for long-term purchases

  • This feature is an extension of the Inherit PO Lines feature.

  • Upon creation of the vendor bill by INFlow conversion; 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 unbilled purchase order lines will be billed.

    • Date validation (Month and Year only.) is made between the XML’s Transaction Date and the Expected Receipt Date of the purchase order lines.

    • Audit Trail Error Message is logged if there are no unbilled lines where the expected receipt date falls within the same month/year as the XML date

  • Feature dependency:

    • The Advanced Receiving feature must be enabled.

    • The purchase order form of the referenced bill must display the Transaction Line Field: Expected Receipt Date.

Bug Fixes

INFlow Approval

  • A bug causing vendor bill credits to skip being displayed in the INFlow Portal’s Approve AP Transactions list page has been fixed.

  • A bug causing the re-trigger approval and approval override button on vendor bill credits in the NetSuite Full access user interface has been fixed.

  • A bug causing transactions to be approved when no approvers are found has been fixed.

    • Affected transactions uses the [STA] Approval Matrix : DYNAMIC APPROVER FIELD ID to determine the next approvers.

    • When no approver is found, the error message will be stored in the [STA] INFLOW SCRIPT NOTES field of the transaction. (Error message: No approvers found from Approval Matrix. Please check the Approval Matrix setup and criteria.)

INFlow Portal

  • A bug causing the item’s amortization template to override the amortization schedule of the transaction when saving a vendor bill in the INFlow portal has been fixed.

  • A bug causing the amortization schedule to be empty on new vendor bill expense lines create via the line splitting feature has been fixed.

Vendor Record

  • A bug causing an error when adding new subsidiaries under the subsidiaries sublist has been fixed.

 Fixed error

User will no longer encounter this error message:

JS_EXCEPTION TypeError Cannot read properties of undefined (reading 'saveRecord') or JS_EXCEPTION TypeError Cannot read properties of undefined (reading 'validateLine')

Other changes

  • The custom record “Bank Details” (ID: customrecord_2663_entity_bank_details) configuration has been updated to allow attachments and show notes.

SuiteApp Bundle Update Instructions / Notes

“Update Deployments“ must be selected for the following scripts:

  • [STA] INFlow Approve Bills

  • [STA] Approval History

Patches Consolidated in this release

For questions or concerns, please get in touch with support@staria.com.

  • No labels