dynamics365-fo

Classifies Dynamics 365 F&O procurement, receiving, invoicing, and ledger operations by risk for safe execution.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill dynamics365-fo-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dynamics365-fo
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/erp/dynamics365-fo
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill dynamics365-fo-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating Microsoft Dynamics 365 Finance & Operations through an AI agent is risky because routine actions like confirming a PO, posting a product receipt, or posting a vendor invoice commit money, move stock, and write audited ledger vouchers that cannot simply be undone. This Skill gives the agent the operator judgment to classify each action as read, reversible write, committing write, or destructive, and to know the recovery path before acting. ## Core Features & Use Cases - Action risk classification matrix: Maps every F&O operation family (PO confirmation, product receipt posting, vendor invoice matching, journal posting, inventory close, period reopening) to a gating level, from pass-through reads to named-approver destructive actions. - Edge-state and recovery playbooks: Covers 29 real gotchas (two independent PO status axes, GR/IR-style accrual clearing, closed/on-hold periods, continuous number sequences, WHS vs basic receiving) plus recovery patterns for cancellations, credit notes, storno reversals, and partial posting failures. - Use Case: When asked to post a vendor invoice that fails three-way matching, the agent recognizes the matching discrepancy hold, refuses to override it, and routes the price or quantity gap to a human instead of paying a mismatched bill. ## Quick Start Ask the agent to confirm a purchase order or post a product receipt in Dynamics 365 F&O and it will first read the PO status, period status, and matching state before proposing the committing action for approval.

Frequently Asked Questions about dynamics365-fo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely post a vendor invoice in Dynamics 365 F&O?

Posting a vendor invoice is a committing action that writes the AP liability, clears the receipt accrual, and settles inventory cost. First read the matching status, PO status, and period status; if matching failed, resolve the price or quantity gap rather than overriding the hold.

What is the difference between PO approval status and PO status in D365 F&O?

Approval status (Draft, In review, Approved, Confirmed, Finalized) tracks workflow authorization, while Purchase order status (Open order, Received, Invoiced, Canceled) tracks physical and financial progress. They move independently, so a Confirmed PO can still have nothing received.

Does this skill cover Dynamics 365 Business Central?

No. Business Central is a different product with a different data model and posting engine, and the skill explicitly excludes it. It also does not cover Dynamics 365 Customer Engagement/CRM, SAP, Oracle, or Coupa, which have their own skills.

Why did my D365 F&O posting fail with a closed period error?

Postings land only in Open ledger periods, and the voucher posts to the period of its transaction date, not today. A Closed period must be reopened by finance, an On hold period blocks the affected module, and a Permanently closed period never reopens.

Can a posted product receipt or vendor invoice be deleted in D365 F&O?

No. Posted documents are never deleted; you reverse them with a corrective posting such as a credit note or a storno reversal voucher dated in an open period. Both the original and the reversal remain permanently in the audit trail.

When should a D365 F&O action require human approval?

Any committing write (PO confirmation, product receipt, invoice or journal posting, subledger-to-GL transfer) needs human approval, and destructive actions like reversing vouchers, cancelling receipts, running inventory close, or overriding a matching discrepancy need a named approver plus a fresh re-read.