Exchange Details
The Exchange Details (vendor line) tab on the IET transaction contains common Vendor fields as described in the "Vendor" topic in the Transactions User Guide. The Exchange Details tab also contains common Accounting fields as described in the "Accounting" topic in the Transactions User Guide. The following fields are not common to Vendor or Accounting tabs.
Of special note are the referenced transaction fields that exist on the Exchange Details tab. When information is entered or inferred, it will be pushed down to all accounting lines if the Reference Type is not Memo. The reason behind this behavior is that the posting lines generated from one Accounting Line can only liquidate one referenced accounting line. Two different references on a Vendor/Accounting line combination are only allowed if the Vendor line performs a Memo reference.
Use of a front-end split major program on the Exchange Details is a restricted action that should be controlled. It does require the entry of the Funding Profile, Priority, and Line on the line with the major program and the use of an event type that uses cash.
Field InformationField Information
Field Name |
Required? |
Field Description |
Calculated Amount |
Calculated |
A system-calculated amount, that is the sum of the Line Amount field found on all 2nd Party Accounting lines to the Exchange Details line. The Calculated Amount must equal the Line Amount. This edit exists to ensure that the net result of internal accounting for the transaction is $0.00 on an application-wide basis. |
Accounting Profile |
Optional |
This field is used to generate the Accounting Lines (2nd Party Accounting) when the transaction is validated or submitted. Lines are generated based on the Accounting Templates defined for the Accounting Profile and the dollar amount entered in the Line Amount field. |
Bank |
Conditionally Required |
An optional IET field for entering a Bank account code to be recorded for the vendor line. This field is required or prohibited based on the Event Type Requirement (ERQ) settings for the event type being used. If the ERQ requires a bank, the system will default a Bank from the Fund (FUND) table, using the Fund and Fiscal Year of the header. A pick exists to the BANK table to assist in data entry. |
Budget FY |
Optional |
Although a common Header and Accounting field, a Budget FY field exists on the Exchange Details tab exists to record a year when the corresponding Header value is not desired. |
Fiscal Year |
Optional |
Although a common Header and Accounting field, a Fiscal Year field exists on the Exchange Details tab exists to record a year when the corresponding Header value is not desired. |
Period |
Optional |
Although a common Header and Accounting field, a Period field exists on the Exchange Details tab exists to record a year when the corresponding Header value is not desired. |
Billing Profile |
System Set |
A field inferred and used for Accounts Receivable updates from a referenced Receivable (RE) transaction used by internal transactions created for payment intercepts and the liquidation of internal receivables. |
AR Dept |
System Set |
A field inferred and used for Accounts Receivable updates from a referenced Receivable (RE) transaction used by internal transactions (ITA and IET) created for payment intercepts and the liquidation of internal receivables. |
AR Unit |
System Set |
A field inferred and used for Accounts Receivable updates from a referenced Receivable (RE) transaction used by internal transactions (ITA and IET) created for payment intercepts and the liquidation of internal receivables. |
Debt ID |
Conditionally Required |
The IET Transaction Type is used to record accounting events for internal loans with the Internal Debt Accounting (IDA) Transaction Code. There are limits on what Debt ID values can be entered:
Please see the Debt Management User Guide for more information on these and other topics. |
Service From Date |
Conditionally Required |
An optional date that will default to the Record Date on the Header unless made required by Transaction Control (DCTRL), in which case, there is no default and the date must be manually entered. |
Service To Date |
Optional |
An optional field that will default to equal the Service From Date if left blank. |
Funding Profile, Priority, and Line |
Optional |
These three funding COA exist on the exchange detail line but are Tertiary as delivered on Configure Page. These fields are intended only for grant revenue transfers and not to manually split expenditures. When displayed, a transaction clone is recommended to closely control their use. |