Ploutos Help

Fee Settings and Market Overrides

Set fees once at the account level so the journal stays believable without a wall of overrides.

Set this once at the account level and the rest of the journal gets easier to trust.

These settings live under Manage accounts -> Estimated fees. They belong to the Ploutos account, not to one specific trade.

Default risk is also account-level, but it is separate from fees. Use Manage accounts -> Default risk when you want manual trade entry and review metrics to use a fixed dollar risk budget per trade. Saving the default risk lets new manual, imported, and synced grouped trades derive an initial stop when entry, size, and market value are available. If you choose Apply once to existing trades, Ploutos also overwrites the initial stop for existing reviewable trades when the needed trade data is available. For grouped trades, Ploutos uses the average entry fill, not the closing fill.

Why this page matters

If imported or synced trades come in without a real broker fee, Ploutos needs a sane estimate.

That matters because:

  • net results should feel believable
  • one market may not cost the same as another
  • the right fee model depends on what you trade

The two fee modes

Per contract ($)

This is the default and the right choice for most futures-first workflows.

Use it when the fee is basically a fixed amount per contract, per side.

Simple example:

  • one MNQ buy or sell costs about $1.29
  • you enter 1.29

Percent of notional (%)

Use this when the fee scales with notional instead of behaving like a normal futures commission.

Ploutos estimates each side as:

  • quantity x price x rate

That usually makes more sense for stocks, ETFs, or other notional-based products than for a standard futures workflow.

When to use market overrides

Overrides are for the few cases where one market is meaningfully different from the default.

Good example:

  • your base setting matches MNQ
  • NQ costs more
  • you add a single override for NQ

Weak example:

  • no real default
  • ten overrides because the base setting was never chosen clearly

If most markets need their own number, stop and rethink the default before filling the whole list with exceptions.

What these settings do not do

They are not a magic rewrite button for every historical trade edge case.

The point is to keep the account on one consistent fee model so new imports and syncs do not keep changing the meaning of net P&L.

Common mistakes

  • editing fee settings in the wrong Ploutos account
  • choosing percent mode for a workflow that is really fixed-fee futures trading
  • adding many overrides before picking a sensible default
  • thinking the setting is trade-specific when it is really account-level

Next pages