🍁 Proudly Canadian — hosted and operated in Canada
White paper The digital supply chain Get the white paper
Agent Libre
Home›Solutions›ERP and business systems
Solutions — Use case

An agent in your ERP,at a fixed amount

On the 3rd of the month, the agent connected to the ERP has already reconciled yesterday’s payments, prepared the purchase orders below the reorder point and flagged two inventory discrepancies. Your vendor or your team sets up that agent, and it calls a language model on every task. With Agent Libre behind it, that model is served in Canada and the month’s amount does not move, whatever the number of calls.

Talk about your ERP
The problem

What breaks when the ERP agent pays for every call

Teams that have connected an agent to their business system run into three difficulties.

01

Month-end decides the bill

For the first three weeks of the month, the agent handles a few hundred entries a day. Then the close arrives: bank reconciliations, adjustments, supplier invoices received late. With a usage-billed provider, the month’s AI spending is decided in those three days, and nobody knows it before the invoice.

02

The chart of accounts re-read on every line

To classify an invoice, the agent re-reads the chart of accounts, the approval policy and the latest entries from the same supplier. That context weighs far more than the line to classify, and it is billed as many times as there are lines.

03

Payroll and margins at a third party

The payroll module holds salaries; the sales module holds prices negotiated customer by customer. An agent that reads those modules sends those fields to the model. With a foreign AI provider, they leave the country on every call, and the service agreement rarely says how long they are kept.

Where Agent Libre fits

You, your tool, and the model that answers it

Your tool stays the same. What changes is the model that answers it.

1
Layer 1 — You

Your organization

Your teams, your data and your rules. You decide what the tool does, and with which data.

2
Layer 2 — The tool

The agent connected to your ERP

The agent that reads and writes in your ERP: it reconciles payments, classifies invoices and prepares purchase orders. Your vendor or your IT team connects it and gives it its rules.

3
Layer 3 — The model

The model that answers the tool

Every time the tool needs an answer, it calls a language model. That model can come from different providers. This is where Agent Libre comes in.

Anthropic
Billed by usage, in the United States.
OpenAI
Billed by usage, in the United States.
Agent Libreour offer
A fixed amount per month, servers in Canada.
Behind the tool

What Agent Libre changes behind your tool

The ERP stays the system of record and the tool stays your vendor’s. What changes sits behind them: the model that answers, the gateway the calls go through and the contract that pays for them.

Connect

One setting in the tool

The link between the agent and the ERP (SAP, Oracle NetSuite, Microsoft Dynamics 365, Odoo, Acomba or others) does not move. The model is chosen in the tool’s settings, in three lines of configuration: the address, the key, the model name. Approval rules and write permissions stay in the ERP.

Reserve

A reserved speed for the ERP

You reserve a processing speed, measured on your real use. The number of entries handled in a day, the number of modules connected, the date in the month: none of that enters the bill.

Log

A log and a budget per team

The Agent Libre gateway records every call: which application, which key, which model, at what time. You give the finance module and the purchasing module separate budgets, and a self-serve report shows which one consumes when.

Keep here

Data in Canada

Salaries, negotiated prices and supplier records go through servers hosted and operated in Canada, and nothing is kept after processing. The gateway masks, as they pass through, the fields you choose to exclude, before they reach the model.

Three rules

What holds for an ERP agent

The ERP decides

The agent proposes an entry or a purchase order. Your approval rules, in the ERP or in the tool, say what it writes on its own and what a person signs. The model does not know those rules; it reads and writes.

Twelve months

The fixed amount is written in the contract for twelve months. It is revised at renewal from measured use, upward or downward.

24 hours of measurement

Before the contract, a gateway placed in front of your current provider measures for 24 hours to one week what the agent really consumes, hour by hour. The reserved speed is set on that measurement, with no commitment on your part.

Where to start

What each team decides before connecting the tool

Changing the model behind the agent takes a few minutes. The decisions that matter are made beforehand, in the ERP and in the tool.

FOR THE FINANCE DIRECTOR

Set the amount above which an entry proposed by the agent waits for a signature, and have it written into the ERP’s approval workflow before changing the model. Ask your vendor to keep a record of rejected proposals: the external auditor will ask for it at year-end.

FOR PURCHASING

Decide whether the agent may create a purchase order with an already approved supplier, or only prepare it. Check that the approved supplier list and the negotiated prices come to it from the ERP on every call rather than from a copy in the tool: that is what keeps it from ordering at the old price.

FOR PAYROLL AND HUMAN RESOURCES

List the employee record fields the agent does not need for its work (social insurance number, banking details, date of birth) and have the gateway mask them before sending. A field that is not sent does not have to be protected.

FOR THE IT TEAM OR THE ERP ADMINISTRATOR

Check that your vendor’s tool lets you choose the model address and the key; that is the only setting to change. Run the old and the new model side by side over one full month-end, and compare the proposed entries with those your accountants approved, before switching everyone over.

Frequently asked questions

What we get asked on this topic

Does Agent Libre provide the agent that works in the ERP?

No. The agent and its link to the ERP, whichever one it is, come from your tool’s vendor or from your team. Agent Libre serves the language model that agent calls, and the gateway that logs and masks as calls pass through.

Does the model classify an invoice to the right account as well as another one?

On this kind of task, quality depends mostly on what the tool gives the model: the chart of accounts, the approval policy, examples of approved entries. A model that receives those elements classifies the common cases correctly. Ambiguous cases, an invoice that touches two accounts for instance, have to go through a person anyway.

What happens on closing days, when entries pile up?

Requests that exceed the reserved speed wait their turn, with no cut-off and no charge. An entry that waits a few seconds longer does not delay the close. If every month-end exceeds it by a wide margin, the reserved speed is revised at renewal.

What does the model see when the agent reads an employee record or a negotiated price?

It sees what the tool places in the request, nothing more: it has no access to the ERP itself. The Agent Libre gateway removes the fields you have excluded before sending. Once the answer is returned, nothing is kept beyond processing, and nothing is used to train a model.

What does a second module connected to the same model cost?

Nothing more as long as the reserved speed is enough for both. If purchasing joins finance and requests often wait, the speed is revised at renewal, and the new amount is written in the contract for the next twelve months.

To go further

See also

Procurement and logistics

What a purchasing department checks before putting a model served in Canada behind the tool that reads its tenders, contracts and delivery slips.

Use case

Project management

Minutes, risk register, status report: what a model served in Canada changes behind your project tool, and what each team decides before connecting it.

Use case

Re-reading: the line item nobody looks at

Why the context re-read on every entry weighs more on spending than the answer itself.

Blog
White paper

Your company has two supply chains

The first one you already know. Materials come in, they are transported, stored, transformed, delivered. Every step has a supplier, a lead time, a unit cost. When the margin tightens, you walk down that chain step by step, and you generally know where to look.

The second one moves information instead of materials. A price request comes in and becomes a quote. An order comes in and becomes a production order, an invoice, a confirmed delivery. A site report becomes a change order, or it does not. This chain runs through every one of your departments and it employs a large share of your people.

Where to start

The 24-hour to one-week audit

We measure your actual consumption at your current provider: who calls what, what it costs, and what is leaving your walls. Free, no commitment, and the report is yours even if you go no further.

Book the audit Write to us