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

Version 1 Next »


Table of Contents


Overview

As part of NetSuite’s core processes, existing transactions are locked and restricted for editing, while new transactions cannot be created for any locked or closed period. FlowAP’s conversion process creates a transaction based on the date specified in the XML. Due to this, there are instances where the XML’s date falls under an already locked and/or closed period. This page details how FlowAP handles these scenarios and how NetSuite’s own configuration regarding date-period mismatch handling plays a key part in all of this.

NetSuite Preferences

FlowAP Subsidiary Setup

Known Use Cases

  • No labels