{"slug": "centralized-procurement-d365-global-address-book-vendors", "title": "Centralized procurement D365: global address book + vendors", "summary": "The article explains how multi-legal-entity enterprises using D365 Finance can avoid vendor data duplication by leveraging the Global Address Book and centralized procurement features. The Global Address Book creates a single canonical vendor record (party) that is released to each legal entity with per-LE metadata, while centralized procurement allows one legal entity to purchase on behalf of another. This architecture ensures consistent vendor data, enables cross-LE spend reporting via a simple query, and eliminates the need for custom sync services or manual intercompany transactions.", "body_md": "Multi-legal-entity enterprises standing up centralized procurement on D365 Finance face a recurring master data problem. The same vendor gets purchases from multiple LEs, each with its own currency, tax rules, and approval hierarchy. Without discipline, the same vendor ends up configured three or four times - different addresses in each LE, different contact emails, different payment terms that don't actually reflect the contract.\nTeams reach for custom sync services or per-LE vendor duplicates. Neither is necessary.\nConfigure separate vendor records per LE with custom sync. Adds a custom integration service between LEs to keep vendor data aligned. The service becomes a dependency that has to be maintained, monitored, and upgraded indefinitely. Every field addition requires integration changes.\nRoute all requisitions through manual intercompany transactions. Avoids duplicating vendors but shifts the pain to operations. Every cross-LE purchase becomes a multi-step manual process. Procurement teams resist; shadow-procurement workarounds appear within a month.\nEnable procurement categories per LE and consolidate via Excel Power Query. Looks simple in design but means spend visibility lags behind transactions by whatever the reporting cycle is. CFO asks for \"current total spend with Vendor X\" and waits for a manual refresh.\nThe global address book plus centralized procurement features in D365 F&O.\nWhat each piece does:\nGlobal address book is the party-based master data layer that sits above legal entities. Each vendor is a party in the global address book with one canonical record. The party is released to each LE that transacts with it, with per-LE vendor metadata layered on top (payment terms, posting profile, default financial dimensions).\nCentralized procurement allows one LE to purchase on behalf of another. The purchasing LE issues the PO, receives from the vendor, and then inter-companies the goods or services to the requesting LE. Standard feature, configured at the purchasing-LE level.\nShared vendor governance - new vendor requests route through a central procurement workflow. The vendor is created at the party level, then released to LEs with approval. No vendor exists in any LE without central approval.\nThe rules that keep global address book clean:\nWithout discipline, the global address book becomes the same mess as per-LE records with extra steps.\nWhat stays LE-specific:\nThe party data (name, address, tax registration) stays at the global level. The operational behavior stays per-LE. Both are automatically consistent because they're one object with layered attributes.\nCentralized procurement doesn't mean centralized approval. Each LE configures its own approval workflow based on:\nThe workflow is LE-local. The vendor record is global. The PO knows which LE it's from and applies the right workflow.\nWhen LE A buys on behalf of LE B:\nStandard functionality. Configured once per LE pair at setup.\nWith shared vendor master, cross-LE spend reporting is a query, not a consolidation project. Power BI over the shared vendor tables, financial dimensions cutting across LEs, and Procurement analytics workspaces surface:\nAll of this works because the vendor is one record.\nA working centralized procurement architecture has:\nThe feature existed before the requirement. Getting the architecture right is about using it correctly, not extending it.", "url": "https://wpnews.pro/news/centralized-procurement-d365-global-address-book-vendors", "canonical_source": "https://dev.to/sapotacorp/centralized-procurement-d365-global-address-book-vendors-27mj", "published_at": "2026-05-24 05:37:06+00:00", "updated_at": "2026-05-24 06:02:28.773727+00:00", "lang": "en", "topics": ["enterprise-software", "data"], "entities": ["D365", "D365 Finance", "Power Query"], "alternates": {"html": "https://wpnews.pro/news/centralized-procurement-d365-global-address-book-vendors", "markdown": "https://wpnews.pro/news/centralized-procurement-d365-global-address-book-vendors.md", "text": "https://wpnews.pro/news/centralized-procurement-d365-global-address-book-vendors.txt", "jsonld": "https://wpnews.pro/news/centralized-procurement-d365-global-address-book-vendors.jsonld"}}