AI assistants in day-to-day operations
A copilot that sits next to the document, works inside your permissions and hands back a draft with evidence — four everyday tasks from the warehouse, procurement and finance, and the line it will not cross.
- Published
- Author
- Konis Software
A warehouse operator is looking at a goods-receipt note and cannot see why a line refuses to close. A bookkeeper opens a posted entry and wonders why the invoice landed in box 8b of the Serbian VAT ledger. A procurement clerk holds an invoice that is one line larger than the purchase order. None of these three questions belongs on a separate “AI screen”. All three are asked where the work is — next to the document already open, in plain words, as if a colleague who knows where everything lives were sitting alongside.
That is the whole ambition of an assistant in operations: to be that colleague. What separates it from a chat window is three things you do not see at first glance. It sees exactly the rows you see — not one more. It is bound to the space you are working in, so in the warehouse it answers about stock, not payroll. And it never acts on its own: it hands back an answer with the documents behind it, or a draft you read, correct and release. A proposal, not a decision.
This piece is not about what AI is or where it is going; enough has been said about that. It is about four questions that actually come up during a working day — in the warehouse, in procurement, in finance — and about what an honest assistant returns for each, and what it refuses to do.
The assistant is bound to a space and to your permissions
The assistant has no account and no access rights of its own. It works in your context: if you cannot see a customer's ledger card, neither can it when you ask, because it asks with your eyes. It is also tied to the space you are in. A copilot opened over a receipt in the Warehouse space knows the warehouse context — document, item, location, lot — and is useful there. The same copilot will not compute payroll or open someone else's analytics, not because it cannot, but because that is neither your job on that screen nor your right. The narrow context is not a limitation; it is why the answer is correct.
Four questions from a working day
“Explain this posting”
A bookkeeper opens an entry posted from a construction-services invoice and does not understand why VAT was self-assessed and why the line went to box 8b instead of 8a. Rather than hunt for a colleague or leaf through the rulebook, they ask the assistant over that entry. The answer is not “that is how it is done”; it is: the supplier is liable for construction-sector turnover, so the reverse charge applies under the article cited, which is why the line sits in 8b. Alongside the explanation sit the posting scheme used and links to the invoice and the purchase order. The assistant changes nothing — it explains a record that already exists, in the language of the person looking at it.
“Find the receipt for this invoice”
The supplier invoice has arrived, but the clerk does not know which goods it came in against. They ask the assistant to find the receipt. It searches by purchase-order number, supplier, amounts and dates, and returns a candidate — a receipt with its number, a jump straight to the document, and a view of what matched: same supplier, same order, an amount that agrees line by line. If exactly one convincing candidate exists, it shows it as a proposal to confirm. If there are several — two receipts from the same supplier in the same week — it lists both and does not choose. Choosing stays with the person, because the person knows what the documents do not say.
“Has this already been entered?”
The most expensive error in incoming invoices is entering the same liability twice: the same invoice goes in twice and is paid twice. Before posting it, the clerk asks the assistant whether it is already in the system. It checks by the supplier's tax ID, document number and amount and returns an answer with evidence: yes, the same invoice is already posted under entry so-and-so — here it is; or no, nothing matches on those three fields. If the match is partial — same amount and supplier, different number — it says so as a suspicion, not a verdict, and leaves the person to compare. Here, “I cannot be sure” is a correct output, not a flaw.
“Draft a message to the supplier”
A delivery arrives one line short of the dispatch note, or an invoice is dearer than the agreed price. The procurement clerk needs to tell the supplier. The assistant drafts a message that cites the specific document and the specific discrepancy: order number, item, agreed and invoiced price, the difference. The message is a draft — the clerk reads it, adds the tone the relationship with that supplier calls for, corrects what needs correcting, and sends. The assistant does not send it. Composing the note is a tedious few-minute job the assistant reduces to reading, correcting and sending; the sending is a decision a person makes.
| Question | What the assistant returns | Evidence attached | What stays with the person |
|---|---|---|---|
| Explain a posting | The rule and scheme in plain language | Posting scheme, links to invoice and order | Nothing — or a correction if it disagrees |
| Find the receipt | A candidate receipt with a jump to it | Match on supplier, order and amount | Confirmation, or a choice among candidates |
| Check for a duplicate | Yes/no with the entry behind it | Match on tax ID, number and amount | Comparison when the match is partial |
| Message a supplier | A draft citing the discrepancy | The document and values it refers to | Tone, correction and sending |
Evidence and a jump to the source
What separates the assistant from a search box you cannot rely on is that every answer carries the record behind it and a path to it. Not “this invoice is probably a duplicate”, but “the same invoice is posted under entry 2026-4471, open it” — one click, without leaving the screen. A claim you cannot click and check is of no use in operations; it is a hint, and in finance you do not post or pay on a hint. So the jump to the source is part of the answer, not an extra you have to ask for.
- For a posting explanation: the name of the rule or scheme applied, and a link to the document the entry came from.
- For a found receipt: the document number and the fields it matched on — supplier, order, amount.
- For a duplicate check: the entry that posted the original, and the three fields that do or do not agree.
- For a supplier message: the document and the concrete values — agreed against invoiced — the text refers to.
What the assistant does not do
- It does not post or pay. It proposes a draft entry; it reaches the ledger only when a person confirms it.
- It does not send messages. It writes a draft; sending is a click a person makes, because a sent message cannot be recalled.
- It does not approve or exceed your limit. If you may not approve an amount, neither may the assistant in your name.
- It does not choose when several candidates are plausible. It lists them and stops; the choice carries a consequence, so it stays with the person.
- It does not answer without a source. If it cannot show the record behind a claim, it says it does not know rather than guess.
- It does not look past your permissions. A question about data outside your scope gets “that is outside your access”, not a number.
An assistant in operations does not need to be clever instead of you. It needs to bring the work ready for a single decision — and the evidence you make that decision on.
How NG One approaches it
The NG One assistant is not a separate product beside the ERP but a panel that opens over a document in the space you are working in — Warehouse, Procurement and suppliers, Finance and compliance. You ask in plain words, and it answers in your context and within your permissions: the same rows you would see, the same space you are in. Every output is a draft or an answer with a jump to the record behind it — a posting explanation leads to the invoice, a found receipt to the document, a duplicate check to the entry. Nothing is posted or sent without a person's confirmation.
The value of an assistant in operations is not measured by how clever it sounds but by how reliably it shortens the path from a question to a check. Explain the posting and show the scheme. Find the receipt and show what matched. Check the duplicate and show the entry. Draft the message and stop before sending. An assistant that works this way does not ask for trust — it hands over evidence, and leaves the decision to whoever is accountable for it.