---
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.