Applications · Dealer network
Your channel sells for you. Give it a system that says so.
Onboarding, agreements, deal registration, scheme claims and performance, for distributors, dealers, brokers, agents and resellers. Each partner works a branded portal scoped to their own hierarchy, and the settlement they are arguing about has a trail.
onboarding · agreements · KYCDeal registration & conflict rulesSchemes, claims & settlementScoped portal per partner
Territory → partner → claim → settlementChannel context and scheme evidence meet before a claim becomes payable.DL-096 · CL-742 · Reconciliation exception
MTGold dealer · ElectricalMeridian Trade LinksPune belt · West · Priya Nair · Channel operations₹4.86 Lclaimed
Claimed₹4.86 L→Evidenced₹4.31 L₹55,000 gap
14:08•••
Confirm the invoice/credit-note link and recapture three in-period display proofs with the partner.
Sell-in, DMS, invoices and geo-tagged display evidence attached.
Evidence-matched amount only
The partner relationship becomes operational when territory and money stay connected.
DL-096 is more than a portal identity. Its coverage, activation, scheme participation, evidence and settlement authority remain visible through the complete channel motion.
See coverage as an operating network
Hubs, clusters, partners, activation and claim exposure share one territory context.
West Channel Coverage · 42 districts · 68 active nodesKeep relationship and readiness together
Agreement, KYC, certification, scheme eligibility and ownership remain on DL-096.
DL-096 · Meridian Trade LinksReconcile before declaring payable
Sell-in, sell-out, invoices and display proof state exactly what CL-742 can support.
₹4.31 L evidenced · ₹55,000 gapSeparate validation from approval
Priya validates evidence. Sanjay decides the settlement path. Payment stays downstream.
Priya Nair → Sanjay RaoChannel management that survives an audit of its own incentives.
Most partner programmes run on a portal for documents, a spreadsheet for schemes, and email for disputes. These rows are where that costs money.
Partner onboarding
Portal + spreadsheets
→A form, a document upload, and a shared drive.
Evidence-led network
Application, KYC, document expiry, agreement e-sign and territory assignment on one track: a partner cannot transact before the gate clears.
Deal registration
Portal + spreadsheets
→A registration form, and a channel conflict argument.
Evidence-led network
Registration checks the live pipeline for conflict, locks protection for a defined window, and names the arbiter when two partners collide.
Schemes & incentives
Portal + spreadsheets
→A scheme circular in PDF, computed in a spreadsheet.
Evidence-led network
Scheme rules are a decision grid on the platform; entitlement is computed from actual sell-through, so the payout math is inspectable by both sides.
Claims & settlement
Portal + spreadsheets
→Claims by email, settled after three follow-ups.
Evidence-led network
Claims raised in the portal with evidence attached, auto-checked against scheme and sell-through, and routed to the authority matrix for release.
Enablement & certification
Portal + spreadsheets
→A content library, and no idea who read it.
Evidence-led network
Product content, pricing and certification tracked per user per partner, with expiry, and uncertified users lose the entitlement.
Performance visibility
Portal + spreadsheets
→A monthly deck, argued over on a call.
Evidence-led network
Every partner sees a live scorecard scoped to their own hierarchy: their numbers, never their neighbour's, from the same trail your channel head reads.
The same portal serves brokers in lending, dealers in manufacturing, franchisees in retail and agents in insurance. The hierarchy, the scheme grid and the claim workflow are meta; the shape of the channel is yours.
Pay what is evidenced. Keep every exception visible.
Territory, partner, scheme, sell-in, sell-out, invoice and display evidence reconcile on one claim before the channel team decides.
DL-096 and CL-742 remain one canonical partner-to-settlement thread.Recommendation heldReview recorded · unpaid
Declared and evidenced performance
ERP orders · 44 invoices · Primary ledger matched
Partner DMS · Q2 extract · 52 units not evidenced
INV-4881–4924 · 52 units await credit-note boundary
Geo-tagged photos · 30 Jun · 3 proofs expired before period end
What remains outside the payable evidence
DMS vs invoice evidence
Proof date outside Q2
Subject to both checkpoints
The complete claim decision trail
Portal claim linked to Q2-GROWTH-24
44 ERP invoices account for 1,260 units
52 declared units lack matching invoice evidence
15 current; 3 fall outside the scheme period
Evidence board · settlement boundary
A claim is not payable merely because it was submitted.
Filter the evidence match to isolate the 52-unit gap and three out-of-period display proofs without losing what already reconciles.
Source, period and finding remain attached to CL-742.Primary ledger matched
52 units not evidenced
52 units await credit-note boundary
3 proofs expired before period end
Channel operations → regional head
The payable amount and the authority to approve it are not the same thing.
Priya owns evidence reconciliation. Sanjay owns the regional decision. Payment remains downstream of both.
The prepared path can be revised without erasing the original claim.Field partner mobile · complete evidence task
Resolve the outlet evidence without shrinking the settlement context.
The channel owner can see the partner, exception, evidence, consequence, prepared path and named regional action together.
Record → gap → evidence → consequence → prepared settlement → named action.14:12•••
Pune belt · Outlet review today
Confirm the invoice/credit-note link and recapture three in-period display proofs with the partner.
Sell-in matched; invoice and display boundaries remain cited.
Partner evidence task and partial settlement remain linked.
Priya Nair→Sanjay Rao
Priya validates before Sanjay decides.Evidence review recorded. Claim remains unpaid.The channel operation, generated.
Multi-tier hierarchies (distributor, dealer, sub-dealer and individual agent) are modelled, not flattened. The operating surface joins each capability to the same partner and territory identity.
Partner lifecycle
Application, due diligence, credit checks, agreement versions, renewal dates and suspension, with the reason and approver on every state change.
apply · verify · renewHierarchy & territory
Multi-tier channel structures with territory, product-line and price-band entitlement, so visibility follows the org chart.
tier · territory · entitlementDeal registration
Registration with duplicate and conflict detection against direct pipeline, protection windows, and expiry warnings before the window closes.
conflict · window · arbiterOrders & sell-through
Primary orders from the partner and secondary sell-through reported back, reconciled so schemes compute on what actually sold.
primary · secondary · reconScheme engine
Volume, growth, slab and combination schemes as decision grids with effective dates, simulated before they are published.
slab · effective date · simClaims & disputes
Claim raising with evidence, automated eligibility checks, partial approval with a reason, and a dispute lane with its own SLA.
evidence · partial · disputeEnablement & certification
Content, pricing and training assigned by tier, with certification state and expiry gating what a partner may quote.
assign · certify · expirePartner portal & app
A branded web portal and mobile app for order placement, claim status, stock visibility and support: scoped to the partner's own node.
brand studio · scoped · mobilePartner joins → governed settlement
A claim that settles on evidence, not on escalation.
Programme eligibility and evidence can prepare a settlement. They cannot approve a claim or release payment.
“which dealers have claims open past 30 days and what is blocking each one”Prepared by the system · validated and decided through named human gates
Claim raisedPORTAL · EVIDENCE ATTACHED
↓Claim-check agentSCHEME · SELL-THROUGH
↓Within scheme?SLAB · EFFECTIVE DATE
↓Channel managerAPPROVES OR PARTS
↓ReleaseAUTHORITY MATRIX · CREDIT NOTE
↓SettledPARTNER NOTIFIED · TRAIL
Three agents on the channel. The relationship stays yours.
Agents prepare onboarding, evidence and scheme context. Channel owners retain approval and relationship authority.
Chases documents, checks expiry and readiness, and tells the partner exactly what is still missing.
credit and legal gates stay humanScreens registrations for conflict against live pipeline and proposes the protection window.
contested deals go to the arbiterValidates every claim against the scheme grid and sell-through, and drafts the partial with its reason.
release follows the authority matrixWatches ordering rhythm and stock ageing per partner and flags the ones going quiet before the quarter ends.
scorecards scoped per partner
Bring one scheme circular. Watch it become a rule.
A 90-minute working session: your channel hierarchy, one scheme and its claim workflow drafted as an FRS, approved, and generated to a staging tenant with a partner portal you can log into.
For your technical team
The partner portal is meta on the platform: the same identity model with partner users scoped to their own node, durable execution behind every claim, and settlement decisions attributable to the policy version that allowed them.