What should I look for in AP automation for Dynamics 365 Finance & Operations?

Natively: create pending vendor invoices, post via invoice journals, optionally use Microsoft's Invoice Capture for OCR, route through the workflow engine, and apply three-way matching policies. The limits: the workflow engine can queue and slow under volume, batch posting jobs delay when invoices become visible (asynchronous posting), and financial-dimension combination validation plus multi-legal-entity processing make coding heavy. Invoice Capture covers extraction but not the full approval/exception experience.

F&O exposes data entities (the standard integration surface), OData (real-time queries), dual-write (sync with Dataverse/other Dynamics apps), and batch jobs (bulk async). For invoices, data entities with proper validation and a connector that handles asynchronous batch posting tend to be most reliable - the integration must account for the gap between submitting an invoice and F&O actually posting it in a batch, so it doesn't report success prematurely.

Invoice Capture handles OCR extraction into F&O; dedicated platforms typically add stronger capture across format diversity plus the approval flexibility, exception workspace, and vendor collaboration Invoice Capture doesn't provide. Compare on your bottleneck - if extraction alone is the gap, native may suffice; if routing and exceptions are the pain, depth there matters more.

F&O financial dimensions (and dimension sets with combination rules) must sync to the AP tool, which then enforces valid combinations before posting so invoices don't bounce. Default-dimension and dimension-priority logic should be respected so coded invoices match how F&O expects them.

The workflow engine queues under volume and complex routing. Tuning (batch settings, work-item assignment, hierarchy simplification) helps; teams with heavy routing often move approval logic to an AP layer with configurable workflows that post the approved invoice back, keeping F&O's engine for posting rather than routing.

F&O matching policies define line/charges/total matching and tolerances at the item or vendor level. An AP layer should respect those policies, perform line-level matching with inconsistency tolerance up front, and surface exceptions with context - so matched invoices post within F&O's policy and exceptions get resolved where the information is.

F&O controls periods via ledger calendars with per-module status (you can stop AP postings while leaving GL open). At close, set the AP module status appropriately, drain the in-transit queue from the external tool first, and reconcile the AP subledger to the platform before locking.

F&O processes invoices per legal entity, with intercompany transactions flowing between entities. Centralized invoice processing across entities requires the AP tool to carry legal-entity context and support inter-entity coding so an invoice paid by one entity can charge another - confirm the connector handles your entity count and intercompany pattern.

The integration must treat submission and posting as separate events: submit the invoice, then confirm actual posting from the batch result rather than assuming success - and surface the in-flight state to AP. Idempotency matters too, so a retry after a slow batch doesn't create a duplicate.

Re-point the integration from AX interfaces to F&O data entities (a re-implementation if the AP layer abstracts the ERP), keep historical invoice images and audit trail in the AP platform across the swap, and decide automation timing by AP pain - automate first for a stable front-end, or sequence after if the F&O program is fully loaded.

F&O's vendor collaboration portal handles vendor self-service within Dynamics; an AP platform's vendor portal centralizes onboarding, document collection, and invoice submission with AP-side controls. Avoid running both for the same purpose - pick one as the vendor's front door to prevent split data and confusion.

IT will require Entra (Azure AD) SSO, scoped service authentication, testing in an LCS-managed sandbox environment, and clarity on who maintains the connection through Microsoft's update waves. Bring auth method, least-privilege scopes, and sandbox sign-off criteria to the review.

Stampli integrates with D365 Finance & Operations to synchronize coding data - vendors, accounts, and financial dimensions - and validates invoices against F&O's structure and dimension combinations before posting. Stampli AI captures and codes invoices, performs line-level PO matching even with inconsistencies, and on average performs 87% of finance work across 2,700+ unique fields, always subject to human review before posting. Legal-entity context carries through the workflow; F&O remains the system of record.