Invoice Matching and Intercompany Purchase Orders in Dynamics 365 F&SCM

How invoice matching works for intercompany trade

When a purchasing legal entity participates in an intercompany trade, it can use accounts payable invoice matching like any other purchasing entity. The validation is switched on through the accounts payable parameters, and the behavior depends on how the Post invoice with discrepancies setting is configured. When that setting requires approval, the system checks matching before it allows posting.

The key point for finance leaders is that two sets of posting requirements apply at the same time: the invoice matching rules of the purchasing entity and the intercompany trade rules that link it to the selling entity. Both must be satisfied before an intercompany vendor invoice can post.

• Enable invoice matching validation on the accounts payable parameters for the purchasing legal entity.
• Set Post invoice with discrepancies to Require approval if you want discrepancies routed for review.
• Confirm the intercompany vendor and customer records point to each other's legal entity and the correct account.

Price discrepancies on intercompany invoices

Consider a sales order created in the purchasing entity that automatically generates an intercompany purchase order and a matching intercompany sales order in the selling entity. After goods are received and the selling entity updates its invoice, the purchasing entity may create its vendor invoice. If the unit price on that invoice drifts beyond the configured price tolerance, the system flags the discrepancy.

Here is where the intercompany rule overrides the approval path. Even if a user approves posting with matching discrepancies, the intercompany vendor invoice still fails to post when its totals differ from the intercompany sales order. The only reliable fix is to correct the invoice price so it equals the amount on the sales side, rather than relying on the tolerance or approval to carry it through.

• A price tolerance of 2 percent gives no room for an intercompany invoice that is off by a full order of magnitude.
• Approving a discrepancy does not bypass the requirement that intercompany totals agree.

Quantity matching and receiving requirements

Quantity is treated the same way as price. The quantities on the intercompany purchase order and the intercompany sales order must be equal for posting to succeed, and this rule takes precedence over any invoice matching approval that would otherwise apply. Receiving requirements on the item model group add a further dependency, because the financial side cannot be finalized until goods are physically received and the packing slip is posted.

In practice, an intercompany invoice update can fail simply because stock is not yet received. The sequence matters: the selling entity posts the packing slip first, the purchasing entity receives the product automatically, and only then can both invoices post cleanly.

• Confirm that the purchase order action policy for the intercompany vendor automatically posts both the customer invoice and the intercompany vendor invoice, where that is the intended design.
• Build the receiving and packing slip steps into the month-end close calendar so invoices are not waiting on goods that have not moved.

What CFOs and CIOs should watch for

For a CFO, the main risk is timing. Intercompany postings can stall at period end if receipts or invoice corrections are incomplete, which delays consolidated reporting. For a CIO, the risk is configuration drift: intercompany setup spans two legal entities, and a change in one party's tolerance or approval settings can produce failures that look like a fault in the other.

Dynamics-Minds typically recommends documenting the intercompany trade design before go-live, testing a price discrepancy and a quantity discrepancy end to end in a non-production environment, and assigning clear ownership for corrections on both sides of the trade.

• Document the intercompany customer and vendor pairing, including the corresponding accounts in each legal entity.
• Test a discrepancy scenario in a sandbox before setting approval-based posting in production.
• Define who corrects an intercompany invoice when the other entity's data is the source of the error.

Decision rules

• If an intercompany vendor invoice fails to post after an approved price discrepancy, then correct the unit price to match the intercompany sales order rather than adjusting the tolerance.
• If intercompany invoices are delayed at period end, then review whether packing slips and product receipts were posted in the selling entity before the close.
• If you change the price tolerance in one legal entity, then retest intercompany trade in both legal entities before the change goes live.
• If you require approval for invoices with discrepancies, then make sure your intercompany pairings are documented so approvers understand why some discrepancies cannot be overridden.

Common questions