Yetkin Assistant connects to permitted tools, not to your database; everyone gets answers only from what they are allowed to see. Tools that take action show a summary and wait for your approval. Personal and financial data is not sent to the AI model; assistant actions are written to a record that cannot be altered.
A bank teller doesn’t walk into the vault; they carry out the transactions they are authorised for, by the rules and with your signature. Yetkin Assistant works the same way.
Related page: See the solution page
The tools the assistant uses are defined in an MCP (Model Context Protocol) layer: 29 tools, four risk classes, an approval ticket and a second approval where needed. Adding a new AI use means adding a new tool, with its rules, to this layer.
How we do it: A safe step into AI on an MCP foundationThe end-of-day Z report from new-generation tills comes into Portal as the till declaration closes and sits next to ERP sales and the cashier’s declaration. Differences show up in colour on accounting’s control screen.
How we do it: New-generation tills and the end-of-day Z reportAt day end the cashier declares cash and card totals. Portal compares the declaration with ERP sales, the Z report and bank movements; every closed declaration goes to the store manager and area manager for approval, and on to head office accounting for checking. In a multi-store cosmetics chain, a till difference is discussed the same evening, not the next morning.
How we do it: Cashier declaration and instant till controlWe’ll walk through this flow using your own stores, roles and systems.
About cookies. This site uses only what it needs to work. With your consent we also collect visit statistics with Google Analytics to improve the site; we do not use advertising cookies. Details: Cookie Policy (in Turkish).
