L.U.C.A.
An agent you talk to. Ask it something and it answers from the real ledger; ask it to do something and it does it — through the same procedures the product runs on, as you, with your permissions, and with a preview before anything irreversible.
What it includes
Ask
- Answers derived from your posted books, not from a summary written last night
- Reads only what your own permissions allow, and says so plainly when they do not
- Cites the documents behind the answer
- Runs any of the built-in reports and reads you the result
Show its work
- Streams as it goes, so you watch it think rather than wait at a spinner
- Every tool it called is listed, collapsed, for when you want to check
- Drop in a photo of an invoice and it reads it before drafting anything
- Conversations are kept, so you can come back to what it did last week
Act
- Create an invoice, a bill, a payment, a contact, an item — described in a sentence
- Reconcile a bank line, match a transaction, apply your rules
- Request an absence, submit something for approval, send a signature request
- Post, void, file, settle, dispose — always behind a preview you confirm
Ask
- Answers derived from your posted books, not from a summary written last night
- Reads only what your own permissions allow, and says so plainly when they do not
- Cites the documents behind the answer
- Runs any of the built-in reports and reads you the result
Act
- Create an invoice, a bill, a payment, a contact, an item — described in a sentence
- Reconcile a bank line, match a transaction, apply your rules
- Request an absence, submit something for approval, send a signature request
- Post, void, file, settle, dispose — always behind a preview you confirm
Show its work
- Streams as it goes, so you watch it think rather than wait at a spinner
- Every tool it called is listed, collapsed, for when you want to check
- Drop in a photo of an invoice and it reads it before drafting anything
- Conversations are kept, so you can come back to what it did last week
An agent with hands
It can do the work. That is exactly why it asks first.
Most assistants bolted onto a business system can read. This one can write, post, file and void — which changes what the safety argument has to be. It is not a tone of voice or a careful prompt: it is the same permission checks, the same procedures and the same audit trail the rest of the product uses, plus a rehearsal before anything that cannot be taken back.
What it can reach
The ledger
Accounts, journal entries, trial balance, income statement, balance sheet, account balances.
Sales and purchases
Invoices, bills, orders, their simplified flavours, and the customers and suppliers behind them.
Money in and out
Customer and supplier payments, listed or created.
The bank
Unmatched lines, auto-matching, reconciling to a document, excluding a line, applying your rules.
Tax and AEAT
Settlements and the Modelo 303 lifecycle: create, recompute, file, void.
Fixed assets
Capitalise, revalue, transfer, dispose, and run the monthly depreciation.
People
Absences, balances, accruals, and the approvals that gate them.
Stock
Warehouses, stock moves, adjustments and transfers.
Loans
Create, activate, record a repayment, accrue the interest, void.
Signatures and approvals
Raise a signature request, submit for approval, act on one, recall your own.
Reports
Discover the built-in reports and their parameters, then run one by name.
And everything else, by name
Whole areas have no dedicated tool — the CRM, most of HR, documents, portals, admin. It browses the catalogue of business procedures, asks one to describe its arguments, and calls it.
It acts as you, not as an administrator
Every call carries your identity into the database, so row-level security and your permissions decide the answer. If your role cannot see payroll, neither can the assistant while you are the one asking — and it tells you which permission is missing instead of quietly returning less.
Irreversible things are rehearsed first
Posting, voiding, filing, settling and disposing all default to a dry run. That call does not execute: it returns a preview and a one-time token. Committing means calling again with that exact token — so the agent physically cannot post something it has not shown you.
Creating a document hands you a filled-in form
Ask for an invoice and you get the invoice form, populated, on screen. You check the lines, the tax and the customer and you save it. The draft is the deliverable — the agent does not post it behind your back.
Photograph the invoice, skip the typing
Attach a document and it is read before the conversation continues, so what comes back is a draft with the supplier, the date, the base and the tax already in it rather than a request for you to type them.
A budget that stops before the work starts
Usage is metered per organisation and checked before a single token is spent, not billed after the fact. The CRM’s AI has its own separate pool, so neither surface can starve the other.
It can be wrong, and the screen says so
The disclaimer sits under the chat box permanently rather than in a first-run dialog nobody rereads. Everything it produces is reviewable before it counts: a draft you save, a preview you confirm, a tool list you can open.