TradeInputSource (FIX tag 578)

StringFIX 4.4FIX 5.0 SP2

TradeInputSource (tag 578) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 578
Name: TradeInputSource
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2

What the specification says

Type of input device or system from which the trade was entered.

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

A real message using tag 578

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	207
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
60	TransactTime	20240101-12:00:00.000
552	NoSides2 entries	2	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
578	TradeInputSource	EXAMPLE
54	Side	1	Buy
37	OrderID	ORD-10042
578	TradeInputSource	EXAMPLE
10	CheckSum	018

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 578 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	directly on the message body
AllocationInstructionAlert	BM	—	Optional	directly on the message body
AllocationReport	AS	—	Optional	directly on the message body
TradeCaptureReport	AE	Optional	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	Optional	inside the TrdCapRptAckSideGrp component
TradeCaptureReportRequest	AD	Optional	Optional	directly on the message body

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 578 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[578];field?.name;   // "TradeInputSource"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