News
General
Opening balance in the Polish localization of Dynamics 365 – good practices
Continuing our series on best practices for deploying the Polish localization of Microsoft Dynamics 365 – and tailoring it to headquarters’ requirements – this article focuses on the opening balance. Think of it not just as a technical checklist, but as a cornerstone that keeps business processes running smoothly and ensures compliance with Polish accounting and tax rules. Why the opening balance deserves a deep dive An opening balance is far more than a table of balances. It’s the foundation on which day-to-day operations and finance processes will run in the new system. Because of that, your data analysis has to respect every nuance of Polish accounting and tax law. Start with a local-requirements list Creating a quick local requirements list helps you to: Check data completeness See which data are covered out of the-box Spot the gaps that need tweaks or custom solutions A common scenario: credit notes for invoices from the legacy system Dynamics 365 lets you issue a credit note against an invoice booked inside D365, because the system keeps the link between the two documents and prints the right references. The headache comes when you need to credit an invoice that lived only in your old system. We recommend: Load open receivables in the opening balance – but skip the full detail of every historic sales invoice. Re-entering it all is rarely worth the effort. Add a small custom feature that lets users type the key details of a historic invoice manually (or import them if you have a lot). How sophisticated should that customisation be? During analysis, collect data on: How many credit notes you issue How often they show up What types of credit notes they are These numbers tell you whether a simple form is enough or you need a more advanced tool.And remember: even rare, low-value transactions still carry reporting and tax obligations. The opening balance is a starting line, not a finish line Too many projects treat the opening balance as the “end” of data migration. In reality, it’s the launchpad for ongoing processes. Skip key data now and errors will pop up after go-live. Areas that typically need attention: Corrections to JPK_V7 for periods handled in the legacy system Revaluations of open customer and vendor transactions in foreign currency FX revaluation of bank and cash transactions Data for the bad-debt relief scheme Information needed for split payment VAT deferred to future reporting periods Key take-aways Treat the opening balance as a continuation of business processes—not just a snapshot of account balances. Good analysis is never wasted time; it pays for itself later in the project. Lean on a team that knows D365 and the Polish localization inside out to design the right customisations. Keep solutions consistent—get your solution architect involved early. Involve your users. Their day-to-day insight is gold for process analysis. Good luck with your implementation – and remember, a solid opening balance sets the tone for everything that follows!
7F
Best practices for Dynamics 365 Polish Rollout – pt. 3
Part 3. Running the polish localization in the production environment After the implementation phase comes the critical moment—go-live. This is when all the work done during analysis and configuration is tested in real-world operations. The practices below help keep the system stable, compliant with Polish law, and aligned with group processes. Data migration and verification A smooth data migration—and a double-check afterwards—is the foundation of a successful start-up, especially for tax and reporting data. Examples of critical data: company details used in tax returns (NIP, address) customer and vendor records: addresses, VAT numbers, tax groups links to the correct tax offices key localization parameters such as NBP exchange-rate import or sales-credit-note functions Organising work in the support phase Good habits from implementation keep quality high after go-live. Efficient handling of service tickets and user requests is essential. Choose a ticketing system that sets priorities automatically—e.g., a VAT-return issue should outrank a posting-template change. Decide who may raise tickets—every user or only key contacts? Define ticket format, required attachments, response times, and support responsibilities. Automate workflows—task assignment, notifications, escalations. Separate tickets into errors (need immediate action) questions/training needs (handled through user support) Proactive checks of data and reports Do not wait until the deadline to prepare tax reports. Errors mean penalties and process delays. Check ahead of time: completeness and accuracy of the JPK_V7 file—leave time for fixes other JPK files the first sales invoice printout—verify data before posting Test environment and system updates Keep a dedicated test environment to analyse tickets and trial changes before they reach production. For every update: Review Microsoft’s release notes. Assess the impact on Polish-localization settings. Test key processes before the new version goes live. Monitoring legal changes ERP systems must adapt quickly to new regulations. Track legal updates proactively (e.g., KSeF, JPK_CIT, JPK_KR). Involve the team in spotting potential system impacts. Use the analysis-phase documents and lessons learned—they are your roadmap. Summary Clear communication and fast ticket resolution are the keys to smooth operations after go-live. They prevent misunderstandings, shorten response times, and build user trust. Consider user-satisfaction surveys to gather feedback and continually improve support. Effective change management reduces user anxiety about the new system and ensures a seamless shift to the new way of working. >> You can read Part 2 [HERE] <<
7F
Best practices for Dynamics 365 Polish Rollout – pt. 2
Part 2. Effective and correct implementation of polish localization requirements Once the analysis phase is complete, it is time for implementation. At this stage, well-organised work and clear team communication are critical. The practices below will help you introduce the Polish localization in D365 efficiently while staying fully compliant with both local law and group rules. Organise project work To keep control of scope and progress: Use task-management tools such as DevOps or Jira. They let you split the work into phases (e.g., system configuration, functional tests, development, UAT) monitor progress and react quickly to delays Update task statuses regularly, assign owners and deadlines. Include configuration and testing tasks, not only development work. Communicate effectively inside the team Make sure every team member understands the Polish localization requirements. Clarify doubts as soon as they appear. Hold 2–3 status meetings per week, sized to the team and the workload. Discuss detailed operational issues in smaller working groups—avoid pulling the whole team into every matter. Define the right scope Not every function needs full automation—balance configuration and testing effort against how often the feature will be used.Example: Withholding tax: extensive setup in the “Taxes” module may be too time-consuming for occasional transactions; a manual process could be enough. If D365 lacks a function required in Poland, plan dedicated modifications, for example: corrections to sales invoices issued in the legacy system NBP exchange rates with a one-day shift (not available in standard D365) taxpayer validations (White List, VIES, GUS) Test and validate thoroughly Tests must cover the entire process, not just single D365 functions: system-to-system integrations data validation after migration performance tests for complex processes regression tests, especially when key processes change Add system alerts and messages where useful. Involve end users at every stage—their experience is vital when designing test scenarios. Provide clear user instructions. Clarify team roles and manage knowledge Include a System Architect to keep solutions consistent and reduce risk during changes. Work with a complete process map—many processes start outside Finance (e.g., in purchasing or logistics). Training: Run sessions for both the Polish and central teams to bridge knowledge gaps. Well-trained users greatly increase the chance of a smooth go-live. Summary Help the group team understand Polish requirements early. Organise work with tools like DevOps or Jira, broken into logical phases. Check whether automation makes economic sense case by case. Remember integration, regression, and performance tests. Maintain clear communication and use small-group meetings for detailed issues. >> You can read Part 1 [HERE] <<
7F
Struggling to integrate yesterday’s ERP with today’s tech? Here’s what you need to know.
As smart tools and connected platforms reshape the way we work, businesses are under constant pressure to innovate, adapt, and deliver more value with greater efficiency. Yet, for many organizations, a significant barrier to transformation lies within their ERP system. Many legacy ERPs were designed decades ago, built for a world where cloud computing, mobile connectivity, and IoT devices were science fiction. Back then, these systems served as robust backbones for finance, inventory, and operations. But fast forward to today’s tech-driven landscape, and those same systems often stand in the way of progress. The integration dilemma Modern business operations rely on interconnected systems. Manufacturing Execution Systems (MES), Customer Relationship Management (CRM) tools, cloud platforms, data analytics dashboards, and IoT-enabled devices are all integral to running a responsive, data-driven business. The problem? Legacy ERP systems weren’t designed with these technologies in mind. Integrating older ERPs with newer tech can be a nightmare. Their rigid architecture, limited APIs, and proprietary frameworks make it difficult (sometimes even impossible) to communicate with modern platforms. Even when integration is technically feasible, it often requires costly custom development, middleware solutions, and ongoing maintenance. This patchwork approach leads to increased downtime, data silos, poor visibility, and a serious drag on agility. Worse still, these legacy systems can’t keep pace with the real-time demands of today’s operations. Imagine trying to implement predictive maintenance with IoT sensors feeding data every second only to have it bottlenecked by an ERP that processes data in overnight batches. Why modern ERP makes a difference Modern ERP systems are built with integration in mind. Cloud-native, API-rich, and often modular by design, they act as the digital backbone that connects your entire tech stack. Whether you’re trying to automate workflows between your MES and supply chain system, or feed real-time customer data from your CRM into financial planning tools, a modern ERP makes it seamless. Here are some of the benefits: Unified data: Say goodbye to silos. A modern ERP centralizes data from across your enterprise, enabling better decision making and real-time visibility. Scalability: Cloud-native ERPs grow with your business. You can add users, modules, or even new locations without massive IT overhead. Faster integrations: With open APIs and pre-built connectors, modern ERPs drastically reduce the time and cost of integrating new systems. Real-time insights: Access dashboards and analytics tools that feed on live data, not yesterday’s reports. Improved user experience: Modern interfaces are intuitive, mobile-friendly, and designed with the end user in mind. Holding on to a legacy ERP because “it still works”? Clinging to yesterday’s ERP system might feel like the safe, cost-effective option but it could be quietly costing your business in missed opportunities, inefficient processes, and integration headaches. As the pace of innovation accelerates, the gap between old and new systems will only widen. Adopting a modern ERP doesn’t just solve today’s integration problems. It sets your business up with a flexible, future-proof foundation.
RamBase
Best practices for Dynamics 365 Polish Rollout – pt. 1
Part 1. Good Analysis Is the Key to Success Rolling out an ERP system such as Microsoft Dynamics 365 inside an international group is demanding. In Poland, success depends on capturing local requirements early in the analysis stage. Remember: analysis is not wasted time—it is an investment that pays back many times later in the project. Give the Central Team Complete Information Make sure the central rollout team gets a full list of Polish localization needs. Don’t assume anything is “obvious.” What is routine for a Polish team may be unknown to colleagues abroad. Example — sales invoices and their correctionsPrepare a list of all invoice types now used, with sample source documents: sales invoices corrective sales invoices and corrections of corrections advance and final invoices and their corrections sale of fixed assets accounting notes any other types not listed above Include Rare and Low-Value Transactions The ERP system must cover every business scenario, even ones that happen only occasionally. Rare cases still carry accounting and tax obligations. Example: A transaction that changes VAT because of an adjustment to input tax on goods and services recorded as fixed assets. Check Formal Requirements Early Confirm, during analysis, the needs for: printouts (e.g., VAT invoices, transaction confirmations) future integrations (e.g., with KSeF — the National e-Invoice System) tax returns and reports (JPK, VAT-EU, CIT-8, etc.) What We Often Forget Elements most often skipped or underestimated: unusual corrections (e.g., correcting a correction or an advance invoice) purchases from one-time suppliers opening balances for specific functions, such as bad-debt relief, year-end valuation of foreign-currency transactions, or split payments settlements with employees for travel expenses, advances, and credit cards formats for tax transfers Summary The sooner you spot gaps between group rules and Polish law, the easier it is to plan the needed adjustments. The implementation team must understand the specifics of the Polish localization and be ready to compromise or revise group rules when necessary.
7F
Merit ERP: Enhancing Beauty Production Management
Nuco is a contract manufacturer of color cosmetics for global beauty brands. The company oversees the entire proces – from concept to final, shelf-ready product. In 2021, Nuco implemented the Merit ERP system for managing production, strategic and operational planning, logistics, warehousing, sales, finance, and human resources. Handling customer orders is a complex process carried out by different departments. It involves registration, verification, approval, planning, preparation – up to production, packaging, and shipment. The process-oriented Merit system allows Nuco to manage dozens to hundreds of production orders daily, 24 hours a day, in three shifts. Merit ERP also supports planning and managing production. It automatically updates the strategic and operational plan, considering days, resources, and machines. Nuco analyzes plan execution according to defined criteria in Qlik Sense. Using kiosks on the production floor, Nuco registers everything that happens in production: weighing and using raw materials, quality control, issuing labels, dosing and pressing, packaging, and many other operations in the Merit system. In the warehouse, Merit ERP organizes the processes of receiving raw materials, issuing them to production, and finally, receiving finished products, labeling, and preparing them for shipment. Importantly, Merit enables Nuco to meet quality standards through traceability, i.e., tracking batches of raw materials, materials, and products. With the Merit ERP system, Nuco has complete control over production. It plans, calculates costs, monitors production, traces batches while maintaining quality requirements, and analyzes efficiency… Production with Merit simply goes beautifully!
Asseco BS
Pretec is modernizing its operations with RamBase Cloud ERP
Pretec, a leading supplier of steel products to the construction industry, has chosen RamBase Cloud ERP as its new digital platform. The company wanted to modernize its systems and move away from on-premise solutions to a flexible, cloud-based platform that can support its growth and future IT needs. Limitations with on-premise Pretec has grown from a small business in Sarpsborg, Norway, to an international player with 300 employees and operations in seven countries. Before implementing RamBase Cloud ERP, they used Visma Business and SuperOffice – both on-premise solutions that no longer satisfied the need for flexibility and integration. A comprehensive IT analysis conducted in 2023 revealed that the company required enhanced system support for several of its core processes. Additionally, the desire to provide customers with better digital documentation for products, quality, and environmental standards played a key role in the decision to switch systems. The choice fell on RamBase Cloud ERP Pretec considered several ERP solutions before choosing RamBase, including alternatives such as Jeeves, Microsoft Dynamics 365, Visma Business NXT and NetSuite. What really appealed to Pretec about RamBase Cloud ERP was the holistic user interface for all users and main processes. A decisive factor was also the ability to follow documentation and status at line level throughout the process in the system. Block Quote This, combined with the fact that RamBase was a cost-effective choice, fitted perfectly with Pretec’s needs for both future growth and modern IT solutions. Goals for the future Pretec is in the process of implementing the system and has already held its first workshop with the RamBase team. The aim of the implementation is to give Pretec’s employees a more efficient and streamlined working day. RamBase will support the most important business processes and provide employees with an efficient and modern solution for handling daily tasks. Through good collaboration, Pretec will be well prepared to meet future requirements in an increasingly digitized world.
RamBase
Salesforce Launches AgentExchange: the Trusted Marketplace for Agentforce
AgentExchange empowers partners, developers, and the Agentblazer community to build and monetize agentic AI components, fueling the next generation of businesses in the $6 trillion digital labor market AgentExchange includes more than 200 partners, including Google Cloud, Docusign, and Box, building trusted Agentforce solutions that businesses can use to rapidly build AI agents Developers can discover, try, and buy hundreds of prebuilt partner actions, topics, and templates on the marketplace or surfaced directly within Salesforce’s agent building tools SAN FRANCISCO – March 4, 2025 – Salesforce (NYSE: CRM), the #1 AI CRM, today launched AgentExchange, the trusted marketplace and community for Agentforce that is built into Salesforce, opening up new opportunities for partners, developers, and Agentblazers to participate in the rapidly expanding $6 trillion digital labor market. Building on the success of Salesforce AppExchange — the first and world’s largest enterprise cloud marketplace, which has grown to more than 13 million app installs — AgentExchange expands the capabilities and ecosystem of Agentforce, Salesforce’s digital labor platform. AgentExchange launches with more than 200 initial partners and hundreds of ready-made actions, topics, and templates that have passed rigorous security and customer reviews. Combined, these solutions will help organizations quickly create and deploy AI agents to improve productivity, efficiency, and innovation in any profession or industry. “Accelerating our speed of execution is critical to Goodyear’s ability to deliver for our customers and maximize our end-to-end value proposition. We’re excited about the potential of the ready-to-use solutions from AgentExchange to enhance our speed, efficiency, and customer experience,” shared Goodyear CEO and President Mark Stewart. Block Quote Partners are already building Agentforce components for AgentExchange. For example: Google Cloud: Build Agentforce agents, grounded in Google Search via Vertex AI and with the ability to reference up-to-the-minute data, news, and current events. Box: Enable Agentforce agents to extract insights from unstructured data and power actions with that information, using natural language to interact with content in Box. Docusign: Generate agreements, route for signatures, track status, and gain key insights — automating workflows and boosting efficiency. Workday: Streamline critical employee self-service workflows such as onboarding, benefits management, and career development, freeing up HR teams and significantly enhancing the employee experience. “When we launched AppExchange in 2005, it helped our customers get even more value from our platform with prebuilt apps, workflows, and integrations. It also gave our partners an opportunity to participate in the emerging cloud economy and build thriving businesses,” said Brian Landsman, EVP & GM, Global Business Development & Partnerships at Salesforce. “With AgentExchange, we’re doing much the same — opening up Agentforce for partners, startups, and Agentblazers to participate in the digital labor market and build agentic AI on Salesforce.” “AgentExchange empowers customers to seamlessly integrate trusted AI solutions within their workflow,” said Alice Steinglass, EVP & GM of Platform, Integration and Automation at Salesforce. “Now our developer community can directly tap the expertise of our partner ecosystem to get the right industry-specific solutions so they can build and implement AI agents, and be the pioneers turning their businesses into Agentforce companies.” New AgentExchange and Agentforce features include: New partner-built components: Partners and Agentblazers can now offer four types of agentic components: Actions: Expand the jobs agents built with Agentforce can do by adding new integrations — ranging from Apex, flows, APIs, and prompts — to tailor industry-specific components. Prompt templates: Use pre-written, reusable prompts that ensure consistent interactions and help agents gather information, assist users, and achieve specific goals. Topics: Focus and refine agent behavior by grouping actions and instructions around a single task or job. This helps to ensure agents deliver consistent results and stay within guardrails. Agent templates: Deliver comprehensive AI solutions by combining multiple topics and using the powerful actions partners have created, complete with metadata and global instructions that span across topics. Easily discover, try, and buy AI solutions: AgentExchange simplifies the process of finding and deploying the right trusted AI solutions. Customers can explore AgentExchange solutions directly on the marketplace or within Salesforce’s Agent Builder tool to identify the right solutions for their use case, product, or industry. Use standard and Slack actions: Partners and Agentblazers can now offer out-of-the-box Agentforce actions, including Slack, in packaged Agentforce topics and templates on the AgentExchange. These actions empower partner-delivered agents with built-in CRM and Slack capabilities, such as creating a case, canceling an order, updating a Slack canvas, searching Slack, or sending direct messages. Access trusted, industry-specific agent solutions: AgentExchange connects businesses with Salesforce partners who have deep expertise in specific industries. Businesses can implement pre-built, customizable solutions that address unique challenges, accelerating AI adoption and maximizing its impact. Rigorous security reviews and customer feedback ensure trust in every solution listed on AgentExchange. Collaborate and innovate with Agentblazers: AgentExchange fosters a collaborative ecosystem where businesses, partners, and individual Agentblazers can connect, share best practices, and innovate together, accelerating the adoption of agentic AI. Block Quote AgentExchange solutions Partners who have AgentExchange listings or are actively developing Agentforce components include: Sales & service Appiphony: Offers document generation fully integrated with Agentforce. Bucher + Suter: Enables seamless escalation from agent to human within Agentforce, preserving context for smooth transitions. Docusign: Generates documents, routes for signature, and tracks doc and signature status. Highspot: Provides Agentforce users with curated sales content and AI-powered analytics to increase buyer engagement and close more deals. Neuron 7: Directs enterprise service teams through optimal resolution paths for swift, accurate problem-solving. SalesWings: Integrates customer intent data to enhance prospect engagement and sales performance. Seismic: Delivers AI-powered personalized content at scale from Salesforce, ensuring the right content for every opportunity stage and accelerating sales. TechSee: Empowers sales, service, and field service teams with AI-driven visual intelligence to enhance remote assistance and customer support. Finance, operations, and talent Asymbl: Offers AI-powered recruiting solutions to streamline talent workflows. Bullhorn: Recruitment Cloud Agents leverage over 90 actions to accelerate the entire recruiting lifecycle, improving key processes such as candidate matching, talent engagement, and hiring recommendations. Certinia: Enables managers to monitor a client’s health score, diagnose potential issues, and recommend remedies to customer issues. FinDock: Integrates payment and CRM data, empowering payment agents. InvestorFlow: Simplifies prospect targeting and opportunity aggregation for financial deals. OpenText: Automates document management, reducing storage costs and errors, for better efficiency and management.
Salesforce
MarekMac
MarekMac
RamBase
