PromptPartner DE

Guide

How do you get at the figures in your own ERP?

There are three ways: reports and exports, an application programming interface (API) or a copy of the data in a database of your own. For an AI agent the interface is usually the cleanest way, because a dedicated technical user then reads only what that user may read.

Overview: overdue ordersIllustration with sample data
  1. Order 5120 · Sample LtdERP, orders
  2. Order 5133 · Example plcERP, orders
  3. Open items Sample LtdERP, receivables
  4. Open: order 5140 has no datecheck in ERP

Checked by your accounts team

Why the data is hard to get at

The ERP holds almost everything an owner wants to know: open orders, margin per customer, stock, open items. Even so, you often get at it only through fixed reports.

A new report usually means a job for the ERP partner. So someone exports to Excel and puts the figures together by hand, and does it again every month.

For AI agents the question goes deeper. A quote agent needs prices, an order agent needs items and customers, a reporting agent needs the bookings. Without read access to the ERP, exactly this data is missing.

  • Reports and exportsA file saved to a fixed place at regular intervals. Often a good start for reports.

  • Interface (API)A dedicated technical user reads with read-only rights, only in the areas you allow.

  • A copy of the dataThe data also sits in a database of your own, and the agent reads it there.

What you have in hand at the end

An agent with read access answers questions such as “Which orders are overdue?” or puts together an overview, from the figures in the ERP today. Before the figures go any further, someone on your team checks them.

This is how it works when you give an agent read access:

  1. You write down which questions the agent should answer, and list which data sits in the ERP and which in Excel or on the drive.
  2. For each source you decide how confidential it is.
  3. Your ERP partner or your IT sets up a technical user with read-only rights. It sees only the areas you allow.
  4. The agent reads through the interface and answers the questions. Writing comes later, if at all, and then as a draft that counts only once it's approved.

Unless you choose otherwise, your agents run in your own environment and we operate them. We build on what you run, and we keep a second way open: your own server and open models.

More on the pages Data and security and Where they run.

More on reports and knowledge

What has to be in order first

Before an agent reads your ERP, settle these five points:

  • Your ERP version and where it runs. In the cloud or on your own server: this decides which interface is available.
  • Licence and user. Check with your ERP partner whether the technical user needs a licence of its own.
  • Clean master data. Customer numbers, item numbers and cost centres used the same way everywhere.
  • One person in charge. Someone in your firm grants access and can take it away again.
  • A written data agreement. It says where the data sits, who sees it and when it is deleted.

What your software can already do

What Abacus, Microsoft and Proalpha say in public about their interfaces:

Abacus. The Abacus REST API gives access to a range of REST web service interfaces. Access runs through a service user that you set up in Abacus user management and that signs in via OAuth.[1]

Source: Abacus, REST API documentation

Microsoft Dynamics 365 Business Central. Business Central offers a REST API (version 2.0) through which other applications exchange data. In Business Central online the APIs are switched on by default; in an installation on your own server they have to be enabled first.[2]

Source: Microsoft Learn

Proalpha. In an announcement from April 2026, Proalpha writes that it will rely on an API-centred reference architecture and REST interfaces. Alongside it comes the Proalpha Integration Platform, based on n8n, on your own server or in the cloud. The announcement gives no date for availability.[3]

Source: Proalpha blog, 16 April 2026

Your ERP partner and your IT know which data your version provides through the interface. In the trial run we put in writing what your software already does on its own.

More guides

Questions about data from your ERP

May an agent go straight into the ERP database?

The cleaner way is the vendor's interface, because the technical user's rights apply there and your ERP partner knows them. Either way, agree any direct access to the database with your ERP partner first.

Can the agent also write data into the ERP?

That comes after reading. At first it only suggests, and if it writes later, it does so as a draft that counts only once it's approved.

Who sees the data the agent reads?

You decide, through the technical user's rights and through how confidential each source is. Secret files go only to a model that runs under your firm's name. Everything else is in the data agreement.

Which questions do we start with?

With questions your team puts together by hand in Excel every month today, such as open orders or overdue items. You already know the right answer, so it's easy to see whether the agent reads correctly.

Our ERP is older and has no interface. What now?

Then exports remain, for example a file saved to a fixed place at regular intervals. The agent reads that file, and for reports that can be a good start.

You see whether it fits on cases you've already finished.

In the trial run we make our drafts for those cases and put them next to yours. You see where they match, where they differ and what data is missing, and then you decide.

How the trial run works