How Ninon fits your close
A concise end-to-end view of the workflow implemented in the product today—from data ingest to documented reviewer outcomes.
Entities and mapping
Define the legal or accounting scopes in your group and map them to ERP identifiers where connectors require it.
Ledger lines in scope
Load lines through supported connectors or governed CSV/Excel import (persisted column mapping; entity by name or code — no UUID). Optionally a partner code for corridors.
Reconciliation session
Open a session for the period. Matching proposes pairs (and 1:N groups) with score and explanations. A balance matrix aggregates corridors.
Human review
Controllers approve, reject or reopen. The unmatched queue requires a reason (timing, FX, missing document, in-transit…). Chasers attach to lines. Default = human review.
Organisational memory
Validated decisions feed memory. Auto-match exists only when a client rule is active — traced and reversible. Not an autonomous close agent.
Automation (optional)
Export the reconciliation pack (amounts, unmatched lines, author, hash) and a flat consol file (proposed eliminations, remaining breaks). Proposed journals are exportable — never posted to the ERP. Optional scheduled runs.
Journey FAQ
- How do we start without an ERP connector?
- CSV/Excel import (column mapping, entity by name or code), session, matching and human review. ERP connectors later. Recommended commercial entry: Close Pilot.
- What does a reconciliation session produce?
- Scored proposals, unmatched queue with reasons, balance matrix, traced reviewer decisions, and a reconciliation pack (CSV/PDF: amounts, unmatched lines, author, hash). Flat consol export — not a statutory consolidation module.
- Does organisational memory replace consolidation?
- No. It reuses validated patterns and decisions across closes on the intercompany scope — without replacing consolidation or the ERP.