STATEMENT WORKFLOW / 6 MIN READ

How to map broker commission CSV and Excel statements

Match broker export columns to a consistent IB statement: source IDs, decimal formats, unknown entitlement and safe repeat imports. Includes a worked mapping.

Column mapping changes the shape of a report, not the meaning of its numbers. Confirm the period, currency and commission basis before matching headers.

Use this guide

Fictional examples. No broker password or account required.

Check what the report actually measures

A trading-history export, partner commission statement and withdrawal history are different evidence. Before importing, identify whether each row is a trade, a commission accrual, a monthly total or a payment. Combining a monthly total with its underlying trades would count the same commission twice. Keep the original export separately and work with an anonymized copy.

IBDock’s statement importer expects a statement snapshot with expected, reported, received and fee amounts. It does not turn raw trades into verified IB commission. A report that contains volume but no commission amount needs a separate agreement calculation and an eligibility check. Do not map lots or deposits into the reported commission column.

A worked mapping with unfamiliar column names

This fictional report uses a semicolon delimiter and a decimal comma. “Commission” is a reported amount, not a contractual expectation. There is no expected column, so expected remains unknown. The result is $1,200.50 reported, $1,150.00 received and $10.50 fees; the remaining $40.00 needs review. It is not automatically overdue.

Fictional broker export mapped into a USD statement
Broker export columnExample valueMap to
Referencesep-001Source ID
FirmSample PartnersBroker
Month2026-09Period
CCYUSDCurrency
Commission1200,50Reported
Paid1150,00Received
Charges10,50Fees
Not supplied—Expected: leave unmapped

Resolve decimal formats before confirming

Select the delimiter and decimal format explicitly. A comma can separate fields or represent a decimal; a grouping separator can make the same text ambiguous. The current importer rejects ambiguous formatting rather than guessing. Review a small sample and compare the result with the original statement before confirming.

Current sample imports accept USD only. Do not rename an EUR currency column to USD to pass validation. Reconcile currencies separately and retain conversion evidence outside this preview until a supported conversion workflow exists. Blank reported, received or fee fields are not silently treated as zero; enter zero only when your source evidence supports it.

Keep the same source IDs when you retry

An exact repeat import is deduplicated using broker and source record identity. Changing a previously imported amount is refused rather than silently replacing the original. Giving the changed row a fresh ID to bypass that refusal risks double counting. Investigate a corrected export and preserve its relationship to the original record.

A format profile records headers, column positions and parsing settings, not statement rows. Download it explicitly and reload it for a later export with identical ordered headers. A changed header layout requires a fresh review. The profile is a convenience, not evidence that a broker format is officially supported.

Finish with a review, not just a successful upload

Confirm the broker names, month, row count, currency and totals. In the desk, review unknown expected amounts and settlement gaps. The next-step link carries the selected month to a local review pack; that pack contains statement CSV, a checklist note and review questions. It excludes separate broker receipts and partner settlement journals.

The public review runs in the current tab and clears on refresh. Files are not uploaded by this flow. Export the review pack to keep a readable record of the review. Downloaded files remain under your control; store them securely. Signing in alone does not save or upload the review. Use anonymized samples until the service’s data-handling and recovery arrangements are confirmed.

  • Original report retained separately
  • No overlap between totals and underlying detail
  • Expected amount left unknown where unsupported
  • Stable broker/source IDs checked
  • Mapped totals compared with the source
  • Review pack saved before leaving the preview

Put the method to work.

Try the sample workspace. No broker password required.

Map a sample statement →

Editorial scope: product reporting guidance with fictional examples. No paid broker placement, investment recommendation or independent audit claim. Product capabilities are described as of the update date shown above.

Report a guide issue or suggest a correction →

Continue reading

IB month-end close checklist: statements, receipts and partner shares ↗

How to reconcile IB commissions across multiple brokers ↗

A multi-broker IB commission tracking template ↗

IB commission payment differences: partial payments, fees and carry-forward ↗