Built for teams reporting real revenue

The net sales formula is simple on paper and ugly in a spreadsheet. Automate it where the deal already lives.

Gross sales minus returns minus allowances minus discounts equals net sales. The formula is textbook; the pain is that most CRMs hold gross and leave the deductions to a monthly Excel wrestling match. Strkr tracks the four components per deal, rolls them up per period and per segment, and reports net sales inside the CRM without a reconciliation step.

What this audience is actually dealing with

The pains that bring buyers here.

Teams reach the net sales formula question in one of three ways. A finance partner asks for the net number for a board slide and the sales team realizes the CRM only reports gross. An auditor asks for the audit trail on how a specific discount got applied and nobody can find it. The CFO notices the churn-adjusted ARR number does not reconcile to the billing system and the team spends four days finding the gap. In each case the fix is the same: track the four components of the net sales formula on the deal itself, enforce approvals on each component, roll up to the period and segment with the audit trail intact. The pain the team is feeling is not a formula problem; it is a data-model problem that forces every finance review into a spreadsheet.

Gross-only CRM

The pipeline value is the ticker price, not the paid price.

Most CRMs track the deal value and call it done. Returns, allowances, and discounts live in the billing system or a Google sheet. Reporting net sales means exporting both sides and reconciling in Excel every month. Strkr tracks the four components (gross, returns, allowances, discounts) on the opportunity so net sales reports natively without export math.

Discount approval drift

Nobody can tell who approved the 22 percent off.

A deal closes at 22 percent off list and the CFO asks who approved it. The CRM shows the discount field but not the approver, the reason, or the policy band it fell outside of. Strkr enforces an approval flow on discounts past configurable thresholds (10, 15, 25 percent) with the approver, reason, and policy band logged on the record for the audit trail.

Return and refund blindness

The sales team keeps credit for a deal that got refunded.

A deal closed in January refunds in March. The sales dashboard still shows the January win. The forecast dashboard still shows the January pacing. The rep still shows the quota attainment credit. Strkr handles returns as a structured event on the opportunity with a date, reason, amount, and the net sales report corrects history without rewriting the January win date.

Allowance mystery line

What even counts as an allowance in your model.

Allowances (price concessions, warranty credits, promo credits) show up differently across industries and most sales teams have a loose definition. Strkr lets the admin define allowance types (promotional credit, warranty adjustment, goodwill credit, service-level credit) with per-type approval rules and GL mapping, so the net sales math stays consistent across the team.

Period-close chaos

Finance closes the month and sales did not know.

Finance closes the month on the fifth business day and sales submits a late discount adjustment on the seventh. The net sales number for the month ends up wrong on the board slide. Strkr respects a period-lock policy that freezes net sales inputs after the configured close date and routes late adjustments to a post-close variance log that finance reviews explicitly.

Segment reporting that stops at gross

Net sales by segment is a mystery for the first quarter after launch.

A VP of sales wants net sales by segment (SMB, mid-market, enterprise) to see where the margin story is. Most CRMs report gross by segment and the finance team has to layer the discount and return data from billing. Strkr runs net sales by any dimension (segment, region, product line, rep, team) with the four components rolling up on every slice.

The components the formula actually needs

What each piece of the net sales formula looks like in Strkr.

Net sales equals gross sales minus returns minus allowances minus discounts. The formula is 10 words. The work is in the structured fields, approvals, and GL mappings that make the four components reliable. The nine cards below are how each component is structured on a Strkr opportunity so the roll-up math is reproducible.

Gross sales

The list price value at close.

Gross sales on an opportunity is the list price value at close before any discount or adjustment. The field is required on close-won and locked once the deal moves past Negotiation unless an approver reopens it. The lock prevents the common "I will fix it later" drift that corrupts gross sales for retrospective reporting.

Returns

Structured events on the opportunity after close.

A return is a structured event with date, amount, reason, and reference to the billing credit if the billing system is integrated. Returns can be partial (percent of the original value) or full. The event triggers a net sales recomputation on the period and the segment without rewriting the original close date on the opportunity.

Allowances

Credits issued without a physical return.

Allowances are credits issued without a physical return: promotional credits, warranty adjustments, goodwill credits, service-level credits. The admin defines allowance types with per-type approval rules and GL mapping. The structural effect is that the net sales line can be sliced by allowance type to see which concessions are growing or shrinking over the year.

Discounts at close

Approval-enforced discount with policy bands.

Discounts applied at close are entered as either an absolute amount or a percent. The approval flow enforces configurable thresholds (10, 15, 25 percent) requiring the appropriate approver, a reason, and the policy band tag. The record carries the approver, timestamp, and reason for the audit trail.

Early-pay discounts

Credits applied post-close on invoice timing.

Early-pay discounts (common in B2B with 2 percent net 10 terms) apply post-close based on invoice payment timing. The discount lands as a structured event on the opportunity with a reference to the invoice from the billing system. Net sales recomputes to subtract the early-pay discount from gross without rewriting the close date.

Price concessions

Mid-contract reductions tracked explicitly.

Price concessions (a mid-contract rate drop in exchange for a renewal commitment) are a specific allowance type with its own approval ladder. The concession value flows into the net sales math for the appropriate period, and the opportunity record carries the original pricing and the concession reason for exec review.

Credit memos

Billing-system credits that flow back to the deal.

Credit memos issued in the billing system (Stripe, QuickBooks, NetSuite, Zoho Books) flow back to the originating opportunity via the integration and land as a credit event. The admin configures the mapping once and the ongoing math runs without a manual reconciliation step.

Period boundaries

When does a return in May affect January net sales.

Strkr supports two policies for period attribution: original-period attribution (the return subtracts from the January net sales) or current-period attribution (the return subtracts from May net sales). The admin configures which policy applies per return type. The dual support covers both GAAP-oriented and management-reporting-oriented preferences.

Multi-currency math

FX rate at close versus FX rate at return.

For teams running international deals, Strkr captures the FX rate at close on gross and at the time of each adjustment on returns and allowances. The net sales report in USD rolls up with the right rate per event, so the FX exposure line is clean and the finance partner does not have to layer currency math by hand.

The reports every finance partner asks for

Net sales reports that answer the Monday CFO question.

The reports below are the ones finance partners we worked with asked for repeatedly over the last two years. Each one answers a specific board-slide or exec-review question. They ship in the Strkr template so a new finance partner lands on a clean baseline.

Net sales trend

Monthly gross versus net over 24 months.

The gross and net sales lines plotted monthly over 24 months with the gap (discount, returns, allowances combined) shaded. The report answers the question "are our concessions growing faster than our top line." A healthy trend holds the gap percentage flat even as volume climbs. A worrying trend shows the gap widening quarter over quarter.

Discount band distribution

How many deals closed in each discount band.

Deals closed in each discount band (0 to 5 percent, 5 to 10 percent, 10 to 15 percent, 15 to 25 percent, over 25 percent) counted and summed per period. The report surfaces the band distribution shift that often signals discounting creep: more deals landing in the 10 to 15 band this quarter than last suggests the floor is moving.

Return rate by product line

Which product has the return problem.

Return rate (returns divided by gross sales) by product line, by segment, by rep. The report surfaces the specific product line that is driving most of the return volume, which is usually one or two SKUs in a long tail. Product teams and sales ops read this report monthly to catch the problem before it compounds.

Allowance type ranking

Which concession type is growing fastest.

Allowances by type (promotional, warranty, goodwill, service-level) ranked by period-over-period growth. The report answers "where is the margin leak going." A growing goodwill-credit line usually signals a service-quality problem feeding into retention; a growing promotional-credit line usually signals a discount-driven motion that needs attention.

Rep-level net attainment

Quota attainment on net sales, not gross.

Quota attainment per rep calculated on net sales rather than gross. The report surfaces the reps who hit gross quota through heavy discounting and shows a different ranking than the gross-attainment view. Compensation plans that tie commission to net sales (increasingly common for CFO-aligned sales ops) run off this report natively.

Segment margin snapshot

Net sales by segment for the exec deck.

Net sales by segment (SMB, mid-market, enterprise) with gross-to-net percentage. The report answers the exec question "where is our margin story strongest." The output pastes into a board deck without a reformat step. The segments are configurable so a team running by vertical rather than size can slice the same math.

Post-close variance log

What changed after the period closed.

Every adjustment made after the configured period close shows in the variance log with the opportunity, type, amount, approver, and reason. Finance reviews the variance log on the monthly close call. The log is append-only so no adjustment slips through unexamined.

Approval policy compliance

Which deals closed with the right approval chain.

For discounts past the configurable thresholds, the report shows which deals carried the complete approval chain and which carried an exception. Teams targeting SOC 2 or ISO 27001 audits run this report quarterly to surface policy misses before the auditor does.

Where the math breaks and how Strkr guards it

The structural pieces behind the net sales reports.

The reports above are the surface. The structural pieces below are what makes the reports reliable at close time two years into a Strkr deployment. Each is a specific guardrail against the common failure mode we see on competitor stacks.

Immutable gross value

Gross locks when the deal closes.

Once an opportunity closes, the gross value is locked. Changes require an approver and log as a structured amendment event with reason. The lock prevents the common pattern where a rep edits gross after the fact to improve attainment math; the amendment event is the auditable path.

Event-sourced adjustments

Returns, allowances, discounts as append-only events.

Every adjustment is an append-only event with timestamp, actor, amount, reason, and reference. The net sales value on the opportunity is computed from the event stream, not stored as a mutable number. Retrospective reporting is reproducible because the event history is intact.

Approval policy per threshold

Discount above 15 percent needs a VP approver.

The admin configures approval thresholds (10, 15, 25 percent) with required approver role per threshold. The flow routes the approval request, logs the response, and gates the discount application until approval lands. The approval policy ships in the stage definition so late-stage discount-chasing hits the gate reliably.

Billing-system integration

Stripe, QuickBooks, NetSuite, Zoho Books wired.

The billing-system integration flows refund events, credit memos, and payment timing back to the originating opportunity. The admin configures the mapping once and the ongoing math runs automatically. The integration is bidirectional for the systems that support it, so a credit issued in billing lands as an event in Strkr within minutes.

Period-lock enforcement

Post-close adjustments route to the variance log.

When the configured period close date passes, further adjustments to deals in that period route to a variance log instead of silently updating the historical number. Finance explicitly reviews the variance log on the following close call. The policy keeps board-reported numbers stable without blocking legitimate post-close corrections.

GL mapping

Every component maps to a GL account.

Gross sales, each return type, each allowance type, each discount type carries a GL account mapping. The export to the general ledger (Netsuite, QuickBooks, Sage Intacct) runs with the right account codes so finance does not re-code every month. The mapping is configurable per segment and per product line for multi-entity teams.

Head-to-head

Strkr net sales reporting vs Freshworks CRM.

Freshworks CRM is the honest head-to-head because the product aims at the same mid-market revenue reporting audience and the comparison surfaces where structural data-model decisions diverge. Salesforce Revenue Cloud, Zoho CRM Plus, and HubSpot Sales Hub are the other common comparisons.

Feature Strkr Freshworks CRM
Gross versus net tracking Four components tracked on every opportunity natively Gross tracked; net typically requires custom fields plus export
Discount approval flow Threshold-based approval with approver, reason, policy band logged Workflow-based approvals, policy-band logging limited
Return and refund events Append-only structured events on the opportunity Typically requires integration with billing or custom module
Allowance taxonomy Admin-defined allowance types with per-type GL mapping Not a native concept; often custom-fielded
Period-lock policy Lock date with variance log for post-close adjustments Reporting snapshots; post-close edits mutate history
Billing system integration Native connectors to Stripe, QuickBooks, NetSuite, Zoho Books App marketplace integrations, mapping configuration varies
Audit trail depth Event-sourced; every adjustment reconstructable Audit log on records, event-sourced math typically absent
Rep attainment on net Native net-attainment report with gross-to-net comparison Attainment on gross by default, custom report for net
FX handling FX captured at close and at each adjustment event FX supported, event-level precision varies
Pricing posture Flat per seat, net sales reporting on every paid tier Advanced reporting on higher tiers, revenue tracking addon
How teams use Strkr

Net sales motions running on Strkr right now.

The playbooks below are from actual deployments where the finance partner, sales operations, and sales management agreed on the net sales math as a required artifact for their monthly close. The specifics are blurred where the customer requested but the shape and the metrics are real.

B2B SaaS, 48 seats

The monthly close went from four days to half a day.

A 48-seat B2B SaaS team ran a four-day monthly close process because the finance partner was reconciling discounts, refunds, and allowances from the CRM, the billing system, and three Google sheets. The team moved to Strkr with the full net-sales model enforced on every opportunity. Discount approvals routed through the stage flow, returns landed as structured events from the billing integration, allowances were defined with four types and GL mappings. The next monthly close ran in half a day. The finance partner said the shift was that the net number was already correct in the CRM on close day; the close process became a review-and-sign step instead of a reconciliation project.

Mid-market services, 32 seats

Discount creep caught before it hit the quarterly number.

A 32-seat services firm noticed its gross-to-net gap had been widening for three quarters and could not explain why. The team installed the discount band distribution report in Strkr and ran a six-quarter backfill. The report surfaced that the 15 to 25 percent band had grown from 8 percent of deals to 22 percent of deals over 18 months. The sales leader instituted a VP approval on anything past 15 percent and tightened the policy band. Within one quarter the 15 to 25 band dropped back to 11 percent and the gross-to-net gap closed by 2.5 points. The CFO said the single highest-leverage change was moving the approval policy out of a wiki page and into an enforced flow.

FinServ, 24 wealth advisors

Allowance types gave compliance the audit trail they needed.

A 24-advisor wealth firm had a compliance audit coming and needed an audit trail on fee waivers, goodwill credits, and service-level adjustments. The team defined four allowance types in Strkr with per-type approvers and GL mapping. Every fee waiver landed as a structured event with the approver, reason, policy band, and GL code. The audit ran clean because the trail was already in the system; the compliance officer did not spend 60 hours assembling it after the fact. The firm kept the allowance taxonomy as a permanent part of the operating model.

Multi-currency SMB, 16 seats

FX exposure line reconciled to the billing system first month.

A 16-seat SMB running deals across USD, EUR, and GBP had been reporting net sales in USD with month-end FX rates applied uniformly, which was costing them accuracy on international refunds that happened months after close. The team moved to Strkr with event-level FX capture: the gross FX rate at close, the return or allowance FX rate at the adjustment event. The first month after launch the FX exposure line reconciled to the billing system within half a percent. The finance partner stopped running a separate FX reconciliation and used the Strkr report directly for the board slide.

Enterprise, 95 seats

Net attainment surfaced a different top-rep ranking.

A 95-seat enterprise team moved commission plans from gross attainment to net attainment on the sales operation leaders recommendation. The first quarter after the change the top-three rep ranking shifted: the number-one rep on gross had been number four on net because the gross number was carrying 18 percent of discount creep. Compensation stayed within the plan envelope but the message to the sales floor changed: the reps who held price got recognized. Over the next two quarters the discount band distribution tightened without a new policy because the compensation signal did the work. The CRO called the change the single highest-leverage sales operations shift of the year.

Automate the net sales formula where the deal lives.

Start a 14-day trial with the net sales model enabled on every opportunity. Returns, allowances, discounts tracked as structured events; discount approval flow enforced at close; billing integration wired for Stripe, QuickBooks, NetSuite, or Zoho Books. Close the next month in half a day instead of four.

Common questions

What buyers in this bucket ask most.

What is the net sales formula and how does it differ from gross sales?

Net sales equals gross sales minus returns minus allowances minus discounts. Gross sales is the list-price value of the deals closed in the period. Returns are items sent back or credits issued for a product return. Allowances are credits issued without a physical return (goodwill, warranty, service-level credits, promotional credits). Discounts are reductions applied at close. The net sales line is the one that matches what the customer actually paid, which is the line the CFO and board care about most. The gross line often overstates the top line by 10 to 20 percent depending on the discount posture of the business.

Why does the net sales formula need a CRM feature instead of a spreadsheet?

The formula itself is simple. The work is in making the four components reliable across hundreds or thousands of deals a quarter. Returns and allowances happen weeks or months after close. Discounts need approval policies enforced at the point of sale, not after. Period-lock enforcement needs to be structural, not based on remembering to stop editing. A spreadsheet can hold the math; the spreadsheet cannot enforce the policy. The CRM feature is the enforcement layer that makes the spreadsheet math match reality.

How does Strkr handle a return that happens in March on a deal that closed in January?

The return lands as a structured event on the original opportunity with the March date and the return amount. The admin can configure one of two period-attribution policies: original-period attribution (the net sales for January is adjusted down) or current-period attribution (the net sales for March carries the negative adjustment). Original-period attribution is more common for GAAP-aligned finance teams. Current-period attribution is more common for management-reporting teams that want the current month to reflect current cash. Either way the audit trail shows the return as a March event tied to a January opportunity.

Can Strkr enforce a discount approval policy without blocking the sales motion?

Yes. The approval policy is configurable per threshold (common pattern: discounts up to 10 percent auto-approve, 10 to 15 percent require manager, 15 to 25 percent require VP, over 25 percent require CRO). The approval flow runs inside the deal with the approver notified immediately, so the typical turnaround is minutes, not days. The policy gates the stage transition that applies the discount, not the whole deal, so the AE can keep the opportunity moving while the approval resolves. Teams that install the policy report both compliance and discount-creep improvement.

Does Strkr integrate with the billing system so refunds flow automatically?

Yes. Strkr ships native integrations with Stripe, QuickBooks, NetSuite, and Zoho Books. A refund or credit memo issued in the billing system lands as a structured event on the originating opportunity within minutes. The admin configures the mapping once (which billing event types correspond to which net sales adjustment types) and the ongoing math runs automatically. Teams running a billing system Strkr does not have a native connector for can wire the integration through the flow builder with a webhook, which covers roughly 95 percent of billing systems in use at mid-market.

How does Strkr handle multi-currency net sales for international teams?

Every gross value and every adjustment event captures the FX rate at the time of the event. The net sales report in the reporting currency rolls up with the right rate per event, so a return in March on a January deal uses the January FX rate for the gross and the March FX rate for the return, which is the correct accounting treatment. The event-level FX precision avoids the common error of applying a month-end rate uniformly across historical adjustments. For teams that report in a single reporting currency with multiple transaction currencies, the FX exposure line reconciles cleanly to the billing system.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.