Transaction matching application: Difference between revisions
From ACT Wiki
Jump to navigationJump to search
imported>Doug Williamson (Add link.) |
imported>Doug Williamson (Add link.) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
==See also== | ==See also== | ||
*[[Application]] | |||
* [[Bank payment obligation]] | * [[Bank payment obligation]] | ||
* [[Baseline]] | * [[Baseline]] | ||
* [[Data matching]] | * [[Data matching]] | ||
* [[Physical supply chain]] | * [[Physical supply chain]] | ||
* [[Transaction]] | |||
[[Category:The_business_context]] | |||
[[Category:Technology]] | |||
Latest revision as of 11:26, 14 July 2022
(TMA).
A transaction matching application compares submitted data with prespecified criteria (the 'baseline') and declares a match or non-match.
TMAs are used in bank payment obligations.
An example of a TMA is the SWIFTNet Trade Services Utility (TSU).
This is a matching system for trade documents designed to allow banks to provide funding at various stages throughout the physical supply chain.
