Default standard transaction description

Every invoice profile needs at least one transaction description so you can transfer data using the Transfer module. The default transaction is used in the Transfer job, but you can change this.

Mark a transaction description as the default standard transaction description

When you are using Manager and editing an invoice profile, you can mark a standard transaction as the default standard transaction.

To mark a transaction description as the default standard transaction description, open the invoice profile, right-click the transaction description, and select Default.

After you mark the default standard transaction description, it is used in Transfer jobs if the Transfer job specifies <Default>.

Select a standard transaction description in the Transfer job

When you are editing a Transfer job, you can select a standard transaction to use instead of the default standard transaction description.

To select a transaction description, edit the job description and select one you want in the Transaction description box in the General settings for Transfer jobs. If you want to use the default standard transaction, select <Default>.

Use one transaction description for each invoice type (when using a system job)

If you are using a job description based on the system invoice profile, you do not have to create a transaction description for every invoice profile. Instead, you can do the following:

Create one transaction description for each invoice type. Then, make sure each transaction description contains all of the fields from each invoice profile of the same type. For example, the transaction description for PO invoices should contain system variables for all of the fields from all of the PO invoice profiles.
In the Transfer job description, select any invoice profile in the Standard transaction description box except <Default>. This tells INVOICES to use all the transaction descriptions you created in step one.

If you select <Default>, the default transaction description for each invoice profile is used instead, and if a default transaction does not exist, the job stops.