Summary 1. Identified the operational and strategic costs of fragmented Procure-to-Pay (P2P) processes across procurement and finance functions.2. Highlighted how manual, siloed workflows lead to approval bottlenecks, data inconsistencies, and invoice disputes.3. Explained how ERP integration eliminates manual handoffs by connecting procurement and finance into a unified, data-consistent system.4. Demonstrated the business value of real-time visibility across spending, commitments, and vendor payment status.5. Positioned a strong P2P process as a direct driver of cost efficiency, financial control, and business agility. Table of Contents 1. Introduction2. The Problem3. What Changes with Integration4. What Businesses Gain5. Conclusion Introduction We implemented this solution for a leading North American commercial vehicle manufacturer with complex multi-entity operations, where disconnected procurement and finance processes had a significant impact on business performance. Procurement and finance are central to business performance, yet in many organisations they continue to operate in silos. Each function manages its own data, workflows, and priorities, creating gaps that undermine efficiency, accuracy, and leadership visibility across the organisation. This disconnect is not merely an internal inconvenience. Over time, it leads to missed deadlines, strained vendor relationships, and financial reporting that lags the pace at which business decisions need to be made. For organisations looking to scale or compete in demanding markets, these gaps represent a genuine strategic risk. The Procure-to-Pay (P2P) cycle sits at the centre of this challenge. Spanning everything from raising a purchase request to issuing final payment, it is where delays and mismatches are most visible, and where the cost of inefficiency is most directly felt by both operational teams and leadership. The Problem Figure 1: Procure-to-Pay Cycle Problems Without Integration vs. Outcomes with ERP Integration Despite advances in enterprise technology, many organisations still rely on fragmented, manual approaches to procurement and finance. Email-based approval chains, spreadsheet-driven tracking, and disconnected systems remain common each introducing friction that slows the P2P cycle and reduces data reliability. Approval bottlenecks cause purchase orders to stall, disrupting timelines and delaying downstream activities. Duplicate data entry creates inconsistencies that consume significant time to identify and correct. Invoice mismatches between what was ordered, received, and billed result in payment disputes that erode vendor trust and divert finance team effort away from higher-value work. Beyond day-to-day operational impact, the absence of real-time visibility creates a deeper structural problem. Leadership is left making spending decisions based on stale or incomplete data, budget adherence is difficult to monitor, and bottlenecks go undetected until they have already caused delays. The organisation becomes reactive responding to problems rather than preventing them. How the Integration Works Figure 2: ERP Integration Architecture Source Systems, Azure Logic Apps Middleware, and Target D365 Modules The integration follows an event-driven model a design approach in which processes are triggered by specific business events rather than scheduled batch runs or manual interventions. This shift has significant implications for speed, accuracy, and responsiveness throughout the P2P cycle. When a purchase request is created, a vendor record is updated, or an invoice is submitted, the integration layer responds immediately. Data is extracted through secure, authenticated APIs, validated against predefined rules, transformed into the format required by the target system, and pushed into the ERP without human intervention and typically within seconds. This real-time responsiveness eliminates the latency inherent in batch-based integrations, where data may be hours out of date by the time it reaches the systems that need it. For procurement and finance teams working to tight timelines, that difference is material and directly impacts how quickly decisions can be made and acted upon. What Changes with Integration ERP integration addresses these challenges by connecting procurement and finance into a unified, data-consistent system. Rather than information being passed manually between teams or re-entered across platforms, it flows automatically triggered by real business events and governed by standardised rules applied consistently across the organisation. When a purchase request is raised, all relevant data is immediately available to every stakeholder in the approval chain without manual handoffs or follow-up emails. Approvals are routed automatically based on predefined rules, timelines are enforced, and exceptions are flagged in real time rather than discovered days later during reconciliation. Standardisation is another significant benefit. With all users working from the same data and the same process definitions, the inconsistencies that arise from team-specific workarounds are eliminated. Audit trails are complete and reliable, compliance becomes easier to demonstrate, and the system can adapt as the organisation evolves without requiring constant manual adjustment. What Businesses Gain The benefits of a well-integrated P2P system extend across every level of the organisation. Procurement teams process requests and approvals faster, with significantly less administrative burden. Finance teams reconcile invoices more efficiently and gain clearer visibility into outstanding commitments and cash flow. Vendors receive timely, accurate payments improving commercial relationships and, over time, creating opportunities for preferential terms and stronger partnerships. At the leadership level, integration delivers something particularly valuable: reliable, real-time insight. Executives can monitor procurement activity, track budget adherence, and assess financial performance without waiting for manually compiled reports. This enables faster course correction, more confident planning, and better alignment between procurement strategy and broader business objectives. Organisations in high-volume, multi-entity environments such as Daimler Truck North America, a leading North American commercial vehicle manufacturer operating brands including Freightliner, Western Star, and Thomas Built Buses across complex, multi-geography supply chains benefit most significantly. In industries where operational precision and cost control are non-negotiable, the ability to manage procurement and payments with full visibility and minimal friction is a genuine competitive differentiator. To conclude, a well-designed integration does more than automate existing steps it transforms the Procure-to-Pay cycle into a fast, reliable, and transparent process that serves operational teams, finance leadership, and the wider business alike. The principles outlined in this article event-driven architecture, modular parent-child orchestration, delta processing, and comprehensive logging form the foundation of an integration that can scale with the business and adapt to evolving requirements. For organisations operating in complex, high-volume environments, this is not a technical upgrade. It is a strategic enabler. Ready to modernize … Continue reading From Approval Bottlenecks to Real-Time Visibility: Transforming Procure-to-Pay Through ERP Integration for a Leading North American Commercial Vehicle Manufacturer →

Executive Summary Modern finance organizations operating in highly regulated, asset-intensive industries such as Oil & Gas and Marine Services face a growing paradox. While enterprise ERPs like Microsoft Dynamics 365 are designed to be systems of record, the surrounding financial ecosystem—banking portals, tax authority platforms, HR systems, and reporting tools—often remains fragmented and manually operated. This fragmentation introduces three systemic risks: This article presents a connected finance architecture where ERP, banking systems, and statutory compliance platforms are deeply integrated through APIs, transforming finance operations into a frictionless, auditable, and real-time engine. The solution described eliminates file-based handoffs, reduces human dependency, and establishes the ERP as a single source of financial truth. Industry Context: Why Energy & Marine Finance Is Uniquely Complex Organizations in the energy and marine sectors operate under conditions that magnify finance risk: In this environment, manual finance operations are not just inefficient—they are dangerous. Case Environment Overview The organization profiled in this implementation exhibits the following characteristics: Pre-Integration Challenges Before integration, finance operations were characterized by: These processes introduced latency, reconciliation gaps, audit exposure, and key-person dependency. The Core Problem: Disconnected Financial Workflows The central failure point was workflow discontinuity. Although financial transactions originated in the ERP, execution and compliance occurred outside it, breaking end-to-end traceability. Finance Stage System Used Risk Introduced Invoice Entry ERP Low Approval ERP Low Payment Execution Bank Portal High GST Filing GSP Portal High Reconciliation Excel Very High Every manual handoff created: The Vision: A Connected Finance Ecosystem The transformation goal was not automation for its own sake, but financial continuity. Design Principles Architecture Overview: ERP-Centric Integration Dynamics 365 Finance & Supply Chain was positioned as the financial command center. From this hub: This architecture eliminated spreadsheet dependency entirely. Regulatory Automation: Solving GST, E-Invoicing, and E-Way Bills The Compliance Challenge Manual GST compliance introduces risks such as: The Solution Integration with ClearTax enabled direct statutory interaction from Dynamics 365. Automated Capabilities Compliance ceased to be an external obligation and became a native ERP function. Automated Banking: From Approval to Disbursement Without Re-Entry The Payment Risk Manual bank instruction entry introduces: The Integrated Payment Flow This ensured zero data re-entry between ERP and bank. Governance Controls Embedded in the System 3-Way Matching Enforcement Mandatory matching between: This applies to both services and materials, ensuring no unauthorized leakage. N-Level Approval Framework Approval workflows span: Each approval is: HR Integration: Eliminating Expense Fragmentation HR expense data from Eazework flows directly into Dynamics 365. Benefits: Reconciliation and Audit Readiness A 1:1 relationship between bank accounts and main accounts was enforced. This resulted in: Decision Intelligence: Power BI as the CFO’s Cockpit Power BI dashboards provide: Dashboards refresh three times daily: Finance leaders operate on live data, not yesterday’s spreadsheets. Proof & Metrics Dimension Outcome Legal Entities 7 + 1 consolidation Compliance Scope GST, IRN, E-Way Bills Payment Modes NEFT, RTGS Manual Entry Eliminated Data Accuracy Single vendor master Reporting Latency Near real-time Step-by-Step Implementation Playbook FAQs a. Can E-Way Bills be cancelled from the ERP?Yes. Cancellation is automated and synchronized with the GST portal. b. How are On-Account payments handled?Payments can be created manually and auto-applied later without reconciliation issues. c. What happens to rejected vendors?They are auto purged after six months to maintain data hygiene. d. Closing Thought: Finance Without Friction The future of finance is not additional manpower-it is architectural integrity. Organizations that eliminate manual interfaces between ERP, banks, and regulators achieve: The frictionless finance engine is no longer optional. It is the new baseline. To conclude, for Oil & Gas and Marine service providers, financial complexity is not going away. Multi-entity structures, regulatory obligations, and high-value transactions will only intensify. The answer is not more people – it is better architecture. When ERP, banking, and compliance systems are genuinely connected, finance transforms from a cost center into a control center. Transactions execute without re-entry. Compliance happens within the workflow. Reconciliation closes itself. This implementation demonstrates that frictionless finance is not a future ambition – it is an available reality today. The only question left for finance leaders in this space is simple: How long can you afford to operate without it? Ready to Transform Your Finance Operations? If your organization is still bridging ERP, banking, and compliance through spreadsheets and manual processes, it is time for a different conversation. Our team has deep expertise implementing connected finance architectures for Oil & Gas and Marine service providers – from Dynamics 365 configuration to GST automation and real-time banking integration. Write to us at transform@cloudfronts.com and discover how quickly your finance function can move from fragmented to frictionless.

Global energy service providers operate across multiple jurisdictions, currencies, and regulatory regimes. This complexity demands precision in financial reporting and transparency in profitability analysis. Achieving reliable site-level profitability in such an environment requires a holistic architectural approach to financial consolidation rather than incremental fixes or tactical workarounds. Legacy State Challenges Strategic DecisionThe organization implemented Dynamics 365 Finance & Supply Chain as a unified financial backbone, replacing legacy IFS systems and spreadsheet-driven workflows. This decision was accompanied by a critical architectural trade-off: moving away from locally customized, entity-specific account structures toward a single, global Chart of Accounts (COA). Benefits of Standardization Unified COA StructureThe global COA was standardized using a 1000–6000 series: This created a common financial language across the organization, enabling both global consolidation and local statutory compliance. Engineering Derived Dimensions for Data Integrity Standardizing accounts alone was insufficient to achieve granular profitability visibility. The architecture required a mechanism to enforce dimensional consistency and eliminate manual errors. Derived Dimension FrameworkFive core dimensions were defined: Segment, Sub-Segment, Region, State, and Site. System Integration Operational Customization From Static Spreadsheets to Dynamic Power BI Dashboards Legacy Reporting Modernized Workflow Reporting Model Operational Cadence Frameworks Proof and Metrics Step-by-Step Implementation Playbook FAQs a. How do you handle different fiscal years?The system supports reporting for both January–December and April–March fiscal calendars to meet diverse statutory requirements. b. Can we track unbilled revenue?Yes. Project Management modules track planned versus actual work, allowing finance teams to post and reverse accrued revenue monthly. c. What happens if a site selects the wrong dimension?This risk is mitigated through derived dimensions, which automatically populate dependent dimensions based on the selected Site code. To conclude, this architecture not only addresses immediate challenges but also positions the organization for long-term sustainability. It enables leadership to make informed decisions based on reliable, timely data, while ensuring compliance across diverse regulatory environments. Ultimately, the shift represents a move from reactive financial management to proactive, strategic control-delivering clarity, accountability, and resilience across global operations. Connect with CloudFronts to get started at transform@cloudfonts.com

In Microsoft Dynamics 365 Finance & Operations, direct SQL access to Sandbox environments is restricted for security reasons. However, you can access the Sandbox database from a DEV VM using Just-in-Time (JIT) access and SQL credentials provided through Lifecycle Services (LCS). This guide explains the complete process step-by-step. Prerequisites Before connecting, ensure you have: Step 1: Request JIT Access Open your Sandbox environment in LCS. Navigate to: Environment → Maintain → Enable access Depending on organization policies: Common access types: Step 2: Retrieve SQL Connection Details After JIT access is enabled: Go to: Environment Details → Full details You will find: Example: Field Example Server axdbserver.database.windows.net Database AxDB Authentication SQL Authentication Step 3: Whitelist DEV VM Public IP (If Required) Some environments require firewall whitelisting. From DEV VM: In LCS: Maintain → SQL firewall configuration Add: Wait a few minutes for propagation. Step 4: Open SSMS on DEV VM Launch: SQL Server Management Studio Step 5: Enter Connection Details In SSMS: Server Name Paste SQL server name from LCS. Example: axdbserver.database.windows.net Authentication Select: SQL Server Authentication Login Enter SQL username from LCS. Password Enter temporary password from LCS. Step 6: Configure Encryption Settings Click: Options → Connection Properties Ensure: Step 7: Connect to Database Click: Connect If successful, you can access: Important Notes Sandbox Databases Are Usually Read-Only Microsoft restricts many write operations. Avoid: unless explicitly approved. Access Is Temporary JIT access expires automatically after the approved duration. You may need to: Production Database Access Direct Production DB access is heavily restricted and generally unavailable. Use: instead. Common Connection Errors Login Failed Possible reasons: Cannot Open Server Requested by Login Usually firewall issue. Solution: SSL / Certificate Error Enable: Recommended Best Practices Use Read-Only Queries Prefer: SELECT TOP 100 * FROM CUSTTABLE Avoid update/delete statements. Use Views Instead of Base Tables Many standard views provide safer reporting access. Avoid Heavy Queries Large queries may impact environment performance. Example SQL Query SELECT TOP 10 ACCOUNTNUM, NAME FROM CUSTTABLE ORDER BY CREATEDDATETIME DESC Security Recommendations To conclude, Using Just-in-Time (JIT) access to connect a Sandbox database through SQL Server Management Studio (SSMS) in Microsoft Dynamics 365 Finance & Operations provides a secure and controlled way to troubleshoot, validate data, and perform reporting activities without granting permanent elevated access. Reach out at transform@cloudfronts.com.

What happens when a global manufacturing giant needs to modernize its operations without grinding critical business processes to a halt? The answer is not a rip-and-replace approach – it is a carefully engineered integration strategy that lets modern and legacy systems co-exist, communicate, and complement each other. Are you planning an ERP upgrade but worried about what happens to the legacy systems your operations depend on? If so, this is for you. One of North America’s leading commercial vehicle manufacturers faced exactly this dilemma. With decades of investment in legacy financial and warehouse management systems, a hard cutover to a new ERP was not an option. Yet the need for a modern, scalable platform was undeniable. Their solution? Introduce Microsoft Dynamics 365 Finance & Operations (D365 F&O) as the new operational backbone – while keeping their legacy systems in play for financial control – and build robust, bi-directional integrations to bridge both worlds. At CloudFronts, we had the privilege of architecting and implementing those integrations. This blog walks you through three core data flows: Spot Purchase Orders, Advance Shipment Notices (ASN), and Goods Receipt Notes (GRN) – and what it really takes to make a modern ERP talk to a legacy system without missing a beat. Why Replace When You Can Integrate? Legacy systems in large manufacturers are not just old software. They carry years of financial logic, vendor relationships, and compliance configurations that are too risky to discard overnight. Replacing them introduces enormous operational and compliance risk. Doing nothing, however, is not an option either. The approach our client took – and one we increasingly recommend for manufacturers, distributors, and large enterprises – is a co-existence model: This means the business gets the agility of a modern ERP on day one, without putting financial operations at risk. The three integrations do the heavy lifting. Architecture at a Glance Before diving into each integration, it helps to understand the overall data flow pattern and the Azure services involved: Component Role D365 F&O System of record for purchasing and receiving operations Legacy System Retains financial control, inventory management authority Azure Logic Apps Parent-child middleware: orchestrates, transforms, and routes data Azure Blob Storage Checkpoint management for reliable incremental processing Azure Table Storage Full execution logs for traceability, audit, and failure replay The three integrations work in concert: Integration 1: Spot Purchase Orders — D365 F&O to Legacy Business Problem A Spot Purchase Order is an ad-hoc purchase order raised outside of long-term contracts — often for urgent material procurement. Spot POs are created and managed in D365 F&O by procurement teams. However, the legacy system is the system of financial record, meaning every Spot PO created in D365 must be reflected in the legacy system for financial commitment tracking and vendor payment processing. Without integration, this would require manual re-entry – a process prone to error, delay, and duplication. How the Integration Works Parent Logic App – Spot PO Orchestrator The primary Logic App runs on a scheduled recurrence and uses a checkpoint mechanism stored in Azure Blob Storage to fetch only incremental changes – purchase orders created or modified since the last successful run. This ensures efficiency and prevents reprocessing of already-handled records. The workflow determines the operation type required for each PO: For each scenario, the Logic App fetches enriched data from multiple D365 F&O OData entities and constructs a structured JSON payload tailored for the legacy system’s API. ⚙ Tech Note: OData Entities Used PurchaseOrderHeaders, PurchaseOrderLinesV2, PurchaseLineDataEntities, WHSPurchLines, StatusCustomDatas Child Logic App – SendRequest (Reusable) Rather than embedding API communication logic directly in the orchestrator, we separated it into a reusable child Logic App. This child app receives the constructed payload, retrieves an OAuth 2.0 Bearer token, and executes the HTTP POST call to the legacy system’s API endpoint. This modular design pays dividends during maintenance: any change to authentication logic or API communication is made once in the child app and automatically applies to all parent integrations. Failed Record Handler Every enterprise integration needs robust failure recovery. When an API call fails: Sample Payload – Spot PO Create Sample JSON Payload: {   “userId”: “JSMITH”,   “order”: “456789”,   // Last 6 digits of D365 PO number   “vendor”: “VEND001”,   “receiptLoc”: “SITE01”,   “vendorOvrdCd”: “14”,   “lineItems”: [{     “orderLine”: “001”,     “item”: “ITEM001”,     “openQty”: 10,     “deliveryDate”: “061526”,  // MMddyy format for legacy compatibility     “comment”: “MPSSYS order – JSMITH” }] } } ✓ Business Impact: Zero manual re-entry of purchase orders between systems. Every Spot PO created or changed in D365 F&O is automatically reflected in the legacy system within minutes. Integration 2: Advance Shipment Notices — Legacy to D365 F&O Business Problem An Advance Shipment Notice (ASN) is a notification sent by the legacy WMS to the receiving system, informing it of an incoming shipment before it physically arrives. D365 F&O needs to receive ASNs to create Inbound Load Headers and Load Lines – enabling warehouse teams to prepare for receiving. Without this integration, receiving teams in D365 would be blind to incoming shipments until trucks arrived at the dock – eliminating any opportunity for advance dock scheduling, labor planning, or inventory pre-positioning. The Hybrid Integration Approach This integration presented an interesting technical challenge: the standard D365 F&O Inbound ASN V5 API supports a well-defined XML format, but the business required additional fields beyond what the standard API supports. The solution was a two-step Hybrid ASN Integration approach: ⚙ Tech Note: API Endpoint Pattern Insert:  POST {{BASE_URL}}/api/connector/enqueue/{{ACTIVITY_ID}}?entity=Inbound ASN V5 Enrich:  PATCH on InboundLoadHeaders and WHSASNWorkData Smart Insert vs. Update Determination To handle scenarios where an ASN might be re-sent for corrections or resynchronization, the integration includes a check before processing: This idempotent design prevents duplicate inbound loads from being created when the legacy system re-sends an ASN. One nuance worth noting: in D365’s standard ASN structure, the LoadId, ShipmentId, and LicensePlateNumber must carry the same value. The legacy system’s outbound ASN payload is configured to honour this requirement – ensuring clean data entry … Continue reading How a Top North American Commercial Vehicle Manufacturer Connected D365 F&O with Legacy Systems Without Disrupting Operations →

Summary In modern web application development, debugging efficiency plays a critical role in overall productivity. While full Internet Information Services (IIS) is powerful, it often introduces unnecessary complexity and slows down development cycles. This article explores how IIS Express (iisexpress.exe) provides a lightweight, fast, and developer-friendly alternative for debugging. You will learn how to use IIS Express effectively, understand its advantages over full IIS, and discover practical ways to streamline your debugging workflow for faster and more efficient development. Debugging Faster with IIS Express: A Practical Guide for Modern Developers In modern application development, debugging speed and flexibility can significantly impact productivity. While full IIS is powerful, it often introduces overhead that slows down iterative development. This is where IIS Express (iisexpress.exe) becomes a powerful yet underutilized tool. This article explores how to effectively use IIS Express for debugging, why it matters, and how it can streamline your development workflow. What is IIS Express? IIS Express is a lightweight, self-contained version of Internet Information Services (IIS) designed specifically for developers. It allows you to: Why Use IIS Express for Debugging? Where is IISExpress.exe Located? It is typically found at: C:\Program Files\IIS Express\iisexpress.exe How to Run IIS Express Manually You can start IIS Express from the command line: iisexpress.exe /path:”C:\MyApp” /port:8080 Parameters Explained: a. /path → Physical path of your applicationb. /port → Port number to run the application Debugging with IIS Express in Visual Studio Step 1: Set Project to Use IIS Express a. Open Project Propertiesb. Go to the Web sectionc. Select IIS Express Step 2: Start Debugging Press F5 or click Start Debugging. Visual Studio will: Attaching Debugger Manually Sometimes you may need to debug an already running instance. Steps: You can then add breakpoints in your code. You can add break points in code. Common Debugging Scenarios IIS Express vs Full IIS Feature IIS Express Full IIS Setup Minimal Complex Admin Rights Not required Required Performance Lightweight Production-ready Use Case Development Production Best Practices Strategic Insight Many developers default to full IIS for debugging, but this introduces: IIS Express provides a developer-first approach, enabling: Final Thoughts Debugging should be fast, predictable, and low-friction. IIS Express achieves this by providing a lightweight yet powerful runtime environment. Whether you are building APIs, web applications, or integrations, mastering IIS Express can significantly improve your development efficiency. Key Takeaway Use IIS Express for fast, isolated, and efficient debugging-without the overhead of full IIS. If you are implementing of F&O and want more clarity in your finance processes, feel free to reach out to us at transform@cloudfonts.com. We have helped multiple organizations streamline exactly these scenarios.

Summary In modern enterprise systems, tax visibility is no longer optional-it’s critical for compliance, reporting, and integrations. This blog explains how to programmatically extract detailed tax components (like GST and surcharges) in Microsoft Dynamics 365 Finance & Operations using standard, Microsoft-aligned methods. It highlights a scalable approach that avoids unsupported workarounds while enabling line-level transparency and integration-ready outputs. In enterprise systems, taxation is often treated as a black box, calculated correctly, yet rarely understood in depth. However, as organizations scale globally and compliance requirements tighten, visibility into tax components becomes a strategic necessity, not just a technical detail. Working with Purchase Orders in Microsoft Dynamics 365 Finance and Operations, one common challenge is: How do we break down tax into its individual components (like 18% GST, 5% surcharge) programmatically? This article explores a clean, scalable, and Microsoft-aligned approach to extracting tax components using standard framework classes-without relying on fragile or unsupported methods. The Problem: Tax Visibility Beyond Totals Most implementations stop at: But modern business scenarios demand: To achieve this, we must go deeper into the tax calculation pipeline. The Standard Tax Calculation Flow In D365 F&O, Purchase Order tax calculation follows a structured pipeline: PurchTable   ↓PurchTotals   ↓Tax Engine   ↓TmpTaxWorkTrans (Tax Components)  The key insight here is: Tax components are not stored permanently—they are generated dynamically during calculation. The Solution: Leveraging PurchTotals and Tax Framework Instead of accessing internal or temporary structures directly, we use standard classes provided by Microsoft. Here is the working approach: PurchTable      purchTable;PurchTotals     purchTotals;Tax tax;TmpTaxWorkTrans tmpTaxWorkTrans; purchTable = PurchTable::find(“IVC-00003”); purchTotals = PurchTotals::newPurchTable(purchTable);purchTotals.calc(); tax = purchTotals.tax(); tmpTaxWorkTrans = tax.tmpTaxWorkTrans(); while select tmpTaxWorkTrans{    info(strFmt(“Tax Code : %1”, tmpTaxWorkTrans.TaxCode));    info(strFmt(“Tax % : %1”, tmpTaxWorkTrans.TaxValue));    info(strFmt(“Tax Amount : %1”, tmpTaxWorkTrans.TaxAmountCur));} Why This Approach Matters 1. Aligns with Microsoft Standard This method mirrors what the system does when you click “Sales Tax” on a Purchase Order form. 2. Avoids Unsupported APIs No dependency on: 3. Works Pre-Posting Unlike TaxTrans, this approach works before invoice posting, making it ideal for: Real-World Output For a Purchase Order with: The output becomes: Tax Code : 18Tax % : 18Tax Amount : 198 Tax Code : 5Tax % : 5Tax Amount : 55 This level of granularity enables: Extending the Approach You can filter by line: where tmpTaxWorkTrans.SourceRecId == purchLine.RecId 2. Multi-Currency Scenarios The same logic works seamlessly for: Tax is calculated in: Integration-Ready Design This structure can be easily exposed via: Strategic Insight In many projects, developers attempt to: These approaches introduce: The better approach is to embrace the framework, not bypass it. Final Thoughts Tax calculation in D365 Finance & Operations is not just about numbers-it’s about designing for transparency, compliance, and scalability. By leveraging: you gain: Key Takeaway If you need tax components in Purchase Orders, don’t query tables, trigger the calculation and read from the framework. If you are implementing of F&O and want more clarity in your finance processes, feel free to reach out to us at transform@cloudfonts.com. We have helped multiple organizations streamline exactly these scenarios.

SummarySales tax configurations in Microsoft Dynamics 365 Finance and Operations can go beyond simple percentage calculations. In scenarios where taxes are layered or interdependent, businesses often require a tax-on-tax (cascading tax) setup. This blog explains how to configure an 18% primary tax and an additional 5% tax calculated on top of it, ensuring accurate, automated, and compliant tax calculations for complex service-based industries like Oil & Gas. Sales Tax Setup in Microsoft Dynamics 365 Finance & Operations (18% + 5% Tax-on-Tax) In global and industry-specific implementations, taxation is not always flat. Many organizations, especially in regulated sectors, require layered tax calculations where one tax is applied on top of another. In one such implementation within Microsoft Dynamics 365 Finance and Operations, this configuration was successfully used for a service-based company in the Oil and Gas industry. The requirement was straightforward but technically nuanced: a. Apply a primary tax of 18% on the service valueb. Apply an additional 5% tax on the total amount after the first tax This type of setup is commonly required when: a. Multiple statutory taxes are interdependentb. Regulations mandate tax calculation on already taxed valuesc. Service contracts involve multi-layered billing structures By configuring this correctly, businesses can eliminate manual calculations and ensure compliance. Understanding the Requirement The logic follows a cascading structure: a. First, calculate 18% on the base amountb. Then, calculate 5% on (Base Amount + 18% tax) Example Calculation: a. Item price = ₹100b. 18% tax = ₹18c. 5% tax on ₹118 = ₹5.9d. Total tax = ₹23.9e. Final amount = ₹123.9 This demonstrates how the second tax depends on the first, making configuration accuracy critical. Step-by-Step Configuration 1. Create Sales Tax CodesNavigate to:Tax > Indirect taxes > Sales tax > Sales tax codes a. Create Tax Code 1Name: Tax18Percentage: 18% b. Create Tax Code 2Name: Tax5Percentage: 5% 2. Configure Tax-on-Tax For Tax5 (5%): a. Enable: Calculate tax on taxb. Select base tax: Tax18 This ensures Tax5 is calculated on the net amount + Tax18. 3. Create Sales Tax Group Navigate to:Tax > Indirect taxes > Sales tax > Sales tax groups a. Create: SALES_TAX_GROUPb. Add:i. Tax18ii. Tax5 4. Create Item Sales Tax Group Navigate to:Tax > Indirect taxes > Sales tax > Item sales tax groups a. Create: ITEM_TAX_GROUPb. Add:i. Tax18ii. Tax5 5. Assign Tax Groups a. Assign the Item sales tax group to the itemb. Ensure correct mapping in transactions Tax Calculation Flow Step Amount Base Amount ₹1000 GST18 (18%) ₹180 GST5 (5% on 118) ₹59 Total Tax ₹239 Final Amount ₹1239 a. Tax-on-tax must always be configured on the dependent tax (5%)b. Sequence of tax codes directly impacts calculation accuracyc. Always validate through Sales Order → Invoice → Tax detailsd. Perform complete testing in Sandbox before Production deployment Conclusion Tax-on-tax configuration in Microsoft Dynamics 365 Finance and Operations is a powerful capability that enables businesses to handle complex, cascading tax requirements with precision. By structuring tax dependencies correctly: a. The base tax (18%) is calculated firstb. The dependent tax (5%) is automatically applied on the cumulative amount This ensures: a. Accurate financial reportingb. Regulatory compliancec. Zero manual intervention For industries dealing with layered taxation models, this approach is not just helpful-it is essential. I hope you found this blog useful. If you would like to discuss anything further, feel free to reach out to us at transform@cloudfronts.com.

Email remains a vital communication tool in Dynamics 365 Finance & Operations, powering workflows like invoice delivery, notifications, and approvals. To ensure secure and reliable email transmission, organizations configure SMTP directly within F&O. This guide walks through the streamlined steps to configure SMTP in F&O so your system can send emails seamlessly. Steps to Achieve goal 2. Go to SMTP settings and enter below valuesEnter SMTP Server Details Enable SSL/TLS if required. Server: e.g., smtp.office365.com Port: usually 587 (TLS) 3. Define Sender Address Ensure each user has a valid email address in User options → Email. To conclude, configuring SMTP in Dynamics 365 F&O is a straightforward process that unlocks secure and efficient email communication across your business processes. By entering the correct server details, authentication method, and sender information, you enable F&O to deliver messages reliably without manual intervention. With SMTP in place, Finance & Operations becomes not just a system of record, but a system of communication. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Managing secure operations in Microsoft Dynamics 365 Finance and Operations (D365FO) is crucial for enterprise-level environments. While working in a Dev environment, I recently encountered an issue while posting the packing slip for a Sales Order. After troubleshooting, I identified the problem was related to expired SSL certificates in a cloud-hosted environment. SSL certificates in D365FO environments remain valid for one year. To maintain security and avoid disruptions, it’s necessary to renew these certificates regularly-a process called credential rotation, managed via the Lifecycle Services (LCS) portal. In this blog, I’ll guide you step-by-step on how to resolve this issue through SSL certificate rotation. Why SSL Certificate Rotation is Important When deploying Dynamics 365 Finance Operations as a cloud-hosted environment, SSL certificates are used to encrypt data and ensure secure communication between servers. Expired certificates can disrupt functionality. Regular rotation of credentials is a best practice to maintain smooth operations and robust cybersecurity. Step-by-Step Process to Rotate SSL Certificates in Dynamics 365 Finance & Operations Here’s how you can resolve the issue and renew SSL certificates in your environment: Step 1: Log into the LCS Environment Step 2: Navigate to the Implementation Project Step 3: Initiate Credential Rotation Step 4: Rotate SSL Secrets Certificates Step 5: Wait for the Process to Complete Step 6: Verify the Deployment Status To conclude, regularly rotating SSL certificates not only resolves operational issues but also ensures compliance with enterprise-level cybersecurity practices. By following the above steps, you can maintain the security and functionality of your Dynamics 365 Finance Operations cloud-hosted environments. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com