Positions, teams, and hierarchies

Positions, teams and hierarchies describe how your sales organization is structured over time. They let a plan follow a seat instead of a person, hold credit while a seat is vacant, and give managers and teams the right scope and credit. This page explains each structure and how to maintain it.

The Commission Hierarchy Editor shows the sales team reporting lines for a date.

Before you start

• You need the Bitta Commission Setup Administrator permission set (BAA Comm Setup Admin) to maintain positions, teams and hierarchies.
• Create the participants first. See Participants and payees.
• Every structure is dated. You add new dated rows or versions instead of editing history.

Positions

A position is a stable organizational seat, such as "Sales Rep North", independent of who currently holds it.

1. Open Commission Positions and choose New Position.
2. On Commission Position, enter the code, description, status, effective dates, an optional default plan and a job function code.

Position Status is draft, active, suspended or closed.

Assign a participant to a position

1. On the position card choose Assignments, or open Position Assignments.
2. Choose Assign Position.
3. Enter the participant, position, effective dates, Allocation Percent and whether this is the participant's Primary Position.
4. Optionally enter Credit From and Credit To (the sale dates that generate new credit for the holder), Process From and Process To (the dates results can still be measured, corrected and settled), and the Manager Participant No.

Plan assignments and territory ownership can target a position. When they do, credit follows whoever holds the position on the sale date. Effective Plan Assignments shows assignments a participant inherits through a position.

Vacant position credit

When a sale is credited to a position that has no holder, the credit is held on Vacant Position Credits instead of being lost. Open it from Vacant Credits on the position card.

Action	What it does
Claim	Assigns the held credit to the current or a later holder of the position. The claim is audited and cannot be undone.
Release	Releases the credit so it is never paid. Only a setup administrator can release, and the release is audited.
Request claim payment	Creates the governed manual adjustment that pays the claimed credit. Another user must approve it before it is processed.

Teams

A team groups participants for organization, scope, team credit and team targets.

1. Open Commission Teams and choose New Team.
2. On Commission Team, enter the code, description, status, Team Type Code, the Manager Participant No., effective dates, the Default Allocation Percent offered for new members, and whether Allow Over Allocation is permitted.
3. Choose Members, then Add Team Member.

Each membership on Team Membership has a Member Role Code, an Allocation Percent, Primary Team, Manager, Credit Eligible and effective dates.

• Manager marks the membership of the team's manager. Manager overrides use this flag to find the manager's team when no hierarchy applies.
• Credit Eligible decides whether the member receives a share of team credit.

To change a team from a date, select it and choose New Version. The new version links to the old one, and the old one ends the day before.

Hierarchies

A hierarchy records who reports to whom, and from which date. Each reporting line says that a member (a participant or a position) reports to a manager (a participant or a position) from Effective From through Effective Through.

Hierarchies are used in four places:

• A Manager and descendants user scope uses a hierarchy to decide which participants a manager can see. See Roles and permissions.
• Roll-up additive credit climbs a hierarchy, primary parents first.
• Manager Override components find the participants reporting to a manager in the hierarchy.
• A Hierarchy level approval stage routes to the participant a number of levels above the requester. See Approvals and notifications.

Commission Hierarchies lists the hierarchies in the company, with their type, version, status, dates, node and relation counts, the rule that each member needs one primary parent, and the maximum depth. Choose Open in Editor to work on the selected hierarchy.

Create a hierarchy

1. Open Commission Hierarchy Editor and choose New Hierarchy.
2. Enter the Code, for example SALES-MGMT, a Description and the Hierarchy Type. Manager hierarchies drive manager scope and approvals.
3. Enter Effective From and, if the hierarchy ends, Effective Through.
4. Choose Allow Multiple Parents if a member can report to more than one manager at the same time, for example through a dotted line. Keep Require Primary Parent on so that every member has one primary line before a secondary line is added. Maximum Depth limits the number of levels. Zero means unlimited.

The new hierarchy is active at once. Use its code on roll-up credit rules, hierarchy approval stages and manager scopes.

See the tree for a date

On Commission Hierarchy Editor, choose the Hierarchy and an As of Date. The page shows the tree for that date: members at the top have no manager on the date, and each member appears under the manager it reports to. Each line shows Reports To, Relation Type, Primary Parent, Rollup Percent and the dates of the line.

Choose Show All Dates to list every reporting line on all dates instead, including ended and future lines, with the End Reason of each ended line.

Add, change and end reporting lines

Action	What it does
Add Reporting Line	Adds a line in which the Member reports to the manager in Reports To, from Effective From. A blank Effective Through runs to the end of the hierarchy. The selected member of the tree is offered as the manager.
Change Manager	Moves the selected member to a new manager from the Change Date. The current line ends the day before, and a new line with the same type, primary flag and roll-up percent starts on the change date.
End Reporting Line	Ends the selected line on the End Date, its last day.

Changing a manager and ending a line need a Reason. The editor refuses a change that would:

• create a cycle, for example a manager reporting to one of their own members (BAACOMM-ORG-HIERARCHY-CYCLE-001);
• give a member two overlapping lines to the same manager, or overlapping lines at all when the hierarchy does not allow multiple parents (BAACOMM-ORG-HIERARCHY-OVERLAP-001). End the existing line first, or use Change Manager;
• reach into a commission period that is frozen, settled or closed (BAACOMM-ORG-HIERARCHY-FROZEN-001). Choose dates after the period.

Members are added to the hierarchy the first time they appear on a line. Every change is recorded in the audit log with the administrator and a request key, so retrying the same request never adds a line twice.

Commission Organization and organization imports

Commission Organization lists the participants within your organization access. Choose Set Up Salespeople to open the guided setup for bulk salesperson setup.

To load or update many records at once, use Organization Import Batches:

1. Choose New Batch and open it.
2. Upload one CSV file per record type from Import CSV: Participants, Participant Links, Positions, Position Assignments, Teams and Team Members. The tooltip of each action lists the expected columns.
3. Choose Validate, open Findings to review them, and correct staged rows in place in the Staged Rows part.
4. Choose Apply. Apply is atomic: any failure rolls back the whole batch.

A batch marked as a dry run only validates and never applies. Validation warns when an earlier applied batch had the same file content, and flags manager chains that would form a cycle. Export Organization downloads participants, positions, position assignments, teams and team members as CSV.

How it works

• Positions, assignments, teams, memberships and reporting lines are dated and append-only. To change something from a date, add a new dated row or version, or end the line in the hierarchy editor.
• Participant transitions (hire, transfer, leave, return, termination) create and end these rows for you, with credit handling of Keep, Transfer to Successor or Stop. See Participants and payees.
• Assignments that target a position are resolved on the sale date, so a transfer changes who is credited from the transfer date only.

What to check if it goes wrong

Symptom	What to do
Credit lands on Vacant Position Credits	The position had no holder on the sale date. Assign the holder, then claim the credit.
A manager override pays nothing	Check that the manager has team members or hierarchy descendants on the period end date. Open Commission Hierarchy Editor with the period end date as the As of Date to see the tree.
BAACOMM-ORG-HIERARCHY-OVERLAP-001 when adding a line	The member already has a line for those dates. Use Change Manager, or end the existing line first.
BAACOMM-ORG-HIERARCHY-FROZEN-001	The dates reach into a frozen, settled or closed period. Choose dates after that period.
An organization import fails on apply	The whole batch is rolled back. Fix the findings and apply again.

Related pages

• Participants and payees
• Territories
• Manager overrides and team credit
• Crediting rules, splits, and overrides
• Quotas, targets, and attainment