Skip to main content

AI Capabilities

The AI Assistant is a chat panel embedded in NomaUBL. Two questions it answers well:

  • How does the product work? — it consults the public documentation at docs.nomana-it.fr and replies with a sourced summary.
  • What is the state of my data? — it queries the NomaUBL database in read-only mode and replies with the matching rows: invoices, statuses, validation errors, e-reporting runs.

Replies stream live as the model writes them; every tool call appears inline as a small pill so the actions taken on the user's behalf remain visible. The assistant works in French or English — it follows the language of the question.

Opening the assistant​

  • Click the ✦ AI Assistant entry in the navbar (top-right, purple gradient pill). The panel slides in as a side drawer that shrinks the workspace.
  • Pick a model from the picker at the top of the panel. Default is the right choice for everyday questions; heavier models (Sonnet, Opus) give longer reasoning at a higher API cost.
  • Press Enter to send a question, Shift+Enter for a newline, ■ to abort an in-flight reply.
  • Closing the panel resets the conversation — the assistant has no memory across sessions.

At a glance​

✦AI AssistantDefault ▾×what is the issue for invoice 10000 / RI / 00001?🔍validation_errors· doc=10000 dct=RI kco=00001Looking up validation errors for this invoice…Invoice 10000 / RI / 00001 fails an XSD check.IssueUBL 2.1 element ordering — AdditionalDocumentReference is placed before ProjectReference / Signature.Likely causeXSL transform emits the element out of order.Recommendations• check the JDE → UBL transform• validate against the UBL 2.1 sequence📋 Copyyes🔍list_invoices· kco=00001Status of invoice 10000 / RI / 00001 — customer · 2025-02-01 · B2C · 140.70 € · 9905 — Validation failedBlocked since 2025-02-01 by the XSD issue above.Ask AI anything…➤Title barmodel picker · closeTool call indicatorname + actual filters usedStreaming replyMarkdown · headings · tablesCopy replypaste into ticket / emailUser questionfree text · FR or ENFollow-up turnmulti-step diagnosisInput areaEnter to send · ■ to abort

Every action the assistant takes on the user's behalf appears as a pill with the actual filters used printed alongside — 🔍 for data lookups against the NomaUBL database, 📖 for a documentation page request, 📥 for the result it received back. There are no hidden steps.

What the assistant can answer​

The assistant is wired to two information sources, both read-only.

About the product​

When asked how a feature works, the assistant runs a small two-step lookup against the public documentation at docs.nomana-it.fr:

  1. list_docs_pages — discovers the available NomaUBL documentation URLs from the site's sitemap (refreshed every six hours, capped at 200 entries). The pill shows up as 🔍 list_docs_pages · discovering NomaUBL docs URLs.
  2. web_fetch — picks the best-matching URL from the list and downloads the page. A 📖 pill shows the URL the assistant chose; immediately after, a 📥 web_fetch_result · ✓ <url> pill confirms the page was received (or 📥 ❌ <error_code> if it failed).

This two-step pattern is how the model stays grounded in the canonical docs — the URL it fetches always comes from the live sitemap, so it cannot invent or hallucinate a page that no longer exists.

Useful when:

  • a user is unsure how a feature behaves ("What does Replace = Skip do on Processing → XML?");
  • a colleague asks for a definition ("Explain flux 10.1 vs 10.3");
  • the answer needs a quick recap of the official lifecycle ("How does an invoice move from 9900 to 10?").

About the data​

Five read-only tools cover the day-to-day operational questions. The assistant also receives the live status catalog (every invoice and e-reporting status code with its tag and FR/EN labels) so it maps phrases like "en litige" or "rejected" to the right code without guessing.

ToolWhat it returnsTypical question
list_invoicesUp to 50 invoices from F564231 with filters: status code, company, BAR routing (B2B / B2BINT / B2C / B2G / OUTOFSCOPE), customer name (substring), issue-date range."Show pending invoices for company 00070 in EUR", "Failed sends since last Monday"
explain_status_codeThe tag name and the FR / EN labels for a status code. Looks up both the invoice catalog (1, 8, 10, 37, 9900–9907 …) and the e-reporting catalog (9950–9957)."What does 9906 mean?", "Status 9954?"
validation_errorsValidation errors from F564236 for a DOC + DCT + KCO triplet (level, source, rule, message — same columns and resolution logic as the Integration Errors page)."What is the issue for invoice 10000 / RI / 00001?"
lifecycle_historyEvery status transition recorded in F564235 for a DOC + DCT + KCO triplet — sequence, status code, message, date / time, plus the PA rejection reason, expected action and status note when present."Why was invoice 12345/RI/00070 rejected by the PA?", "Show the full history of this invoice"
list_ereportsUp to 50 e-reporting runs from F564240 with filters: flux (10.1 / 10.3), company, status code (9950–9957)."Last ten 10.3 reports for company 00070", "Pending e-reporting runs"

The assistant decides on its own when to call a tool — there is no manual trigger. A safety cap stops the agentic loop after 5 tool iterations per turn, so a runaway sequence cannot drain the API budget. When a tool fails, the assistant reports the tool name, the inputs it tried and the error code that came back, so the user can investigate.

Conversation examples​

The transcripts below come from a real session. The user asks in French; the assistant answers in French. The same panel works identically in English.

Example 1 — Diagnosing one invoice​

User quel est le problème pour la facture 10000 / RI / 00001

🔍 validation_errors · doc=10000 dct=RI kco=00001

AI Assistant Je vais chercher les erreurs de validation pour cette facture.

La facture 10000 / RI / 00001 a une erreur de validation XSD :

Problème : Structure UBL 2.1 invalide. L'élément AdditionalDocumentReference est trouvé à une position non autorisée.

Cause probable : L'ordre des éléments dans le document UBL ne respecte pas le schéma. AdditionalDocumentReference devrait apparaître après ProjectReference, Signature ou AccountingSupplierParty.

Recommandations :

  • Vérifier la transformation JD Edwards → UBL générée par NomaUBL.
  • S'assurer que les éléments UBL sont ordonnés conformément à la norme UBL 2.1.
  • Contrôler les données source dans JD Edwards (type de document, références additionnelles).

Souhaitez-vous que je consulte le statut global de cette facture ?  📋

User oui

🔍 list_invoices · kco=00001

AI Assistant

Statut de la facture 10000 / RI / 00001 :

AttributValeur
ClientLE CLIENT
Date d'émission2025-02-01
Type de documentB2C
Montant HT130,00 €
TVA10,70 €
Montant TTC140,70 €
Statut🔴 9905 — Échec de validation

Récapitulatif : la facture est bloquée en validation depuis le 1er février 2025 à cause de l'erreur XSD ci-dessus (élément AdditionalDocumentReference mal positionné).

Besoin d'aide pour corriger cette facture ?  📋

A single triplet (DOC + DCT + KCO) is enough to start a diagnosis. The assistant chains its own follow-ups — first the validation table, then the invoice header — and offers the next reasonable step.

Example 2 — Counting validation failures across the fleet​

User combien de factures au total ne sont pas valides ?

🔍 list_invoices · status=9905

AI Assistant

Résultat : 50 factures en échec de validation (statut 9905).

Les résultats affichent le maximum de 50 entrées. Le nombre total exact peut être supérieur.

Répartition observée :

  • Majorité : société 00002 (49 factures).
  • Minorité : société 00001 (1 facture) et autres.
  • Types de documents : surtout des RI (factures), 1 RM (facture d'avoir).
  • Période : principalement mars-avril 2026.

Recommandations :

  • Vérifier si toutes ces factures sont touchées par le même problème XSD.
  • Examiner en priorité les données source de la société 00002.
  • Lancer un audit sur la transformation JD Edwards → UBL.

Voulez-vous que je vous montre les erreurs détaillées d'une autre facture pour confirmer si c'est le même problème ?  📋

The 50-row hard cap on list_invoices is part of the safety design — for an exhaustive count, the E-Invoicing page is the right tool. The assistant is good at characterising a problem (which company, which document type, which period), then handing back to the dedicated screen for the full list.

Example 3 — Reading the PA rejection history​

User pourquoi la facture 12345 / RI / 00070 a-t-elle été rejetée par la PA ?

🔍 lifecycle_history · doc=12345 dct=RI kco=00070

AI Assistant

Voici l'historique complet de la facture 12345 / RI / 00070 :

DateStatutMessage
2026-04-12 09:149900 — Créée—
2026-04-12 09:159901 — ValidéeXSD + Schematron OK
2026-04-12 09:189903 — Envoyée à la PAsubmission_id=ABC-42
2026-04-12 09:429904 — Rejet PAREJ_ADR — code adressage destinataire inconnu

Motif PA : REJ_ADR — l'identifiant SIREN/SIRET du destinataire n'est pas reconnu sur l'annuaire PPF.

Action attendue : vérifier le code adressage du client dans JD Edwards puis relancer le pipeline.

Souhaitez-vous que je vérifie l'annuaire PPF pour ce destinataire ?  📋

When the rejection comes from the Plateforme Agréée and not from the local validation step, validation_errors is empty — lifecycle_history is the right tool because it surfaces the PA's own message (REJ_ADR, REJ_FMT, REJ_DESTINATAIRE …) along with the expected action.

Example 4 — Looking up how the product works​

User qu'est-ce qu'un flux 10.1 ?

🔍 list_docs_pages · discovering NomaUBL docs URLs

📖 web_fetch · https://docs.nomana-it.fr/nomaubl/application/ereporting/

📥 web_fetch_result · ✓ https://docs.nomana-it.fr/nomaubl/application/ereporting/

AI Assistant

Le flux 10.1 est le canal e-reporting français pour les transactions B2BINT — ventes vers un acheteur dans un autre État membre de l'UE. Pour ce flux :

  • chaque facture est déclarée individuellement (un envoi par facture, pas d'agrégation) ;
  • la PA dépose la déclaration auprès de l'administration fiscale via le PPF ;
  • le format est XML AFNOR XP Z12-014.

À distinguer du flux 10.3 qui agrège les transactions B2C et hors-périmètre par période. Source : docs.nomana-it.fr/nomaubl/application/ereporting  📋

The two-step lookup (list_docs_pages then web_fetch) is mandatory — the documentation API only allows fetching URLs that were returned by a previous tool result, which prevents the assistant from fabricating documentation links.

Reading the responses​

  • Tool pills show the actual filters applied (status=9906 dateFrom=2026-01-01 …). If a result looks off, the pill usually tells you why.

  • Pill icons map to a specific kind of action:

    IconPillMeaning
    🔍list_invoices, lifecycle_history, list_ereports, validation_errors, explain_status_code, list_docs_pagesRead-only call against the NomaUBL database or the docs sitemap.
    📖web_fetchThe model is fetching a documentation page — the URL is shown in the pill.
    📥web_fetch_resultThe page came back. ✓ followed by the URL means success; ❌ followed by an error code means the fetch failed.
    🌐web_searchA web search was issued (only when search is enabled).

  • Markdown rendering turns headings, bullet lists, code spans and tables into the visual elements visible in the panel — no plain-text dumps.

  • Streaming means the bubble fills in as the model writes; clicking ■ stops it cleanly without ending the conversation.

  • 📋 Copy at the bottom of an assistant reply copies the raw Markdown to the clipboard — handy to paste into a ticket or an email.

What the assistant cannot do​

  • Write data. No tool can modify the database. Configuration edits, validation re-runs and status changes stay out of scope.
  • Browse the open web. Documentation lookup is restricted to the allow-list configured by the administrator (the default is docs.nomana-it.fr).
  • See files. The chat is text-only. Pasting a UBL XML inline works (within the model context window), file uploads do not.
  • Persist conversations. Closing the panel or refreshing the page resets the thread. The same question on a fresh panel starts fresh.
  • Reach across customers. Read-only tools target the database the current user is authenticated against — same scope as the rest of the application.

The administrator can disable the data tools entirely (the assistant then relies solely on documentation lookup), restrict the documentation domains, override the model defaults, or change the system prompt — all from the global template.

Tips & best practices​

  • Start with the question, not the tool. "Show pending invoices for company 00070 in EUR" is enough — there is no need to ask the assistant to call list_invoices explicitly.
  • Use natural status names. "En litige", "rejected by the PA", "awaiting deposit" all map to the right numeric code automatically — the assistant carries the live status catalog.
  • Be specific with identifiers. For validation or lifecycle questions, include the full triplet (DOC + DCT + KCO); without it the assistant has to guess or call list_invoices first.
  • For PA rejections, prefer lifecycle_history over validation_errors. Local validation only stores XSD / Schematron failures in F564236; PA-side rejections (REJ_ADR, REJ_FMT, …) live in the lifecycle table and only lifecycle_history surfaces them.
  • Read the tool pills. They are the audit trail of the conversation — including 📥 web_fetch_result markers that confirm a documentation page was actually retrieved (or report the failure code if it wasn't).
  • Treat the panel as an external API. Anything sent is forwarded to the model provider — no API keys, no full credit-card numbers, no PII beyond what the public documentation already contains.
  • For deep audits, fall back to the dedicated pages. The assistant is optimised for quick lookups and explanations. For repeat workflows, the Dashboard, E-Invoicing, E-Reporting and Integration Errors pages remain the source of truth.