how do I create an Advanced Intercompany Journal Entry with the REST API which specifies due to/due from subsidiaries

AI generated answer (using internal Slack threads):

To create an Advanced Intercompany Journal Entry with the REST API which specifies due to/due from subsidiaries, you can use the

POST

method to the

{{REST_SERVICES}}/record/v1/advIntercompanyJournalEntry

endpoint. Here is an example of the request body:

json
{
  "trandate": "2025-01-16",
  "subsidiary": { "id": "1" },
  "currency": { "id": "1" },
  "memo": "testmemo",
  "lines": [
    {
      "account": { "id": "552" },
      "entity": { "id": "322" },
      "debit": 10.00,
      "eliminate": true,
      "lineSubsidiary": { "id": "3" },
      "department": { "id": "1" }
    },
    {
      "account": { "id": "482" },
      "entity": { "id": "1440" },
      "credit": 1000,
      "eliminate": true,
      "lineSubsidiary": { "id": "3" },
      "department": { "id": "1" }
    },
    {
      "account": { "id": "111" },
      "entity": { "id": "1440" },
      "debit": 1000,
      "eliminate": true,
      "lineSubsidiary": { "id": "6" },
      "department": { "id": "1" }
    },
    {
      "account": { "id": "551" },
      "entity": { "id": "319" },
      "credit": 1000,
      "eliminate": true,
      "lineSubsidiary": { "id": "6" },
      "department": { "id": "1" }
    }
  ]
}

In the above example, the

lineSubsidiary

field is used to specify the due to/due from subsidiary. If you encounter an

INVALID_CONTENT

error, it could be due to missing or incorrect fields in your request body. Make sure all the required fields are included and the values are correct. If you are still encountering issues, you may need to check the request headers you are sending. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******