ores.refdata.netting_agreement

Table of Contents

A netting agreement is the legal document, such as an ISDA Master Agreement, that lets one legal entity of the firm and one counterparty replace what each owes the other under it with a single net amount. It is the legal fact behind a netting set: a set opened under an agreement belongs to the agreement's two parties, and a set with no agreement holds trades that do not net.

The agreement's two parties never change across its versions: both columns are fixed, so a new version that changes either is refused. A netting set copies them and pins the copy to the agreement, so a set cannot be filed under another counterparty's agreement, and the copy stays true. Closing an agreement does not close its sets, as for every soft foreign key in the schema; a set's agreement is checked when the set is written.

1. Flags

2. Columns

2.1. id

UUID uniquely identifying this netting agreement.

Surrogate key for the agreement record.

2.2. agreement_number

The reference the two parties give the agreement.

Unique within the legal entity that signed it.

std::string("NA-") + std::string(faker::string::alphanumeric(10))

2.3. party_id

The legal entity of the firm that signed the agreement.

References the parties table. Fixed for the agreement's life.

ctx.generate_uuid()

2.4. counterparty_id

The counterparty that signed the agreement.

References the counterparties table. Fixed for the agreement's life.

ctx.generate_uuid()

2.5. agreement_type

The family of master agreement.

ISDA for the ISDA Master Agreement; AFB and FBF for the French agreements; OTHER for any other signed-off master agreement.

std::string("ISDA")

2.6. governing_law

The law the agreement is governed by.

Free text, such as English law or New York law.

std::optional<std::string>("English law")

2.7. description

Optional description of the agreement.

std::optional<std::string>("Test netting agreement")

3. Artefact columns

The import names the counterparty by LEI where the store holds the party and counterparty uuids. Publishing resolves them in the target tenant.

3.1. agreement_number

3.2. version

3.3. counterparty_lei

3.4. agreement_type

3.5. governing_law

3.6. description

4. Artefact indexes

4.1. counterparty_lei

5. SQL

5.1. Flags

5.2. Checks

expression
"agreement_type" in ('ISDA', 'AFB', 'FBF', 'OTHER')

6. Foreign keys

6.1. party_id

6.2. counterparty_id

7. C++

7.1. Flags

7.2. Repository

7.3. Domain includes

#include <optional>
#include <string>
#include <boost/uuid/uuid.hpp>

7.4. Entity includes

#include <optional>
#include <string>

7.5. Conventions

7.6. Table display

column header
agreement_number Number
agreement_type Type
governing_law Governing Law
modified_by Modified By
version Version

7.7. Presentation

7.7.1. Detail fields

field label widget type is_key is_required placeholder
agreement_number Number agreementNumberEdit line_edit true true Agreement reference
agreement_type Type agreementTypeEdit line_edit false true ISDA, AFB, FBF or OTHER
governing_law Governing Law governingLawEdit line_edit false false Governing law
description Description descriptionEdit line_edit false false Enter description

7.7.2. Columns

enum_name field header type width
AgreementNumber agreement_number Number string 140
AgreementType agreement_type Type string 80
GoverningLaw governing_law Governing Law string 160
Description description Description string 200
Version version Version int 80
ModifiedBy modified_by Modified By string 120
RecordedAt recorded_at Recorded At timestamp 150

8. See also

Emacs 29.3 (Org mode 9.6.15)