Groups run multiple SAP Business One companies; questions span all of them. In this demo, TEKAI answers across companies in one conversation — consolidated receivables, inter-company positions, group-level stock — without exports or spreadsheet stitching.
If you run more than one legal entity on SAP Business One, you know the routine this replaces. Each company is its own database, so any question that spans them starts with someone logging in twice.
Every group question costs the same toll: total outstanding across entities, group stock of one item, who owes whom internally — each one means an export per company and a spreadsheet to merge them, converting currencies by hand along the way.
The toll isn’t only effort; it’s staleness. The answers age while they’re being assembled. By the time the merged sheet reaches the group CFO, the receivables have moved, the stock has shipped, and the inter-company position has changed. So group-level visibility becomes a month-end exercise — not because the questions only matter monthly, but because answering them costs too much to do daily.
And multi-entity structures are normal long before a business feels large: a trading arm and a manufacturing arm, an India operation and an overseas subsidiary, a new venture kept in its own books. SAP Business One handles each entity cleanly — it’s the questions that span entities that have always paid the tax.
On a demonstration database with multiple companies — an India company running in rupees and a US company running in dollars — one conversation produces group-wide answers. Receivables consolidate across entities and currencies into a single view. Item availability reads across every company’s warehouses, so “how much of this item does the group hold” is one question, not one per entity. Inter-company balances are stated both directions — what each company owes the other, from each side’s books.
Follow-up questions drill back down: the group number decomposes into per-company detail on request, each entity in its local currency. The demo also goes beyond tables — a customer ageing dashboard, with a company selector that switches between a single entity and the whole group rolled up, described in a sentence and built live in the chat.
Every figure comes from a demonstration database, not customer data. On your own system, the same conversation runs across your own entities.
That is the working definition of multi-company in TEKAI: you don’t configure a consolidation, you ask for one. When cross-company questions become as cheap as asking them, group-level visibility stops being a month-end exercise and becomes a daily habit — the same question the CFO asked at quarter-close is available any Tuesday morning, current to the minute.
Cross-company reach is scoped like everything else in TEKAI: a group CFO sees the consolidation; a company accountant sees their company. The AI’s breadth is exactly the user’s authorisation, no wider — connecting a second company to the conversation never widens what any individual user is allowed to read.
That boundary is what makes the pattern adoptable in a real group. Multi-entity structures usually exist precisely because access should differ between entities; an AI layer that flattened those walls would be a non-starter. TEKAI inherits them instead (/tekai/security/).
Multiple SAP Business One companies (SQL or HANA) · TEKAI priced per company — ₹5,000/company/month India, $150 global · your own AI subscription (Claude, ChatGPT or Perplexity) · permission-scoped access, nothing trained on your data (/tekai/security/).
Yes — pricing is per company; cross-company questions work across the companies that are subscribed.
Consolidations state their currency and can present in a chosen reporting currency — in the demo, two companies running in rupees and dollars land in one table converted to system currency.
Yes — both-direction positions are the classic question for this pattern: who owes whom internally, stated from each side.
No — it’s operational consolidation on demand. Statutory consolidation remains your accounting process; this answers the day-to-day group questions that can’t wait for it.
New to the category? Start with the overview: AI for SAP Business One, explained.
Update, August 2026: TEKAI now also works with Gemini, Microsoft Copilot, and Grok.