Accounting classification of RepoMech end-node trades

Determine whether end-node trades assigned by RepoMech should be accounted as first-leg final sales with derivative second-leg recognition under FASB ASC 815, or as secured borrowings under FASB ASC 860-10-40-5(c)(1), given that the second-leg counterparty may differ from the first-leg transferee due to the mechanism’s multilateral netting structure. Clarify the applicable GAAP treatment to ensure consistent balance-sheet representation for end-nodes in chains formed by RepoMech.

Background

RepoMech reorganizes second-leg repo obligations into chains and cycles, fully netting matched-trade flows for intermediate nodes while assigning excess flows to end-nodes. For intermediate nodes, the absence of a repurchase obligation implies first-leg final sale treatment with second-leg FMV recognition, aligning with pre-reform accounting. However, for end-nodes, the mechanism’s multiparty structure means the counterparty for the second-leg may differ from that of the first-leg, raising ambiguity under ASC 860’s effective control criteria.

The paper notes that existing repo accounting standards do not explicitly address scenarios where counterparties change between legs or where multiparty contracts exist. The authors outline a possible approach to preserve counterparty continuity by also replacing first-leg contracts, but they state that the classification for end-node trades under RepoMech remains unresolved.