Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.2Field

TargetCompID <56>

Tag
56
Type
String
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows TargetCompID <56> as defined in FIX 4.2. For the current standard, see tag 56 TargetCompID in FIX Latest.

TargetCompID <56> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

TargetCompID is the assigned identifier of the firm receiving the message. With SenderCompID (49) it identifies the two ends of a FIX session.

Where it is used

StandardHeader (component) . In all, 46 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=153|35=D|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|11=ORD-1001|1=ACCT-01|21=1|55=AAPL|54=1|60=20261116-08:30:00.000|38=1000|40=2|44=190.50|59=0|10=128

Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.

Related tags: SenderCompID <49>

Description (from the Orchestra file)

Assigned value used to identify receiving firm.

Used in

Components and repeating groups (1)

NameKindPresence
StandardHeaderComponentRequired
All 46 messages that can carry TargetCompID, including through components and groups