Skip to content
Bitta Apps

Chapter 3 of 8Page 6 of 6

Change subscriptions

Approvals and contract lock

Let a manager approve amendments, holds, terminations and price increases above a threshold with Business Central workflows; lock contracts.

updated: applies-to: 1.3.5.0

Approvals let a manager approve large changes before they take effect: amendments, holds, terminations and price increases above a value you set. They use Business Central's own approval workflows, so approvers work in Requests to Approve as for any other approval. The contract lock freezes a contract against lifecycle changes, for example during a dispute or an audit.

Use it when a seat cut, a pause or a termination of a large account must not happen without a second person, or when a contract must not change until an issue is settled.

Turn on Approvals and Contract Lock

Approvals and Contract Lock is a module of Subscription Features. Turn it on in the assisted setup's Features step (Which features do you use?) or on the Subscription Features page, then reload the browser page. While it is off, the approval requests, contract locks, lock history and approval thresholds are hidden everywhere, including search, and no change needs approval. A contract that is locked stays locked: its lock error offers Open Subscription Features, so you can turn the module on and unlock the contract. The data stays.

Before you start

  • Approvers are set up in Business Central's Approval User Setup, as for any approval workflow.
  • On the Bitta Subscriptions Setup page, group Approvals:
    • Approval Amount Threshold (LCY): the monthly amount from which a change needs approval.
    • Approval % Threshold: the share of the contract's monthly amount from which a change needs approval.
    • A change needs approval when it reaches either threshold. When both are 0, every change of a kind with an enabled workflow needs approval.
  • Locking and unlocking contracts needs the permission set BAA SUBSCR LOCK (Bitta Subscriptions - Lock Contracts). Bitta Subscriptions - Admin includes it.

To set up an approval workflow

  1. Search for Workflows. Or, on the Subscription Approval Requests page, choose Workflows.
  2. Choose New Workflow from Template. In the category Bitta Subscriptions, choose one of the four templates:
    • Subscription amendment approval
    • Subscription hold approval
    • Subscription termination approval
    • Subscription price increase approval
  3. In the workflow, open the response that creates the approval request and choose the approver type: Approver, Salesperson (the contract's salesperson's approver) or Workflow User Group, and the limit type.
  4. Turn on Enabled.

Approvals are opt-in: without an enabled workflow, no change needs approval, whatever the thresholds.

How a change gets approved

The value of a change is its monthly amount in local currency: the monthly amount of the lines a hold pauses or a termination ends, the monthly change of an amendment, or the monthly increase of a price increase run.

Change When it needs approval After approval
Amendment Finish in the amendment wizard saves it as Open and sends an approval request It becomes Scheduled and the daily amendment job applies it on its effective date. Apply on the request applies it now
Hold Finish in the hold wizard sends a request; the hold is not placed yet Choose Apply on the request. The hold is placed with every check again
Termination Finish in the termination wizard (also Do Not Renew in the Renewal Cockpit) sends a request Choose Apply on the request, as for a hold
Price increase Propose Escalations writes the escalation entries as Proposed with Waiting for approval; one request per contract and run The approval writes the rows to Microsoft's Contract Price Update (or the planned lines in Automatic mode). Then run Perform Price Update as before

The approver approves, rejects or delegates in Business Central's Requests to Approve, or on the Subscription Approval Request page. A rejected change changes nothing.

To follow approval requests

Search for Subscription Approval Requests, or choose Approval Requests in Approvals and Follow-ups on the Navigate tab of a customer contract (next to Lifecycle History; also under Related > Customer Contract). Each request shows the Request Type, the Status (Open, Pending Approval, Approved, Rejected, Canceled or Applied), the Monthly Amount (LCY), the Share of Monthly Amount % and who requested and decided it. The views are Pending Approval, Approved, Not Applied, Rejected and Open.

On a request:

  • Send Approval Request and Cancel Approval Request send or withdraw it.
  • Apply applies an approved hold, termination or amendment now. If it fails, Error Text says why.
  • Cancel Change drops the change: the amendment is canceled, the held-back price increases are dropped, or the hold or termination is not placed.
  • Approvals shows the approval entries; Change opens the amendment, hold or termination.

The role center cues Changes Pending Approval and Approved Changes to Apply count the requests.

To lock a contract

  1. On a customer contract, choose Lock, then Lock Contract.
  2. Enter the Reason, for example Billing dispute. Users who try to change the contract see it.

The contract shows Locked. Unlock Contract removes the lock. Lock History (Navigate > Approvals and Follow-ups on the contract), and the Contract Locks page, show who locked and unlocked it, when and why. The Locked Contracts cue counts locked contracts.

What the lock blocks

  • Finishing or applying an amendment, placing, resuming or canceling a hold, applying or reopening a termination.
  • Price increase proposals (the contract is skipped and reported), granting a promotion.
  • Let Expire, Do Not Renew and renewal quotes, also Microsoft's Create Contract Renewal Quote.
  • Sending or applying an approval request.
  • Device activation: on a locked contract the devices stay Awaiting Activation, and the activation logs why.
  • Changes of the Bitta Subscriptions fields on the contract. The message names the lock reason and links to the contract.

What the lock allows

  • Reading the contract, renewal notices, recording customer answers and follow-ups.
  • Microsoft's own billing, invoices and Microsoft's fields on the contract.
  • Revenue recognition: Allocate Revenue, Calculate, Create Revenue Allocations and Post Revenue Schedule run on locked contracts, and never need approval, so every month can close.

What happens in Microsoft Subscription Billing

  • The approval runs on Business Central's workflow engine: approval entries, comments, delegation and notifications are Microsoft's.
  • Nothing changes in Subscription Billing until the change is applied. Then the same engines as without approval write Microsoft's subscription lines.
  • Device activation, device returns, device quantity syncs and Cancel Trial never need approval. Activation still respects the lock.

Limits

  • A price increase that waits for approval is not in Microsoft's Contract Price Update. It shows as a Proposed escalation entry with Waiting for approval, and on the request.
  • On a locked contract, Bitta Subscriptions fields still look editable on the page. The change is refused when it is saved.
  • Thresholds and workflows are checked when the change is made. An amendment scheduled before a workflow was enabled is applied without approval.
  • Approving a hold or termination does not apply it: the requester, or another user with the hold or termination permission, chooses Apply.
  • The API (holds, terminations) and Batch Changes cannot send approval requests. A change there that needs approval is refused with a message that names the wizard. Amendments from the API get a request.

See also

Next step

Ready to try Bitta Subscriptions?