Accounting Email Pipeline

Problem

Accounting mail processing often becomes a repetitive loop: classify the attachment, identify the client, file the document, and reconcile payments. Doing this manually means reopening files, copying fields, and deciding which duplicates or incomplete items need follow-up. pipeline-comptable targets this workflow by chaining the common steps while preserving the output of each stage.

How It Works

The skill does not implement business logic directly. It calls the four modules in order: classification, recognition, filing, and matching. Each step reads and writes the same JSON dossier, so one step can hand its result to the next. Once filing is complete, step ⑤ runs automatically; --no-rapprochement can skip it when needed.

The main outputs are:
- stdout: a consolidated JSON report organized by document, with each section filled by its responsible step.
- stderr: a readable summary listing filed items, duplicates, pending items, and open questions.

When reporting to an accountant, describe only what was completed, what decisions are pending, and what needs attention. Do not expose script names, paths, JSON internals, or indexes. If documents have been filed, proposing payment reconciliation is the natural next action.

Boundaries

The orchestrator links existing modules rather than deciding business questions. It processes, files, and matches, but does not draft follow-up or reminder emails itself; those actions are escalated through the email workflow for validation. Classification applies only to mail mode. If documents are submitted directly, the flow starts with recognition.