Demiton · Schema

intercompany_transaction contract v2

Transactions between companies in your group, for elimination on consolidation.

CompanyConstructionCivil EngineeringProject ManagementComplianceMCPArtificial IntelligenceOpen Contracting

Properties

Name Type Description
amount number the transaction amount
currency currency the currency of the amount
reversed boolean whether the entry has been reversed
direction string outgoing from this entity or incoming to it
posted_on string the posting date
gl_account string the intercompany account the transaction posts to
external_id string the source's intercompany transaction number
source_type string whether it came from a journal, a sales document or a purchase document
legal_entity string the legal entity whose books record this side
business_unit string the consolidation business unit
document_date string the document's date
document_type string payment, invoice, credit memo, refund, order or return order
offset_account string the balancing account in the other branch
partner_action string whether the transaction was accepted, returned or cancelled
partner_entity string the group entity on the other side
document_number string the document number in this entity
partner_document_number string the matching document number in the partner entity
View JSON Schema on GitHub

JSON Schema

demiton-io-intercompany_transaction-v2-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://docs.demiton.io/registers/intercompany_transaction/v2.json",
  "title": "intercompany_transaction contract v2",
  "type": "object",
  "required": [
    "amount",
    "direction",
    "external_id",
    "legal_entity",
    "partner_entity",
    "posted_on"
  ],
  "properties": {
    "amount": {
      "type": "number",
      "description": "the transaction amount",
      "x-demiton-requiredness": "required",
      "x-demiton-type": "money"
    },
    "currency": {
      "type": "currency",
      "description": "the currency of the amount",
      "x-demiton-requiredness": "optional"
    },
    "reversed": {
      "type": "boolean",
      "description": "whether the entry has been reversed",
      "x-demiton-requiredness": "optional"
    },
    "direction": {
      "type": "string",
      "description": "outgoing from this entity or incoming to it",
      "x-demiton-requiredness": "required"
    },
    "posted_on": {
      "type": "string",
      "description": "the posting date",
      "x-demiton-requiredness": "required",
      "x-demiton-unit": "day",
      "format": "date",
      "x-demiton-type": "date"
    },
    "gl_account": {
      "type": "string",
      "description": "the intercompany account the transaction posts to",
      "x-demiton-requiredness": "optional",
      "x-demiton-reference": true
    },
    "external_id": {
      "type": "string",
      "description": "the source's intercompany transaction number",
      "x-demiton-requiredness": "required"
    },
    "source_type": {
      "type": "string",
      "description": "whether it came from a journal, a sales document or a purchase document",
      "x-demiton-requiredness": "optional"
    },
    "legal_entity": {
      "type": "string",
      "description": "the legal entity whose books record this side",
      "x-demiton-requiredness": "required",
      "x-demiton-reference": true
    },
    "business_unit": {
      "type": "string",
      "description": "the consolidation business unit",
      "x-demiton-requiredness": "optional"
    },
    "document_date": {
      "type": "string",
      "description": "the document's date",
      "x-demiton-requiredness": "optional",
      "x-demiton-unit": "day",
      "format": "date",
      "x-demiton-type": "date"
    },
    "document_type": {
      "type": "string",
      "description": "payment, invoice, credit memo, refund, order or return order",
      "x-demiton-requiredness": "optional"
    },
    "offset_account": {
      "type": "string",
      "description": "the balancing account in the other branch",
      "x-demiton-requiredness": "optional"
    },
    "partner_action": {
      "type": "string",
      "description": "whether the transaction was accepted, returned or cancelled",
      "x-demiton-requiredness": "optional"
    },
    "partner_entity": {
      "type": "string",
      "description": "the group entity on the other side",
      "x-demiton-requiredness": "required",
      "x-demiton-reference": true
    },
    "document_number": {
      "type": "string",
      "description": "the document number in this entity",
      "x-demiton-requiredness": "optional"
    },
    "partner_document_number": {
      "type": "string",
      "description": "the matching document number in the partner entity",
      "x-demiton-requiredness": "optional"
    }
  },
  "x-demiton-register-type": "intercompany_transaction",
  "x-demiton-contract-version": "2.0.2",
  "x-demiton-store": "tenant",
  "x-demiton-axes": [],
  "x-demiton-measures": [],
  "x-demiton-provenance": {
    "standards": []
  },
  "description": "Transactions between companies in your group, for elimination on consolidation.",
  "x-demiton-contract-url": "https://docs.demiton.io/registers/intercompany_transaction/",
  "x-demiton-register-catalog": "https://docs.demiton.io/concepts/register-catalog"
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/demiton-io-intercompany_transaction-v2"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.