The transaction set and its child transactions are linked through a Master-Detail relationship and are used to capture bank statement imports in FinDock. Every transaction on your organization’s bank account will become a single transaction record linked to a transaction set that groups all the records in that import.
Transactions in FinDock can be either automatically matched, manually matched or ignored. For more information on the matching of transactions and creating payment from them, see Processing bank statements.
Transaction Sub Elements capture elements within the Transaction such as included Charges. These are slaved to the transaction in terms of matching and will be automatically matched against the indicated account. Transaction Sub Elements are only used with CAMT.053 imports at the moment.
Customizing the Transaction Set and transaction objects
In general, customizations with regards to custom fields and/or validation rules are not supported on the transaction set and transaction objects.
The exception to this rule is the creation of rollup summary fields on the transaction set object to reflect the number of transactions matching certain criteria (such as debit and credit transaction count). This will lead to Locked Row errors when the attached transaction records are created or updated.
Customizing the Transaction Sub Element object
Customizations with regards to custom fields and/or validation rules are not supported on the transaction sub element object.