IRPEA : Intelligent Research, Programming & Engineering AI

Management software, written to measure.

IRPEA writes management software and artificial intelligence systems, and works on two fronts: bespoke developments for companies whose current tooling does not cover a need they have, and the publishing of its own management suite, the IRPEA ERP.

9
Areas covered
44
Services described
12
Standards implemented
112
Technologies
IRPEA

Our practices9 practices, one point of contact.

01/09Artificial intelligence

We integrate language models into production applications, where the difficulty is not the demonstration: it lies in the traceability of the answers, the cost per request, the response time and the behaviour of the system when the model is wrong, knowing that an assistant answering without citing its source does not reach production at a customer subject to audit.

6 services describedView practice

Auto-rotating · use the arrows to browse the practices

What we do

Nine areas of expertise, and what they cover.

01

Artificial intelligence

  • Claude
  • Anthropic
  • Gemini
  • OpenAI
  • Python
  • TypeScript

We integrate language models into production applications, where the difficulty is not the demonstration: it lies in the traceability of the answers, the cost per request, the response time and the behaviour of the system when the model is wrong, knowing that an assistant answering without citing its source does not reach production at a customer subject to audit.

  • Business agents and assistants connected to the information system
  • Retrieval-augmented search over your documents (RAG), with source citation
  • Structured extraction: invoices, payslips, contracts, receipts
  • Classification, summarisation, translation, speech recognition
+ 2 more services on the full pageRead the full page

Auto-rotating · use the arrows to browse the areas

A project

From the first conversation to the warranty.

Durations hold for a medium-sized project; they are indicative and adjusted at costing, depending on the state of your existing system.

0145 minutes

First conversation

Your context, what the current tool does, what is blocking, with no commitment whatsoever.

023 to 10 days

Scoping

Reading of the existing system, interviews with users, drafting of the scope and costing by work package, all invoiced then deducted from the project if it goes ahead.

03In two-week cycles

Development

A usable version at the end of each cycle, on a staging environment you have access to at all times.

041 to 3 weeks

Acceptance

Your users test on their own data, fixes are included and new requests are costed separately.

051 to 5 days

Go-live

Data takeover, switch-over, close monitoring during the first week.

063 months

Warranty

Correction, free of charge, of any deviation from the delivered scope.

Deliverables

What you receive

The list is the same on every project, whatever its size, it appears in the quote, and its absence at delivery is grounds for withholding the balance.

The source code

In your Git repository, with the complete history of changes.

The tests

Runnable with a single command, they describe the expected behaviour and act as a safety net during later changes.

The operations documentation

Environment variables, deployment procedure, restoration procedure.

The data schema

Table structure and versioned migration scripts.

The credentials

Hosting, database, third-party services — opened in your name, not ours.

A handover session

A walk through the architecture with your teams, questions included.

Ways of working

Four ways of working together

01Firm price, payment milestones

Fixed price

Who leads
IRPEA, on a written scope
Suited when
Well-defined need, result describable in advance
Limit
Any change of scope goes through an amendment
02Days consumed, monthly statement

Time and materials

Who leads
You, at the agreed pace
Suited when
Shifting priorities, team reinforcement
Limit
The budget depends on duration, not on a result
03Per work package or per day

Subcontracting

Who leads
Your project management
Suited when
Agency, IT services firm or software vendor needing a technical work package
Limit
We do not hold the end-customer relationship
04Monthly fee, major changes excluded

Maintenance

Who leads
Shared, under an annual contract
Suited when
Application in service to fix and extend
Limit
Assumes access to the code and a staging environment
Latest work

Platforms in service.

All are public and can be visited; projects covered by a non-disclosure agreement do not appear on this page.

IRPEA

www.irpea.com/erp

Online multi-company management suite: accounting under the French general chart of accounts, electronic invoicing, payroll and social declarations, sales, purchasing, inventory and production, spread over more than sixty modules.

React 19Next.jsTypeScriptTursoVercelIA

RetailSuit

www.retailsuit.com

Year-end rebate and financial analysis platform for retail, with computation of commercial agreements and reporting per banner.

ReactNext.jsNode.jsTypeScript

Keywork

www.keywork.fr

Job search platform: job postings, applications, matching between recruiters and candidates.

ReactNext.jsNode.jsTypeScript

Indawords

www.indawords.com

E-book sales platform, from the catalogue through payment to the reader’s library.

ReactNext.jsNode.jsTypeScript

EasyCofounder

easycofounder.com

Co-founder matching platform: profiles, complementary skills, introductions.

ReactNext.jsNode.jsTypeScript
In-house product

The IRPEA® ERP

A complete management suite, developed and maintained by the company: accounting under the French general chart of accounts, electronic invoicing, payroll and social declarations, sales, purchasing, inventory, production, multi-company consolidation; usable by a business on its own as well as by an accounting firm managing its client portfolio.

It also serves as a test bench: in September 2026, three successive audit campaigns covered payroll, the chaining of declarations, then accounting, each producing fixes and non-regression tests.

13
modules
807
capabilities
12
standards
Software base · current state
5,783
automated tests
0
failure

A failed test blocks the delivery, and this figure is recorded by hand after the checks have run; it is not recomputed on display.

The latest updates

Shipped and running in the ERP; each page of the website has the details (in French).

Formats and standards implemented
PCGAccounting

French general chart of accounts

ANC regulation 2014-03

FECAccounting

Accounting entries file

Art. A47 A-1 LPF

L123-12Accounting

Mandatory accounting books

Art. L123-12 C. com.

EN 16931Tax

Factur-X electronic invoicing

European standard EN 16931

CA3Tax

VAT return

Art. 287 CGI

LiasseTax

Corporate tax return package and result

Forms 2050 to 2058

NEODeSSocial

Nominative social declaration (DSN)

DSN Phase 3 technical specification

PASSocial

Withholding of income tax at source

Art. 204 A CGI

RGPDData

Data protection (GDPR)

Regulation (EU) 2016/679

AI ActData

Artificial intelligence governance

Regulation (EU) 2024/1689

NF525Tax

Inalterability of point-of-sale data

Art. 286-I-3° bis CGI

ISO 20022Banking

SEPA credit transfers and direct debits

pain.001.001.03 · pain.008.001.02

One ERP, several ways to work

Each company keeps its own file; its accountant works in it with exactly the rights agreed

IRPEA serves the business that runs its own company as well as the accounting firm managing a client portfolio: the same data, no double entry, everyone in their own space and at their own access level.

Who uses IRPEA

Business
Small and mid-sized companies managing themselves
  • The whole ERP
  • One or several companies
  • Customisable menu and dashboard
Business with an accountant
Company working with an accounting firm
  • Its own management space
  • Invites its firm
  • Chooses what the firm can see
Accounting firm
Firm with a team
  • Client portfolio
  • Dedicated eight-area menu
  • Staff and assignments
Independent accountant
Chartered accountant working alone
  • Simplified firm mode
  • Fees and engagement letters
  • Same production tools

Firm staff join their firm by invitation only; a firm is verified (professional registration) before inviting companies.

The firm ↔ company relationship

🏛️ The firm
  • • Partners, managers, staff, trainees, assistants
  • • A portfolio for each team member
  • • Two-factor authentication required once subscribed
📜 The engagement
  • • Engagement letter signed online
  • • Assignments: bookkeeping, review, tax, social, payroll, legal, advisory
  • • Tamper-proof log of the relationship
🏢 The company
  • • Keeps its file and its data
  • • Restricts, suspends or ends it at any time
  • • Sees every action of the firm in its log
What a team member can do in a client file
Their role in the firm
a trainee enters data but cannot delete
The engagement assignments
no payroll assignment, no payroll access
The company’s choice
it can close its sales or HR
Right granted

The lowest of the three applies: a firm can never do more than the engagement letter and the company allow.

The monthly cycle, from document to advice

  1. 1
    Documents

    the company uploads invoices and statements, even as photos, or answers a request

  2. 2
    Reminders

    requests with due dates, automatic reminders, online questionnaires

  3. 3
    Bookkeeping

    entries, bank reconciliation, FEC import to take over a file

  4. 4
    Returns

    VAT prepared and checked, instalments computed, payroll returns verified, also in bulk

  5. 5
    Deadlines

    each company’s calendar according to its regime, e-mail reminders

  6. 6
    Advice

    dashboards, cross-file analyses, benchmarks, consolidation

The firm tracks everything on a monthly production board, file by file, and each step can trigger an e-mail to the client through automation rules.

The client’s space, set up by the firm

Full ERP
the company uses every module of its plan
Portal
a simple space: dashboard, documents, requests, messages, sales
Tailored
the firm opens screen by screen, profile by profile, with its branding

The firm only configures the space with the company’s consent, which it can withdraw to get its full ERP back.

Who decides which e-mails are sent

Platform — turns a notification type off or on for everyone
Company file — the administrator sets each type and each channel
Profile — one rule per role, if the file wants it
User — everyone chooses what they receive, by e-mail or in the app

Each level can only restrict the one above; security messages (codes, password) are always sent.

Technical foundation

112 technologies, all of them transferable.

The day you take the project in-house or hand it to another provider, recruiting must not be an obstacle, which is the practical reason behind this choice of widely used tools.

112
technologies
Languages, interfaces and environments
  • TypeScript
  • JavaScript
  • Python
  • Rust
  • Java
  • PHP
  • Symfony
  • Laravel
  • C#
  • VB.NET
  • Dart
  • Swift
  • SQL
  • React 19
  • Next.js 16
  • Vite
  • React Native
  • Flutter
  • Electron
  • Tailwind CSS
  • HTML5
  • CSS3
  • jQuery
  • WLangage
  • WinDev
  • WebDev
  • WinDev Mobile
  • HFSQL
Databases
  • PostgreSQL
  • MySQL
  • Oracle
  • SQL Server
  • DB2
  • MongoDB
  • Elasticsearch
  • SQLite / LibSQL
  • Turso
  • Redis
  • Supabase
  • Neon
  • PlanetScale
  • Xata
  • Upstash
  • Vercel Postgres
  • Vercel KV
  • Vercel Blob
  • Vercel Edge Config
  • MariaDB
  • Cassandra
  • DynamoDB
  • Firestore
  • CockroachDB
  • ClickHouse
  • Snowflake
  • BigQuery
  • InfluxDB
Server, cloud and big data
  • Node.js
  • Vercel
  • Docker
  • Continuous integration
  • Edge and serverless
  • REST API
  • GraphQL
  • Web services
  • HDFS
  • Sqoop
  • PySpark
  • HBase
  • Hive
  • AWS
  • Azure
  • Google Cloud
  • OVHcloud
  • Kubernetes
  • Terraform
  • GitHub Actions
  • GitLab CI
  • Nginx
  • Linux
  • Kafka
  • RabbitMQ
  • Airflow
  • Prometheus
  • Grafana
Artificial intelligence and regulatory formats
  • Claude
  • Gemini
  • OpenAI
  • Vector databases
  • AI agents
  • Prompt engineering
  • n8n
  • Factur-X
  • FEC
  • DSN NEODeS
  • EDI-TVA
  • EN 16931
  • Mistral AI
  • Llama
  • Hugging Face
  • LangChain
  • LlamaIndex
  • PyTorch
  • TensorFlow
  • scikit-learn
  • Whisper
  • Ollama
  • pgvector
  • Qdrant
  • Pinecone
  • UBL
  • UN/CEFACT CII
  • Peppol
Questions

What we are asked most often.

Who owns the code produced?

You do, upon full payment of the service, the assignment covering the bespoke developments; generic components and reused internal tools remain the property of IRPEA and are licensed to you for perpetual use, royalty-free.

What happens if you are no longer available?

The code is in your repository, the credentials are in your name and the technologies used are widespread, so a developer who knows TypeScript and PostgreSQL takes over the project, which is the reason we avoid obscure tools.

Where is the data hosted?

Wherever you decide, and in the European Union by default; if your business requires hosting in France or a particular certification, say so at scoping: it changes the infrastructure choice and the budget.

Do you take over code written by someone else?

Yes, after a preliminary reading invoiced by the day, which serves to measure the real state of the project and to say whether a takeover is more economical than a rewrite, knowing that the answer is sometimes the rewrite.

How does invoicing work?

A detailed quote by work package before any start, then, on a fixed price: deposit on order and balance at acceptance; on time and materials: monthly statement of days consumed, payment falling due at thirty days, in accordance with art. L441-10 of the French commercial code.

How soon can you start?

The first conversation is scheduled within a week, while the actual start depends on the workload at the time; we state it in the quote rather than discover it along the way.

Do you use subcontractors?

Occasionally, for skills we do not have — design, network expertise — in which case you are told in the quote, and IRPEA remains solely responsible to you.

Do you use AI to write the code you deliver to us?

Yes, as a tool, and the code produced is reviewed, tested and owned line by line, because what is delivered commits the company, whatever tool was used to write it.

Do you work outside France?

Yes, remotely or on site, the questions of permanent establishment, VAT and applicable law being examined before any commitment.

Do you offer staff provision?

No: temporary work, umbrella employment and for-profit labour lending are excluded from the company’s corporate purpose, and we sell a service with an expected result.

The company

A structure on a human scale.

IRPEA is a registered trademark, run from Illiers-Combray, in the Eure-et-Loir department of France, by Rachid AMIMI, software engineer, who has worked for more than six years on management systems, online platforms and artificial intelligence applications.

The IRPEA trademark was filed with the French patent and trademark office (INPI) on 3 September 2026 under number 5294193, in classes 9 and 42 — software and IT services — and the domains irpea.com and irpea.fr are held by its owner.

Engagements take place in France and abroad, remotely or on site, the questions of permanent establishment, VAT territoriality and applicable labour law being examined before signing.

The projects we take on share one trait, they are bound by outside rules, and those rules are precise: an invoice must comply with EN 16931 to go through Chorus Pro, the French public invoicing portal, an accounting entries file (FEC) must come out as eighteen pipe-separated columns with CRLF line endings and a name of the form SIRENFECYYYYMMDD.txt or the tax administration rejects it, and a nominative social declaration (DSN) is filed in ISO-8859-15 — details that cannot be guessed, and that a piece of software ignores at a high price for its owner.

The company is deliberately small, so you talk to the engineer who writes the code and who has read your specification; when a project exceeds that capacity, we say so before signing.

Intelligent Research, Programming & Engineering AI

You talk to the engineer who writes the code and who has read your specification; when a project exceeds that capacity, we say so before signing.

IRPEA