AgreementDesc (FIX tag 913)

StringFIX 4.4FIX 5.0 SP2

AgreementDesc (tag 913) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 26 message types, always optionally.

At a glance

Tag: 913
Name: AgreementDesc
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 26

What the specification says

FIX 4.4

The full name of the base standard agreement, annexes and amendments in place between the principals applicable to a financing transaction.

FIX 5.0 SP2

The full name of the base standard agreement, annexes and amendments in place between the principals applicable to a financing transaction. See https://fpml.org/coding-scheme/master-agreement-type for derivative values.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 913

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	123
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
913	AgreementDesc	EXAMPLE
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	218

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 913 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	FIX 4.4	FIX 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	inside the FinancingDetails component
AllocationInstructionAlert	BM	—	Optional	inside the FinancingDetails component
AllocationReport	AS	Optional	Optional	inside the FinancingDetails component
CollateralAssignment	AY	Optional	Optional	inside the FinancingDetails component
CollateralInquiry	BB	Optional	Optional	inside the FinancingDetails component
CollateralInquiryAck	BG	Optional	Optional	inside the FinancingDetails component
CollateralReport	BA	Optional	Optional	inside the FinancingDetails component
CollateralRequest	AX	Optional	Optional	inside the FinancingDetails component
CollateralResponse	AZ	Optional	Optional	inside the FinancingDetails component
Confirmation	AK	Optional	Optional	inside the FinancingDetails component
ExecutionReport	8	Optional	Optional	inside the FinancingDetails component
IOI	6	Optional	Optional	inside the FinancingDetails component
NewOrderSingle	D	Optional	Optional	inside the FinancingDetails component
OrderCancelReplaceRequest	G	Optional	Optional	inside the FinancingDetails component
OrderCancelRequest	F	Optional	Optional	inside the FinancingDetails component
OrderStatusRequest	H	Optional	Optional	inside the FinancingDetails component
Quote	S	Optional	Optional	inside the FinancingDetails component
QuoteCancel	Z	Optional	Optional	inside QuotCxlEntriesGrp › FinancingDetails
QuoteRequest	R	Optional	Optional	inside QuotReqGrp › FinancingDetails
QuoteRequestReject	AG	Optional	Optional	inside QuotReqRjctGrp › FinancingDetails
QuoteResponse	AJ	Optional	Optional	inside the FinancingDetails component
QuoteStatusReport	AI	Optional	Optional	inside the FinancingDetails component
QuoteStatusRequest	a	Optional	Optional	inside the FinancingDetails component
SecurityList	y	Optional	Optional	inside SecListGrp › FinancingDetails
SecurityListRequest	x	Optional	Optional	inside the FinancingDetails component
SecurityListUpdateReport	BK	—	Optional	inside SecLstUpdRelSymGrp › FinancingDetails
TradeCaptureReport	AE	Optional	Optional	inside the FinancingDetails component
TradeCaptureReportRequest	AD	Optional	Optional	inside the FinancingDetails component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 913 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[913];field?.name;   // "AgreementDesc"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44

Try the decoder Source on GitHub