AllocationReport (MsgType AS)

applicationFIX 4.4FIX 5.0 SP2

AllocationReport is the FIX message with MsgType AS, defined in FIX 4.4 and FIX 5.0 SP2. It is an application-level message: it carries a business event rather than managing the session. Its body has 69 top-level members once the standard header and trailer are counted.

A real AllocationReport

AllocationReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength136
35MsgTypeASAllocation Report (aka Allocation Claim)
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
755AllocReportIDEXAMPLE
71AllocTransType0New
794AllocReportType3Sellside Calculated Using Preliminary (includes MiscFees and NetMoney)
87AllocStatus0accepted (successfully processed)
857AllocNoOrdersType0Not specified
54Side1Buy
53Quantity1000000
6AvgPx1.09215
75TradeDate20240101
10CheckSum223
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.

Message body — FIX 4.4

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

Message body — FIX 5.0 SP2

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

What changed between the dialects

Present in FIX 5.0 SP2 only (12)

tag 715, tag 828, tag 829, tag 442, tag 582, tag 578, tag 991, tag 1011, tag 579, tag 819, PositionAmountData, RateSource

Handle AllocationReport 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);if (message.msgType === "AS") {  message.name;            // "AllocationReport"  // fields are keyed by tag; repeating groups live on message.groups}// Problems come back as data, never as exceptions:issues;                    // FixIssue[]fix.validate(message);     // dictionary-level problems

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