{"id":3231,"date":"2026-11-11T12:35:36","date_gmt":"2026-11-11T07:05:36","guid":{"rendered":"https:\/\/www.nevastech.com\/blog\/?p=3231"},"modified":"2026-11-11T12:35:36","modified_gmt":"2026-11-11T07:05:36","slug":"dynamics-gp-intercompany-setup","status":"publish","type":"post","link":"https:\/\/www.nevastech.com\/blog\/dynamics-gp-intercompany-setup\/","title":{"rendered":"Dynamics GP Intercompany Setup: Due To, Due From and Common Pitfalls"},"content":{"rendered":"

If your organization runs more than one legal entity in Microsoft Dynamics GP<\/a>, you will sooner or later need to record transactions between them. One company pays a shared invoice, another provides services to a sister company, or head office allocates costs across subsidiaries. Without a proper process, each of these means two separate journal entries in two separate companies, and plenty of room for mistakes.<\/p>\n

Dynamics GP’s Intercompany Processing feature is designed to solve this. You enter a transaction once in one company, and GP automatically creates the matching entry in the other company, using Due To and Due From accounts to keep both sets of books balanced.<\/p>\n

The setup itself is not complicated, but small decisions made at the start can cause reconciliation problems for years. In this guide, we explain how intercompany works in GP, how to set it up properly, and the common pitfalls we see when reviewing GP systems for our clients.<\/p>\n

<\/span>How Intercompany Processing Works in Dynamics GP<\/span><\/h2>
\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n