An OnlyFans revenue dashboard works when it holds a small number of reconciled measures, a visible date range, and a change log beside every chart. Keep earned transactions, deductions, and bank transfers in separate views so the same money is never counted twice. Mark unavailable data as missing rather than letting it display as a zero.
What sits underneath a dashboard that can be trusted?
A plain transaction table, built from source records, is the foundation every view and chart queries.
Useful fields include source record ID, transaction date, revenue category, gross amount, deduction, adjustment, and currency, plus an import date and source reference. Any recordkeeping system that clearly shows your income and expenses qualifies under IRS guidance (IRS: Recordkeeping). Do not put fan names or private conversations in a broadly shared management sheet when an internal identifier is enough, and preserve the raw records so totals can always be rebuilt.
| Field | Example entry | Why it exists |
|---|---|---|
| Source record ID | OF-2026-0417-088 | Traces the row to its platform origin |
| Transaction date | 2026-04-17 | Places revenue in the correct period |
| Revenue category | Subscription renewal | Separates subscriptions, tips, and priced messages |
| Gross amount and deduction | $15.00 / $3.00 | Shows both the fan price and the fee taken |
| Currency | USD | Keeps mixed-currency totals from blending |
Which views serve which decisions?
Three views cover the decisions a creator actually makes: earnings, cash, and operations.
The earnings view shows receipts and adjustments by period, the cash view matches transfers with deposits and outstanding balances, and the operating view connects acquisition, paid starts, retention, and workload. A bank deposit should never also appear as a new sale; it is a movement of money already recorded in the earnings history. When one view moves, the others explain whether the cause is sales, timing, or effort.
- Earnings view: what was earned, by category, by period.
- Cash view: what actually arrived, what is pending, and what is stuck.
- Operating view: what it cost in hours to produce the revenue.
- One rule across all three: a transfer moves money, it never creates it.
How do gross and post-fee figures stay straight?
Every revenue figure carries an explicit label, and the fee is applied by one documented rule.
Show gross and post-fee values side by side rather than blending them, because the platform fee is calculated as 20% of the total fan payment and deducted from each payment (OnlyFans Terms of Use). Keep currencies separate unless an exchange-rate method is recorded, and flag incomplete imports rather than displaying an unexplained drop to zero. A chart that silently mixes bases will agree with itself and disagree with the bank.
- Step 1
Record gross first
The fan-facing price, straight from the source record.
- Step 2
Apply the fee once
One documented rule produces the post-fee column; no per-row guesswork.
- Step 3
Label every chart
Gross or post-fee stated in the title, not left to memory.
- Step 4
Quarantine currency
Mixed currencies sum only through a recorded conversion method.
What belongs in the change log beside the charts?
Any event that could move a number: offers, staffing changes, outages, and new acquisition campaigns, each with its date.
Reconcile the monthly total to the authoritative account records before explaining trends — reconcile first, explain second. If a discrepancy appears, isolate its source and affected period before writing a story over it. A polished graph should never conceal missing transactions or an untested formula.
| Log entry | Example | Question it answers later |
|---|---|---|
| Offer launch | Custom-video bundle, Apr 12 | Why priced-message revenue moved |
| Staffing change | Chatter shift added, May 1 | Why response speed and renewals moved |
| Outage or delay | Upload failed, May 19 | Why that week shows a gap |
| Campaign start | Labeled push, Jun 2 | Why acquisition traffic jumped |
How do you test a dashboard before trusting it?
Rebuild one closed period from raw records and compare it to what the dashboard displays.
If the totals match, the pipeline is trustworthy; if they differ, every conclusion drawn so far is provisional. Check that a single bank deposit appears exactly once across views, and that an unexplained zero traces to missing data rather than a broken formula. The weekly habits that keep these numbers current are laid out in the weekly metrics review, and tax-time record duties sit in tracking income and expenses.
- Step 1
Pick one closed month
A period with no pending transfers or open refunds.
- Step 2
Sum the raw records
Outside the dashboard, directly from the source export.
- Step 3
Compare, don't average
The gap must reach zero or be explained line by line.
- Step 4
Date the verification
Note when the check ran, so trust has a timestamp.
Frequently asked questions
What should a revenue dashboard include?
A transaction table built from source records, three views — earnings, cash, and operations — and a change log beside the charts. Keep gross and post-fee figures labeled separately, and mark missing imports as missing. Anything the dashboard cannot trace to a source record is decoration.
How is a dashboard different from the platform's own earnings page?
The platform page reports the platform's view; your dashboard adds categories, fees, your own hours, and reconciliation against the bank. The two should agree on gross receipts for the same period. When they do not, the dashboard has an import or formula problem to fix first.
Should the dashboard show gross or net revenue?
Both, in separate labeled columns. Gross shows what fans paid, which matters for pricing and offer decisions; post-fee shows what reaches you, which matters for budgets. The platform fee is 20% of each fan payment under the current terms, so the gap is predictable rather than mysterious.
How do I keep a dashboard safe to share with a team?
Use internal identifiers instead of fan names, keep message content in the platform tools, and limit access by role. Raw exports live somewhere stricter than the summary sheet. Anyone whose role ends loses access the same day.
Why does my dashboard disagree with my bank deposit?
Timing and scope, usually. Payouts process on their own schedule, fees and refunds sit between earnings and cash, and a dashboard that counts a deposit as income counts the same money twice. Separate the earnings view from the cash view and reconcile each to its own source.
How often should a dashboard be reconciled?
Once a month against the authoritative records, plus a spot check whenever an import fails. Reconciliation comes before trend explanations — a number that has never been verified explains nothing. Date each verification so trust has a record.
Build your next step
Continue with a related guide
Sources and further reading
- IRS: Recordkeeping— A recordkeeping system suited to the business that clearly shows income and expenses, and records that substantiate return entries.
- OnlyFans Terms of Use— The 20% fee calculated on the total fan payment and deducted from each payment.
How this guide is produced: Editorial policy · Methodology · Authors · About · Disclaimer
Need support with your next step?
Choose promotion channels deliberately, respect their rules, and measure which traffic becomes subscribers — then read the numbers to find the bottleneck before adding spend or workload.