# Ninon · full LLM corpus (English) Concatenation of every public markdown mirror. Prefer `/llms-en.txt` for the short brief. --- --- title: "Intercompany reconciliation software" description: "Intercompany reconciliation software: GL breaks into a validated pack — Close Pilot then Workspace. Human sign-off, without replacing consolidation or ERP." locale: en canonical: https://www.ninonai.com/en last_updated: "2026-09-01" --- # Intercompany breaks reconciled and documented — without rebuilding spreadsheets every month Ninon brings subsidiary GL lines into one workspace, proposes reconciliations with business-readable rationales, and carries your decisions into the next close. You sign off; the file holds up to internal control and statutory audit. For consolidation and group financial control teams on multi-entity scopes (core ICP: roughly 5–25 entities, mixed ERPs or disparate CSV exports). ## Four steps, one clear story - **1 · Your data** — GL extracts, ERP or group CSV in one close session. - **2 · Ninon automates** — Ranked intercompany proposals with readable business rationales. - **3 · You stay in charge** — Approve or reject each match — audit-ready, no black box. - **4 · AI memory** — Decisions and patterns carried into the next close. ## Why intercompany still stalls so many closes Commonly cited orders of magnitude on multi-entity groups — useful to frame your business case, not a Ninon performance claim. ### Share of the close cycle On extended group scopes, intercompany reconciliation can absorb a material slice of the countdown — often quoted between a quarter and two fifths of consolidation coordination time. ### Cost of broad close suites Enterprise platforms cover the full record-to-report chain with six-figure annual budgets and multi-month rollouts — heavy when the burning issue is ledger-level intercompany matching. ### Enter via a Close Pilot A Pilot on a real close period (CSV, review, audit pack) proves value before an annual Workspace — Essentiel self-serve remains for 2–5 entity scopes. ## Frictions every group consolidation and controllership team knows Ninon takes on these frictions before you sign off — on the intercompany scope of your general ledger. - Intragroup treasury flows or management recharges booked with different narrations across subsidiaries - Email chasing without structured evidence to hand to the statutory auditors - The same recurring intercompany breaks reopened from scratch each close ### Line-by-line spreadsheet glue across entities Subsidiary extracts rarely align by magic—amounts, dates, currencies and narrations drift, and finance ends up patching workbooks that age badly. Ninon ingests GL into one session and proposes pairs with business-readable rationales—replacing brittle spreadsheet rework every period. ### Residuals without a single narrative for control or audit When evidence lives in email fragments, the file weakens under scrutiny. Each proposal carries explanation and confidence before your decision; you stay in charge, with detail auditors and controllers can reopen. ### The same corridor debated again next close Without structured memory, recurring corridors get reopened like surprises. Per-organisation memory keeps approvals and repeating motifs so the next period starts higher up on flows already settled between entities. ## A focused intercompany layer — not a six-month close programme Transaction-level depth on subsidiary general ledger that close-checklist tools rarely cover, without the all-in enterprise platform project. ### Reconciliation engine with business-readable rationales Exact matches, narration similarity and memory hints — each hypothesis carries plain-language context you can review before approval. ### Focused workflow: session → run → review The workspace centres on a period session, a reconciliation run, and reviewing proposals—the flow group finance teams need for intercompany without scattered screens. Designed for velocity on this specific workload. ### Short path to value once data is connected Create your workspace, define entities, import general-ledger lines (file upload or connectors where available), then open a closing session and run reconciliation. Start in the product; add automation with your IT partner when volumes justify it—see the Guides section for integration options. What Ninon delivers: intercompany reconciliation with rationales, per-organisation memory, and human sign-off. Forecasting, group commentary, FX policy, and the rest of record-to-report stay in your existing systems and processes. ## Time and budget leaks—and where Ninon bends the curve No miracle spreadsheet: the pains above often materialise as steering hours lost to coordination, emergency adviser spend or close-date slip. Ninon targets observable gains on this intercompany slice—time back for substantive control, clearer dossiers for stakeholders, proportionate implementation. ### Hours lost to spreadsheets and email back-and-forth Manual chase-downs crowd out focus on material risk. Hypotheses are prioritised and narrated before approval; recurring motifs carry forward so each cycle sheds rework. ### Audit or advisory invoices inflated by opaque files When everyone decodes the ledger separately, clarification is billed by the hour. Readable rationales align group finance and auditors on a shared story and can shorten back-and-forth. ### Budget and timeline focused on the intercompany layer Skip sprawling programmes unrelated to the pain: governed imports and scheduled automation deliver early value where friction is measurable—a tighter effort-to-impact ratio until your own ROI model proves out. ## FAQ **Q.** Who is Ninon for? **R.** Group finance and consolidation teams that want to industrialise intercompany reconciliation across subsidiaries—explainable proposals, traceability for internal control and external reviewers, ways to connect your ledger data, and a UI centred on the close session and review—with implementation effort scaled to that scope. **Q.** Does “AI-assisted” remove human reviewers? **R.** No. Default is human review of every proposal. Auto-match exists only when you activate traced, reversible client rules — not an AI that closes the period on its own. Finance / consolidation keep sign-off for the audit trail. **Q.** Which ingestion paths are credible out of the box? **R.** Structured GL extracts: CSV/Excel with column mapping (entity by name or internal code — no UUID required) plus evolving ERP connectors. Dates, accounts, narrations, currencies, amounts, and optionally a partner code for corridors. **Q.** Will Ninon collapse every FX shock automatically? **R.** It highlights residual deltas with traceable rationale; policy decisions on thresholds and hedging narratives stay firmly with your treasury policy owners. **Q.** Does Ninon replace our consolidation or ERP suite? **R.** No. Ninon targets the intercompany reconciliation slice: proposals, evidence, and review. Your consolidation platform, statutory reporting, and ERPs remain the system of record; Ninon complements them on this workflow. **Q.** How do we model ROI credibly with the CFO office? **R.** Use directly attributable KPIs — consolidation labour hours per close, elapsed time until no blocking items outside the tool, ad-hoc auditor or adviser remediation spend — then compare before and after once workloads stabilise with the same subsidiaries and currencies. Ninon preserves logs and rationales that help evidence those calculations. **Q.** Where can finance teams read practical guides? **R.** Open the Guides hub from the footer: French-first articles under /guides and English under /en/guides—definitions, prudent close KPIs, and when spreadsheets hit their ceiling. The public homepages / and /en describe the current product scope. **Q.** What does Ninon cover in the group finance stack? **R.** Ninon is an intercompany GL satellite: corridor matching, review plus unmatched queue, client rules for auto-match, an exportable reconciliation pack (amounts, orphans, author, hash) and a flat consol export. Out of scope: the rest of the close cycle, ERP posting, replacing consolidation. ## Start in the dashboard, wire integrations when you need scale For consolidation and group financial control, the simplest path is the product itself: open a session for the period, load GL lines, run reconciliation, then approve or reject proposals—no integration project required to begin. When volumes or operating rhythm call for automation (scheduled extracts, hooks into your existing close chain), your IT organisation or integration partner can connect Ninon to those flows. Access stays under your governance—named users like today, or secured technical channels for scheduled jobs, aligned with your security standards. OpenAPI: `/openapi.json` · Guide: `/guides/rest-api-integration.md` · `POST /api/reconciliation/{sessionId}/run` ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Pricing — Close Pilot and Interco Workspace" description: "Pricing: Close Pilot (€3–6k), Interco Workspace (€18–28k/year), Group/Scale (€35–60k+/year) and Essentiel teaser — intercompany software." locale: en canonical: https://www.ninonai.com/en/pricing last_updated: "2026-08-05" --- # Close Pilot, then annual Workspace Public pricing: in one close, turn intercompany GL breaks into a validated reconciliation pack — without replacing consolidation or your ERP. The recommended entry is a Pilot on a real period; the core plan is an annual Workspace. Essentiel self-serve stays a teaser for 2–5 entities. ## Three packs for group finance | Pack | Prix | Rôle | | --- | --- | --- | | Close Pilot | €3–6k excl. VAT · one-shot | One real period: CSV/Excel ingest, up to ~8 entities, reconciliation session, review and exportable audit pack — with a kickoff workshop. | | Interco Workspace | €18–28k / year excl. VAT | Recurring sessions, organisational memory, human sign-off, governed CSV and/or 1–2 connectors, consolidation-team seats — optional SSO. | | Group / Scale | €35–60k+ / year excl. VAT | Multi-connectors, API and webhooks, SLA, assisted onboarding, portfolios beyond 15–25 entities and higher volumes. | | Essentiel | From €199 / month excl. VAT | Self-serve teaser for 2–5 entities and modest volumes: workspace, session and review. Not the recommended pack for multi-subsidiary core ICP groups. | Indicative prices excl. VAT. The Pilot is creditable against the first annual Workspace or Scale contract if signed within 60 days. Formal quotes depend on entities, volumes and integrations. ## Close Pilot success criteria The Pilot sits on a real close (about 2–3 weeks). Before kickoff we agree measurable success criteria — so the Workspace decision rests on a file, not a generic demo. - Data: usable CSV/Excel GL extracts for the chosen period, with entity mapping. - Deliverable: reconciliation pack (proposals, approve/reject, rationales) exportable for control. - Scope: typically up to ~8 entities on one period session — then expand under Workspace. - Timeline: kickoff, matching, team review, readout — aligned to your close calendar. ## FAQ **Q.** Where should a multi-entity group start? **R.** With a Close Pilot (€3–6k excl. VAT indicative) on a real period, then annual Interco Workspace (€18–28k/year) if success criteria are met. Essentiel (~€199–299/mo) is a 2–5 entity teaser, not the group procurement path. **Q.** Is the Pilot creditable against the annual? **R.** Yes, as a public indicative rule: credit against the first Workspace or Scale annual if signed within 60 days of readout — details on the quote. **Q.** Do we need an ERP connector to start? **R.** No. Pilot and freemium start with CSV/Excel. ERP connectors typically stay behind a subscription or invoice entitlement. **Q.** Does Ninon replace consolidation? **R.** No. It is a satellite for intercompany GL reconciliation; consolidation and ERP remain systems of record. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Workspace estimator" description: "Frame an indicative excl. VAT budget (entities, seats, GL volume) for Essentiel or Interco Workspace, then continue with a Close Pilot." locale: en canonical: https://www.ninonai.com/en/estimate last_updated: "2026-08-15" --- # Estimator — frame Workspace or Pilot Enter ballpark entity count, seats, and monthly GL line volume. You get an indicative monthly figure and annual equivalent to position Essentiel or Interco Workspace. Beyond guardrails — or for a Close Pilot — use the commercial offer. ## Indicative bands (readable without JavaScript) These rows are computed server-side from the same engine as `POST /api/pricing/estimate`. | Scenario | Entities | Seats | GL lines / month | Result | | --- | ---: | ---: | ---: | --- | | 2–5 entity teaser | 3 | 6 | 200,000 | €246 / mois · Essentiel (self-serve teaser) | | Core ICP (~8 entities) | 8 | 10 | 600,000 | €20,440 / an · Interco Workspace (annual) | | Upper Workspace band | 18 | 20 | 1,500,000 | €28,000 / an · Interco Workspace (annual) | | Above caps → Scale | 40 | 80 | 10,000,000 | Group / Scale scope — commercial conversation | Recommended next step: Close Pilot (€3–6k excl. VAT), creditable toward Workspace. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Close Pilot intercompany — 2–3 weeks, audit pack" description: "Ninon Close Pilot (€3–6k excl. VAT indicative): CSV/Excel, reconciliation session, traced review and audit export on a real period — before an annual Interco Workspace." locale: en canonical: https://www.ninonai.com/en/pilot last_updated: "2026-08-05" --- # Book a Close Pilot One real period, a validated reconciliation pack, written success criteria — then decide on an annual Interco Workspace. ## What the Pilot must prove - Data: usable CSV/Excel GL extracts for the chosen period, with entity mapping. - Deliverable: reconciliation pack (proposals, approve/reject, rationales) exportable for control. - Scope: typically up to ~8 entities on one period session — then expand under Workspace. - Timeline: kickoff, matching, team review, readout — aligned to your close calendar. Indicative: €3–6k excl. VAT one-shot, creditable against the first annual Workspace or Scale contract if signed within 60 days. ## 2–3 weeks aligned to your close 1. Kickoff + entity mapping + CSV import for the target period. 2. Reconciliation session, traced human review, memory of recurring patterns. 3. Audit-pack export + readout → go/no-go on annual Workspace. ## FAQ **Q.** What is a Ninon Close Pilot? **R.** A one-shot engagement (typically 2–3 weeks) on a real period: CSV/Excel ledger import, reconciliation session, human review and audit-pack export — without replacing consolidation or the ERP. **Q.** How much does the Pilot cost? **R.** Public indicative range: €3–6k excl. VAT. Exact amount depends on entity count (often ≤ 8) and calendar. A credit may apply to the first annual Workspace if signed within 60 days. **Q.** Do we need an ERP connector? **R.** Not for the Pilot: the standard entry is CSV/Excel. ERP connectors stay behind paid / Workspace once the flow is proven. **Q.** How is this different from Essentiel (~€199/mo)? **R.** Essentiel is a self-serve teaser for 2–5 entities. The Pilot is the recommended entry for multi-entity groups that want proof on a real close before an annual Workspace (€18–28k/year indicative). **Q.** What happens after the Pilot? **R.** A readout against written success criteria, then an annual Interco Workspace quote if you go ahead — or limited freemium if timing is wrong. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Trust & procurement — hosting, DPA, SSO, roles" description: "Ninon procurement checklist: SSO and roles, GL data, subprocessors (Stripe, Resend…), retention, DPA — for security review before a Close Pilot." locale: en canonical: https://www.ninonai.com/en/trust last_updated: "2026-09-01" --- # Trust and security This page is the procurement checklist to send to security / IT / purchasing. It summarises practices reflected in the product. It does not replace a contractual questionnaire, a signed DPA, or your own risk assessment. ## Authentication, SSO and roles Workspace access uses authenticated sessions (magic link or bootstrap). Organisations can configure SAML SSO when that capability is enabled for the deployment. Application roles: admin (configuration, billing, SSO), member (sessions, review, imports as permitted), viewer (read-only). Sensitive actions (ERP connectors, webhooks, SSO admin) are restricted to authorised roles. ## Financial data, retention and ERP General ledger lines and reconciliation artefacts (proposals, decisions, exports) are stored per organisation in the application database. ERP OAuth tokens are encrypted at rest before persistence. Retention: data remains available for the life of the contract / organisation; deletion or export on request at end of relationship per the DPA. Use least-privilege ERP apps and rotate secrets per your policy. ## Email and payments Transactional email (magic links, Pilot ops notifications) goes through Resend. Card payments and Stripe subscriptions / quotes are processed by Stripe; Ninon does not store full card numbers. Invoice entitlements can be activated outside self-serve checkout when the contract provides for it (Pilot, Workspace). ## Subprocessors (public overview) Typical subprocessors when configured: Stripe (payments), Resend (email), PostHog (product analytics, if enabled), file storage (e.g. Vercel Blob, if enabled), application host and PostgreSQL for the deployment. Exact residency (cloud region) depends on hosting configuration — request the current sheet from your contact. Full list and DPA: procurement / NDA phase. ## What this page is not We do not publish marketing-only compliance badges. Ninon does not replace ERP or consolidation. For SOC 2, ISO, pen-tests or detailed architecture, rely on materials provided under NDA during procurement. ## Procurement checklist - Cloud hosting + per-organisation database — region to confirm - DPA / terms — internal outline available; legal version attached to quotes - SAML SSO — when enabled - Roles admin / member / viewer - ERP tokens encrypted at rest - Session reconciliation-pack export (CSV / PDF: amounts, unmatched lines, author, hash) - No SOC 2 / ISO marketing badges — NDA materials if available - Commercial entry: Close Pilot (not Essentiel card checkout for multi-entity groups) ## FAQ **Q.** Does Ninon replace my ERP or consolidation tool? **R.** No. Ninon ingests general ledger lines for intercompany reconciliation. ERP and consolidation remain your statutory systems of record. Proposed journals are exportable; Ninon does not post to the ERP. **Q.** Where is financial data stored? **R.** Per organisation in the Ninon application database. ERP OAuth tokens are encrypted at rest. Exact cloud region depends on hosting — confirm during procurement. **Q.** Does Ninon display SOC 2 or ISO badges? **R.** Not on the public site. For SOC 2, ISO or NDA reports, request up-to-date materials from your sales or security contact. **Q.** Which subprocessors handle data? **R.** Depending on configuration: Stripe (payments), Resend (email), optionally PostHog (analytics), file storage and the deployment host / PostgreSQL. Contractual list in the DPA. **Q.** Which roles and SSO? **R.** Admin, member and viewer roles. SAML SSO is configurable when the feature is enabled on the environment. **Q.** How do we start without a group card subscription? **R.** Via a Close Pilot (quote / engagement) or limited CSV freemium. Essentiel self-serve is a 2–5 entity teaser, not the group procurement path. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany reconciliation workspace" description: "From entities and ledger lines to reconciliation sessions, reviewer decisions, and organisational memory." locale: en canonical: https://www.ninonai.com/en/product last_updated: "2026-09-01" --- # 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. ## FAQ **Q.** How do we start without an ERP connector? **R.** CSV/Excel import (column mapping, entity by name or code), session, matching and human review. ERP connectors later. Recommended commercial entry: Close Pilot. **Q.** What does a reconciliation session produce? **R.** 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. **Q.** Does organisational memory replace consolidation? **R.** No. It reuses validated patterns and decisions across closes on the intercompany scope — without replacing consolidation or the ERP. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "ERP and ledger integrations" description: "Overview of how Ninon connects to Dynamics 365 Business Central, Xero, NetSuite, SAP Business One, SAP S/4HANA, Sage Intacct, and governed file imports." locale: en canonical: https://www.ninonai.com/en/integrations last_updated: "2026-09-01" --- # Integrations and data sources Ninon ingests general ledger lines for intercompany reconciliation. Supported paths depend on your ERP and hosting configuration; your admin workspace lists live connection status. Connectors use OAuth or stored credentials where applicable; CSV and Excel uploads follow the documented column layout. Not every ERP exposes the same fields—entity mapping (erpLinks) is often required for multi-branch setups. - **Dynamics 365 Business Central** — OAuth through Microsoft; company mapping via Business Central company identifiers. - **Xero** — OAuth (PKCE); tenant selection when multiple organisations are connected. - **NetSuite** — Browser OAuth or scripted token registration; subsidiary mapping for SuiteQL extracts. - **SAP Business One** — Service Layer URL and company database; optional branch (BPLID) mapping per entity. - **SAP S/4HANA** — Published OData service; manual bearer or OAuth client credentials; company code mapping. - **Sage Intacct** — Web services credentials; location-based mapping when entities split by LOCATIONID. - **CSV and Excel (general ledger)** — Governed import: FR/EN aliases, persisted column mapping, entity by name or code (no UUID). Recommended when no live connector is configured. - [Dynamics 365 Business Central intercompany reconciliation](/en/integrations/dynamics-365-bc.md) - [NetSuite intercompany reconciliation](/en/integrations/netsuite.md) - [SAP S/4HANA intercompany reconciliation](/en/integrations/sap-s4hana.md) - [SAP Business One intercompany reconciliation](/en/integrations/sap-business-one.md) - [Xero intercompany reconciliation](/en/integrations/xero.md) - [Sage Intacct intercompany reconciliation](/en/integrations/sage-intacct.md) ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Product changelog" description: "Notable customer-visible changes to the Ninon workspace and public site." locale: en canonical: https://www.ninonai.com/en/changelog last_updated: "2026-05-13" --- # Changelog High-level release notes for teams evaluating or operating Ninon. Internal refactors and security patches may be omitted when there is no user-visible impact. ## 2026-05-13 — Public compare hub and trust pages Added a comparison hub with archetype briefs (no vendor-by-vendor pricing claims), methodology page, trust centre, changelog, integrations overview, and product journey page. Extended sitemap coverage for these routes. ## 2026-05-01 — Ongoing intercompany workspace improvements Continued iteration on reconciliation sessions, ledger import paths, and billing alignment for self-serve deployments. See guides for technical detail on CSV, Excel, and connector behaviour. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Group finance guides" description: "Short reads on intercompany reconciliation, Close Pilot, multi-ERP, organisational memory, FX close gaps, Dynamics 365 BC, audit trails, close ROI, spreadsheets, ledger import, ERP connectors, and REST integration." locale: en canonical: https://www.ninonai.com/en/guides last_updated: "2026-08-05" --- # Group finance guides Short reads on intercompany reconciliation, Close Pilot, multi-ERP, organisational memory, FX close gaps, Dynamics 365 BC, audit trails, close ROI, spreadsheets, ledger import, ERP connectors, and REST integration. - [Intercompany reconciliation: from GL to an auditable file](/en/guides/intercompany-reconciliation-explained.md) — What intercompany reconciliation means in consolidation, why it slows closes, and how group teams structure the work without losing audit evidence. - [Close ROI: serious metrics for intercompany teams](/en/guides/group-close-roi-checklist.md) — How finance leadership can model payback on intercompany reconciliation with defensible metrics—hours, cycle time, audit drag—without software fantasy savings. - [Beyond Excel: continuity for intercompany work](/en/guides/interco-beyond-spreadsheets.md) — Why multi-ERP portfolios graduate from Excel to a governed workspace: continuity across closes, reviewer evidence and APIs for automation without a monolithic ERP programme. - [Intercompany FX at close: policy owners and explainable residuals](/en/guides/intercompany-fx-close-gaps.md) — Why FX residuals on intragroup balances need treasury policy sign-off—and how group finance documents explainable breaks without pretending software sets rates. - [Business Central: from OAuth to intercompany reconciliation sessions](/en/guides/dynamics-365-bc-intercompany.md) — Connect BC companies to Ninon, map entity GUIDs, and run intercompany matching on general-ledger lines without replacing your Microsoft stack. - [Audit trail: evidence on intercompany reconciliation decisions](/en/guides/intercompany-reconciliation-audit-trail.md) — What auditors and internal control expect from intercompany matching: proposal evidence, reviewer decisions, and continuity across closes—not inbox threads. - [Close Pilot: prove intercompany reconciliation on a real period](/en/guides/close-pilot-intercompany.md) — How to frame a Ninon Close Pilot in 2–3 weeks: ledger CSV, session, review, audit pack and success criteria before an annual Workspace. - [Multi-ERP: one intercompany pack despite heterogeneous systems](/en/guides/multi-erp-intercompany-reconciliation.md) — Multi-ERP groups: normalise ledger exports, start with CSV, then connect BC, NetSuite, SAP or Intacct without replacing consolidation. - [Organisational memory: do not restart from zero each close](/en/guides/organisational-memory-group-close.md) — Reuse reconciliation patterns and decisions from one close to the next: fewer re-litigated intercompany breaks in group finance. - [REST integration: trigger matching from your systems](/en/guides/rest-api-integration.md) — Authentication, how to trigger a run, and HTTP response modes (queued vs in-process) for IT and integration partners. - [Feed the general ledger: ERP export, columns, and API call](/en/guides/ingest-ledger-csv-api.md) — Business scope, exact column headers, entity resolution, text and multipart ledger import (.csv/.xlsx), JSON counters and per-line errors. - [NetSuite and Xero connectors: register tokens via API](/en/guides/erp-oauth-netsuite-xero-api.md) — Operational reference for NetSuite and Xero token registration, admin role, and post-connect sync behaviour. - [ERP connector operations and erpLinks mapping](/en/guides/erp-connectors-runbook.md) — Operational reference: per-connector entity mapping keys, Xero tenant selection, NetSuite browser or scripted OAuth, SAP B1/S/4 variants and Intacct location pagination. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany software, spreadsheets, ROI, audit" description: "Four Ninon thematic landings — intercompany SaaS positioning, escaping spreadsheet close risk, prudent CFO KPI framing and audit-ready documentation habits." locale: en canonical: https://www.ninonai.com/en/solutions last_updated: "2026-08-05" --- # Group finance solutions These pages complement the homepage and shorter guides: they target high-intent searches from group finance, consolidation and controllership teams while staying inside the product scope published on this site. - [Intercompany reconciliation software: a cockpit for group finance](/en/solutions/intercompany-reconciliation-software.md) — What a modern intercompany SaaS covers: ledger scope, human approval, memory across closes and APIs—so group finance can close with less spreadsheet risk. - [Intercompany work and Excel: when the spreadsheet turns into the main close risk](/en/solutions/intercompany-vs-excel.md) — When Excel stops scaling for multi-entity intercompany: version sprawl, weak evidence trails, lost context—and how a governed workspace differs from a giant ERP programme. - [Intercompany ROI: a KPI framing finance leaders can defend](/en/solutions/group-close-roi-framework.md) — Defensible KPIs for intercompany payback—labour hours, cycle friction, advisory drag—and why tools supply evidence rather than magically computing ROI. - [Intercompany audits: evidence-first dossiers—not just balanced trial balances](/en/solutions/intercompany-audit-documentation.md) — How structured explanations and approvals support internal control and auditors on intercompany work—without over-claiming compliance or certifications. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Compare intercompany approaches" description: "Archetype briefs to align finance and IT—without vendor-by-vendor claims." locale: en canonical: https://www.ninonai.com/en/compare last_updated: "2026-05-13" --- # How to think about intercompany tooling These briefs compare solution archetypes, not individual vendors. They help finance and IT align on scope: what must stay in the ERP or consolidation stack, where spreadsheets break, and when a focused intercompany workspace earns a place. Named searches (BlackLine, FloQast, Excel) live on /alternatives — still without competitor price grids. ### Broad close-management suites Often span account reconciliation, tasks, and controls across record-to-report. Strong when you need a wide programme; heavier to adopt when the burning issue is narrowly intercompany breaks on GL lines. […](/en/compare/vs-close-management-suite.md) ### Consolidation or ERP–first setups Statutory consolidation and ERPs remain systems of record. Intercompany work still needs a governed workspace for proposals, evidence, and reviewer sign-off unless you fully standardise extracts and workflows inside those tools. […](/en/compare/vs-consolidation-first.md) ### Spreadsheet and email processes Maximum flexibility early on; weak audit trails and version sprawl as entities and narrations diversify. A common stepping stone before structured tooling. […](/en/compare/vs-spreadsheet-process.md) ### Dedicated intercompany layer Ninon’s focus: GL lines in period sessions, explainable match proposals, human approval, and organisational memory across closes—without replacing your consolidation suite or ERP. […](/en/compare/ninon-fit-checklist.md) ## FAQ **Q.** Do you compare named vendors? **R.** Not on this hub: archetypes only, without vendor pricing grids or unsourced quantitative claims. Named searches (BlackLine, FloQast, Excel) are on /alternatives, with the same rule: no invented competitor prices. **Q.** Do these pages replace an RFP? **R.** No. They help finance and IT align internally. Your procurement diligence, vendor questionnaires, and legal review still apply. **Q.** Where is Ninon’s product positioning documented? **R.** On the dedicated intercompany brief (/compare/ninon-fit-checklist), the /product journey, /solutions landings, /alternatives for named vendors, and the homepage FAQ. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Comparison methodology" description: "How Ninon frames public comparison content: scope, sourcing discipline, and what we do not claim about third parties." locale: en canonical: https://www.ninonai.com/en/compare/methodology last_updated: "2026-05-13" --- # Methodology for public comparison pages We publish category-level briefs to help buyers structure conversations internally. We do not substitute for your procurement diligence, vendor questionnaires, or legal review. ## What we compare We compare archetypes of tooling and operating models (breadth of suite, system of record vs. satellite workflow, spreadsheet risk, dedicated intercompany layer). We avoid unsourced quantitative claims about named vendors. ## How we describe Ninon Claims stay within the product surface documented on this site: reconciliation sessions on GL data, match proposals with rationales, reviewer actions, memory, file and connector ingest, billing and SSO where applicable. If a capability is not shipped in the product, we do not market it here. ## Review cadence Pages carry a last-reviewed date in the UI. When product scope changes, we update the relevant brief in the same release window whenever possible. ## FAQ **Q.** Where do Ninon claims come from? **R.** Only from the product surface documented on this site: GL reconciliation sessions, explainable proposals, human approval, organisational memory, file and connector ingest, billing and SSO where applicable. **Q.** Are these pages updated? **R.** Yes. Each page shows a last-reviewed date. When product scope changes, the relevant brief is updated in the same release window whenever possible. **Q.** May I cite a comparison brief? **R.** Yes, using the canonical URL (e.g. /compare/ninon-fit-checklist or /en/compare/ninon-fit-checklist) and noting it is an archetype comparison, not a vendor benchmark. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany alternatives — BlackLine, FloQast, Excel" description: "When group finance looks past BlackLine, FloQast or Excel for intercompany reconciliation: mid-market fit, Close Pilot, and what Ninon does not replace." locale: en canonical: https://www.ninonai.com/en/alternatives last_updated: "2026-09-01" --- # Intercompany alternatives These pages answer named searches (BlackLine, FloQast, Excel) without turning Compare into a vendor scorecard. We name the tool people already have in mind, describe the job they hired it for, and say when a dedicated intercompany workspace is a better next step — without inventing their prices or feature grids. - [BlackLine alternative for mid-market intercompany](/en/alternatives/blackline.md) — When a dedicated intercompany workspace is a better next step than an enterprise Intercompany Hub — without inventing BlackLine pricing or feature grids. - [FloQast alternative for intercompany reconciliation](/en/alternatives/floqast.md) — FloQast is a close-management and compliance platform. Ninon is a dedicated intercompany reconciliation workspace — not a SOX or close-checklist suite. - [Excel alternative for intercompany reconciliation](/en/alternatives/excel.md) — Why group intercompany work outgrows shared workbooks — and what a governed workspace adds without claiming to “replace Excel” everywhere. ## FAQ **Q.** Is this a BlackLine vs Ninon benchmark? **R.** No. It is a displacement page for people who already search that name. Quantitative vendor comparisons stay off this site. **Q.** Why name vendors here if Compare refuses to? **R.** Because the search is nominal. Compare answers “what kind of tool”. Alternatives answers “I already have this name in mind”. Different intent, same honesty rule on unpublished numbers. **Q.** Where are Ninon’s prices? **R.** Only on /pricing and /estimate. Alternative pages never restate a competitor’s quote. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Named-alternatives methodology" description: "How Ninon writes BlackLine, FloQast and Excel alternative pages: we name the vendor, we do not invent their pricing or unpublished capabilities." locale: en canonical: https://www.ninonai.com/en/alternatives/methodology last_updated: "2026-09-01" --- # How we write named-alternative pages Compare stays archetype-only. Alternatives exists so a buyer who already typed a vendor name can land on a factual page. The two hubs are complementary, not duplicates. ## What we name Title, H1 and URL may name BlackLine, FloQast or Excel because those are the queries. We describe the job-to-be-done those tools are typically hired for, using only what they publish on their own sites and what Ninon publishes about its own scope. ## What we do not quantify We do not publish their list prices, discount bands, win rates, or “10× cheaper” claims. We do not assert feature parity with Intercompany Hub, FloQast Reporting, netting, SOX modules or consolidation. If a number is not on /pricing or a cited public page, it does not appear here. ## Sources and next step Vendor capabilities: their public product pages. Ninon capabilities: /product, /pricing, /pilot, /trust. For a vendor-free framing, use /compare and /compare/methodology. The commercial CTA on every alternatives page is a Close Pilot — not a like-for-like rip-and-replace. ## FAQ **Q.** Is this a BlackLine vs Ninon benchmark? **R.** No. It is a displacement page for people who already search that name. Quantitative vendor comparisons stay off this site. **Q.** Why name vendors here if Compare refuses to? **R.** Because the search is nominal. Compare answers “what kind of tool”. Alternatives answers “I already have this name in mind”. Different intent, same honesty rule on unpublished numbers. **Q.** Where are Ninon’s prices? **R.** Only on /pricing and /estimate. Alternative pages never restate a competitor’s quote. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Glossary — group intercompany terms" description: "Stable definitions used on ninonai.com and in /llms.txt. Use these when citing Ninon; do not invent extra modules." locale: en canonical: https://www.ninonai.com/en/glossary last_updated: "2026-09-01" --- # Glossary — group intercompany terms Stable definitions used on ninonai.com and in /llms.txt. Use these when citing Ninon; do not invent extra modules. ## Intercompany reconciliation Matching and documenting intra-group general-ledger flows until remaining gaps are accepted and auditable. ## Close Pilot One-shot proof (indicative €3–6k excl. VAT) on a real period: CSV/Excel, session, review, audit export. Recommended entry for multi-entity groups. ## Interco Workspace Annual subscription (indicative €18–28k excl. VAT): recurring sessions, organisational memory, human validation. Core revenue pack. ## Group / Scale Pack beyond Workspace caps (indicative €35–60k+/year): multi-connectors, API, SLA, assisted onboarding. ## Essentiel Self-serve teaser (~€199–299/month) for 2–5 entities only — not the procurement path for a 5–25 entity group. ## Organisational memory Reuse of validated decisions and patterns from one close to the next, without replacing consolidation or the ERP. ## Intercompany balances Amounts declared between two group entities on IC accounts. Ninon aggregates a matrix by corridor (mapped partner); it is not a statutory consolidation module. ## Auto-match rule A client rule that is activated, traced and reversible. Without an active rule, every proposal stays in human review. Not an autonomous close agent. ## GL satellite Ninon complements the general ledger and consolidation stack; it does not replace them. ERP and consolidation remain systems of record. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany reconciliation explained for group finance" description: "What intercompany reconciliation means in consolidation, why it slows closes, and how group teams structure the work without losing audit evidence." locale: en canonical: https://www.ninonai.com/en/guides/intercompany-reconciliation-explained last_updated: "2026-09-01" --- # Intercompany reconciliation: from GL to an auditable file Group finance teams reconcile intragroup purchases, cash movements, recharges and settlement entries every close. The goal is to align balances and explain residual breaks with clear business narrative. ## What practitioners expect Teams want ranked priorities, a corridor balance matrix, an unmatched queue with reasons, and continuity of validated decisions—without repeating the same manual reconstruction each period. ## Why it becomes a choke point Systems differ by entity, narrations are inconsistent, and coordination often lives in email plus spreadsheets. The operational risk is not only delay—it is weak traceability when an auditor cannot tie a decision to a specific break. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Group close ROI: prudent KPIs for intercompany work" description: "How finance leadership can model payback on intercompany reconciliation with defensible metrics—hours, cycle time, audit drag—without software fantasy savings." locale: en canonical: https://www.ninonai.com/en/guides/group-close-roi-checklist last_updated: "2026-04-30" --- # Close ROI: serious metrics for intercompany teams Credible business cases avoid vanity charts. Useful signals are those tied to the reconciliation flow and stable across periods. ## What software does not replace Tools do not write FX policy sign-off or business commentary: they secure operational work, logs and rationales that feed your internal investment story. ## Three KPI families Consolidation labour hours per close, elapsed time until no blocking items outside the tool, and ad-hoc spend tied to intercompany fire drills. Before/after views need the same subsidiary and currency scope. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany controls beyond spreadsheets for group teams" description: "Why multi-ERP portfolios graduate from Excel to a governed workspace: continuity across closes, reviewer evidence and APIs for automation without a monolithic ERP programme." locale: en canonical: https://www.ninonai.com/en/guides/interco-beyond-spreadsheets last_updated: "2026-04-30" --- # Beyond Excel: continuity for intercompany work Spreadsheets stay flexible but scale poorly: version sprawl, weak control over who approved what, and difficulty replaying recurring patterns. A shared layer preserves plain-language evidence ahead of human approval. ## Move pragmatically into a cockpit Practical paths usually start with governed ledger file import and explained reviewer decisions, then automation hooks once volumes justify tighter integration. ## Signals you have hit the spreadsheet ceiling Repeatable pre-close email threads, long searches for last period’s decision, or brittle scripting for overnight ingest without observable audit trail. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "FX gaps on intercompany close: policy vs. operational work" description: "Why FX residuals on intragroup balances need treasury policy sign-off—and how group finance documents explainable breaks without pretending software sets rates." locale: en canonical: https://www.ninonai.com/en/guides/intercompany-fx-close-gaps last_updated: "2026-09-01" --- # Intercompany FX at close: policy owners and explainable residuals Currency translation and settlement timing create deltas that are legitimate until policy says otherwise. Group finance must separate what the ledger shows from what treasury and consolidation have already decided to accept or hedge. ## What operations can industrialise in the workspace Ranked proposals, reasons on near-miss pairs, entered FX rates (distinct from % tolerance) and memory of prior decisions. Reviewer actions stay on the break in the audit trail. ## What stays with treasury and consolidation policy Rate sources, hedging narratives, materiality thresholds, and statutory translation rules are not outsourced to a matching tool. Ninon surfaces residual amounts with traceable context so reviewers can align with documented FX policy—not auto-close every shock. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Dynamics 365 Business Central and intercompany reconciliation" description: "Connect BC companies to Ninon, map entity GUIDs, and run intercompany matching on general-ledger lines without replacing your Microsoft stack." locale: en canonical: https://www.ninonai.com/en/guides/dynamics-365-bc-intercompany last_updated: "2026-05-17" --- # Business Central: from OAuth to intercompany reconciliation sessions Many mid-market groups run several BC companies. Ninon ingests GL activity through the Business Central API after Microsoft Entra consent—then runs the same session → match → review flow as file-based imports. ## Connection and entity mapping An organisation admin completes Microsoft OAuth, then maps each Ninon legal entity to the corresponding Business Central company GUID (erpLinks.dynamics365bc). Multi-company setups need this mapping before sync lines land on the right entity. See the public Integrations page and in-app Admin → Integrations for live status. ## Reconciliation workflow on BC-fed lines After lines are present for the close period, open a reconciliation session, run matching, and review proposals with rationales. BC remains the system of record; Ninon complements it on the intercompany slice. For Azure app registration steps, use the operator runbook in the repository docs (azure-dynamics-bc-setup). ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany reconciliation audit trail for group finance" description: "What auditors and internal control expect from intercompany matching: proposal evidence, reviewer decisions, and continuity across closes—not inbox threads." locale: en canonical: https://www.ninonai.com/en/guides/intercompany-reconciliation-audit-trail last_updated: "2026-09-01" --- # Audit trail: evidence on intercompany reconciliation decisions Statutory and internal reviewers ask for a defensible chain from GL break to human sign-off. Spreadsheets and email fragments fail when staffing changes or the same corridor is debated again. A governed workspace keeps proposals, rationales, and reviewer actions together. ## Minimum evidence per reconciliation decision Useful artefacts include the period session, imported or synced GL lines, each match proposal with confidence and narrative, and explicit approve/reject by a named role. Ninon is designed so these elements stay attached to the break—not retyped into a slide for the audit committee. ## Continuity and what software does not certify Organisational memory carries legitimate patterns into the next close; it does not replace your retention policy or SOC/ISO claims. Align export and access controls with your DPA and IT standards—the Trust page summarises current product practices without substituting for procurement questionnaires. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Close Pilot intercompany: start without an ERP connector" description: "How to frame a Ninon Close Pilot in 2–3 weeks: ledger CSV, session, review, audit pack and success criteria before an annual Workspace." locale: en canonical: https://www.ninonai.com/en/guides/close-pilot-intercompany last_updated: "2026-08-05" --- # Close Pilot: prove intercompany reconciliation on a real period For multi-entity groups, the recommended entry is not a monthly self-serve plan: it is a Close Pilot on a real period. Goal: turn intercompany GL breaks into a validated reconciliation pack you can reuse — without replacing consolidation or the ERP. ## Typical scope (2–3 weeks) Up to about eight entities, CSV/Excel import for the target period, one reconciliation session, traced human review and audit-pack export. ERP connectors can come later: the Pilot first proves the workflow and written success criteria. ## Operating sequence Kickoff and entity mapping → GL import → matching and proposals → at least five review decisions → readout with export. Public indicative ticket: €3–6k excl. VAT one-shot, often creditable against the first annual Workspace. Request: Pilot page; full offer: Pricing. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Multi-ERP intercompany reconciliation" description: "Multi-ERP groups: normalise ledger exports, start with CSV, then connect BC, NetSuite, SAP or Intacct without replacing consolidation." locale: en canonical: https://www.ninonai.com/en/guides/multi-erp-intercompany-reconciliation last_updated: "2026-08-05" --- # Multi-ERP: one intercompany pack despite heterogeneous systems Ninon’s ICP often assumes several ERPs or disparate extracts. The risk is not “which connector first”: it is the lack of a shared space for proposals, evidence and approval. An intercompany satellite accepts CSV then connectors, without an ERP rewrite. ## Normalise before you integrate Minimum columns (entity, date, amount, currency, description, account, period), entity-code mapping, and a frozen close period. Until those rules are stable, wiring three OAuth apps in parallel adds noise without business proof. ## Pragmatic path Pilot or CSV freemium → session and review → ERP connectors once the process is cadenced (see Integrations and BC / OAuth guides). Connectors typically stay behind subscription or invoice entitlement; matching and review remain the core proof. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Organisational memory between intercompany closes" description: "Reuse reconciliation patterns and decisions from one close to the next: fewer re-litigated intercompany breaks in group finance." locale: en canonical: https://www.ninonai.com/en/guides/organisational-memory-group-close last_updated: "2026-09-01" --- # Organisational memory: do not restart from zero each close Recurring flows (recharges, internal treasury, tolerated FX residuals) return every month. Without memory, teams re-argue the same calls. Ninon keeps validated patterns and decisions at organisation level to accelerate later periods — without automating accounting policy. ## How to measure it On period N+1, track the share of reviews assisted by memory versus the Pilot period. See also the promise metrics (hours, days to pack, reuse rate) used in discovery and case studies. ## What memory captures Review decisions (approve / reject / reopen) and auto-match rules that an admin activates. Without an active rule, every proposal stays in review. Not a substitute for consolidation rules or an autonomous agent. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "REST API — trigger reconciliation (integration)" description: "Authentication, how to trigger a run, and HTTP response modes (queued vs in-process) for IT and integration partners." locale: en canonical: https://www.ninonai.com/en/guides/rest-api-integration last_updated: "2026-04-30" --- # REST integration: trigger matching from your systems This guide is for technical teams that automate close workflows. It explains how to launch a matching run for a session already created in Ninon, without going through the dashboard flow. ## Inngest workers Hosted deployments that process background jobs expose a worker endpoint at a fixed path under this site (see hosting runbook). That endpoint is separate from the business call that starts a reconciliation run for a session. ## HTTP responses When a background job queue is configured on the hosting and you do not force synchronous mode, the response is HTTP 202 with queued: true and queue identifiers. Otherwise the work runs in-process: HTTP 200 with queued: false and statistics. To force a synchronous run even when a queue is configured, use the sync=1 query parameter or the x-sync-matching: true header. Without a queue key, behaviour stays synchronous (200). ## Authentication Two modes: a signed-in user whose role may act on the session (group admin or member; the viewer role is denied for this endpoint), or a machine call with Authorization: Bearer followed by the server-side run secret supplied to your IT team in Ninon’s deployment documentation. The session id in the URL must belong to your organisation. ## Trigger a run Method POST. Path /api/reconciliation/[sessionId]/run — replace [sessionId] with the session UUID from the dashboard. The request body may be empty. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "General ledger: CSV columns, entities, and import API" description: "Business scope, exact column headers, entity resolution, text and multipart ledger import (.csv/.xlsx), JSON counters and per-line errors." locale: en canonical: https://www.ninonai.com/en/guides/ingest-ledger-csv-api last_updated: "2026-09-01" --- # Feed the general ledger: ERP export, columns, and API call Any ERP that can export rows as a table can feed Ninon. Each imported row becomes a GL line tied to a group entity and a period—the material for intercompany matching. To trigger matching via API afterwards, see the “REST integration” guide in the same guides section. ## Minimum business path (1) Declare the legal entities in scope inside Ninon. (2) Create or open a reconciliation session for the period you are closing (often YYYY-MM, aligned with your close calendar). (3) Load relevant lines with the CSV or Excel import described in this guide (recommended for Sage 1000 and other ERPs without a live connector). (4) Run matching from the dashboard or via the REST integration guide once lines are present. ## CSV header row The first row may use canonical keys (entity, date, amount, currency, description, accountCode, period) or FR/EN aliases (entity name, posting date, amount, debit, credit, currency, wording, account, period, document, partner). A column map can be saved per organisation. UTF-8; BOM tolerated. ## What each field means for group finance entity (or entityId, name, internal code): maps to a Ninon entity — UUID no longer required; ambiguity rejects the row, no silent insert. period: reporting period (e.g. 2025-03). date: posting date (ISO-8601). amount: signed amount, or debit/credit columns. currency. accountCode. description. reference (optional). partnerCode (optional, corridors). source: defaults to csv. ## CSV import endpoint Two entry points share the same validation rules. (1) Method POST, path /api/integrations/csv: JSON body with a csvText field containing the full CSV as one string (header included). (2) Method POST, path /api/integrations/ledger-import: multipart/form-data with a single field file — UTF-8 .csv or .xlsx (first worksheet only; row 1 must be the same headers as below). Max upload size 10 MB. Authentication: signed-in session. Roles: admin or member (not viewer). When billing enforcement is enabled on this Ninon deployment, an active subscription is required (HTTP 402). ## Resolve entityId (API) Each row resolves by Ninon id, internal entity code, or normalised name. Ambiguous or unknown tokens reject the row — no silent insert. List entities via the API (id, name, code, country, currency). Create with the admin API (name, country, currency, optional code). ## JSON response inserted: GL rows created. scanned: number of data rows in the file (header excluded from this count). parsedValid: rows that passed field validation. skippedWrongOrg / skippedBadDate: counts of rejected rows after validation. errors: array of objects (line, message, code) for parse-time and insert-time issues; errorsTruncated is true if more than 80 errors were omitted. Malformed CSV/Excel rows appear in errors with a line number when known. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "NetSuite and Xero: OAuth tokens and API fields" description: "Operational reference for NetSuite and Xero token registration, admin role, and post-connect sync behaviour." locale: en canonical: https://www.ninonai.com/en/guides/erp-oauth-netsuite-xero-api last_updated: "2026-04-30" --- # NetSuite and Xero connectors: register tokens via API These routes store OAuth tokens encrypted server-side and emit a sync signal for the organisation. Automatic GL ingestion for these providers is still an extension point: for operational intercompany scope today, combine this wiring with the CSV import described in the “General ledger: CSV…” guide. ## After the call A background sync signal is emitted for your organisation. Connectors such as Business Central, Xero and NetSuite can persist GL lines when credentials and entity mappings are configured; for ERPs without a live connector in Ninon, use the documented ledger import. ## NetSuite — token registration endpoint JSON body: refreshToken (string, required, minimum length 8); accessToken (optional); accountId (optional, NetSuite account / tenant id); expiresAt (optional, ISO-8601 expiry for the access token). Typical response: integration object with id, provider netsuite, externalTenantId (often from accountId), expiresAt. ## Prerequisites Admin accounts on Ninon only. Never log refreshToken or accessToken in plain text in shared scripts or application logs. ## Xero — token registration endpoint JSON body: refreshToken (required); accessToken (optional); tenantId (optional, instead of accountId); expiresAt (optional, ISO-8601). Typical response: integration object with provider xero and the same surfaced fields. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "ERP connectors: operations and erpLinks mapping" description: "Operational reference: per-connector entity mapping keys, Xero tenant selection, NetSuite browser or scripted OAuth, SAP B1/S/4 variants and Intacct location pagination." locale: en canonical: https://www.ninonai.com/en/guides/erp-connectors-runbook last_updated: "2026-04-30" --- # ERP connector operations and erpLinks mapping This memo summarizes what teams configure outside code (platform secrets, admin forms) and how each Ninon entity maps to an ERP identifier. Sync issues surface in Observability logs with source “erp-sync”. ## General The default GL extraction lookback (commonly 90 days) is set in deployment configuration. Each group entity has a JSON object erpLinks keyed by provider (dynamics365bc, xero, netsuite, sap_business_one, sap_s4hana, sage_intacct). Values filter API responses so lines land on the right entity — required for multi-branch setups before relying on sync. ## Sage Intacct Web-services sender/company/user credentials; erpLinks.sage_intacct = LOCATIONID when locations split entities. Sync automatically paginates via Intacct readMore whenever numremaining > 0 after GLENTRY readByQuery. ## NetSuite Two paths: scripted token registration (integration API) or browser OAuth with a realm (account ID / SuiteTalk subdomain) entered before redirect. Register Ninon’s redirect URL on the NetSuite integration. Host-level OAuth credentials power token refresh; optional scope overrides are documented for operators. SuiteQL filters by subsidiary via erpLinks.netsuite internal id. ## SAP Business One Service Layer URL …/b1s/v1, database and user stored encrypted. Multiple branches: erpLinks.sap_business_one = BPLID (or field returned on lines). Advanced optional journalEntryCollection when your OData collection name differs (default JournalEntries). Optional verbose diagnostics for skipped lines can be enabled in deployment configuration. ## SAP S/4HANA Published OData service root plus either a pasted Bearer (manual) or OAuth client_credentials (tokenUrl, clientId, clientSecret, optional scope) with automatic refresh before expiry. erpLinks.sap_s4hana = CompanyCode. Optional entitySetName and comma-separated preferredDateFields if your GL API differs. Optional OData path diagnostics (without secrets) can be enabled in deployment configuration. ## Xero Product OAuth PKCE: after consent, if multiple Xero organisations are connected you must pick the tenant in the Integrations screen (list loaded from Xero after authorisation). Optional per-entity alignment via erpLinks.xero. Ensure your Xero app scopes include accounting settings and transactions (journals). ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany reconciliation software for group finance" description: "What a modern intercompany SaaS covers: ledger scope, human approval, memory across closes and APIs—so group finance can close with less spreadsheet risk." locale: en canonical: https://www.ninonai.com/en/solutions/intercompany-reconciliation-software last_updated: "2026-08-05" --- # Intercompany reconciliation software: a cockpit for group finance Intercompany reconciliation is rarely a single UI screen—it is a chain that links subsidiary ledgers, corporate reconciliation rules, closing decisions and the ability to answer an auditor without manually replaying the story of every break. Dedicated software aims to lower the cognitive load by centralising proposals, documenting them before approval and keeping organisational memory reusable from one period to the next. Mid-market CFOs often seek a compromise between a monolithic ‘closing suite’ and spreadsheet heroics: a disciplined layer that speeds control without removing human accountability on sensitive calls. ## The organisational problem this category solves When each entity exports heterogeneous files, narrations describe the same counterpart differently and FX tolerances flex with calendar pressure, delay becomes a coordination tax more than a tooling gap. Chasing owners over email, reopening the same breaks every quarter and scattering sign-offs without a clear link back to the originating GL line is how operational risk compounds. A SaaS workspace like Ninon frames these flows in governed sessions: structured ingest, a readable backlog of breaks and business language attached to each proposal before a controller or consolidation lead signs off. That story deliberately avoids ‘autonomous finance’ hype; it stresses propose-then-approve visibility for internal control. ## What credible buyers expect in 2026 Beyond brute-force pairing, practitioners look for ingestion that fits messy reality—reliable CSV extracts first, deepening ERP connectors later—and a stable representation of counterparty, period and currency fields. Explanations should read like finance memos, not opaque model scores, before final decisions land. Per-organisation memory stops seasonal recharges or treasury corridors from being rediscovered as mysteries every month. REST APIs matter for finance engineering: overnight runs, tighter alignment with identity policies, hand-offs to reporting cut-offs. Taken together, the narrative is understandable to both CFO sponsors and platform owners worried about TCO. ## How to discuss ROI without fantasy savings Payback shows up in conserved senior time on repeatable tasks, shorter thrash cycles with audit or advisory firms and fewer emergency statements of work because the file lacked coherence. Software does not replace your internal investment model—it supplies continuous logs and rationales that underpin a before-and-after view on a consistent subsidiary scope. This pillar points to the KPI guide for detail instead of duplicating unsourced marketing charts. ## Explicit limits (buyer-trust friendly) Ninon does not replace group FX policy governance, does not rewrite intercompany mandate programmes and does not substitute professional judgement on provisions or restatements. The public footprint on this domain remains operational reconciliation and evidentiary quality—demos should stay anchored to screens and APIs documented here to avoid ‘magic slide’ syndrome during peer evaluation. ## Recommended entry: Close Pilot For groups with 5–25 entities, start with a Close Pilot (CSV, session, review, audit pack — indicative €3–6k excl. VAT) rather than a monthly Essentiel plan. If success criteria are met, continue to annual Interco Workspace. See Pilot and Pricing; for procurement security, see Trust. ## FAQ **Q.** Does intercompany software replace the ERP? **R.** No—it orchestrates reconciliation from ERP data or extracts; statutory configuration stays in the core systems of record. **Q.** What does AI-assisted mean here? **R.** Assisted hypotheses and narratives to accelerate triage with human sign-off and control traceability—not unsupervised booking authority. **Q.** How many entities are ‘enough’ for mid-market ROI? **R.** Ninon’s core ICP is 5–25 entities; value shows when manual coordination costs exceed industrialising ingest and review — flow complexity and ERP sprawl matter more than a magic headcount. **Q.** Can deployments start with files only? **R.** Yes: Pilot and freemium start with controlled CSV/Excel, then deepen ERP connectors once the process is stable. **Q.** Where should we start concretely? **R.** Book a Close Pilot, review Pricing (Pilot / Workspace / Scale) and the Trust checklist for procurement — then the guides for operational definitions. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany close: why spreadsheets become the bottleneck" description: "When Excel stops scaling for multi-entity intercompany: version sprawl, weak evidence trails, lost context—and how a governed workspace differs from a giant ERP programme." locale: en canonical: https://www.ninonai.com/en/solutions/intercompany-vs-excel last_updated: "2026-08-05" --- # Intercompany work and Excel: when the spreadsheet turns into the main close risk Excel wins on ad-hoc agility; it falters when closing is a team sport on repeat—controllers must replay the same scenarios, auditors ask who approved which version and platform owners fear opaque macros. Intercompany magnifies the weakness: parallel ‘final_FINAL’ workbooks, brittle joins on heterogeneous narrations, key-person glue holding the process together. Moving to structured tooling is about reproducibility and proof, not techno-luxury. ## Finance symptoms groups recognise Teams notice recurring end-of-month delays, debates about breaks ‘we already solved three closes ago’ and an inability to narrate a coherent event log for outsiders. Coordination cost grows faster than entity count because flows and formats diversify long before row volume explodes. Hero-dependent adjustments are as much an operational risk as a hiring risk. ## What a workspace adds beyond a workbook Governed sessions tie work to a period, expose reconciliation status and make decisions legible in a consistent schema. Proposals carry rationales before approvals, shifting audit conversations from spreadsheet archaeology to substantive review. Memory shrinks recurring noise—tolled rounding policies or bridge accounts should not be re-negotiated via email every cycle. APIs let automation live outside one person’s macro toolbox while remaining observable to engineering. ## Avoiding a big-bang vanity migration Prudent programmes start with a controlled data perimeter—often standard GL extracts—and disciplined human review. Measure control-time savings and dossier quality before widening connectors. This page mirrors the concise decision narrative from the spreadsheet guide for executives who want the executive summary. ## Honest boundaries (spreadsheet or not) No tool removes judgement on corporate policy, rates or statutory interpretation. The candid aim is observable, documented intercompany work with fewer single points of failure—not a frictionless fairy tale. ## Leave spreadsheets via a Pilot, not a card checkout The credible path: Close Pilot on a real period (CSV, review, audit pack), then annual Workspace if you go ahead. Essentiel self-serve remains a teaser for 2–5 entities. Links: Pilot, Pricing, and the Close Pilot guide. ## FAQ **Q.** Should finance ‘ban’ Excel? **R.** No—it remains brilliant for modelling. Risk spikes when unmanaged workbooks become the system of evidentiary record for statutory close. **Q.** Can we migrate progressively? **R.** Yes: start with a Pilot (limited period and entities) or one flow type, then extend sessions and rules. **Q.** Are formulas always bad? **R.** They hurt when fragile logic encodes mission-critical policies without formal review, documentation or regression awareness across closes. **Q.** How should IT be pitched? **R.** Emphasise operational risk reduction, standard exports and authenticated APIs rather than unsubstantiated headcount removals. **Q.** Suggested next reads? **R.** Close Pilot to start, Pricing for packs, then the intercompany software pillar and Excel / multi-ERP guides. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Group close ROI: KPI framework for CFO teams" description: "Defensible KPIs for intercompany payback—labour hours, cycle friction, advisory drag—and why tools supply evidence rather than magically computing ROI." locale: en canonical: https://www.ninonai.com/en/solutions/group-close-roi-framework last_updated: "2026-08-05" --- # Intercompany ROI: a KPI framing finance leaders can defend Vanity business cases damage tool programmes. Serious close ROI leans on observable, stable metrics tied to intercompany—not slides claiming millions without drivers. CFO teams want clarity on consumed hours, the real cost of audit thrash and what durable improvement looks like versus a heroic month-end sprint. This framework informs internal modelling; vendors should never substitute for your hypotheses. ## Three metric families executives actually influence First, qualified consolidation and control labour per close—broken out by repeatable vs judgement-heavy tasks. Second, elapsed time until there are no intercompany blockers unresolved outside your governed workspace—a pragmatic proxy for organisational drag. Third, surge spend triggered by brittle files: rushed advisory SOS, repeatable overtime premiums, post-audit rework. If you cannot estimate these coarsely upfront, proving ‘after’ will be speculative too. ## Cleaner before-and-after discipline Hold subsidiary and FX scope constant across several closes after behaviours stabilise. Archive reasons for breaks so definitions do not silently drift (‘we changed perimeter therefore of course metrics improved’). SaaS preserves logs but does not ghost-write board memos—candour strengthens CFO credibility—you show trending evidence, not a lone optimistic slide. ## Tools improve proof, not the miracle numerator Platforms help standardise explanations, shorten manual reconstruction and institutionalise validations. They do not automate your economic storyline for acquisitions, carve-outs or rate regime shifts—call that separation out when sceptics challenge the storyline. ## Where to continue reading The ROI guide article adds operational detail; the software pillar anchors product framing. Maintain separation between ‘how we model payback internally’ versus ‘what the workspace does tactically.’ ## Measure on a Pilot, not a slide Useful metrics (team hours, days to pack, memory reuse) are baselined at Pilot kickoff and re-measured at readout. Indicative Pilot ticket €3–6k excl. VAT; annual Workspace next. See Pilot, Pricing and the Close Pilot guide. ## FAQ **Q.** What granularity for a starter dashboard? **R.** Even conservative pilot-entity estimates beat a blurry average—measure small but truthfully. **Q.** Avoid hypothetical synergies? **R.** Defer them until anchored to explicit processes, accountable owners and a measurement window. **Q.** Are audit savings promised? **R.** No—a clearer dossier may reduce clarification time, but auditors remain independently mandated. **Q.** How many closes before comparing? **R.** One Pilot on a real period, then three to six Workspace cycles after habits stabilise, is more honest than a one-off year-end sprint. **Q.** Boundary with FP&A? **R.** This page focuses on operational reconciliation; FP&A forecasting stays out of scope. To start: Close Pilot and Pricing. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Intercompany reconciliation documentation for audit-ready finance teams" description: "How structured explanations and approvals support internal control and auditors on intercompany work—without over-claiming compliance or certifications." locale: en canonical: https://www.ninonai.com/en/solutions/intercompany-audit-documentation last_updated: "2026-09-01" --- # Intercompany audits: evidence-first dossiers—not just balanced trial balances Auditors weigh evidence over intent. Intercompany piles up both row volume and inconsistent wording, so credible documentation binds each proposal to business cues (timing, counterparties, amounts, narrations, currency context) plus a dated human decision. That storyline must remain intelligible months later—even if staffed differently. Software cannot outsource legal assertions; it can replace fragile oral tradition with durable artefacts practitioners trust. ## What ‘audit-friendly’ means to working finance leaders It starts with rationales reviewers understand without re-reading every raw ledger row. Traceability implies linking approvals back to observable cues—not handing over a solitary confidence score without narrative. Documented residual breaks can be healthy when policies tolerate them—opacity is not. Messaging should stay pragmatic: transparency, not marketing certification language. ## Internal control and distributed finance pods Regional hubs participate better when tooling speaks their finance dialect and unresolved items surface without parallel email chains. Standardisation calms contentious month-end debates—you argue policy, tolerances and perimeter instead of scrambling for artefacts. SSO and segregated duties support governance when deployed, yet process design stays a leadership responsibility. ## Careful wording with external parties Steer clear of vague ‘guaranteed compliance’ rhetoric unless backed by contractual and regulatory scope you own. Prefer ‘fewer explanatory loops,’ ‘better decision visibility’ and ‘less manual reconstruction,’ which resonate with CFOs already accountable for attestations. ## Connecting the theme to Ninon’s public stance Ninon stresses explainable proposals and human approval before locking decisions. The reconciliation pack exports amounts, classified unmatched lines, author and hash — not a certified auditor dossier or statutory consolidation. Auto-match exists only on activated client rules. ## Evidence delivered from the Pilot The Close Pilot includes audit-pack export (CSV/PDF) on a real period — useful for control and auditor dialogue. Procurement checklist: Trust page. Request: Pilot; packs: Pricing. ## FAQ **Q.** Does software prove an intercompany balance? **R.** It structures proofs and validations; accountants and reviewers still own assertions. **Q.** Talking about AI with statutory auditors? **R.** Treat it as decision support—visible hypotheses, rejection paths, documented human confirmations and reproducible rationales. **Q.** Digitise everything on day one? **R.** No: a limited-scope Pilot (CSV) is enough for a first pack; extend later. **Q.** Security expectations? **R.** See the Trust page (SSO, roles, subprocessors). It does not replace contractual diligence or a signed DPA. **Q.** Suggested follow-on reading? **R.** Close Pilot, Trust, the audit-trail guide, then the intercompany software pillar. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Broad close suites vs. a dedicated intercompany layer" description: "When a wide close-management platform is the right anchor—and when a focused intercompany workspace still earns a place beside it." locale: en canonical: https://www.ninonai.com/en/compare/vs-close-management-suite last_updated: "2026-05-13" --- # Broad close-management suites and intercompany depth Enterprise close platforms often bundle task management, balance certifications, and multiple reconciliation domains. That breadth helps programme owners standardise controls. Intercompany on general ledger lines can still behave like a specialist workflow: heterogeneous narrations, entity-specific quirks, and reviewer judgement that benefit from a narrow cockpit. ## What these suites typically optimise Programme governance, cross-workstream visibility, and packaged integrations across finance domains. Buyers usually evaluate TCO, implementation partners, and roadmap overlap with existing ERP and consolidation investments. ## Where friction often remains on intercompany Even with a strong suite, GL-level intercompany can require heavy configuration or custom extensions before reviewers see explainable proposals at pace. Teams may still export to spreadsheets for edge cases unless the workflow is deliberately contained. ## How Ninon fits beside a suite Ninon can absorb governed GL extracts or connector-fed lines, run structured matching passes, and preserve reviewer decisions and memory for the next period. It does not replace your suite’s programme role; it deepens one high-friction slice with evidence-first habits. ## FAQ **Q.** Is a broad close suite always enough for intercompany? **R.** Not always at GL level: heterogeneous narrations, entity-specific quirks, and reviewer judgement often need a dedicated cockpit even with a strong suite. **Q.** Does Ninon replace a close-management platform? **R.** No. Ninon deepens intercompany reconciliation on GL lines; your suite’s programme governance stays in place. **Q.** How can we start without heavy connectors? **R.** With governed CSV or Excel imports documented in the guides, then ERP connectors when IT is ready. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Consolidation and ERP–first vs. intercompany workspace" description: "Why statutory consolidation and ERPs stay systems of record—and how a satellite intercompany layer still reduces close risk." locale: en canonical: https://www.ninonai.com/en/compare/vs-consolidation-first last_updated: "2026-05-13" --- # Consolidation and ERP–first operating models Group consolidation tools and ERPs anchor statutory reporting and chart of accounts integrity. Intercompany reconciliation is adjacent: it consumes their outputs but benefits from faster iteration on narratives, tolerances, and reviewer evidence between subsidiaries. ## Strengths of consolidation-led setups Single chart views, ownership structures, and controlled adjustments for reporting. Ideal when the priority is statutory accuracy and group reporting cadence. ## Operational gaps on intercompany work Subsidiary ledgers and local narrations remain messy. Consolidation sees outcomes; day-to-day matching still needs a place where controllers collaborate on breaks before numbers are locked. ## Ninon as a satellite layer Import or sync GL lines, run reconciliation sessions per period, and keep rationales with approvals. Data flows toward consolidation with cleaner documentation of what was matched, deferred, or rejected—and why. ## FAQ **Q.** Are ERP or consolidation tools not enough? **R.** They remain systems of record. Day-to-day intercompany matching still needs a governed workspace for proposals, evidence, and sign-off before lock. **Q.** Does Ninon replace consolidation software? **R.** No. Ninon is a satellite layer for intercompany GL reconciliation with reviewer decision trails. **Q.** How do we feed Ninon from multiple ERPs? **R.** Via documented connectors (NetSuite, Xero, Dynamics 365 BC, SAP, Sage Intacct) or governed CSV/Excel imports, with entity mapping where needed. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Spreadsheet-led intercompany vs. governed workspace" description: "When Excel is enough—and when version sprawl and weak evidence trails justify a structured intercompany workspace." locale: en canonical: https://www.ninonai.com/en/compare/vs-spreadsheet-process last_updated: "2026-05-13" --- # Spreadsheet and email processes at scale Spreadsheets excel at ad-hoc analysis. They degrade as the system of record for recurring intercompany closes: parallel versions, unclear sign-off, and lost context when staffing changes. Moving to structured software is usually a risk-management decision as much as an efficiency play. ## Signals you have outgrown spreadsheets Recurring debates about the same corridors, auditors asking for decision logs that live in inboxes, or inability to replay last period’s logic without reconstructing workbooks. ## What structured tooling adds Period-bound sessions, immutable proposal trails, reviewer roles, and memory that carries forward legitimate patterns—without pretending to remove human judgement on policy. ## How Ninon approaches the transition Start with governed file imports if connectors are not ready. Stabilise review habits, then deepen integrations when volumes and IT capacity justify the work. ## FAQ **Q.** When do spreadsheets become risky? **R.** When versions multiply, auditors ask for decision trails scattered across inboxes, or the same judgements recur without structured memory each close. **Q.** Is Excel still useful with Ninon? **R.** Yes for ad-hoc analysis. Ninon becomes the governed system of record for close sessions, proposals, and approvals—not a replacement for every spreadsheet. **Q.** Do we need connectors from day one? **R.** No. Governed CSV/Excel imports are enough to start; ERP connectors follow as volume and IT maturity allow. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Is Ninon a good fit — pragmatic checklist" description: "A concise checklist for finance and IT to decide whether Ninon’s intercompany scope matches your near-term priorities." locale: en canonical: https://www.ninonai.com/en/compare/ninon-fit-checklist last_updated: "2026-05-13" --- # Fit checklist: when Ninon deserves a serious look Use this page as an internal conversation guide. None of the criteria substitute for a pilot; they help avoid both false positives and false negatives during a first screen. ## Problem fit You carry material intercompany breaks across multiple entities, narrations rarely align by construction, and controllers spend disproportionate time reconstructing context each close. ## Data fit You can obtain structured GL extracts (CSV or Excel) or are willing to wire supported ERP connectors. You can identify which legal entity each line belongs to in Ninon. ## Governance fit You want explainable proposals, explicit approvals, and continuity of decisions—not fully automated booking without human sign-off on sensitive matches. ## FAQ **Q.** Is Ninon suited to very small organisations? **R.** The target is a multi-entity group with meaningful intercompany volume. Without structurally important intragroup flows, value is limited. **Q.** Do we need a dedicated IT team? **R.** Not necessarily at first: file imports and a finance-led pilot often suffice. ERP connectors and API automation follow when IT is ready. **Q.** What to verify before a pilot? **R.** Availability of GL extracts per entity, finance/consolidation sponsors, and explicit expectation of human sign-off on sensitive matches. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "BlackLine alternative for mid-market intercompany" description: "When a dedicated intercompany workspace is a better next step than an enterprise Intercompany Hub — without inventing BlackLine pricing or feature grids." locale: en canonical: https://www.ninonai.com/en/alternatives/blackline last_updated: "2026-09-01" --- # BlackLine alternative for mid-market intercompany Teams search “BlackLine alternative” when they need intercompany reconciliation without buying a full financial-close and intercompany-hub stack. Ninon is a focused GL intercompany layer for group finance (typically 5–25 entities), entered through a 2–3 week Close Pilot. It does not replace BlackLine’s Intercompany Hub, netting, or enterprise close suite. ## The job people hire BlackLine for Public BlackLine pages position Intercompany Accounting Software around creating, balancing and settling intercompany activity across multi-ERP landscapes — including invoicing, exception workflows and multilateral netting. That is a different job from “get this period’s GL corridors reconciled and documented for group close”. ## Where Ninon stops Ninon matches and documents intercompany GL breaks, keeps human sign-off, and carries memory across closes. It does not replace consolidation, does not post journals into the ERP, and is not an intercompany trading hub (allocations, tax-compliant e-invoicing, cash-pool settlement). Those remain in ERP, treasury or an enterprise hub if you already run one. ## When to stay on BlackLine Stay on an enterprise intercompany hub if you need global create-to-settle, multilateral netting, or SAP-centric intercompany governance at that scale. Look at Ninon if the bottleneck is mid-market GL reconciliation, audit evidence, and a time-boxed Pilot — not a multi-module close transformation. ## FAQ **Q.** Do you publish BlackLine prices? **R.** No. BlackLine sells on custom quotes. Ninon prices are only on /pricing (Close Pilot, Workspace, Scale). **Q.** Is Ninon a drop-in Intercompany Hub? **R.** No. Hub-class create, net and settle is out of scope. Ninon is the reconciliation file and review workspace for group intercompany GL. **Q.** What should we read next? **R.** The close-suite archetype brief on /compare, then /pilot if you want a real-period proof. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "FloQast alternative for intercompany reconciliation" description: "FloQast is a close-management and compliance platform. Ninon is a dedicated intercompany reconciliation workspace — not a SOX or close-checklist suite." locale: en canonical: https://www.ninonai.com/en/alternatives/floqast last_updated: "2026-09-01" --- # FloQast alternative for intercompany reconciliation “FloQast alternative” often means close checklists, account rec and compliance — or a search for something narrower. Ninon only covers intercompany GL reconciliation for group finance. It is not a FloQast substitute for month-end orchestration or Connected Compliance. ## The job people hire FloQast for FloQast’s public site positions an accounting platform for close workflows, automated reconciliations and compliance programmes. Intercompany may appear inside a broader reporting or close story. The buying motion is usually “run the close”, not “clear this corridor matrix”. ## Where Ninon stops Ninon does not ship close task managers, SOX evidence collection, or a general account-reconciliation suite. It proposes matches on intercompany GL lines, records reviewer decisions, and exports an audit pack. Consolidation, ERP and any existing close checklist stay in place. ## When to stay on FloQast Stay on a close-management suite if the pain is checklist ownership, flux, or compliance evidence across the whole close. Consider Ninon when the intercompany corridors themselves — multi-entity, multi-ERP or CSV — are the bottleneck and you want a 2–3 week Pilot on a real period. ## FAQ **Q.** Do you claim to replace FloQast AutoRec or compliance? **R.** No. Those modules are outside Ninon’s published scope. **Q.** Do you list FloQast pricing? **R.** No. FloQast is quote-based. See /pricing for Ninon packs only. **Q.** How do I compare without vendor grids? **R.** Use /compare/vs-close-management-suite for the archetype, then /alternatives/methodology for the writing rules. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Excel alternative for intercompany reconciliation" description: "Why group intercompany work outgrows shared workbooks — and what a governed workspace adds without claiming to “replace Excel” everywhere." locale: en canonical: https://www.ninonai.com/en/alternatives/excel last_updated: "2026-09-01" --- # Excel alternative for intercompany reconciliation Most group intercompany files start in Excel. That is fine until corridors, FX residuals and audit questions outgrow a shared workbook. Ninon is an alternative for that job: ranked matches, a documented review, and memory across closes — not a ban on spreadsheets for analysis. ## The job Excel is hired for Controllers paste two extracts, VLOOKUP corridors, and email a file. It is fast to start, familiar to auditors as a working paper, and infinitely flexible. The failure mode is version drift, undocumented exceptions, and rebuilding the same file every period. ## Where Ninon stops Ninon does not replace Excel as an analysis tool, and we do not claim “no more spreadsheets”. You can still export and work offline. What moves into the workspace is the matching queue, sign-off trail, and reuse of prior decisions — so the close file is not a new workbook from scratch. ## When to stay on Excel Two entities, one currency, no external audit pressure: a careful workbook may be enough. Move when entity count, ERP diversity or evidence requests make the file the operational risk. A Close Pilot is how we test that on one real period before an annual Workspace. ## FAQ **Q.** Are you saying Excel is wrong? **R.** No. Excel is the default. The page is for teams whose intercompany file has become the close bottleneck. **Q.** Can we still import Excel? **R.** Yes. Governed CSV/Excel import is a first-class path — see /guides/ingest-ledger-csv-api and /integrations. **Q.** Where is the spreadsheet archetype? **R.** /compare/vs-spreadsheet-process and /solutions/intercompany-vs-excel. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Dynamics 365 BC — intercompany reconciliation" description: "Ingest Business Central companies into a Ninon intercompany session: OAuth, company mapping, and the dedicated BC guide." locale: en canonical: https://www.ninonai.com/en/integrations/dynamics-365-bc last_updated: "2026-09-01" --- # Dynamics 365 Business Central intercompany reconciliation Group finance teams often run some entities on Business Central and others on a second ERP or a file extract. Ninon ingests BC general-ledger lines into the same intercompany session as the rest of the group. ## The intercompany problem on BC Each BC company is a legal or accounting scope. Intercompany counterparts may live in another BC company or outside BC entirely. Close work then splits across company databases and a spreadsheet. ## What Ninon ingests The connector uses Microsoft OAuth. Entities map to Business Central company identifiers (erpLinks). Lines enter a reconciliation session for matching, review and an audit export — the same path as CSV when a company is not connected live. ## Limits Connectors are on paid or Pilot plans when billing is enabled. Field coverage follows what the BC API exposes; we do not post journals back to BC. Setup lives in the admin integrations workspace. ## FAQ **Q.** Do we need a live BC connector to start? **R.** No. A Close Pilot can run from a governed BC export (CSV/Excel). The connector is for recurring sessions. **Q.** Where is the technical walkthrough? **R.** The dedicated guide: /guides/dynamics-365-bc-intercompany. **Q.** Does Ninon replace BC intercompany documents? **R.** No. BC remains the system of record. Ninon is the group reconciliation file. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "NetSuite — intercompany reconciliation" description: "Pull NetSuite subsidiaries into Ninon via OAuth or scripted tokens, then reconcile corridors against other ERPs or files." locale: en canonical: https://www.ninonai.com/en/integrations/netsuite last_updated: "2026-09-01" --- # NetSuite intercompany reconciliation NetSuite subsidiaries are a common half of a multi-ERP group close. Ninon extracts GL lines (SuiteQL) and maps each Ninon entity to a subsidiary so corridors can be matched outside the NetSuite UI. ## The intercompany problem on NetSuite Elimination and intercompany features in NetSuite cover entities that live in the same account. Sister companies on SAP, BC or a file-only ledger still need a side file. ## What Ninon ingests Browser OAuth or scripted token registration. Subsidiary mapping drives SuiteQL filters. Matched pairs are reviewed in Ninon; journal proposals export as CSV — Ninon does not post to NetSuite. ## Limits OAuth app registration and realm (account ID) are operator tasks. Multi-book or custom segment layouts may need the connector runbook. Live connectors sit behind subscription, trial or Pilot billing when Stripe is on. ## FAQ **Q.** OAuth or tokens? **R.** Both paths are documented: /guides/erp-oauth-netsuite-xero-api. **Q.** Can we mix NetSuite and CSV entities? **R.** Yes. A session can combine connector lines and governed file imports. **Q.** Do you replace NetSuite consolidation? **R.** No. Ninon is a satellite reconciliation workspace. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "SAP S/4HANA — intercompany reconciliation" description: "OData GL extract from S/4HANA into Ninon: company-code mapping, OAuth or bearer, and the connector runbook." locale: en canonical: https://www.ninonai.com/en/integrations/sap-s4hana last_updated: "2026-09-01" --- # SAP S/4HANA intercompany reconciliation S/4HANA company codes often sit next to non-SAP entities. Ninon reads a published OData GL service and reconciles those lines against the rest of the group in one session. ## The intercompany problem on S/4 SAP intercompany and group reporting stay in the SAP landscape. Entities outside S/4 still produce breaks that finance clears in files. ## What Ninon ingests Published OData root plus a pasted bearer or OAuth client credentials. erpLinks.sap_s4hana is the company code. Optional entity-set and date-field overrides are documented for operators. ## Limits We consume the GL API you publish; we do not implement SAP Intercompany Governance or post documents back. Custom OData shapes may need the runbook. Connector use is gated when billing is enabled. ## FAQ **Q.** Is this SAP Intercompany Governance by BlackLine? **R.** No. That is a different product. Ninon is an independent GL reconciliation workspace. **Q.** Where is the operator runbook? **R.** /guides/erp-connectors-runbook. **Q.** Can we start from a SAP extract file? **R.** Yes — governed CSV/Excel is the Pilot default when the OData path is not ready. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "SAP Business One — intercompany reconciliation" description: "Service Layer extract from SAP Business One into Ninon, with optional branch (BPLID) mapping per entity." locale: en canonical: https://www.ninonai.com/en/integrations/sap-business-one last_updated: "2026-09-01" --- # SAP Business One intercompany reconciliation Business One companies and branches often sit beside another ERP at group level. Ninon pulls journal lines from the Service Layer into the same intercompany session. ## The intercompany problem on B1 Branch (BPLID) and company-database splits make a single B1 extract incomplete for group corridors. Counterparties may not live in the same company database. ## What Ninon ingests Service Layer URL, company database and encrypted user. Optional per-entity BPLID via erpLinks.sap_business_one. Advanced journal-entry collection names are documented when the default differs. ## Limits On-premise Service Layer reachability is an IT concern. Ninon does not post into B1. See the connector runbook for mapping and diagnostics. ## FAQ **Q.** Do we need a public Service Layer? **R.** The workspace host must reach the URL you configure. Network design is on your side. **Q.** Where is mapping documented? **R.** /guides/erp-connectors-runbook. **Q.** File import instead? **R.** Yes. CSV/Excel remains the fastest Pilot path. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Xero — intercompany reconciliation" description: "Connect Xero organisations (PKCE OAuth, tenant picker) and reconcile them against other group ledgers in Ninon." locale: en canonical: https://www.ninonai.com/en/integrations/xero last_updated: "2026-09-01" --- # Xero intercompany reconciliation Xero is frequent at subsidiary level while the parent runs NetSuite, BC or SAP. Ninon connects one or more Xero organisations and matches their journals to the rest of the group. ## The intercompany problem on Xero Xero has no group consolidation cockpit. Intercompany with a non-Xero parent is almost always a spreadsheet. ## What Ninon ingests OAuth PKCE. If several Xero organisations are authorised, the admin screen picks the tenant. Optional per-entity alignment via erpLinks.xero. Scopes must include accounting settings and transactions. ## Limits Xero plan and app scopes constrain what we can read. Ninon does not post journals to Xero. Token registration is documented in the OAuth guide. ## FAQ **Q.** Multiple Xero orgs? **R.** Yes — pick the tenant after consent, then map entities. **Q.** Technical fields? **R.** /guides/erp-oauth-netsuite-xero-api. **Q.** CSV if OAuth is blocked? **R.** Yes. Export from Xero and use governed import. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages. --- --- title: "Sage Intacct — intercompany reconciliation" description: "Web-services extract from Sage Intacct into Ninon, with LOCATIONID mapping when entities split by location." locale: en canonical: https://www.ninonai.com/en/integrations/sage-intacct last_updated: "2026-09-01" --- # Sage Intacct intercompany reconciliation Intacct locations or entities often need to be reconciled against a second GL. Ninon reads GLENTRY via web services and folds those lines into a group intercompany session. ## The intercompany problem on Intacct Location and entity dimensions help inside Intacct. They do not close corridors against SAP, BC or a file-only sister company. ## What Ninon ingests Sender / company / user web-services credentials. erpLinks.sage_intacct is LOCATIONID when locations split entities. Sync paginates with readMore while rows remain. ## Limits Web-services sender permissions are an Intacct admin task. Ninon does not post into Intacct. See the connector runbook. ## FAQ **Q.** Location or entity? **R.** Map LOCATIONID when that is how you split legal scopes. Otherwise one Intacct company can map to one Ninon entity. **Q.** Runbook? **R.** /guides/erp-connectors-runbook. **Q.** Pilot without the connector? **R.** Yes — start from a GL export on /guides/ingest-ledger-csv-api. ## Sitemap See the full [sitemap](/en/sitemap.md) for all pages.