An X++ and SSRS extension for Dynamics 365 Finance & Operations that gives you branded, multilingual business documents plus rules-driven distribution by print, email and archive. Built to order after a fixed quotation. Built to order by ECOSIRE for Dynamics 365 F&O (build-to-order) — indicative price from $899.00 USD; request a quote for a scoped proposal.
An X++ and SSRS extension for Dynamics 365 Finance & Operations that gives you branded, multilingual business documents plus rules-driven distribution by print, email and archive. Built to order after a fixed quotation.
Built to order
Every Dynamics 365 Finance & Operations implementation reaches the same week: the finance team opens a customer invoice, sees the stock Microsoft layout, and asks for the company logo, the group's typography, the legal entity's registration numbers, a QR code, bilingual columns, and a footer that satisfies the local tax authority. What follows is usually weeks of Visual Studio SSRS work that only one person in the building understands, repeated for the sales order confirmation, the packing slip, the free text invoice, the project invoice, the purchase order, the customer statement, the payment advice and the credit note.
Distribution is the second half of the problem. Native print management lets you set a destination per module, account and level, which is genuinely useful and often enough for simple cases. It struggles when the rule is conditional — this customer group receives a PDF by email to the address stored on the contact marked for invoicing, that country's documents must be in Arabic with an English column beside it, government entities get two copies printed and one archived, and anything above a value threshold goes to a shared mailbox for review. Teams end up exporting to PDF and mailing manually, which means no record on the transaction of what was sent, to whom, or when.
ECOSIRE builds a document output and distribution layer for Dynamics 365 Finance and Supply Chain Management, written in X++ as extensions with no overlayering, plus the SSRS report designs themselves.
We rebuild your document set as proper SSRS reports in a dedicated model, extending the standard report data provider classes and contracts rather than replacing the posting logic behind them. Layout elements that change often — logo, letterhead image, bank details, registration numbers, signature blocks, terms and conditions text, footer disclaimers — are moved out of the RDL and into configuration tables held per legal entity and per document type. When the group rebrands or a bank account changes, a finance user edits a form; nobody opens Visual Studio.
We cover the documents that matter to your business, typically: customer invoice, free text invoice, project invoice, credit note, sales order confirmation, sales quotation, packing slip, picking list, purchase order, purchase inquiry, customer account statement, payment advice and collection letter. The exact list is fixed in your quotation.
Document text is resolved by language at print time using the standard label and translation infrastructure, so a customer flagged as Arabic-speaking receives an Arabic document, including right-to-left layout variants where required, while an internal copy prints in your working language. Per legal entity design assignment means one deployment serves the whole tenant: each company can have its own letterhead, colour, numbering presentation, tax registration block and footer, without cloning reports.
A distribution rule engine sits on top of standard print management. Rules are evaluated against the posted document and can test customer or vendor account, customer group, country or region, legal entity, document type, currency, document value, delivery mode, and any field you nominate during scoping. Each matched rule produces one or more actions: print to a specific network printer via the Document Routing Agent, email a PDF with a configurable subject and body template, attach the generated file to the source record through the standard document management framework, or write it to a SharePoint or Azure Blob location. Email recipients can be resolved from the contact purpose on the party record, so invoices go to the accounts payable contact rather than the sales contact.
Generation and sending run through the SysOperation batch framework, so a month-end statement run for thousands of accounts is a batch job with proper task splitting rather than a blocked client session. Every send attempt is logged: document, recipient, channel, timestamp, user or batch job, and outcome. Failures are retryable from a log form, individually or in bulk, and the log is exposed as a data entity over OData for Power BI. When a customer says they never received the invoice, the answer is a record, not a recollection.
Organisations implementing or already live on Dynamics 365 Finance & Operations that need their outbound documents to look like their brand and satisfy local statutory content. It is particularly relevant to groups running several legal entities or several countries in one tenant, to businesses invoicing in more than one language, and to finance teams currently exporting PDFs and emailing them by hand because native print management cannot express their rule.
There is no ready-made product to download. We build it for you.
1. Scoping call. You send us your current document examples or the layouts you want, we agree the document list, the languages, the legal entities, and the distribution rules. Statutory content requirements are captured here. 2. Fixed quote. A written scope and a fixed price, with the build window stated. Work starts only when you approve. 3. Build. Typically two to four weeks depending on the number of documents. Development takes place in our environment against your platform and application version. 4. Install in test. The deployable package is installed in your sandbox through your LCS project. We configure the design records, load your letterhead assets, set up the distribution rules and print you real documents from your own data for review. 5. Production. After sign-off, the same package goes to production through your release process, and we support the first live document runs. 6. Support. A support window from go-live covers defects and questions. Additional documents or new rules are quoted as enhancements.
Source code is handed over. Your team can add the fourteenth document design without coming back to us.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Cannot get a bank account change or a new tax registration line onto the invoice without raising a development request and waiting for a release. Moving that content into configuration per legal entity means they edit a form and print the corrected document the same morning.
Runs month-end statements by exporting PDFs and emailing them from Outlook, with no record on the account of what went out. Batch generation with rule-driven email and a full send log removes the manual step and answers disputes with evidence.
Watches document design consume developer weeks on every rollout to a new country or legal entity. A configuration-driven layer with per-entity designs and language resolution turns each new rollout into setup work rather than another SSRS project.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| Branding and statutory content held as configuration, not in the RDL | Included | Partial support | Included |
| Per legal entity document designs from one deployment | Included |
From $899.00
Starting point — quoted to your scope
| Included |
| Conditional distribution rules beyond module/account/level | Included | Partial support | Partial support |
|---|
| Recipient resolution from contact purpose on the party record | Included | Partial support | Partial support |
|---|
| Full send log with retry and OData exposure | Included | Partial support | Partial support |
|---|
| Multilingual output including right-to-left layout variants | Included | Partial support | Partial support |
|---|
| Extension-only, no overlayering of Microsoft code | Included | Partial support | Included |
|---|
| Full X++ and RDL source handed over to the customer | Included | Included | Not included |
|---|
An X++ extension that imports bank statements into Dynamics 365 F&O and fuzzy-matches lines against payments, deposits and fees. Built to order for your legal entities after a scoping call and fixed quote.
A behaviour-aware treasury forecasting app for Dynamics 365 Finance & Operations. Built to order as an X++ extension after a scoping call and a fixed quote — nothing is pre-built or downloadable today.
A built-to-order forecasting and planning layer for Dynamics 365 Finance & Operations, with external demand signals, explainable forecasts and scenario comparison. Scoped and built by ECOSIRE after a fixed quote.
A build-to-order X++ extension that captures vendor invoices, extracts line data, matches them against purchase orders with tolerance rules and routes exceptions through F&O workflow. ECOSIRE builds it for your entity structure after a fixed quote.