bug: fees and taxes not returned in transactions details

[bolirev]

Describe the bug

The CLI’s sc broker transaction details output shows all fee- and tax-related fields as for BUY transactions, while the Scalable app shows the same order with fees and a total that matches quantity × price + fee. Please clarify whether the CLI should expose those amounts or if is expected.

Steps to reproduce

Log in: sc login
List BUY transaction IDs:

sc broker transactions --type-filter BUY | jq -r '.. | objects | .items[]? | .id'

Fetch details for one ID:

sc broker transaction details --transaction-id <id>

Expected behavior

In the Scalable Capital app, the same order shows a breakdown where total amount matches quantity × transaction price + fee (i.e. fees are visible in the app, not reflected in the CLI output above).

fees therefore should not be from CLI

Actual behavior

Fee- and tax-related fields are all empty (<none>):

fee, transactional_fee, taxes, trade_tax_amount, capital_gains_tax, church_tax, solidarity_tax, source_tax, financial_transaction_tax: <none>
linked_transaction_ids: <none>
documents: 2 (present)

CLI version

0.2.0

Install method

Release artifact

OS and version

Ubuntu 26.04

Architecture

x86_64

Shell

bash

Command

sc broker transaction

Output mode

Human

Logged in before running the command

Yes

Broker context selected

Yes

Additional context

No response

Checklist

• I have searched existing issues.
• I am using the latest available version of the CLI.
• This is about the Scalable CLI, not an account, trading, payment, or broker support request.
• I have removed tokens, IDs, and personal financial data.

[fbenz]

The human-readable output is currently missing several fields that are available in the JSON output, including:

• security_trade.trade_transaction_amounts.transaction_fee
• security_trade.trade_transaction_amounts.venue_fee
• security_trade.trade_transaction_amounts.crypto_spread_fee
• security_trade.aggregated_transaction_taxes.total_tax

You could check whether the data you are looking for is present in the JSON output for the same transaction by running:

sc broker transaction details --transaction-id <id> --json

We are planning to add these missing fields to the human-readable output as well.