Skip to main content

TM Transaction Batch Upload – Unknown Entities Are Now Stored with the Transaction

The batch upload endpoint now accepts transactions that contain an unknown entity, instead of rejecting them.

What changed​

  • A transaction containing an unknown entity is accepted and stored in Transaction Monitoring.
  • Unknown entities are not created or updated in CLM, and they are not used in business rules (BRM). Their details are kept within the transaction data only.
  • On the alerts pages, the unknown entity's ID and name are read from the transaction and shown as text.

How to send entities​

  • To reference a known CLM entity, set by_external_id to its CLM entity ID. Any other fields you send for that entity are ignored.
  • To send an unknown entity, set external_entity_type to "unknown" and don't provide by_external_id. The entity details you embed are stored with the transaction as sent.
  • For each entity, use either by_external_id or external_id, never both.
  • The main entity of a transaction must be a known CLM entity (provided via by_external_id). It can't be an unknown entity.
  • At least one entity in each transaction must provide by_external_id.

See Transaction Batch API for details.

Available from the end of November 2025.