Skip to content
Bitta Apps

Chapter 7 of 8Page 2 of 2

Integrate and migrate

Collections bridge

The add-on for Bitta Subscriptions with Bitta Collections: account standing on contracts, credit hold checks, dunning suspensions and renewal risk.

updated: applies-to: 1.3.5.0

Bitta Subscriptions Collections Bridge is an optional add-on for companies that use both Bitta Subscriptions and Bitta Collections. It shows each customer's account standing where you work with subscriptions, can warn or block new amendments for customers on credit hold, can pause subscriptions when a dunning step runs and restart them when the account is cleared, and marks customers in collections as a renewal risk.

Payments and dunning stay in Bitta Collections. Subscriptions and billing stay in Microsoft Subscription Billing. The bridge only connects them.

What you need installed

  1. Bitta Subscriptions and Bitta Collections, from AppSource.
  2. Bitta Subscriptions Collections Bridge. Install it after the two apps. The installation creates the setup with safe defaults: amendments on credit hold Warn, no suspensions, renewal risk from 30 days past due, and collections notes on.
  3. Permission sets: BAA SCB USER (or BAA SCB READ) for users, next to their Bitta Subscriptions and Bitta Collections permission sets. BAA SCB ADMIN for whoever sets it up, and for the job queue user that runs the bridge job. That user also needs Bitta Subscriptions permissions and a license, because the bridge places holds.

Without one of the two apps, the bridge cannot be installed. Neither app needs the bridge.

Set it up

Search for Subscriptions Collections Bridge Setup:

  • Amendments on Credit Hold: what happens when someone starts an amendment for a customer on credit hold in Bitta Collections:
    • Allow: nothing.
    • Warn (default): the amendment wizard shows an Account Standing line on its first step and its review step.
    • Block: new amendments, from the wizard or the API, fail with Show Customer until the credit hold is released.
  • Dunning Suspensions: Suspend at Dunning Stages (off by default), the Suspension Reason Code of the holds, and the Resume Tolerance (LCY), the overdue amount up to which an account counts as cleared.
  • Renewal Risk: Risk Days Past Due (default 30; 0 turns the rule off) and Disputes Are Renewal Risk. A customer on credit hold is always at risk.
  • Activity Log: Log Subscription Changes (on by default).

Then choose Schedule Bridge Job. It runs every 60 minutes. Bridge Job Scheduled shows that it exists. Process Now runs it at once.

Account standing

The Account Standing FactBox is on the Customer Contract and Customer Contracts pages, the Renewal Cockpit, Dunning Suspensions and Collections Notes. For the bill-to customer, the customer who pays, it shows:

  • On Credit Hold, Credit Hold Reason and Credit Hold Since;
  • Overdue Amount (LCY) and Days Past Due;
  • Open Disputes, the Dunning Stage and the Suspended Contracts;
  • Open Promises, the Next Promise Date and Next Promise Amount;
  • the Last Payment Date and Last Payment Amount (LCY), and the renewal risk with its reason.

Choose a value to open what is behind it in Bitta Collections: the hold history, the disputes, the promises, the work item or the overdue entries.

Suspend subscriptions at a dunning step

  1. On the setup, turn on Suspend at Dunning Stages and choose a Suspension Reason Code.
  2. In Bitta Collections, on the steps of your dunning sequences, select Suspend Subscriptions on the steps that should pause the service, for example the final reminder.

When such a step runs for a customer, the bridge queues the customer's active contracts. The bridge job places a hold on each whole contract from the work date, through the normal hold engine (Hold and resume), with a credit for days already billed. Once the customer is off credit hold and owes no more than the Resume Tolerance (LCY) overdue, the bridge job resumes the contract.

Dunning Suspensions lists each suspension with its Status (Pending, On Hold, Resumed or Canceled), the dunning sequence and step, the Hold No., Hold From, Resumed Date, the Closed Reason and any Error Text. If you resume a suspended hold by hand, its suspension is closed.

Renewal risk

In the Renewal Cockpit, the columns Account at Risk and Account Risk Reason appear. A customer is at risk when it is on credit hold, at least Risk Days Past Due past due, or (if the setting is on) has open disputes. The Renewal Forecast report moves their recurring revenue to ARR at risk, with the outcome Account at Risk.

Notes in the collector's activity log

With Log Subscription Changes on, these changes appear in the customer's activity log in Bitta Collections, as type Subscription: terminations with a fee (with the fee invoice), reopened terminations, and the holds that the bridge placed and resumed. Collections Notes lists them, with Logged and any Error Text. A note that could not be logged is tried again on the next run.

API

bittaApps/subscriptions/v1.0/dunningSuspensions lists the suspensions, read only, for a CRM or a customer portal.

Limits

  • The bridge builds no payments, dunning or reminders of its own. Bitta Collections does that.
  • The bridge job writes each record in its own transaction. A failure stays on its row and fails the job queue entry, so you see it.
  • Bitta Collections' cash forecast counts a termination fee once Microsoft's billing posts its invoice, not before.

See also

Next step

Ready to try Bitta Subscriptions?