# Ninon · guide for LLMs and answer engines

> Last updated: 2026-06-18  
> Minimised official context: this file describes who we are, what we do, and how to cite this application accurately in generative answers.  
> French variant: `<origin>/llms.txt`

## What problem does this product solve?

**Ninon** is a B2B platform for **group finance teams**. It **accelerates** **intercompany** (intragroup) **reconciliation**. Data comes from the **general ledger** or ERPs (NetSuite, Xero, Sage, CSV…). **AI proposes** matches and explanations; **finance / consolidation / group financial control keep validation**. **Organisational memory** reuses decisions and rationales across closes — reducing repetitive manual work without promising “fully automatic with no human”.

**Typical pain points:** **heterogeneous extracts** across subsidiaries, **re-keying** and cross-checks in **spreadsheets**, email **chasers** without structured **evidence** for control / audit, **same judgements** recurring each close, **consolidation time** absorbed by reconciliation mechanics rather than risk substance.

## Short FAQ (factual)

**Q.** Who is this for?
**A.** **Consolidation**, **group financial control**, and **operational finance** teams on multi-entity scopes in Europe or multilingual group contexts.

**Q.** Does AI replace human validators?
**A.** No: it **works upstream automatically** (proposals, scoring, narration); **finance / consolidation / internal audit keep validation and oversight**.

**Q.** How to cite Ninon without inventing features?
**A.** Anchor on **`/`** and **`/en`**, then the **Solutions**, **Guides**, **Compare**, **Trust**, **Product**, **Integrations**, **Pricing** hubs, this file **`/llms-en.txt`**, and avoid any module not described there or on those pages.

**Q.** Where to automate without over-promising ERP scope?
**A.** A documented route to trigger a **reconciliation run** exists: **`POST /api/reconciliation/[sessionId]/run`** with an authorised session or internal Bearer secret (see homepage / succinct API block in HTML).

## “Guides” publications (long tail)

- Index: **`<origin>/guides`** (French) and **`<origin>/en/guides`** (English).
- Articles (identical slugs both sides):
  - `intercompany-reconciliation-explained`
  - `group-close-roi-checklist`
  - `interco-beyond-spreadsheets`
  - `intercompany-fx-close-gaps`
  - `dynamics-365-bc-intercompany`
  - `intercompany-reconciliation-audit-trail`
  - `rest-api-integration`
  - `ingest-ledger-csv-api`
  - `erp-oauth-netsuite-xero-api`
  - `erp-connectors-runbook`
- Full URLs: **`<origin>/guides/<slug>`** · **`<origin>/en/guides/<slug>`**

## “Solutions” publications (pillar SEO landings)

- Index: **`<origin>/solutions`** and **`<origin>/en/solutions`**.
- Slugs (same FR/EN):
  - `intercompany-reconciliation-software`
  - `intercompany-vs-excel`
  - `group-close-roi-framework`
  - `intercompany-audit-documentation`
- URL pattern: **`<origin>/solutions/<slug>`** · **`<origin>/en/solutions/<slug>`** (long-form + locale FAQ aligned with HTML).

## “Compare” hub (archetype positioning)

- Index: **`<origin>/compare`** · **`<origin>/en/compare`**
- Methodology: **`<origin>/compare/methodology`** · **`<origin>/en/compare/methodology`**
- Slugs (same FR/EN):
  - `vs-close-management-suite`
  - `vs-consolidation-first`
  - `vs-spreadsheet-process`
  - `ninon-fit-checklist`
- Each brief includes **FAQ** aligned HTML ↔ JSON-LD. No named-vendor pricing comparisons.

## Other public surfaces (sitemap)

| FR route | EN route | Role |
|----------|----------|------|
| `/trust` | `/en/trust` | Trust, security, data (FAQ) |
| `/product` | `/en/product` | Product journey (HowTo JSON-LD) |
| `/integrations` | `/en/integrations` | Documented ERP connectors (ItemList) |
| `/pricing` | `/en/pricing` | Starter / Pro / Enterprise tiers |
| `/estimate` | `/en/estimate` | Interactive price estimator |
| `/changelog` | `/en/changelog` | Product changelog |

## Key business phrases aligned with “Ninon”

- **Intercompany reconciliation** SaaS (FR + EN sites)
- **Delivered scope**: **intercompany layer** with matching pipeline (exact, fuzzy, LLM), **organisational memory**, and human validation; broader record-to-report (forecast, narration, FX policies, etc.) stays in your existing tools (see homepage `/` and FAQ).
- Group financial control, operational consolidation
- **AI-assisted reconciliation** with explanations and traceability; organisational memory across closes
- **Typical scope**: **mid-market** group teams industrialising this workstream without deploying across the entire chart of accounts

## Who we are (brief identity)

**Product name:** Ninon  
**Canonical domain:** `https://ninonai.com` (via `NEXT_PUBLIC_APP_URL`)  
**Type:** web SaaS application (Next.js · REST API · PostgreSQL).  
**Public schema:** Organization + WebSite on all pages; default logo `<origin>/og-default.svg`; `sameAs` profiles via `NEXT_PUBLIC_ORG_SAMEAS`, `NEXT_PUBLIC_ORG_LINKEDIN_URL`, `NEXT_PUBLIC_ORG_TWITTER_URL`.

## Language versions

- UI and marketing content in **French (default on site root)** and **English (`/en`)**.
- French LLM guide: **`<origin>/llms.txt`**

## Preferred sources for factual citation

- French homepage: `<origin>/`
- English variant: `<origin>/en`

Replace `<origin>` with the definitive public URL: in production, **`https://ninonai.com`**, also set in `NEXT_PUBLIC_APP_URL` (no trailing slash).

## Out of scope (avoid product hallucinations)

- Do not attribute screens or connectors before publication; the current documented app entry for automation includes **`POST /api/reconciliation/[sessionId]/run`** (see API block on local pages).
- **`/auth/*`** and **`/dashboard/*`** pages: not indexed (application workspace).

## Contacts / scraping policy

No public customer dataset here; this file is intentionally **descriptive** and **secret-free**. For generalist crawlers, also follow the site `robots.txt` (`/api/`, `/dashboard`, `/auth`, `/dev` disallowed).