On instruction
You ask for a task; Pinnokio carries out the authorised actions.
How it works
From context
to action.
An instruction, a received document or an event starts a scenario within the scope you have authorised. Pinnokio combines understanding of context with deterministic processing for repetitive work.
The principle
Instruction, document or event
- Receive
- Understand
- Execute
- Approve and learn
Exceptions are presented to you; approved processing enriches the file's rules.
Four stages
- 1
Receive
Documents by email, Drive or portal; business data; bank statements; requests.
- 2
Understand
Company, period, file rules and expected processing.
- 3
Execute
The modules and controls suited to the scenario are triggered.
- 4
Follow and learn
Exceptions are presented; approved processing enriches the rules.
Three ways to start a job
On event
A received document or a deadline triggers a defined scenario.
With learning
The file's signatures and rules evolve with approved processing.
Modules, capabilities, scenarios: what makes it possible to do almost anything
Pinnokio is not a list of fixed functions. Modules give it the substance of your business, capabilities give it the actions, business knowledge gives it the rules, and scenarios ("skills") chain it all together according to your request.
Modules: the substance
Invoicing, accounting, fixed assets, contracts, projects, CRM and contacts, communication (email, Telegram), VAT, payroll, expense reports, products, stock and inventory.
See the modules and their availabilityCapabilities: the actions
Search the Internet, analyse files, create Excel, Word and PDF files, create charts, copy a table, review several documents, split and merge, prepare a fillable PDF, send for signature.
Business knowledge: the rules
Amending an invoice means checking its status, checking the period, applying the authorised correction. Reconciling the bank means comparing references, checking amount, currency and date, then matching or asking for clarification.
See a controls use caseScenarios (skills): the sequence
Contract: template, document, signature. Analysis: files, table, chart. Invoicing from a calendar, creating a project from a contract: a scenario combines several tools under your file's rules.
See the use casesA shared context
Each company has its own context: data, processes, organisation, rules and policies. A fiduciary firm has a Pinnokio on the firm's side and a Pinnokio on the client's side, each acting in its own environment.
See the fiduciary solutionChat from ChatGPT or Claude (MCP)Coming soon
Query Pinnokio from your usual AI assistant, using the MCP protocol.
See the MCP pageDepending on your profile: a path, concrete cases
You are a fiduciary
Mandates, rules per client, portal, cockpit: see how work is coordinated file by file.
Fiduciary pathYou are a CFO
An accounting employee who structures, statements to read, forecasts to look ahead.
Finance leadership pathYou run a business
From contract to invoice, CRM, projects, teams: see the work move forward.
Business owner pathProcessing factories
Much of accounting work looks alike from one business to another: extracting data, sorting, posting, reconciling. Pinnokio turns these into shared factories, to which adaptation to the client and to the country context is added. For repetitive work, it does not leave each operation to an isolated probabilistic generation: it relies on rules and learned signatures.
Invoices: signature first
The system looks for a known signature to identify the document. The associated rules cover the supplier or customer, the currency and amount ranges, VAT codes and rates, identified services, and the number and detail of lines.
Bank: history scoring
A scoring based on the history of posted movements suggests the accounts to use, notably when the client keeps its invoices and only sends its statements. Suggestions rest on rules and scoring, not on a language model alone.
The same foundation, adapted to each file
The first level (data extraction) is common. The client and the country are layered on top: suppliers, accounts, VAT, chart of accounts.
See the accounting moduleNew case: process, then learn
A document outside the known framework is handled in an adapted way. For example, a supplier offering a new service leads to the rules being enriched.
Controls, exceptions, approvals
Controls
Amounts, currency, period, VAT and action rights are checked according to the processing.
Exceptions
Situations outside the usual rules follow adapted processing, with intervention or approval depending on the case.
Approval thresholds
You define what moves forward on its own and what requires approval.
What Pinnokio does not promise
No guarantee of zero errors: Pinnokio describes its controls and submits exceptions. Identifying a signature with a high confidence threshold does not mean that the whole journal entry is correct at that level.
Frequently asked questions
Does Pinnokio use a language model for every operation?
Not for repetitive operations: they go through learned signatures and rules (deterministic processing). Understanding context is used to steer the work, to handle new cases and to talk with you.
How does Pinnokio learn?
Each approved processing enriches the file's rules: suppliers, debtors, habits and reconciliation methods. A new case is processed, approved, then learned.
Who defines what is approved by a person?
You do. Tasks move forward within the authorised scope; exceptions and decisions placed under approval go back to the authorised person.
Pricing
How much does it cost?
You pay as you go, in credits, with no mandatory subscription. Here is the order of magnitude.
- Supplier invoice processed
- 65 credits
- Bank transaction reconciled
- 35 credits
- Document routed
- 15 credits
- Assistant interaction
- ~3-5 credits
5'000 credits offered on sign-up, no credit card required.
See how it works on your own scenario
A business situation, your tools, your rules: the demo starts from your reality.