As work orders are brought into the system, they are run against a preliminary automated validation script. Should a work order fail any of the given validation rules, the work order will be set to a "validationerror" status. Work Orders set to this status will automatically be ported to the "Invalid Work Orders" view within Floworks. A field service administrator will then need to review the work order. At this point, the administrator can correct the specified error or send the work order in question to be processed by the appropriate field office. The field office is dictated by the current zone that the mechanic on the work order is currently assigned to. If an administrator chooses to correct the specified error, the validation script will re-process the work order on the next cycle. If the work order passes, it will be moved to a "processed" state where it will be picked up by the NetSuite Import Script. Should the work order fail the validation process again, it will be sent back to the "Invalid Work Order" view where it will either need to be corrected or overridden. An overridden work order will not be subject to the preliminary validations and will be picked up by the NetSuite Import Script on the next cycle. A secondary validation will be performed inside the NetSuite Import Script. If a work order fails this the NetSuite validation, it will be sent back to the "Invalid Work Order" screen and marked accordingly with an import error. NetSuite errors must be corrected before a work order can be uploaded in to the system.