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