Agent Lender

Field 1.18 | Matching Date: n/a | Tolerance: n/a | Agent Lender Data Provision: No>

Status: Best Practice Finalised, Last Updated: 24/05/2021

Field 1.18 | Matching Date: n/a | Tolerance: n/a | Agent Lender Data Provision: No

Description:
The unique code of the agent lender involved in the securities lending transaction.

Best Practice:
Where an Agent Lender is used, this field shall contain a valid LEI recognised by GLEIF. The LEI shall pertain to a legal entity and not a branch.

The status of the LEI for all message templates, can be either:

• Issued

• Lapsed

• Pending Transfer

• Pending Archival

Known issue: Agent Lender (Field 1.02 & Field 1.18) not included in the TR's primary-key construction logic. This is an acute problem for some agent lenders who support beneficial owners who have multiple agents. One current workaround is to use the Report Submitting Entity (1.04) as one of the keys then the agent lenders populate this field with their own LEI (instead of the vendor submitting the report with their LEI).

Regarding use of an Asset Manager LEI in this field where the Asset Manager acts as the Agent Lender, see here. (SFTR-20)