What is the simplest useful definition of gross sales?
Gross sales is the total revenue from all sales transactions in a period, before deductions for returns, allowances, discounts, and taxes. It is the top-line number on the income statement, before the deductions walk you down to net sales. In a CRM reporting context, gross sales is the sum of order values before adjustments. The complexity in real-world reporting comes from which deductions actually belong in the gross-to-net walk (returns, allowances, discounts, early-payment discounts, taxes, freight), which can vary by industry and by GAAP interpretation.
How does gross sales differ from net sales, bookings, and recognized revenue?
Four distinct concepts. Gross sales is top-line revenue before deductions. Net sales is gross minus returns, allowances, and discounts. Bookings is the signed contract value in the period, independent of recognition timing. Recognized revenue is the portion of bookings earned in the period per GAAP (ratable for subscriptions, delivered for physical products, milestone-based for services). A 3-year prepaid contract signed in Q1 is $1,200,000 in bookings but only $300,000 in recognized revenue for the full year. The sales team usually reports bookings for pipeline attribution and comp; the finance team usually reports recognized revenue for the income statement. Both are correct for their purposes, which is why the exec team needs a unified report that shows both.
Why do finance and sales always argue about the gross sales number?
The arguments come from four typical sources. First, discounts: sales reports list price, finance reports net price. Second, timing: sales reports at signature, finance reports at service start or at ratable recognition. Third, returns and allowances: sales reports the original number, finance adjusts retroactively. Fourth, deductions interpretation: freight, taxes, early-payment discounts have different treatments. Each argument has a defensible answer on both sides. The resolution is to run both views on the same artifact so the exec team sees the walk from sales' number to finance's number rather than fighting about which one is "right." Strkr's shipped reports do exactly that.
How does Strkr handle multi-year contracts for gross sales reporting?
Strkr runs a parent-child contract shape where the parent order carries the TCV (total contract value, full commit across the term) and child records carry the recognition schedule per period. For a 3-year contract at $100,000 per year, the parent shows TCV of $300,000 and ACV of $100,000, with 36 monthly recognition events scheduled. Bookings reports the full TCV in the signing period for sales attribution and comp. Recognized revenue reports the monthly portion for the income statement. Mid-term amendments (seat adds, product adds) attach to the parent as structured amendment records with their own recognition schedules. The reporting layer renders both views without the finance team reconciling across spreadsheets.
How does Strkr's discount depth report work?
Every deal in Strkr carries a discount percent (actual price divided by list price) and a reason code (volume, strategic, competitive, promotional, other). The discount depth report shows the aggregate discount percent per period, broken down by reason code, rep, product category, and customer segment. The sales lead sees patterns: reps who over-discount, product categories with margin erosion, segments driving the discount volume. The report feeds the quarterly pricing or comp plan conversation with specific data rather than general vibes. Teams that run this report consistently typically see gross-to-net ratio improvements of 5 to 12 percentage points over two to four quarters.
Can Strkr handle multi-currency gross sales reporting?
Yes. Each order carries the signing-date exchange rate for FX purposes along with the base currency and the booking currency. The quarterly reporting rolls up in a reporting currency (typically USD for US-headquartered firms) with the FX gain-loss recognized explicitly. The audit trail captures the FX conversion math per order so an external auditor can verify the gross-to-net walk across currencies. Teams running 2 to 7 currencies (USD, EUR, GBP, AUD, CAD, SGD, JPY, others on request) run this reporting on the Strkr standard tier without a custom build. The multi-entity shape (US entity signing US customers, EU entity signing EU customers) layers on top with structured entity assignment per order.