NEWWatch an agent's payment get refused, and read the reason, in the live browser demo.Open the demo
AxorumAxorum

Unattributed exposure

Informational

Unattributed exposure is the cumulative amount transacted with a counterparty whose legal identity has not yet been established. It exists because identity resolution often completes after the first transaction rather than before it, which means an unknown counterparty can accumulate meaningful exposure before anyone can attribute it.

How it works

Identity arrives late in practice. A new counterparty appears, transacts, and only later resolves to a known legal entity — or fails to. Systems that enforce limits only on resolved counterparties leave a gap. Closing it requires a separate limit on how much unresolved exposure may accumulate before resolution is required, and a mechanism to detect breaches retroactively when identity arrives after the fact.

Example

Over one week, Northwind's agents pay an unresolved counterparty forty-one times, totalling $2,180. Each payment sits well under any single-transaction limit. Nobody has established who the recipient is. An unattributed-exposure limit of $1,000 would have paused the flow at transaction nineteen and required resolution before continuing.

Common questions

Why not just require identity before the first transaction?

Sometimes that is right. But it blocks legitimate first-time counterparties and does not fit flows where the counterparty is discovered at runtime. The practical answer is usually a threshold rather than a gate.

What happens when identity resolves and the counterparty turns out to be prohibited?

That is a retroactive breach: transactions that were permissible under available information at the time and are not permissible under the information that arrived later. It requires a detective control and a documented response, not a preventive one.

By Tim Fisher, Co-founder, Axorum · Updated