Skip to content
Bitta Apps

Chapter 7 of 8Page 3 of 3

AI features

AI assistants (preview)

Use Bitta Collections from Microsoft Copilot and other AI assistants through the Business Central MCP server (preview): what they read, do and need to work.

updated: applies-to: 1.2.0.0

Bitta Collections publishes its collections data as Business Central API pages, and Microsoft's Business Central MCP server offers those pages to AI assistants. A collector can then ask Microsoft Copilot, an assistant built in Copilot Studio, or another assistant that supports the Model Context Protocol about overdue customers, promises and disputes, and have it log a call or record a promise, with the same checks as in Business Central.

Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.

NOTE

Using Bitta Collections through the Business Central MCP server is in preview. The MCP server is a Microsoft feature for Business Central online. Assistants built in Copilot Studio use Copilot credits that Microsoft bills.

What a collector can ask

  • "Which customers are more than 10,000 overdue and not on credit hold?"
  • "What did Fabrikam promise, and did they keep it?"
  • "Which disputes are open for Fabrikam, and who owns them?"
  • "Log a call with Fabrikam: left a message, follow up on Tuesday."
  • "Fabrikam promised 5,000 on invoice 103021 by Friday. Record it."
  • "Open a pricing dispute on invoice 103022."

What an assistant can read and do

Data What it holds What the assistant can do
Customer collection statuses Per customer: balance, overdue amount, collector, risk rating, credit hold, next action, priority score, earliest promised pay date, open disputes and last activity Log an activity, record a promise to pay, open a dispute
Work items The collections worklist: priority score and explanation, overdue amount, next action Log an activity, snooze or close the work item
Activities Calls, emails, notes, letters and every logged step Read
Promises Promises to pay with date, amount, amount received, status and the invoices they cover Read
Disputes Invoice disputes with reason, amount, owner, due date and resolution Read
Payment plans and installments Plans, schedules and what was paid Read
Mail requests Letters and statements sent by post, with tracking Read
Remittances Remittance advices with the matched payment Read

Each action runs the same code as the action on the Bitta Collections page, with the same checks and the same error messages. Recording a promise sets the native Promised Pay Date, and opening a dispute sets the native Dispute Status. No assistant action posts a document, sends an email or a letter, applies cash or moves money. The fields and actions are listed in the Collections API reference. An assistant can filter on every field except the few that are calculated as each record is read, such as the oldest days overdue of a customer; the reference lists them and what to filter on instead.

Permission sets and seats

The assistant works as the signed-in user, or as the Microsoft Entra application it connects as, with that identity's permission sets and Bitta Collections seat. For an application, set them on the Microsoft Entra Applications page.

What the assistant does Permission sets Seat
Reads collections data D365 READ, which includes BAA COLL READ No
Logs activities, snoozes and closes work items D365 READ and BAA COLL EDIT (Bitta Collections - Collector), or D365 ACC. RECEIVABLE No
Records promises and opens disputes The same Yes

D365 BUS FULL ACCESS alone covers all three. The Bitta Collections permission sets cover collections data only, so an assistant also needs read access to customers and their ledger entries. Without it, every Bitta Collections API page refuses with an error that names D365 READ. To give an application a seat, choose Assign Seat on the Bitta Collections License page and pick the application. See Permission sets and License and seats.

Set up the MCP server

An administrator with the Business Central permission set for MCP administration does this once. Microsoft lists it in Configure Business Central MCP Server.

  1. Read-only use needs no setup: the MCP server's default configuration lets assistants read the API pages each user may read.
  2. To let assistants act, open Model Context Protocol (MCP) Server Configurations and create a configuration, for example COLLECTIONS. Turn on Unblock Edit Tools.
  3. In Server Features, activate API Tools. In Available APIs, choose Add APIs by API Group and pick the API group collections from the publisher bittaApps, version v1.0.
  4. Keep Allow Read on for every line. Turn on Allow Actions only for the customer collection statuses and work items pages, the two pages with actions. Leave Allow Create, Allow Modify and Allow Delete off.
  5. Add the standard customers and customer ledger entries APIs if assistants should also see invoices.
  6. Choose Validate, then turn on Active.

Then connect the assistant. In Copilot Studio, add the Dynamics 365 Business Central MCP Server tool and enter the environment, company and configuration. Other MCP clients connect to Microsoft's server with an application registered in Microsoft Entra ID. Microsoft describes each client in Configure Business Central MCP Server and Connect Business Central MCP Server to non-Microsoft hosts.

Keep a person in control

  • Tell the assistant to confirm each action with the user first. For example, in the assistant's instructions: "Before you log an activity, record a promise or open a dispute, tell the user exactly what you will record and wait for them to confirm."
  • Give the Collector set and a seat only to people and applications that may record promises and disputes. A configuration with Allow Read only gives a read-only assistant.
  • Every action is logged as a Bitta Collections activity with the user's ID, like the same action in the app, so a collector or manager can see who recorded what.
  • Promises and disputes recorded by an assistant go through the same checks as in the app: the promise date range, open payment plans, currency and the dispute reason codes.
Collections Activities with a note logged through the Business Central API for Furnace Run Properties
An activity logged through the API shows in Collections Activities like any other.

What's next

See how managers follow the results: Reports and KPIs.

Next step

Ready to try Bitta Collections?