A multi-broker IB commission tracking template

The eight fields in the starter template

The IBDock sample template uses id, broker, period, currency, expected, reported, received and fees. Each row represents a statement snapshot you define, not an individual trade imported automatically from a trading server. Keep that unit consistent across your sample.

Use id for a stable identifier from your source or your own documented import process. Broker identifies the relationship for this preview. Period uses YYYY-MM, such as 2026-09. Currency must be USD in the current preview. Expected is optional; reported, received and fees are required nonnegative amounts.

Enter money without ambiguous formatting

Use 1250.50 rather than a currency symbol or a thousands separator. Amounts can have at most two decimal places. Blank expected amounts remain unknown. Do not enter zero merely to make a missing value pass validation: an unknown expected value and a genuine zero entitlement lead to different conclusions.

Define what fees mean in your source. In this template, the open settlement calculation subtracts received payments and fees from reported commission. If your report already shows net commission after fees, do not subtract the same fee again. Split unlike reporting conventions before importing.

Review before adding records

Choose CSV for a simple text export, XLSX for a single-sheet workbook, or JSON for a structured snapshot. The same validation rules apply to all three. Use literal cell values in Excel rather than formulas: a workbook can contain stale cached formula results that do not match a fresh recalculation.

The preview accepts files up to 1 MB and up to 5,000 records per workspace. Download a template, replace the fictional rows with anonymized examples, check the preview total and only then confirm. A file with an invalid record is rejected; it is not partially applied.

Use one currency and one consistent row definition
Keep original reports separately
Check blank versus zero expected amounts
Compare the preview total with your source
Confirm only after checking the broker and period

What happens when you import the same statement twice?

The preview matches a row using its broker label and source ID. An identical row is skipped, including when you switch from CSV to JSON. If the same identity arrives with changed financial values, the import stops so you can review the correction. Changing the filename does not create a new financial record.

This is a trial identity scheme. Production integrations need durable broker, entity, partner-account and connection identifiers. Two partner accounts at the same broker must never be merged just because their display names look the same.

Know when a template is no longer enough

A template helps you test a common reporting model. It does not independently verify trading volume, determine contractual eligibility or execute a payout. Negative corrections, multiple settlement currencies and trade-level rates require a richer journal and explicit agreement rules.

The public workspace keeps sample imports in browser memory only. A reload clears them. Export your reviewed view if you want to retain the sample, and keep confidential statements out of the public trial. Use the connection checklist to evaluate what a future live integration would need.

Put the method to work.

Try the sample workspace. No broker password required.

Open the statement templates ↗

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.