Report and manage
Troubleshooting
Find out why a reminder or email was not sent, check the daily job and failed steps, run the setup check, and fix blocked calls, license and AI capacity errors.
updated: applies-to: 1.2.0.0
Find and fix the usual reasons why collections work doesn't run. Start with the Collections Setup Check report and the Job status FastTab. Bitta Collections uses the native job queue, email and report setup, so most fixes are made in standard Business Central pages.
Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.
Before you start
- You need the BAA COLL SETUP permission set (the Administrator set) to change the setup, and the permissions to manage job queue entries and email accounts.
- Any user with BAA COLL READ can run the setup check and the reports.
Run the setup check
- Search for Collections Setup Check, or choose Reports > Setup and Control > Collections Setup Check on the role center.
- Turn on Show Information to also list findings that need no action, such as the license status.
- Choose Preview or Send to.
The report lists every gap that stops dunning, emails or holds, each with how to fix it. It checks the setup, customers without a collector, customers without an email address or reminder terms, the email account, the dunning sequences, the credit rules and the license.
Check the collections job
Open Bitta Collections Setup and look at the Job status FastTab.
| Field | What it tells you |
|---|---|
| Last Job Run | When the collections job last finished |
| Last Job Failure Count | How many customers, promises or disputes failed in the last run. Red when more than 0 |
| Last Job Failures | The first 10 failures of the last run, each with its phase and error |
| Last Worklist Refresh | When the worklist was last refreshed |
One customer's error never stops the job; the others are still processed. To see the failed dunning steps with their errors, choose the Jobs > Failed Dunning Steps action, or drill down on Last Job Failure Count. Both open Dunning History filtered to the steps with the status Failed from the day of the last run.
To see the job queue entries, choose Jobs > Job Queue Entries. They are in the category BAACOLL. If no entry exists, choose Prepare > Schedule Jobs.
The job is in Error
When the job can't run at all, for example because its user lost a permission, it uses its 3 attempts, 300 seconds apart. Then it stays in Error and does not start again by itself.
- Open the job queue entry and read the error.
- Fix the cause.
- Choose Set Status to Ready on the native Job Queue Entries page.
Why did a customer not get a reminder?
On the customer card, choose Collections > Dunning > Preview Sequence. It shows which step the next run performs for each open invoice, and why. Nothing is sent. The Dunning Proposal report shows the same for all customers. The usual reasons are:
- The invoice is disputed, has an open promise or a payment plan, or is on hold. Dunning pauses for that invoice.
- The customer was contacted within Min. Days Between Contacts (default 3).
- The step's total is below its minimum amount.
- The sequence or the customer is blocked, or the customer is blocked for privacy.
- The customer has no sequence, and there is no Default Sequence Code.
- A Reminder step needs reminder terms on the customer.
- The step is a Collector Task, so it waits on the worklist for a person.
Dunning History on the customer card lists every step that ran, was skipped or failed, with the reason.
Why was an email not sent?
- No email account. The error reads "No email account is set up for the Collections email scenario, so collections emails can't be sent." Add an account on Email Accounts and assign it to the Collections scenario with Email Scenarios.
- Redirect is on. When Redirect Emails To is filled in, every collections email goes to that address. Clear it before you go live.
- No address. A customer needs a contact with the Collections Email Role To, or an email address on the customer card.
- Run limit. One run sends at most Max. Emails per Run (default 200). The rest wait for the next run.
- Failed sending. Check the native Email Outbox and Sent Emails. The job user updates the email status on the activity log, so that user needs modify rights on the activity log.
Calls to Bitta Apps, Stripe or Lob are blocked
Sandboxes block outbound calls from extensions until you allow them. The license page then says that Business Central blocked the request to Bitta Apps. Letters by post say that the call to Lob was blocked, and Check Payments Now says that the call to Stripe was blocked. Emails and statements are then sent without Stripe links.
- Search for Extension Management.
- Choose Bitta Collections, then Configure.
- Turn on Allow HttpClient Requests.
Production environments allow these calls by default. To activate a license without a call, choose Paste License and paste the license text from Bitta Apps.
License messages
The license page shows the Status of the license. A notification on the setup page, the worklist and the role center tells you when something needs attention.
| Status or message | What to do |
|---|---|
| Not Activated | Choose Start Free Trial, or Enter Activation Code with the code from Bitta Apps |
| Expired | The license keeps working for 14 days after Valid Until. Renew it with Get License |
| For Another Tenant, For Another Environment | Choose Get License in this environment |
| "You have no seat of the Bitta Collections license" | Ask the license administrator to choose Assign Seat for you |
| "Your seat is beyond the seats of the license" | Remove seats that are no longer used, or add users to the license |
Without a usable license or seat, customer ledgers, credit hold releases, cash application and reports keep working. See License and seats.
AI errors
The AI features are a preview and are off by default. These messages come from the Business Central Copilot framework or from Bitta Collections:
| Message | What to do |
|---|---|
| "Copilot is not available for ... An administrator can turn it on in the Copilot & agent capabilities page, and must allow data movement when the environment is outside the United States." | Activate the capability on Copilot & agent capabilities |
| "Copilot has no AI capacity in this environment. An administrator must set up Copilot billing for Business Central before you can use this feature." | Set up Copilot billing. Meanwhile, do the work without AI |
| "There is too much data to send to Copilot at once. Select fewer entries and try again." | Select fewer entries |
| "Payment Match Assist is not turned on." | Turn on AI Match Assist Enabled in Bitta Collections Setup |
| "This payment already has a high-confidence suggestion. Accept or reject it before you ask for AI suggestions." | Decide on the rule suggestion first |
See AI features (preview) for how to turn the features on.
The remittance mailbox can't be read
The message says that the email account uses a connector that can't read a mailbox. In Choose Remittance Mailbox, choose an account with the Microsoft 365 or Current User connector. Then choose Test Mailbox. The job queue user must be able to read the mailbox. See Remittances.
What's next
Look up any field and its default: Setup reference.