Bitta Collections reference
Security and data
Where Bitta Collections keeps its data, which outside services it calls and when, what the AI features send, and how permissions and licensing are enforced.
updated: applies-to: 1.2.0.0
This page explains where Bitta Collections keeps data, which outside services it calls, and how access is controlled. It is written for IT and security reviewers.
Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.
Where the data lives
Bitta Collections is a Business Central extension. All its data is stored in your Business Central environment, in the same database as your customers and ledgers, and is covered by the same backups and environment controls.
- Amounts are not copied. Balances, overdue amounts and open invoices are read live from customer ledger entries and detailed customer ledger entries.
- The app stores collection work only: work items, activities, promises, disputes, credit hold entries, matching suggestions, payment plans, remittances, customer replies, agency placements, mail requests, payment links and online payments.
- Native fields are used where they exist: Promised Pay Date, Dispute Status and On Hold on customer ledger entries, and Reason Codes for hold releases.
- No Bitta Apps server holds your collections data. There is no Bitta Apps cloud service in the collections workflow.
Outside services and when they are called
Apart from feature telemetry, Bitta Collections calls an outside service only for a feature you turn on, or when an administrator chooses an action.
| Service | When it is called | What is sent | Default |
|---|---|---|---|
| Azure OpenAI, managed by Microsoft through the Business Central Copilot framework | When a user chooses an AI action, and when the daily job classifies customer replies with AI reply triage on | Data about the customer being worked on, and the text of a customer reply. See AI features (preview) | Off |
| Lob, Inc. (United States) | When a letter by post is approved and sent, and once a day to read tracking | The letter as a PDF, the recipient and return addresses | Off; test mode until live keys are entered |
| Stripe, Inc. (United States), under your own Stripe account | When an email, statement or letter needs a Pay now link, and once a day to read completed payments | Invoice numbers, open amounts and currency, the customer number and your company name. Card and bank details are entered on Stripe's page only | Off; test mode until you turn it off |
| Your Business Central payment service | Never called by Bitta Collections. The links are built by the payment services you set up in Business Central | Nothing from Bitta Collections | Off |
| Your mailbox, through the Business Central Email module | When remittance reading is on, once a day or when a user chooses to read the mailbox | Nothing leaves Business Central; unread emails are read, never deleted or moved | Off |
| Bitta Apps license service | Only when an administrator chooses Start Free Trial, Get License or Enter Activation Code, or the assisted setup starts the trial | The Microsoft Entra tenant ID, the environment name, the app version and the activation code (none for the trial) | Never in the background |
| Bitta Apps telemetry (Azure Application Insights), through Business Central | When a feature is set up, used or fails | Feature names, counts, durations and error categories. Never user names, customer names, email addresses, addresses, document numbers, API keys, letter content or text that users typed | On, like other Business Central apps that send publisher telemetry |
NOTE
In a sandbox environment, outbound calls are blocked until an administrator turns on Allow HttpClient Requests for the app in Extension Management.
Secrets
The Lob and Stripe keys are stored encrypted in the app's isolated storage, not in a table, and are never shown again after you enter them. The license is a signed text that the app verifies with a public key it ships. License telemetry never logs user names, customer names, tenant IDs, activation codes or license text.
Access control
- Three permission sets control what people can see and do: BAA COLL READ, BAA COLL EDIT and BAA COLL SETUP. See Permission sets.
- The collections API uses the same permission sets and seats as the app, for people and for Microsoft Entra applications. Every API page also needs read access to customers, through D365 READ or a similar set, so a Bitta Collections set never widens access to the customer ledger. See Collections API.
- Only collectors marked Can Release Credit Holds may release a credit hold, and every release needs a reason code.
- The group view reads other companies with each user's own permissions. A company you cannot open shows No Access.
- A seat in the license is separate from permissions. A seat lets a person use licensed actions; permission sets decide what they may open and change.
People stay in control
Nothing in Bitta Collections posts a document or sends an AI-written email by itself. Matching suggestions are accepted by a person and posted through the native Business Central pages. Stripe payments become journal lines that a person posts. AI drafts open in the email editor for a person to send, and a person confirms every reply triage proposal. Letters by post wait in an approval queue by default.
Business use only
Bitta Collections is designed for business-to-business receivables. It is not designed for collecting consumer debts. If you hand accounts to a collection agency, you choose the agency and are responsible for its compliance with the laws that apply to you.
Certifications
TODO owner: state the security review or certification status here only if one exists. Do not claim one that is not in place.