Decionis Commerce for Finance and Supply Chain Management
Plan a partner-led deployment of Decionis Commerce for Microsoft Dynamics 365 Finance and Supply Chain Management. The preview source defines checks for sales orders, vendor payments and vendor bank changes, using a signed policy bundle inside the ERP.
Preview status
This guide describes source model 1.1.0.0. The X++ model has not yet been compiled or tested in a clean sandbox. Marketplace certification and publication remain pending. The behavior below must be verified against the exact package and target environment before production use.
Deployment requires a Decionis implementation partner. A source archive is not an installable Microsoft package, and this page does not provide a self-service install.
Before deployment
- A licensed Finance and Operations development environment and a clean sandbox, with the exact Microsoft application and platform versions recorded.
- A Decionis Commerce subscription and an organization policy for the facts this integration supplies. A required fact the source cannot supply holds the action; review policy compatibility with your partner before enabling checks.
- An API key and a separate installation signing key stored in Azure Key Vault. The deployment must reference the secrets securely, register the installation and its public signing key, and confirm access for the application identity.
- The organization ID, ERP tenant and region, company, and configured agent ID. The source records the configured agent identity for these checks; it does not identify each person who saved a document as a separate agent.
- Policy verification keys installed by an administrator and a valid signed policy bundle for the organization. The source does not fetch new trust keys automatically.
Keep API keys, signing keys, bank details and customer payloads out of screenshots, documents and support messages.
Partner deployment
- Generate the Microsoft model metadata and project in the development environment, then compile them with the matching compiler and reference packages. Include the Decionis Commerce kernel, its dependency and the model’s label file.
- Build the Microsoft Power Platform unified deployable package. Deploy that package to the clean sandbox through the Power Platform admin center and synchronize the database.
- Configure each legal entity’s connection, secret references, policy trust keys, installation identity and sales fallback choice. The central sales guard uses
https://api.decionis.com/v1/guard/validate. - Configure the policy bundle refresh and outbox processing batch tasks. Verify policy delivery, record federation and approval synchronization in the sandbox before enabling enforcement. The optional posture polling endpoint remains unset until a supported endpoint is available.
The source has a company-level enabled setting. With it off, these guards do not run. With a valid policy in shadow mode, local checks record decisions without stopping the action. Confirm the mode and the failure behavior before testing enforcement; shadow results do not prove that posting or saving was blocked.
What the source checks
| Document | Check point | Action in the record |
|---|---|---|
| Sales orders | Save, after the standard sales order validation. | ORDER_ACCEPTANCE |
| Vendor payments | Before a payment journal posts, for each vendor line. | PAYMENT_RELEASE |
| Vendor bank changes | Save, when bank-identifying fields change. | VENDOR_BANK_CHANGE |
Sales orders
The source supplies pricing, estimated cost, delivery country, discounts, account type and lifecycle facts for orders with nonzero-quantity lines. It does not supply inventory availability for multi-line orders or a B2B contract price. Policies requiring those missing facts hold; an order without nonzero-quantity lines has no sales request to evaluate.
Vendor payments
The source checks vendor lines in payment journals before posting. It supplies the amount, prior payments for a marked invoice, recorded beneficiary changes and available bank-position facts. In enforcement mode, every vendor line must be allowed before the journal posts. Missing facts required by policy stop the action.
Vendor bank changes
Changed bank-identifying fields are evaluated before saving. New details start as unverified. When a Decionis approval permits the exact change, the source records that approval for subsequent payment checks. This is an approval record, not independent verification by a bank.
Decisions and approvals
In enforcement mode, the local decision controls whether the action continues:
- PROCEED. Continue when no additional central check is required.
- BLOCK. Refuse the action with its reason.
- HOLD. Stop because facts are missing, stale or unsupported. Correct the data or policy compatibility before evaluating again.
- ESCALATE. Wait for a Decionis case approval. The outbox processor opens the case and brings its outcome back; the save or posting does not wait for a person on a network call.
An approval is bound to the subject and action digest and is consumed once. A rejected case stops the action. Changing the action requires a new evaluation; an earlier approval does not authorize different details. Verify this flow with your partner in the sandbox.
Outage behavior
A valid signed bundle lets local checks run without contacting the central service for each decision. If bundle refresh fails, the last verified bundle remains usable only until it expires.
Sales orders
A local refusal, such as a missing or expired bundle, or a PROCEED decision requiring shared state sends the sales request to the central guard. That guard answers ALLOW or BLOCK for the exact transaction. A BLOCK, HTTP 4xx, invalid response or mismatched transaction stops the save regardless of the fallback setting.
For a transport or client failure, HTTP 5xx or an open circuit, the sales fallback setting applies: FAIL_CLOSED stops; FAIL_OPEN continues and queues a later drift check. A pass-through is ungoverned, not a policy approval. The drift entry belongs to the sales transaction, so a later rollback can remove it.
Vendor payments and bank changes
These money-out paths fail closed in enforcement mode. A missing or invalid bundle, missing required facts or an applicable signed halt stops the action. This preview has no central money-out client: an additional central requirement is refused rather than skipped. The sales fallback choice cannot permit it.
Decision evidence
With the installation signing key configured, recordable local decisions are signed and chained per company in the outbox. Their own connection lets a refusal record survive the refused save’s rollback. The outbox processor sends eligible records to Decionis; verify receipt before treating a local record as centrally available.
A refusal before a usable bundle or digest exists stays as local evidence outside that signed chain. Record IDs, action and facts digests, bundle versions, modes and reason codes support investigation. Central sales checks send the sales transaction to the guard, so review the ERP and Decionis data handling together.
Sandbox validation
Have the implementation partner retain the compiled package hash, exact Microsoft versions, model version, sandbox region, test results and telemetry. Validate enabled and disabled behavior, shadow and enforcement, each document type, approval consumption, stale bundles and both sales fallback choices. Confirm that payments and bank changes stop when required checks cannot complete.
Generate the Microsoft Customization Analysis Report from the compiled model and resolve its required findings before submission. Compiler success alone does not establish sandbox behavior, Marketplace certification or permission to enable the integration in production.
Support
Use Decionis Commerce support for deployment and product questions. Include the model and Microsoft versions, environment region, affected company, action, reason code and decision or record ID. Send a sanitized reproduction; never send credentials or bank details.