TrueNet
A processor-native revenue-cost evidence layer for SaaS operators that backfills official balance activity, reconciles webhooks to charges, fees, refunds, disputes, recoveries, currency conversions, and payouts, maps events to versioned subscription types, and delivers a daily cited artifact while preserving commercial entitlement, invoice, charge, processor balance, bank settlement, accounting recognition, tax, profit, attribution, and correction as separate states.
Founders see recurring revenue metrics and processor balances but still struggle to explain why two subscription types with similar billed value produce different cash after processing costs, refunds, disputes, recoveries, currencies, and failed-payment behavior. TrueNet builds a reconciled waterfall from official account activity. It does not treat a webhook as a complete ledger, a charge as earned or recognized revenue, a processor payout as bank reconciliation, a retry as a directly attributable cost without evidence, an open dispute as final loss, or net processor cash as gross margin or profit. Contract, invoice, payment attempt, charge, fee, refund, dispute, recovery, balance transaction, payout, bank receipt, accounting entry, close, tax treatment, metric interpretation, business decision, and correction remain distinct.
A founder, finance, billing, RevOps, growth, or data owner at a SaaS company using one primary payment processor and lacking a reconciled explanation of processor costs by commercial subscription type.
SaaS founders and finance, billing, growth, or data owners have an identifiable question and existing analytics spend.
Backfill, mappings, normalization, reconciliation, metric contracts, and artifacts can scale through software.
One cross-reference, three inbound connections, and two direct connections provide moderate graph support despite zero related signals in the source summary.
One cross-reference, three inbound and two direct connections, verified subscription-analytics incumbents, a confirmed processor query surface, a concrete founder and finance pain, and no supplied per-subscription-type net normalization support the direction.
The source reports zero related signals, no structural copying cost, incumbents and the processor can add the view, plan mapping and backfill are messy, accounting labels are easy to overclaim, multi-currency and disputes complicate periods, and daily-artifact reliance is not a proven moat.
Discussion
No comments yet — be the first to weigh in.