Daily use
Plan acceptance
Distribute commission plan documents to reps with delivery evidence, and let them acknowledge, accept, reject or comment on their plan inside Business Central.
updated: applies-to: 1.1.2.0
Bitta Commission delivers the exact plan document of a published plan version to each participant and records the delivery as evidence. Sales reps then answer on My Plan Acceptance in Business Central: acknowledge, accept, reject or comment. This page covers distribution for administrators, the response steps for sales reps, and what each response records.
Before you start
- The plan version must be Published or Active. Distribute Plan Documents is not available on other versions.
- Only a user who has the Bitta Commission Setup Administrator or Plan Designer permission set can distribute or make a plan available.
- Each participant needs an Active assignment in the version that is in effect on the work date and inside the version dates, and a Language Code on the participant record. Participants without a language code are skipped.
- Sales reps need the Bitta Commission Participant permission set and a primary user link on their participant record. See Participants.
For administrators: distribute plan documents
- Open the published version on Commission Plan Version. Choose Preview Plan Document to check the Commission Plan Document. A version preview is not tied to a participant assignment, so it carries the UNAPPROVED DRAFT notice.
- Choose Distribute Plan Documents and pick the channel: Business Central, Email, Portal, E-signature or API.
- Read the result message. It shows how many participants were delivered, already delivered, skipped and failed.
- Choose Plan Distributions on the version card. Each distribution shows its Delivery Channel Code, whether it Completed, the number of participants Delivered, Already Delivered, Skipped and Failed, and an Evidence Hash over the distribution and its lines.
- Choose Participant Deliveries to open Plan Distribution Deliveries.
| Field | What it shows |
|---|---|
| Participant ID / Plan Assignment ID | Who received the document, for which assignment. |
| Result | Delivered, Already Delivered, Skipped or Failed. |
| Message | Why the participant was skipped, or the error of a failed delivery. |
| Locale Code | The language of the document, taken from the participant's language. |
| Plan Document Version / Plan Document Hash | The format version and hash of the exact document delivered. |
| Acceptance ID | The plan acceptance chain where the participant responds. |
| Processed At / Line Hash | When the line was processed, and the hash of this evidence line. |
The channel you pick is only recorded on each delivery. For every channel, including Email, Portal, E-signature and API, Bitta Commission creates the same delivery entry in Business Central: it does not send the plan document by email, publishes nothing to a portal and calls no signature service or external API. Participants open and answer every delivery in Business Central on My Plan Acceptance. A participant who already has a live delivery of the same document on the same channel and locale is not delivered twice. Each line is committed on its own, so one failure never stops the others, and an interrupted distribution resumes where it stopped.
To deliver one assignment, open it on Commission Plan Assignment, choose Preview Participant Plan to check the document, and choose Make Available in Business Central. This delivers on the Business Central channel and returns the existing delivery when the same document is already live.
For sales reps: respond to your plan
When a plan is delivered to you, on any channel, Bitta Commission raises a Plan Available notification for you. It names the plan and says it "is available for you to review." If your administrator has set up an Email notification rule for this event and turned on email notifications, the notice also goes out as a short email; the plan document itself is never attached.
- Search for My Plan Acceptance in Tell Me and open it. It shows only the deliveries and responses of the participants linked to your user through a primary user link.
| Field | What it shows |
|---|---|
| Plan Version No. / Plan Document Version | The delivered plan version and plan-document version. |
| Action Code | The delivery or response recorded in the history. |
| Action At | When it was recorded. |
| Delivery Channel Code / Locale Code | How the document was delivered, and its language. |
| Expires At | When the delivery stops accepting responses: 30 days after delivery. |
- Select the delivery and choose View Plan Document to open the exact document that was delivered to you.
- Respond:
- Acknowledge records that you received and reviewed the document.
- Accept accepts the exact delivered plan-document version.
- Reject rejects the plan. Enter a Decision Comment in the dialog; it is mandatory.
- Comment records a comment without changing an earlier response. The comment is mandatory.
The response actions are available only to users who have the Bitta Commission Participant permission set and not the Auditor or Support set.
E-signature deliveries
On a delivery made on the E-signature channel, Accept requires the Signature Provider and Signature Reference of your signature provider. Without both, Business Central shows BAA-WFL-SIGNATURE. Bitta Commission records the reference; it does not connect to the provider.
What a response records
Every delivery and response is a new, append-only entry; nothing overwrites an earlier response. Each entry carries the plan document hash, the plan definition hash, the participant, assignment and plan version, the action, the user, the time and an entry hash. A comment is stored as a SHA-256 hash, not as text. When you accept a new delivery for an assignment you had accepted before, the new entry references the earlier acceptance.
A response is refused when the delivery has expired, was superseded or reversed, when the plan definition no longer matches the delivered document, or when the participant is not linked to your user.
What to check if it goes wrong
| Symptom | What to do |
|---|---|
| A participant was skipped | Add a language code to the participant, or check that the assignment is in effect on the work date and inside the version dates. |
| BAA-WFL-DELIVERY-AUTH | Distribute as a user with the Setup Administrator or Plan Designer permission set. |
| BAA-PLAN-DISTRIBUTION-EMPTY | The version has no active participant assignment. Assign participants first. |
| BAA-WFL-DELIVERY-LOCALE | Set the participant's Language Code before you choose Make Available in Business Central. |
| BAA-WFL-NOTFOUND | Select a delivered plan before recording a response. |
| BAA-WFL-STATE | The delivery has expired or was reversed. Ask for a new distribution. |
| BAA-WFL-SCOPE | The delivery belongs to a participant that is not linked to your user. |
| BAA-WFL-EVIDENCE | The delivery was superseded by a newer document, or the plan definition no longer matches it. Respond on the newer delivery. |
| BAA-WFL-SIGNATURE | Enter the Signature Provider and Signature Reference before you accept an e-signature delivery. |
For the reports in the app, including the plan document, see Commission reports.
What's next
Close the period once the work is done: Close a period.