Knowledge · Guide 5 of 8
From interface to capability
An interface delivers data. A company needs answers it can rely on. The real value lies between the two, and that is where it is decided whether AI access to SAP holds up in daily work.
What an interface does and doesn't do
SAP offers numerous interfaces for retrieving purchase orders, invoices or supplier data. Technically, a great deal is possible with them.
An interface does not know which question was asked, though. It returns fields and values without saying which of them matter for the answer. Whether the twenty missing units on an order are still coming, or whether the line was closed long ago, sits in different fields that have to be combined correctly.
What makes a capability
A capability answers a business question completely. It knows which data it needs, how that data fits together and which conclusion it is allowed to draw.
Take the question of which purchase orders from a supplier are still open. A capability for this considers ordered and delivered quantities, and also whether lines were closed with the delivery-completed indicator. It distinguishes a quantity difference from a delivery that is actually still expected. And it says what its answer is based on.
Why this makes the difference
For users, the difference shows up as reliability. The same question always gets the same answer, however it is phrased. Different questions are never accidentally blended together.
For the company, it shows up as maintainability. A capability is built, tested and approved once. From then on it answers countless variations of the same question without new development for every new phrasing.
Bridge as a catalog of capabilities
That is why Xient Bridge is built as a catalog of tested capabilities rather than a collection of interfaces. Each covers a business task, such as open purchase orders, payment blocks, delivery status or quantity and price discrepancies between order, delivery and invoice.
The AI understands the question in natural language and selects the right capability. The business logic itself stays defined and tested. Bridge combines the convenience of an assistant with the reliability of proven business logic.
Where this leads
Once you build capabilities instead of interfaces, you soon notice the same terms recurring. What exactly is an open purchase order? When does a delivery count as complete? Those questions lead to a shared domain model, the subject of the next guide.
Frequently asked questions
What is the difference between an interface and a capability?
An interface delivers data. A capability answers a business question completely and knows which conclusion the data actually supports.
Does every new question require new development?
No. A tested capability answers many variations of the same business question, regardless of how it is phrased.
Which capabilities does Bridge offer?
The catalog starts in procurement and invoice verification and grows process by process. We clarify which capabilities matter for your company in a first conversation.
Want to see what this looks like in your procurement? Request a demo