Solution · By software
Your clients’ books and payroll live in a3. And someone is still posting invoice by invoice inside a3.
a3innuva Contabilidad, a3asesor Eco, a3ERP and a3innuva Nómina run your books, your ERP and your payroll —but the client’s invoice lands as a PDF in an inbox, someone posts it entry by entry, the bank gets squared line by line, and the tax filings get prepared by reviewing company after company. On top of a3’s APIs and connectors we build the AI that does that mechanical part on its own.
The problem
a3 gives you the software. What it doesn’t give you is someone to post your clients’ invoices.
- The client’s invoice lands in the inbox as a PDF —or in a shared folder, or over WhatsApp— and someone opens it, reads it and posts it into a3 with its date, its base, its VAT and its account.
- Bank reconciliation gets done line by line inside a3, even though the statement is already downloaded and the pattern repeats month after month.
- Before every quarterly filing there is a week of squaring: someone reviews company by company what is missing, what doesn’t add up and which client still hasn’t sent the invoices.
- The same task repeats client by client: same entries, same accounts, same criteria, keyed by hand into every company you keep.
Cost of staying the same
The cost doesn’t show up on the software invoice: it shows up as skilled people acting as a keyboard between the PDF and a3. And it lands at the worst moment, because the load keeps climbing: in Spain, 95% of advisors say regulatory changes increase their workload and regulatory overload is the sector’s top challenge for 64%, while 74% point to a shortage of qualified profiles to hire. The bottleneck is no longer the software: it is that there are no hands, and the ones there are get spent posting invoices. Source: [Barómetro de la Asesoría 2026](https://www.wolterskluwer.com/es-es/news/barometro-asesoria-2026-retos-despacho-profesional), Wolters Kluwer Tax & Accounting España, 30 June 2026 (Spain data).
The solution
An AI layer on top of a3’s APIs and connectors that posts, reconciles and squares on its own
- 1We map with you which parts of your a3 eat the hours: invoice capture and posting, bank reconciliation, pre-filing squaring, or the push from email and Excel. And which clients hurt most.
- 2We connect through a3’s APIs and connectors —depending on your product: a3innuva Contabilidad, a3asesor Eco, a3ERP or a3innuva Nómina— with credentials scoped per company. The AI reads what comes in —an invoice PDF, a statement, an Excel row— and leaves the entry inside a3 with its account, its VAT rate and its criteria, without anyone typing.
- 3We automate the squaring and the cycle: the bank transaction gets proposed already reconciled, the missing invoice gets chased from the client who owes it, and before the filing you get a list of which company is ready and which is not, instead of finding out by reviewing them one by one.
- 4We leave it measured and with a safety net: what % of invoices post clean without intervention, which borderline ones escalate to a person, how much squaring time per company drops, and how many mismatches show up versus the previous manual process.
What changes
What you stop losing
The invoice stops being posted by hand: it enters a3 through the API with its account and VAT, instead of going from PDF to keyboard entry by entry.
Mechanism
Squaring stops being the week before the filing: reconciliation and posting run every day inside a3, and what is missing shows up on the 5th, not the 18th.
Mechanism
The same task stops repeating client by client by hand: the same flow runs across every company you keep in a3, with its own rules, and the hours go back to advising instead of typing.
Mechanism
What we measure: % of invoices posted without intervention, accuracy on account and VAT rate, squaring time per company before the filing, and mismatches versus the previous manual process.
What we measure
Spec sheet
- Work it removes
- having the firm act as the keyboard — posting invoices, reconciling the bank and squaring company by company inside a3
- Typical setup
- 2–4 weeks
- Input
- whatever reaches the firm: an invoice PDF by email, a bank statement, an Excel row, a document the client uploads
- Output
- the data dropped inside a3: a journal entry with its account and VAT rate, a reconciled transaction, a squaring report of what is still missing per client
- Works with
- a3innuva Contabilidada3asesor Ecoa3ERPa3innuva Nóminaa3Marketplace
- Can connect to
- Your a3 install (a3innuva Contabilidad, a3asesor Eco, a3ERP)The email, folder or portal your clients’ invoices come in throughThe bank statement and the Excel files your data hops through by hand today
- What we measure
- % of invoices posted without interventionaccuracy on account and VAT ratesquaring time per company before the filingmismatches versus the previous manual process
- Good fit for
- accounting firms and companies already running their books, ERP or payroll on Wolters Kluwer a3 that want to remove manual invoice keying and client-by-client squaring
- Not a fit for
- processes outside a3, decisions that need case-by-case tax judgment, or firms that want to switch software before automating
Frequently asked questions
In scope, not in ambition. Wolters Kluwer is putting AI inside its products —in June 2026 it launched a3innuva Nómina Expert AI, an agent embedded in the software to reach verified payroll information and automate processes— and that works well for what a3 already knows: its own domain, its own data, its own flow. What it does not cover is the half of the work that happens BEFORE a3 and OUTSIDE a3: the free-text PDF landing in the firm’s inbox, the client who sends invoices over WhatsApp, the Excel nobody normalised, the cross-check between what is in a3 and what the client has not sent yet. That is where our layer comes in. It is built on top of a3 and its AI, not instead of them. Source: Wolters Kluwer launches a3innuva Nómina Expert AI, Wolters Kluwer, 10 June 2026.
No, and if anyone proposes that as a prerequisite, be suspicious. We work on your a3 install as is —a3innuva Contabilidad, a3asesor Eco, a3ERP or a3innuva Nómina—, connecting through its APIs and connectors with credentials scoped to what is needed. Your entries, your accounts and your criteria stay where they are; the AI slots into the repetitive steps and leaves the data inside a3. You keep opening the same a3 as always, just with the posting already done. If some module or filing of yours is closed and has no connection path, we spot it in the first week and tell you the exact bridge before billing you anything.
That is the right question and it is the one that decides whether this is usable at all. Every company you keep stays isolated: the flow runs separately for each one, with its own credentials and its own rules, without mixing data between clients. Every action is traced —which entry the AI proposed, on which document, and who approved it—, which is what you need if a client asks or if there is a review. The models are used via API under contracts that exclude training on your data, and if your client base requires it, we deploy in private mode. Your data stays in your a3.
You assume it will and you design for it, instead of promising it won’t. It starts in propose mode: the AI prepares the entry and someone at the firm approves, the same way you review a junior’s work today. With accuracy measured by case type —this recurring invoice from this supplier of this client is already nailed— you release autonomy where the numbers justify it and keep it on propose where they don’t. Anything borderline always escalates: if the document is illegible, the supplier is new or the amount falls outside the pattern, it does not invent, it flags. The tax judgment stays yours; what we remove is the typing.
Yes, and the approach barely changes: instead of repeating the flow per client, you repeat it per legal entity or cost centre. Supplier invoice capture, bank reconciliation and the push from email or Excel into a3ERP are the same mechanical work. What does change is the order of priorities —in a company the purchasing cycle and the monthly close usually hurt more than filing preparation— and we set that in the first-week mapping, before building anything.
Want it running in your business?
You’ve pinned the problem. We ship the fix and leave it measured.