Subscription
Pitaj duplo (Ask duplo) — AI assistant (beta)
Updated 30/10/2026
Pitaj duplo (Ask duplo) is the AI assistant inside the programme: you ask in plain language, and duplo finds your company’s data and explains it. The assistant never issues or sends anything, it writes to the books only what you confirm (the action card, below), and on SEF it neither fetches nor approves anything — it points you to the page of the programme where that is done.
Pitaj duplo is in beta: the assistant reads the company’s data and answers questions, and only proposes changes to the books as cards that you confirm (see “Actions with confirmation”). We monitor and refine the quality of answers — the thumbs below the answers (helpful / not helpful) help us.
Who can use it
- Plans: Kancelarija with the Accounting add-on (enabled or in trial) and Biro (Accounting is part of the plan). When Accounting on Kancelarija expires or is switched off, Pitaj duplo locks as well — the data stays.
- Roles: Super admin, administrator, member and accountant — but only those to whom the company owner grants access (see below). Technician: no.
- How it is enabled: from the Subscription → Add-ons card, with the “Activate” button — after the owner accepts the assistant’s terms of use (see below). Activation gives a trial credit; after that the credit is topped up on a pro-forma invoice (see “Credit and price”). Who in the team may use it is decided by the company owner per member (see below).
Who in the team may ask — access per member
Access to the assistant does not come automatically with a role. On each member’s card in Team the company owner (Super admin) chooses, in the Pitaj duplo (AI assistant) block:
- Does not use the assistant (default) — the member does not see Pitaj duplo; no company data is sent to the model for their questions.
- Questions only — the member may ask and receive answers over the data their role sees anyway; the assistant prepares no actions for them.
- Questions and actions with confirmation — the member may also confirm actions the assistant prepares; each one runs only after confirmation, within what their role may do.
The company owner always has full access. Access is always capped by the role: a technician has no assistant even if granted one, and an accountant gets nothing through the assistant that they do not see in the programme. Changing the role does not change the access; removing the member deletes it. An administrator sees the setting, only the owner changes it; every change is recorded in the team history. The default “no” is deliberate: company data goes to the model only for the people the owner has chosen.
Accounting agencies (Biro)
An agency on the Biro plan has one assistant for the whole team — under its own subscription and its own credit. Access for members of the agency team is set in the agency’s parent company (Team → member card) and applies in every client company where the team works; it is not changed in the client’s company.
- A company the agency opened (the client does not work in duplo): it is switched off for the assistant until the agency owner switches it on at Subscription → Clients (the “Pitaj duplo” button next to the company), ticking that they hold the client’s written authorisation for the company’s data to be processed by the assistant. The same button switches it off. Switching on and off is recorded in the team history of both companies.
- A company of a client who pays themselves (a linked company): the agency team may use the assistant over its data only once the owner or an administrator of that company gives consent — on their own Subscription page, in the Accounting agency card (“Allow the agency team”), consenting that the data the assistant reads is processed at Anthropic (USA and other countries) under the agency’s subscription. Consent is withdrawn in the same place; ending the link and taking over the company cancel it. The client’s own people buy the add-on for their own use like any company.
On the Clients page the agency sees for each company whether the assistant is switched on, or whether the client has given consent.
Credit and price
Pitaj duplo is not charged monthly: you pay for usage, in advance, as credit in euros. The credit balance is shown on the add-on card and above the conversation thread — it refreshes right after every answer; the month’s total usage is on the add-on card.
- Activation and trial. The company owner (Super admin) activates the add-on on the Subscription → Add-ons card — only after accepting the assistant’s terms of use (two tick boxes, see below); on the Kancelarija plan only while Accounting is enabled. Activation gives the company a trial credit (the amount is shown on the card; once per company). There is no limit in days: you can use the trial credit in a day or over six months.
- Top-up. When the credit is used up (or earlier), the owner chooses a top-up amount on the same card — from the smallest to the largest amount shown on the card (up to €100 in steps of 10, above €100 in steps of 50) — and receives a proforma invoice by email, in dinars at the NBS middle rate on the day of issue. The credit is added as soon as duplo records the payment; until then the open proforma invoice is shown on the card and can be cancelled. While one top-up proforma invoice awaits payment, another is not issued.
- What an answer costs. Each answer deducts from the credit its own price, which depends on the amount of work: how much data the assistant read and how long the answer is. A short answer usually costs a few cents, an answer that reads a lot of data up to a few tens of cents; how much was deducted shows in the credit balance above the thread. Not charged: an answer that did not arrive (interruption before the first word, timeout, failure on the provider’s side) and an answer the assistant declined to give.
- Reservation. Before a question the programme checks that the credit holds at least a small amount for one answer — while the answer is in progress that much is reserved, and afterwards the actual price is deducted. When there is no credit the assistant says so and points to the top-up.
- Validity. Every credit package (trial, payment, credit granted by support) is valid for 12 months from the day it is recorded; the oldest is used first. The unused part expires — 30 days before each package expires the owner receives an email. Purchased credit is not refunded or transferred, including when the add-on is switched off, the plan changes or the company is deleted.
- VAT. Amounts on the card exclude VAT; VAT on the top-up pro-forma depends on the issuer’s VAT status, as for the subscription pro-forma.
The credit belongs to the company: on Biro it is held by the agency’s parent company and used by all team members in all client companies; a client who pays for itself has its own credit.
Changing plans
- Accounting stays with Pitaj duplo. While Pitaj duplo is active on the Kancelarija plan, Accounting is not switched off at renewal without contacting us: a pro-forma with Accounting switched off is not issued — keep Accounting or contact us. When moving from Biro to Kancelarija, Accounting is enabled by ticking the box on the same renewal pro-forma.
- Smaller plan. A move to a plan that does not carry Pitaj duplo (Knjiga, Sveska) locks the assistant from the day of the move. The credit stays recorded and is valid until it expires — it is used again if you return to a plan that carries the add-on; it is not refunded.
Terms of use
Before activation the company owner (Super admin) accepts the assistant’s terms of use on Subscription → Add-ons with two tick boxes: acceptance of section 9a of the Terms and explicit consent that the company data the assistant reads to answer is processed at Anthropic (USA and other countries). Both boxes are required — without both the acceptance is not recorded and the add-on cannot be activated. The version of the text accepted (both parts together), who accepted it and when are recorded; a new version of the terms requires a new acceptance.
Switching it off
On the same card the company owner can click “Switch Pitaj duplo off now”: nobody in the company can use the assistant until the owner switches it on again. The credit stays recorded and continues to expire on its own schedule — it is a usage switch, not a cancellation. Switching on and off is recorded in the team history.
How to ask
The Pitaj duplo item at the top of the side menu (with an arrow next to it) opens the assistant in a new tab, so you ask in one tab and work in the programme in the other: links in answers (“open Invoices”) open the page in the programme tab, and Back to the programme returns to it. The assistant tab has its own shell: on the left the list of your conversations in this company (newest first, 30 at a time with a Load more button), search by title and by the text of your questions, + New conversation and “…” next to each conversation (Rename, Delete); on a phone the list opens with the Conversations button. At the top is the credit balance, in the middle the thread of questions and answers, at the bottom the question box with the Ask button underneath — the box stays at the bottom of the screen even when the conversation is long. If you switch to another company in the programme, the assistant tab reloads for that company when you return to it. While the assistant works, the steps appear above the answer (“Reading: Partner balances…”) — each step is one read of data from the programme. The Stop button interrupts the answer; an interruption before the first word of the answer is not charged.
- A question is sent with Enter (Shift+Enter starts a new line); on a phone or tablet Enter starts a new line and the Ask button sends.
- The Ctrl+K shortcut (⌘K on a Mac) opens Pitaj duplo from any page of the programme and first offers questions for the area you came from (from Bank statements about unmatched payments, from Received invoices about invoices awaiting a response, from Payroll about the payroll run…). On the assistant page itself the shortcut puts the cursor in the question box.
- The answer is in the language of the question (Serbian in Latin script, or English); amounts are in dinars, in Serbian notation.
- Links in the answer lead only to pages of the programme (e.g. Partner ledgers) and to the public documentation; there are no other external links.
- Next to every answer are two small thumbs (helped / did not help) — the rating does not go to the model and changes nothing automatically; in the beta it tells us where the assistant goes wrong, without the text of your question or the answer.
- You delete a conversation from the “…” menu next to its title (Delete); you can also rename it there. Only you see your conversations: other team members do not see yours, nor you theirs.
- A conversation remembers your rights from the moment it started (role, unlocked areas, price level). If the rights change — the super admin changes your role, the company changes its plan or add-ons — the old conversation is locked (marked “locked” in the list, the question box is closed) and you open a new one: history created under different rights is not sent to the model as context. A question the assistant rejects before accepting it (locked conversation, credit used up) stays in the box, so you do not type it again.
When something is missing (the add-on, the terms, per-member access, on Biro the client company being switched on or the client’s consent), the page shows the first thing to sort out instead of the question box — the same check stands before every question.
What the assistant can read
The assistant does not “look at” the database — it calls fixed readers of programme data, and only those you have access to (role, plan, add-ons). Every reader reads the same data as the corresponding page of the programme. In this version:
| Question | What is read | Required |
|---|---|---|
| “How are we doing this year? How much have we invoiced? Who are the biggest customers?” | the business overview as on the Overview page: invoiced, outstanding, quotes and orders pending, turnover by month, biggest customers; stock value only with the right to purchase prices | Overview |
| “Do we have partner X? What is its tax number, address?” | the partner register (name, tax number, registration number, address, company contact, customer/supplier roles) | Partners |
| “How much does service X cost? Do we have item Y?” | the item register — selling prices only when you may see them, stock with a plan that has inventory | Items |
| “What is in stock? Which items are negative?” | stock of goods, materials and products; warehouse value only with the right to purchase prices | Inventory |
| “Which invoices did we issue in September? Invoices for customer X?” | the document list by type, status, customer and period — only the types your role sees; the total as on the Overview (invoices and advance invoices plus, credit notes minus) | Documents |
| “What is on invoice RAČ-2026-71? Was it sent and paid?” | one document with its lines, SEF status and history (without addresses and IP) | Documents |
| “Who is late with payment?” | issued invoices past their due date without a matched payment, with days overdue (advance invoices have no due date — the advance has already been paid) | Sales documents |
| “What has not been posted? Anything to review?” | books status: unreviewed entries, items awaiting allocation from the suspense account, sources without an entry, the latest entry, the opening-balance cut-over — the same source as the For review page | Accounting |
| “Who owes us? Whom do we owe?” | partner balances from the books (customers, suppliers, advances) as of today | Accounting |
| “Which invoices of partner X are unpaid?” | open items of one partner as of a date, with due date and days overdue | Accounting |
| “Show the ledger card of partner X for 2026.” | the partner card by account for a period, with opening balance and running balance | Accounting |
| “How big are the costs in class 5? Are the books balanced?” | the trial balance for a period by class, group or account | Accounting |
| “What was posted to 553?” | the account ledger card for a period | Accounting |
| “Which payments are not matched?” | unmatched bank transactions (date, direction, amount, reference number; the partner only when the programme recognises it in the register — bank statement text is not sent) | Bank statements |
| “Which received invoices are awaiting a response?” | SEF e-invoices without a response, with days since receipt | Received invoices |
| “Did we pay invoice X of supplier Y?” | one received invoice from duplo’s database — amounts, payment, journal entry, lines (SEF is not called live) | Received invoices |
| “How much VAT for September?” | the VAT estimate for the period from documents in duplo — the same as on the VAT page, exchange rates from the table only | VAT (Knjiga and above) |
| “What is the KPO turnover this year?” | the KPO book for a year (totals and the latest rows) | KPO (flat-rate taxpayers) |
| “Which fixed assets do we have and what are they worth?” | the fixed-asset register with cost, accumulated depreciation and net book value as of a date | Fixed assets |
| “Has the September payroll been run?” | the status of payroll and other personal income runs — month, status, payment date, number of employees; no amounts and no names | Payroll |
| “Which clients have work pending?” | only in the agency’s parent company (Biro): counts per client company for which the assistant is switched on — unreviewed entries, unmatched transactions, invoices awaiting a response, overdue invoices | Biro |
| “How do I send an invoice to SEF? What is the chain rule for stock?” | a search of this public documentation — the answer from the chapter and a link to it | — |
| “What do I need to do for month end?” | a month-end checklist from the company’s data: postings, received invoices and the 15-day deadline, bank statements (unmatched and how far they are imported), drafts and overdue invoices, VAT deadlines, payroll run, depreciation — only the areas you see | — |
| “When is VAT due? What is the tax-free amount?” | the deadlines duplo works by (VAT, SEF, e-delivery notes, PPP-PD, eBolovanje) and the current legal parameters in the programme | — |
| “What is waiting for review and why was it posted that way?” | unreviewed automatic entries with their lines and an explanation of each account: posting rule, remembered partner account, the company’s default account or the programme default | Accounting |
| “What is sitting on the suspense account?” | transactions on the suspense account (“to allocate”) with a proposed account from the rules or from earlier allocations of the same payer | Accounting |
| “Which payments can be matched?” | unmatched transactions WITH proposed invoices by the same rules as the Bank statements page (reference number, document number in the description, amount and name, lump payment) | Bank statements |
| “Which posting rules do we have?” | the company’s and the agency’s rules with the number of applications, and rule proposals from repeated corrections | Accounting |
| “Which entries deviate from rule X?” | automatic entries in a period that the rule would change (as the “Apply” dialog on the Rules page) | Accounting |
| “Where do I find that in the programme?” | a link to a page of the programme you may open | — |
The assistant does not call SEF, the bank or the NBS live. Changes in the books it only proposes as a card with confirmation (next section); everything else — issuing documents, sending, approving received invoices — you do in the programme, and the assistant points you to the page. The VAT estimate, deadlines and explanations of postings are not tax advice — your accountant has the final word.
Actions with confirmation (posting under the accountant’s control)
The assistant can propose a change in the books, but never performs it on its own. When you ask for an action (“correct the account on entry NK-2026-00123 from 550 to 539”, “allocate the suspense account”, “match the payments that have a proposal”, “remember a rule for supplier X”), the assistant checks the data with the same rules as the programme and shows a card with exactly what would be written. You review it, untick a row if needed, click Confirm… and then Yes, execute — only then does the programme write the change, with the same core as if you had clicked the button on the corresponding page (same guards: closed year, opening-balance cut-over, entry status, rights). The outcome (what was written, links to the new entries) is written on the card by the programme; the assistant’s text is never proof that something was done.
| Action | What the card does | Required |
|---|---|---|
| Account correction on an entry | “old → new” account on all lines of that account in one entry: the original is reversed and a new manual entry with the same date and source is posted (like the Correct button); with the option to remember the correction as a posting rule for this company or for all agency companies | Accounting, edit |
| Allocation from the suspense account | up to 50 transactions from the suspense account to the accounts you confirm (tick per row); the proposed account comes from the rules or from earlier allocations of the same payer | Accounting, edit |
| Matching payments | up to 50 pairs transaction → invoices — only pairs from the deterministic proposal (exact reference number, document number in the description, same amount with a recognised name, lump payment of the same party) or when the total of the chosen invoices exactly equals the payment; the same as the “Confirm payment” button on Bank statements | Bank statements, edit |
| Reposting by rule | applying a posting rule to existing entries in a period (up to 50) — only entries that this very rule would change, like the “Apply” button on the Posting rules page | Accounting, edit |
| New posting rule | supplier or customer (by name or tax ID), purpose, text in the description and direction → account, for this company or for all client companies of the agency; applies to future postings | Accounting, edit |
Rules that apply to every card:
- Actions are available only to a member whose super admin granted “questions and actions” access (Team → member card) and whose role edits that area; the company owner always. With “questions only” access the assistant does not offer actions but says where they are done in the programme.
- A card is valid for 30 minutes; after that it has expired and you ask for a new proposal. At most three cards are open in one conversation — a newer one replaces the older.
- Before executing, the programme checks that the data has not changed since the proposal (someone reversed the entry or matched the payment in the meantime); if it has, the card fails without writing and you ask for a new proposal.
- The same action executed in the last 24 hours is not proposed again — the assistant says it has already been done. Posting rules are the exception: there the assistant checks whether the same rule already exists (and says so), and a rule you deleted can be requested again straight away.
- The confirm buttons become active a second after display, confirmation takes two steps and never reacts to Enter from the question box.
- The card stays in the conversation as a record: who confirmed or rejected it and when, what was on it and what was written. The record survives deletion of the conversation and of the account — it is kept with the company and is part of the company’s data export (Pitaj duplo module).
What the assistant still does not do: it does not issue documents, send to SEF or by e-mail, approve received invoices, delete anything, change partners, items, the accounts and sub-accounts of the chart of accounts or settings (posting rules are written only through a card you confirm), or work with payroll or personal data. For those it points you to the page in the programme.
What is sent to the model and what is kept
- The model (Anthropic, USA and other countries — see the terms) receives your question, a short description of the company (name, VAT status, plan, date) and the results of the readers the assistant calls. Before sending, the programme masks personal identification numbers, bank accounts of individuals and the names of employees and income recipients from the registers; bank statement text (descriptions, names of unknown payers) is not sent. Individual salaries, sick leave and data about individual persons are not among the readers — the payroll reader gives only the month, status and number of employees.
- duplo keeps the conversations (questions and the text of answers), your ratings and usage per company (the amount of processing and the price of each answer — for the credit). Only you see a conversation; it is deleted when you delete it, when your account is deleted or when the company is deleted.
- Action cards (the proposal, who confirmed or rejected it and when, the outcome) are kept with the company as evidence — also after the conversation or the account is deleted; they disappear only with the company.
- Under its commercial terms Anthropic does not train models on this data and deletes it after at most 30 days, except content its automated systems flag for breaches of its usage rules (up to two years) — details in the terms (9a, P6a).
What the assistant never sees
The assistant’s tools do not read the tables with personal data, so that data cannot leave the database — regardless of what is in them:
- the JMBG, bank account, address, email, date of birth and contracted pay of employees (the Employees register);
- payroll calculations per employee (gross, net, taxes, contributions, deductions) and payslips — the payroll reader gives only the month, the status of the calculation, the payment date and the number of employees;
- recipients of other personal income (JMBG, account) and amounts per recipient;
- sick leave from the eBolovanje portal;
- travel-order expenses and calculations;
- SEF and SEO keys, passwords and member accounts.
The books are a different matter: the trial balance and the account card show the amounts on the payroll accounts (52x, 45x) like any accounting report — totals per payroll run, not per employee, but in a company with one employee that is their salary. If you do not want that, do not give assistant access to members who should not see the books.
Names of employees, income recipients and travellers from the registers are replaced with a placeholder in every text (posting description, note) before sending, account numbers are shortened to the last four digits, and a 13-digit number with a valid JMBG check digit is replaced with a placeholder. Bank text from statements is not sent to the model; descriptions of statement, other-income and travel-order postings go without text (“statement transaction”, “travel order”). Verified on 2026-10-29 on test companies with fictional employees: in 91 requests to the model there was no JMBG, employee name, salary amount or account number. Your question goes to the model exactly as typed — so do not enter JMBGs, account numbers or employees’ personal data in questions.
Export and deletion
In the data export a company that has the add-on — or already has data in it — gets the Pitaj duplo module: assistant settings, accepted terms, credit packages with their use per answer, usage per answer, and action cards (who confirmed what and with which outcome). Conversations with the assistant and answer ratings are not part of the company export — they belong to the user who held them and arrive in that user’s My data (My account → My data: conversations per company and the text of questions and answers).
Conversations are also deleted without your request, because they are tied to the access under which they were created: when you leave a company’s team or are removed, when the super admin lowers your assistant access to “no”, when the agency switches Pitaj duplo off for a client company (all conversations in it), when a company withdraws consent from the agency team or ends the link with the agency (the agency team’s conversations in that company) and when the agency takes over a company. Deleting the company deletes the add-on’s data and all conversations of its members in that company, deleting the account deletes that user’s conversations; the record of accepting the terms stays with the company while it exists (with the name and address of the person who accepted, as proof of the contract).