Intercompany transactions

The elimination postings of a group: the entries that take one company's balance against another's. They are why a consolidated figure is not the subsidiaries added up - revenue lower than the parts, a loan that nets out - so this read explains a difference rather than totalling a month.

The endpoint

MethodPathAnswers
GET/api/v1/organisations/{organisation}/intercompany-transactions Try it The elimination postings of one month

Needs a bearer token, a credential issued for the group, and the intercompany.read scope. These postings belong to a group, so the path names the group's own company: a subsidiary's journal holds its own entries and answers an empty list, never another company's eliminations.

The parameters

ParameterWhat it does
periodThe month, Mon-YYYY. Answers the reporting month when it is not given.
scenarioActual, Budget or Forecast. Answers Actual when it is not given.
page, per_pagePaging, as everywhere.

A parameter it does not take is refused by name rather than ignored, because it would look applied and change nothing.

What it answers

GET /api/v1/organisations/149/intercompany-transactions?period=Sep-2026

{
  "data": [
    {
      "reference": "Entry #3184",
      "date": "2026-09-30",
      "period": "Sep 2026",
      "scenario": "Actual",
      "data_type": "elimination_sales_purchases",
      "type": "Elimination, Sales / Purchases / Services",
      "from_organisation": "Brizo Demo Pte Ltd",
      "to_organisation": "Brizo Demo Services Pte Ltd",
      "description": "Eliminate intra-group sales, September",
      "debit": 1090.00,
      "credit": 1090.00,
      "net": 0.00,
      "line_count": 2,
      "accounts": "4000 - Sales Revenue, 5000 - Cost of Sales",
      "entered_by": "Sarah Lim"
    }
  ],
  "page": 1, "per_page": 50, "total": 1, "has_more": false
}
FieldWhat it says
referenceThe entry's reference: its journal id when it has one, Auto for an automatic elimination, otherwise Entry # and its number.
dateThe posting date.
periodThe month the entry posted in, written the way the journal screen shows it - Sep 2026.
scenarioActual, Budget or Forecast.
data_typeThe stored elimination type, such as elimination_sales_purchases or auto-elimination.
typeThe labels a reader sees for that type, such as Elimination, Sales / Purchases / Services.
from_organisation, to_organisationThe two companies the entry takes the balance between, taken from its debit and credit side. Empty when the entry names no company on that side.
descriptionThe entry's own description.
debit, credit, netThe entry's totals in the group's reporting currency, and net as debit less credit.
line_countHow many account lines the entry posted, after lines on the same account are aggregated.
accountsThe accounts it touches, code and name, up to two of them followed by +N more.
entered_byWho entered the entry. An automatic elimination reads System.

What it does not answer

Only eliminations are answered. An ordinary journal, a CTA or an NCI entry posted in the same month is not, so this is not a second journal list - journal lines is that list, with every entry type in it.

The analysis behind these postings - the entity pairs, the differences between them and the anomalies the detector raises - is the intercompany dataset of consolidation. This read answers the postings themselves, one row per entry.

A month with no eliminations answers an empty data with "total": 0.