Transaction comment formats

B2COPY-generated entries usually follow the short patterns on this page. You can see them in the trading platform’s Comment or Notes field for balance operations and copied positions; administrators may also see the same text in B2COPY transaction views.

How to read a comment

1. 1

   Match the beginning

   Use the table above to find the comment family. For money movements, - means funds leave the account and + means funds arrive.

2. 2

   Read the operation code

   For example, PF means Performance Fee, DW identifies a transfer, and subs records a subscription.

3. 3

   Read the remaining fields

   The rest of the string identifies related accounts, positions, or an operation reference. Symbols such as #, @, $, and & separate special fields described below.

Fee comments

The two-letter code identifies the fee. For calculation rules, see the Fee list and Early Withdrawal Fee for PAMM.

Copy trading, MAM, and PAMM formats

A fee charge appears on the investment account in Copy Trading and MAM. PAMM uses a combined pool, so related fee entries can be reflected on different sides of the master–investor relationship. The payout can differ from the charge when account currencies differ or part of the fee is paid to a partner.

Accrued fee debt

When previously accrued fee debt is collected, AD follows the fee code on the charge. For example:

Copy Trading or MAM: -PF AD|<master>|
PAMM: -PF AD|<master>|<investor>|

The same layout applies to other debt-capable fee codes. A Trade Fee debt collection can omit the original position because it collects an earlier shortfall. The matching fee payout keeps the regular credit format, such as +PF|<investor>|<reference>|; it does not add AD. Learn when debt is created and recovered in Mechanism for deducting accrued fee debt.

Subscriptions and unsubscriptions

Deposits, withdrawals, and transfers

The exact identifier in each field depends on which side of the transfer you are viewing. The <reference> appears on the incoming entry and identifies the related outgoing operation.

PAMM profit-allocation comments

p|@<master>|#<master position>|

This comment connects an investor’s PAMM allocation to a position on the master account. @ introduces the master account and # introduces the master position.

The entry recorded when the allocation opens can show a zero amount, because the result is not known yet. The entry recorded when the position closes carries the realized result, which can be positive or negative.

Copied-position comments

Copied positions use their own comment format. These are position comments, not balance-operation comments.

The optional <part> value distinguishes partial opens or other deal parts that belong to the same master position. For example, &12#550012|1001$3 and #550012 | 1001 &3 both identify part 3; the spaces belong to the format without a setup marker. On platforms with position identifiers too long for the comment field, shorter numeric identifiers can appear instead.

Values inside comments

Optional setup markers

Some platform setups add &<setup> directly after a balance-operation code. For example:

-PF&12|<master>|<investor>|
+DW&12|<source>|<reference>
-UNSUB&12|<master>|<destination>

The marker distinguishes the setup used for the account. It is optional, so otherwise equivalent operations can appear with or without it. In copied-position comments, the marker appears at the beginning instead: &12#....

Older and shortened comments

• Older investor-side PAMM fee records can contain two separators after the fee code, for example -PF||.... This is not a separate fee type.
• Older PAMM deposit records can name both sides of the pair with #, for example +DW|#<master>|#<investor>. New deposits use the standard +DW|<source>|<reference> form.
• Trading platforms limit a comment to 31 characters. If the full value is too long, fields at the end can be removed.
• A configured Balance Deals Mask can add text before or after the standard B2COPY comment.
• A shortened comment can end with one or more | separators or omit fields that normally follow them. Decode the fields that are present rather than assuming the operation is different.

Related configuration and guides

• Balance deals mask — configure text around generated balance-operation comments.
• Balance operations on (un)subscription — configure the balance records created when subscriptions change.
• PAMM links and rollover — understand when PAMM balance requests and settlements are processed.