TEKAI
TEKAI · Trust documentation

TEKAI Security & Architecture

TEKAI connects approved AI interfaces and automation workflows to SAP Business One so approved users can ask questions, receive reports and initiate controlled business actions in natural language. Access is provisioned for the users you approve, every question and action is logged, and it is deployed against your environment — with the specifics documented for every customer in a security workbook before go-live.

The four fears

Every AI-on-ERP conversation has the same four fears. Here they are, answered with architecture.

1. “Will our data leave our control?”

No — by architecture. You bring your own AI subscription, so data moves under your own provider agreement and DPA, not ours. TEKAI runs on per-client isolated servers — no shared tenants — and only the data needed to answer the specific question you asked reaches the model. Never a database dump, never a standing sync.

2. “Will the model train on our data?”

No. TEKAI is grounded, not trained: when you ask a question, the relevant records are retrieved from SAP Business One at that moment, used to compose the answer, and that is the end of their journey. Retrieval reads your data to answer you; training would absorb it into the model — TEKAI does the first and never the second. Your business data is not used to train AI models.

3. “Can the AI change our records?”

Not unless you decide it can. TEKAI is read-only by default. Write actions — creating an order, posting an expense — are enabled per deployment, confirmed by the user before posting, and land in SAP Business One as normal auditable transactions.

4. “Will we know who did what?”

Yes. TEKAI inherits your SAP Business One user authorisations rather than creating a parallel permission set, access is provisioned only for users you approve, and every question, answer and initiated action is logged with user, timestamp and scope — reviewable by your administrators and exportable for audits.

Architecture

Three layers, one controlled path to your data.

AI assistants never touch the database directly. Every request flows through the TEKAI connector, which enforces identity, scope and logging before anything reaches SAP Business One.

LAYER 1 · WHERE PEOPLE ASK
AI interfaces

Claude, ChatGPT, Perplexity, the embedded co-pilot inside SAP B1 screens, and WhatsApp delivery — only interfaces approved for your deployment.

LAYER 2 · WHERE CONTROL LIVES
TEKAI connector

Authenticates approved users, translates questions into governed data requests, and logs every question and action for review.

LAYER 3 · WHERE DATA STAYS
SAP Business One

Your live database — SQL Server or HANA, cloud or on-premise. Data is read for answers and written only through controlled, auditable transactions.

Answers come from live queries at ask-time — your data is not used to train AI models.
Controls

Permissions, audit and action control.

Approved-user access

TEKAI access is provisioned only for the users you approve, configured with your administrators at deployment and recorded in the security workbook.

Audit trail

Every question, answer and initiated action is logged with user, timestamp and scope — reviewable by your administrators, exportable for audits.

Controlled actions

Read-only by default. Write actions — creating an order, posting an expense — are enabled per deployment, confirmed by the user before posting, and land in SAP Business One as normal auditable transactions.

Custom AI behaviour

Assistant behaviour is tailored to your business processes and policies — what it may answer, how it phrases numbers, which exceptions it escalates.

Supported environments

Deployed against your SAP Business One — not a replacement for it.

Database
SQL Server and SAP HANA
Hosting
SAP B1 Cloud and on-premise installations
Existing systems
Works on your current SAP Business One installation — no reimplementation required to enable AI
Version matrix
Confirmed for your exact SAP B1 version and patch level during the pre-deployment assessment
The deployment security workbook

Hosting location, encryption in transit and at rest, authentication method, data-retention windows, connected AI providers and role scopes are documented per customer environment in a security workbook, reviewed with your IT team before go-live. Ask for the template on the review call.

Due diligence

Twelve questions to ask any AI vendor — including us.

Take this list into every evaluation. Our answers are on this page; ask for theirs in writing.

  1. Whose contract does our data move under — yours or ours?
  2. Is the model trained on our data, ever, in any form?
  3. Is our environment isolated, or shared with other customers?
  4. What exactly is sent to the model for a single question?
  5. Can the system write to our ERP, and what confirms a write before it posts?
  6. Does it inherit our existing B1 user authorisations, or create a parallel permission set?
  7. Is every question and action logged, and can we export that log?
  8. Which region does processing occur in?
  9. What is the maintenance cost line, in writing?
  10. What happens to our configuration if we cancel?
  11. How long does setup take on a live system, and does it require downtime?
  12. Can we speak to a reference customer in our industry and region?

If a vendor cannot answer the first six clearly, the conversation is over.

Security questions, answered

What IT teams ask before saying yes.

Does TEKAI train AI models on our data?

No. TEKAI answers by querying your SAP Business One data live at the moment a question is asked. Your business data is not used to train AI models. Provider-level data handling for the AI interfaces enabled in your deployment is documented in your security workbook.

Who can access TEKAI, and how is it controlled?

TEKAI access is provisioned only for the users you approve, configured with your administrators at deployment. Every question, answer and action is logged with user and timestamp, and the access setup for your environment is documented in the security workbook and reviewed with your IT team.

Which actions can TEKAI automate?

Reporting and digests (including WhatsApp delivery), document capture with OCR (receipts and bills to postings), order creation by voice or chat, alerts on exceptions, and predictive analytics such as stock-shortage and cashflow forecasting. Write actions are enabled per deployment, confirmed by the user before posting, and land in SAP Business One as normal auditable transactions.

Which SAP Business One versions are supported?

TEKAI deploys against SAP Business One on both SQL Server and HANA, cloud or on-premise, on your existing installation. Your exact version and patch level are confirmed during the pre-deployment assessment — enabling AI does not require reimplementation.

What are the deployment and pricing options?

TEKAI is scoped to your environment — interfaces enabled, roles, automations and hosting — and priced accordingly on the demo call. Setup on a running SAP Business One system is typically completed within a day, with the security workbook reviewed before go-live.

Business Transformation

Put your IT team in the room.

A 30-minute security review call: architecture walkthrough, the workbook template, and TEKAI running on scenarios from your own operation.

Built on SAP Business One
Technology with Return on Investment.
Book a live demo