# LegiPro - e-invoicing partner screening memo

Date: 2026-06-29

Roadmap task: `SAAS-0046`

Status: partner/product screening note. This is not a CEO/COO sponsorship request and not a claim of an approved partnership, live third-party API access, production deployment, paying users, professional certification or client reliance.

## Page 1 - What to route

LegiPro is a regulatory knowledge layer for existing accounting software. It helps partners add source-backed French accounting, tax and compliance intelligence without rebuilding the underlying regulatory foundation.

It is designed to support accounting, VAT, social, company-law and electronic invoicing workflows while integrating behind existing products rather than replacing them. Partners keep their product, user experience, login, billing and customer relationship. LegiPro supplies the regulatory intelligence layer behind it.

The core asset behind LegiPro is the transformation of thousands of pages of French accounting and regulatory material from 14 major reference corpora into a structured knowledge layer that software can reliably query, explain and cite. The durable value is not the AI model alone. AI models change quickly; curated, source-linked regulatory knowledge is the asset that takes time to build.

The first proof is focused on electronic invoicing, VAT and accounting-treatment review because the official French rollout begins on 1 September 2026. From that date, all companies must be able to receive electronic invoices, and large companies and ETIs must also issue them electronically. SMEs and micro-companies follow for issuing on 1 September 2027.

LegiPro can complement a partner's existing software and AI by selecting the most appropriate source of evidence for each request: structured regulatory knowledge, a specialised workflow, or AI support for more complex analysis. This is intended to improve consistency, traceability and operational cost control.

The same knowledge layer can support multiple product paths without rebuilding the underlying corpus:

- AI assistants inside accounting products;
- API integrations for partner workflows;
- workflow automation and review packets;
- evidence-backed dossier/export generation;
- future regulatory features built on the same source-linked foundation.

Recommended first internal route:

- product owner for accounting, VAT or electronic invoicing workflows;
- ISV or technology partnerships contact;
- API/platform owner;
- AI product owner working on accounting-assistant use cases.

## Page 2 - First proof, boundaries and ask

The proposed first proof is intentionally narrow and credential-free. It uses public information and test data only, so a partner can review the workflow without granting live sandbox credentials on day one.

Example workflow:

1. A partner-style accounting or electronic invoicing screen sends invoice context, a VAT question, period and business facts to LegiPro.
2. LegiPro prepares a source-backed review packet from the relevant corpora.
3. The partner receives an output it can store, route or review inside its own product.

Expected output:

- answerability status;
- cited official sources and source references;
- applicability notes, including period/date limits where available;
- missing facts and caution points;
- draft review packet or dossier/export reference;
- audit reference showing which evidence was used.

The current proof path has three reusable integration assets:

- no-credential e-invoicing/VAT proof fixture;
- shared adapter fixture harness;
- first-wave dry-run adapter stubs for Cegid Loop/Expert, Sage Accounting/Active, Pennylane, Odoo, Abby and Inqom.

These assets are not live third-party integrations. They show the handoff shape a partner product could evaluate before deciding whether to provide sandbox/API access.

Current boundaries:

- no paying users or ARR is claimed;
- no approved third-party partnership is claimed;
- no live third-party API call is claimed;
- Scenario remains locked;
- semantic/vector search remains planned, not active;
- professional certification is not claimed;
- client reliance is not claimed;
- human/professional review remains a boundary;
- all outputs remain review-gated.

Suggested next step:

A 30-minute product/partner screening to decide whether a credential-free electronic invoicing and VAT proof would be useful, which team should assess it, what sandbox/API access path would be appropriate later, and what security, source-rights or liability questions should be answered before any senior escalation.

Public material:

- LegiPro: `https://legipro.fr`
- API/integration page: `https://legipro.fr/bureau-api.html`
- Partner integration pack: `https://legipro.fr/assets/legipro-partner-integration-pack-2026-06-28.json`

Regulatory timing references:

- `https://www.impots.gouv.fr/internationalenbusiness/i-want-understand-electronic-invoicing`
- `https://www.economie.gouv.fr/tout-savoir-sur-la-facturation-electronique-pour-les-entreprises`
- `https://aife.economie.gouv.fr/nos-applications/facturation-electronique-b2b/`