Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:c:chargeable_work_unit [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:c:chargeable_work_unit [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Chargeable Work Unit ====== | ||
| + | |||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Chargeable Work Unit provides the basic unit for cost attribution in the Cost Recovery, Compensation, | ||
| + | |||
| + | A Chargeable Work Unit supports comparison across qualified implementations by providing the architecture with a common basis for measuring work. Examples include one fraud screening action, one anti-money-laundering review, one sanctions screening action, one policy evaluation, one persistence action, one replay action, or one authorized release package. | ||
| + | |||
| + | A Chargeable Work Unit does not expose the full transaction payload, detailed compliance findings, regulated data, or confidential business content. It identifies the work type, the relevant obligation, the qualified Node, the evidence reference, and the cost rule context needed for economic accountability. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | FX Demo Reference Architecture, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Chargeable Work Unit provides the basis for compensation claims, chargeback entries, reimbursement records, settlement instructions, | ||
| + | A Chargeable Work Unit differs from a transaction. One transaction can require multiple chargeable work units, and one chargeable work unit can relate to a non-transactional activity such as persistence, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An FX transaction requires sanctions screening. The sanctions screening Node completes a single screening action and records a single Chargeable Work Unit for that work. The record identifies the work type, the applicable obligation, the performing Node, the evidence reference, and the cost rule context without exposing the full transaction payload. | ||