Reconciled p.12
FY26 territory revenue base: EMEA
+18.4% vs. prior period
Use case
Territory & quota planning
Assign territories and set quotas against the same reconciled revenue base finance’s own forecast already runs on, so a quota change and a forecast change are never two different numbers.
Every territory and quota line reconciles back to
- Booked revenue
- Pipeline stage
- Rep roster & ramp
- Comp plan rules
- Prior-year actuals
The old way
What’s holding territory & quota planning back?
Territory and quota season shouldn’t run on last year’s spreadsheet.
01
Territory boundaries live in one spreadsheet and the quota model lives in another, so nobody can say for sure the two still agree.
02
A quota shift means re-typing dependent comp and revenue-forecast lines by hand, one region at a time.
03
Coverage gets set against last year’s export, because pulling this year’s reconciled revenue means starting another one.
04
When finance and sales compare quota attainment, they’re each reading a different definition of "revenue."
One model, not two
Territory, quota, and the forecast stay on the same base case.
A guided walkthrough of live territory and quota assignments: every figure on screen still carries its citation back to the reconciled revenue behind it.
Why finance and sales agree on the number
Set territories and quotas both teams stand behind
One base case, two teams
Territory and quota assignments sit on the same reconciled revenue base finance’s own forecast already runs on, so the two never quietly drift apart.
Coverage snapshot · FY26
Tied out
82% AMER
64% EMEA
45% APAC
Region
Reps
Quota
Gap
AMER
24
$18.6M
− 4%
EMEA
16
$11.2M
+ 2%
APAC
9
$6.4M
− 1%
Boundary recompute
Reassigned in real time, no rebuild
A quota shift, not a rebuild
Change a quota or a boundary assumption in plain language and the dependent comp and revenue-forecast lines recompute deterministically, not by hand.
Every assignment traces back
A territory or quota figure opens onto the reconciled revenue and pipeline it was built from, never a static export nobody can re-derive.
Lineage trace
- 1 Territory assignment · EMEA
- 2 Reconciled revenue · p.12
- 3 Cited export · FY26 comp
Every assignment opens onto the reconciled figure and citation behind it, never a static export nobody can re-derive.
Key features
Built for territory & quota planning that finance already trusts
Coverage mapped to revenue, not guesswork
Lay territories over the same reconciled revenue and pipeline figures finance’s own forecast already uses, instead of a flat file from last quarter.
Nodes sized by reconciled revenue
Aligned across sales and finance
Rep, quota, and territory owners work from the same governed definitions as finance: a quota number means the same thing in the comp system and the forecast.
Compensation stays scoped
Role-based access keeps quota and comp figures visible only to the people who should see them.
Quota and pipeline, one line
Update a region’s pipeline and its quota gap recomputes in place, no separate reconciliation pass afterward.
AMER
EMEA
APAC
Prescriptive rebalancing: Coming soon
Not a rating. A chain.
Every figure in this plan can show its own proof.
- 1 Filed
- 2 Extracted
- 3 Reconciled
- 4 Cited
- 5 Exported
Reconciled p.9
Quota scenario: Enterprise segment shift
−4.7% vs. prior period
Reconciled p.15
Comp payout recompute: Q2 quota change
+2.3% vs. prior period
Keep exploring
Discover more use cases
Sales capacity planning
Reps, ramp, and territory load connect to the same financial model, so a capacity change flows into cost and revenue together.
See it in actionSales forecasting
Bookings and revenue forecasts run against actuals already reconciled to the ledger, never a side spreadsheet.
See it in actionAccount scoring & segmentation
Segment definitions are set once in the definitions library and reused consistently across finance and go-to-market reporting.
See it in actionFrequently asked
Questions about territory and quota planning.
What makes a territory or quota number "reconciled," rather than just entered?
Every quota and territory figure sits on revenue and pipeline actuals that have already been checked against their source: the plan compares to a tied-out number, not a re-keyed one.
Does changing a quota rebuild the whole plan?
No. Change a quota or boundary assumption in plain language and the deterministic engine recomputes the dependent comp and revenue-forecast lines; the model’s structure doesn’t move underneath you.
Can sales and finance end up using different definitions of revenue for their own quota math?
No, both sit on the same governed definitions layer, so "revenue" means the same thing whether finance or sales is looking at it.
Does Rexfin recommend how to draw territories for us?
Not yet. Today, territory and quota planning connects assignments to the same reconciled revenue base finance already trusts; prescriptive territory optimization is on the roadmap, not a shipped feature.
How does a quota change affect compensation?
Comp payout lines recompute deterministically off the same reconciled revenue and bookings data, with full lineage on the calculation for audit or dispute resolution.
Can I see where a quota-gap figure came from?
Yes, every figure opens onto the reconciled revenue and pipeline data behind it, plus the extraction and check that confirmed it, the same lineage every other modeled number carries.
Do we need a live CRM connection before we can start?
No, Excel, CSV, or PDF upload works standalone, so territory and quota modeling can start before a live connection exists.
Get started
Plan quotas your finance team already believes.
Book a walkthrough and we’ll map a quota scenario against a sample of your own reconciled revenue: cited, traceable, and ready to recompute on the spot.