Payments & Processing

Payment provider and bank transaction fees.

2 min read

Payments & Processing captures the fees taken by your payment providers and bank — the percentage skimmed off each transaction.

Where it sits

Appears under Operating Expenses in the Foreqast table, as an expense. Ledger key: Bank Fees.

What lands here

Stripe / PayPal processing fees
Bank account and transfer fees
FX and payout fees

What to watch out for

Processing fees are not really a fixed cost — they are a percentage of revenue. Carrying a flat monthly rate forward means that in any month your revenue forecast rises, your fee forecast does not, and your margin comes out flattering. Where the blended rate is stable, drive this line from forecast revenue instead so the two move together.

Planning this line properly is what Monitoring margin is for.

How it's forecast

With the default setup — no extensions, no drivers, no custom projections — Payments & Processing is projected from your own booked actuals using the trailing 30-day average: the last 30 days are summed and divided by 30 to get a daily rate, which is carried forward flat and aggregated into each week and month.

daily rate = sum of the last 30 days of actuals ÷ 30
monthly forecast ≈ daily rate × days in month

For Payments & Processing, €1,200 booked over the last 30 days gives €1,200 ÷ 30 ≈ €40/day, so a 30-day month projects to about €1,200. As new actuals import, the window rolls forward and the projection updates on its own.

Horizon: up to 24 months of history and 24 months forward. The table shows 12 months (or 13 weeks / 90 days) by default — scroll horizontally for the rest.

Want a different shape — a fixed cost, a growth trend, or a share of revenue? That's what the Custom Projection extension and driver-based forecasting are for. This page describes the default, historical-only behaviour.