Inqom vs MyUnisoft: AI pre-accounting in France — how to choose 2026

Pre-accounting is routinely described as the least glamorous part of a firm's digital transformation — repetitive, invisible, and hard to sell to clients. Yet it is precisely where artificial intelligence delivers its most measurable gains. Inqom and MyUnisoft are the two names that come up most often when French accounting firms evaluate automation options, and they follow fundamentally different philosophies. Understanding those differences before you deploy saves considerable frustration later.

This article compares both solutions on objective grounds — positioning, architecture, functional coverage, and watch-points — drawing on what we observe in the bookkeeping and accounting review engagements carried out at our Paris practice. No precise pricing is given: both vendors quote by volume of files and activated modules.

Inqom (Visma group) automates accounting production end-to-end through agentic AI and an open architecture. MyUnisoft offers integrated cloud accounting that also covers practice management and client relations. The choice mainly comes down to your tooling strategy: do you want to assemble best-of-breed components, or centralise everything on one platform?

Pre-accounting covers every operation that turns source documents — supplier invoices, bank statements, expense reports, receipts — into accounting entries ready for review. It is the first link in the accounting production chain, and usually the most labour-intensive.

AI intervenes at several levels: optical character recognition (OCR) of documents, automatic categorisation of income and expenses, bank reconciliation, and duplicate detection. Gains vary with the regularity of document flows and the quality of rule configuration, but firms that have deployed these tools consistently report a significant reduction in manual entry time — time that can be redirected towards advisory work.

Inqom, part of the Visma group, positions itself as an end-to-end accounting production automation solution, from source document to financial statements. Its main differentiator is an agentic AI approach: rather than simply recognising individual documents, it aims to automate sequences of tasks without human intervention at each step.

The open "cockpit" model#

Instead of imposing its own tool chain, Inqom bets on interoperability. The solution connects with document capture tools, banks via open banking, document management systems, and other accounting software. This model suits firms that have already invested in an ecosystem — for instance a capture tool alongside their existing general ledger software — and want to preserve that investment.

What changes in practice#

• Posting rules learned on one file become reusable across similar files, reducing configuration overhead over time.
• AI-generated entries are presented to the accountant for validation; they are never imposed.
• The open architecture slots naturally into an existing supplier-cycle automation workflow.

Limitation to plan for#

Inqom's functional depth requires a significant upfront configuration effort. Posting rules must be defined, tested, and refined. A firm expecting immediate results without a run-in period is likely to be disappointed.

MyUnisoft presents itself as cloud accounting for firms and SMEs, but its scope goes well beyond pre-accounting. The platform also covers engagement management, time recording, and client relations through a dedicated portal.

Accounting production#

MyUnisoft automates the retrieval of bank statements and invoice collection. It can be fed by an external capture tool for optical recognition. Bank reconciliation and matching are built in.

Practice management — the structural differentiator#

This is where MyUnisoft structurally separates itself from Inqom:

• An engagement CRM: file tracking, workload allocation across the team.
• Automated time recording: useful for firms billing by time spent or tracking per-file profitability.
• A client portal: clients upload documents, view dashboards, and communicate with the firm without relying on email.

These features make MyUnisoft a full practice management platform, something Inqom does not cover natively.

Limitation to plan for#

MyUnisoft's integrated logic assumes adoption of the platform's ecosystem. A firm that wants to keep its own management tools, or that values composability, should probe the solution's real flexibility before committing.

Both solutions use quote-based pricing, typically calculated by active files and activated modules. What firms frequently underestimate is the total cost of deployment, which includes:

1. The software subscription (ask for a quote covering all relevant modules).
2. Initial configuration of posting rules and connectors.
3. Staff training (accounting assistants and chartered accountants alike).
4. A run-in phase: several weeks before reaching a satisfactory recognition rate.
5. Rule maintenance as tax rules evolve (new VAT rates, new expense categories).

Worked example. A firm managing 80 active files with an average of 60 source documents per file per month processes around 4,800 documents monthly. Without automation, at roughly 4 minutes per document (entry plus check), that is 320 hours of raw data entry per month. A 75% automation rate reduces this to approximately 80 hours of review and validation — a saving of 240 hours monthly. The return on a monthly software subscription becomes straightforward to calculate against an accounting assistant's hourly cost.

This illustration shows the method, not a guaranteed outcome. Real rates depend on document type, scan quality, configuration, and flow regularity.

A mid-sized Paris accounting practice serving SMEs and independent professionals had built its production workflow around a well-mastered capture tool and a long-established accounting package. The question on the table: migrate to an integrated platform (MyUnisoft style) or layer agentic AI onto the existing stack (Inqom style)?

The analysis surfaced two diverging priorities. Partners primarily wanted to cut data entry time. Staff wanted better visibility over file progress and time spent. The conclusion was to run both solutions in parallel on a limited portfolio before deciding. The decisive criterion was not the theoretical recognition rate quoted in the sales deck, but the rate measured on the firm's actual documents — mainly unstructured supplier invoices, photographed expense receipts, and multi-bank statements. Neither solution immediately dominated; the gap was in configuration effort and learning curve, not raw AI capability.

AI does not remove the accountant's review obligation#

This is the point most frequently glossed over in vendor presentations. AI proposes entries — it does not validate them. Accounting responsibility and signature of the financial statements remain the chartered accountant's. Review does not disappear with automation; it refocuses on higher-level anomalies. The engagement letter should formalise this division of roles explicitly.

GDPR and professional secrecy#

Both platforms process accounting data that can contain personal information — payroll details, bank account numbers, client contact data. Two obligations apply:

• Require a signed data processing agreement (DPA) from the vendor.
• Verify hosting: servers in Europe, ISO 27001 certification or equivalent.

The accountant's professional secrecy places additional confidentiality obligations on the firm's digital subcontractors. The CNIL is the reference authority on AI and GDPR compliance in France.

FEC and legal retention#

Whatever the platform, French accounting must produce a usable Fichier des Écritures Comptables (FEC) for tax audit purposes (art. L47 A of the tax procedures code). Source document retention is set at ten years (art. L123-22 of the Commercial Code). Verify that your archiving workflow — including any electronic vault — meets these requirements.

E-invoicing: the 2026-2027 deadline#

The French e-invoicing reform requires connection to an approved partner dematerialisation platform (PDP). The schedule: mandatory reception for all companies from 1 September 2026, mandatory issuance for SMEs and micro-enterprises from 1 September 2027.

For both Inqom and MyUnisoft, ask the vendor a precise question: is it itself a PDP, a dematerialisation operator (OD), or does it rely on a partner? The answer determines whether your production workflow will be compatible by 2027 without additional integration work.

In the engagements we manage, the real productivity gain from an automation solution rarely comes from the tool alone. It comes from the regularity of document flows (a client who uploads documents quarterly cancels most of the AI benefit), from document quality (a blurred photo of a till receipt defeats any OCR), and from the time invested in initial configuration.

Choosing between Inqom and MyUnisoft comes down to a strategic arbitrage between two visions of tomorrow's practice. Inqom suits firms that want to remain free in their tool choices and have the technical capacity to compose an ecosystem. MyUnisoft suits firms that want to simplify their accounting information system and manage their entire activity from a single interface. Neither vision is inherently superior: they reflect different strategies.

Our practical recommendation: test each solution on a real batch of documents (minimum 200 to 300 varied items), measure the recognition rate achieved and the residual correction time, and assess your team's configuration effort. A tool that performs flawlessly in a demo can prove time-consuming in production if posting rules are not properly tuned.

Updated 2026-06-14. This article is for information only and does not replace personalised professional advice. For your specific situation, consult a chartered accountant registered with the Ordre des Experts-Comptables.