Automating SAP Business One with AI: invoices, orders and dunning

When a Canadian SME talks about SAP, it almost always means SAP Business One, not SAP S/4HANA. Business One brings finance, sales, purchasing, inventory and production into one system, installed on the company’s servers or hosted by a partner.

S/4HANA targets large enterprises and integrates differently. This article covers Business One.

SAP puts it plainly in its official training: the Service Layer is a REST API for consuming SAP Business One data, and it follows the OData standards in versions 3.0 and 4.0. In practice, customers, items, orders and invoices are exposed as resources you read and create with standard web requests.

The older DI API is still documented by SAP. On a recent release, the Service Layer is the easiest choice to maintain. If your release is older, your SAP partner can tell you what is available.

Avoid robots that simulate clicks in the interface. They break with every update and bypass the ERP’s controls.

The best candidates are repetitive, high-volume and start outside the ERP, in an email or a PDF.

The agent signs in with its own SAP Business One user, which needs a licence and only the authorizations it requires. It creates drafts. An employee adds them. Every read and every write is logged, on the SAP side and on the agent side.

Then you decide where the AI runs. Sovereign AI runs on a server inside the company or with a Canadian-owned host: your prices and customer data do not go to an outside AI service. Our page on SAP Business One AI integration describes the approach, and the Les Industries Romy case study shows what it looks like at a manufacturer.