Updating Transactions in Capture Expense

This task will update approved expenses in Capture Expense, allowing them to be marked as processed so that they will no longer be returned by the Export Transactions task, or to populate them with a reason why they could not be successfully processed.

Settings

Capture Expense Connection

Required
The Capture Expense REST API connection to use. See the Connecting to Capture Expense article if you require more information on how to create/manage connections.

Input File

Required
The file containing the records to import into Capture Expense. This can be an absolute or relative file path on the local computer or network. The file must contain data in an XML format, a sample of which is shown below.

Defaults to (Output from previous task)

Fail File

Required
The XML file to output any records that the task fails to process to. This can be an absolute or relative file path on the local computer or network. This will contain any errors which occur on the import.

Defaults to capture-expense_import_transactions_fail.xml

Success File

Required
The XML file to output any records that the task successfully processes to. This can be an absolute or relative file path on the local computer or network.

Defaults to capture-expense_import_transactions_success.xml

Prevent Reprocessing

Required
Set this option to True to prevent the same record being processed more than once by Zynk. An <ExternalId> must be provided on the record in the input file for this to work.

Zynk Settings

See Common Task Settings

Examples

A sample input file is shown below.

<?xml version="1.0" encoding="utf-8"?>
<Transactions>
  <Transaction>
    <Id>62c4a1e3-6909-4c11-aa41-05aa90d814c4</Id>
    <Posted>true</Posted>
  </Transaction>
  <Transaction>
    <Id>8eb9b204-6ff5-481b-8f59-06592b301bfb</Id>
    <Posted>false</Posted>
    <Message>Invalid nominal account.</Message>
  </Transaction>
<Transactions>