A drip feed flush extract will extract all remaining transactions regardless of approval and coding status, ie. it will clear out all transactions left in the period.
This is good if you have been creating regular drip feed extracts but it is now time to close the period and there are still transactions to be extracted that do not meet the company's mandatory requirements. To extract these remaining transactions, you would use the drip feed flush extract.
Note: If you are using the drip feed extract, you can have the drip feed flush extract option removed if you know your organization is not intending to use this functionality. This will prevent this option from being accidentally selected.
To create a drip feed flush extract:
The Statement Periods screen appears.
Both scenarios include auto coded transactions when the implementation option Interface - Export - Exclude Auto Coded is disabled.
Note: The number does NOT include approved transactions belonging to an expense report if all the transactions belonging to the expense report are approved and the expense report itself is also approved.
The Extract Options - Advanced dialogue box appears.
While the extract is being generated, a progress window appears.
A window will appear advising you the file has been created and placed in the Vault. (Note: If personal vaults are enabled for your instance, the extract is placed in your personal vault.)
The file will be named similar to the format, Shared Travel Services_<org name>_<date stamp>_<month>_txt (or xml etc).
You will now be able to go to the Shared Travel Services Vault and download the file to your local machine and then upload the file into your organization's finance (ERP) system.
After you have created the extract, an extract summary will appear beneath the Previous Extracts heading of the Statement Periods screen.