The Gatekeeper File Export Process integrates into the current AP Invoice Process. When a Gatekeeper invoice is created in OnBase it will go through the same steps to be imported into Epicor as any other AP Invoice.

However, the process will deviate when the invoice is submitted for posting. If a gatekeeper invoice is submitted for posting and does not have the data required to create the sync file, the invoice will be placed on hold and an error email will be sent.

After the data has been entered the invoice can be posted. Upon posting, an fmx file will be created to transfer the transaction data to Gatekeeper. Data for this file is pulled from the Part, Invoice, UOM and Company specific configuration.

After files are created, a final check is performed against a schema to ensure this is valid for GK import before being moved to the export directory. If this check finds any file to be invalid (could happen due to changes made on invoice after post process is submitted) an email alert will be sent with a reason code and any invalid files attached.

*Note: Refer to the file spec for details of the structure and contents of the sync file.