I am a Senior Manager in the Digital Transformation division at my org and we have been working with UiPath for a few weeks as part of our early RPA footprint. Our initial scope is narrow but high-value: automating vendor invoice processing and SAP data entry, both of which are rules-heavy, high-volume workflows tightly coupled to SAP and our AP operations. Even at this early stage, with only a handful of bots in production, the platform has held up well under real workload conditions. From a development standpoint, UiPath Studio's workflow model (sequences, flowcharts, and state machines) has been a good fit for the branching logic in our invoice workflows, where header/line-item validation, PO matching, and exception routing need to coexist cleanly. Reusable libraries and the package/dependency model have let us standardize common components (SAP login, credential retrieval from Orchestrator assets, logging wrappers, retry-scope patterns) early, which should pay off as we scale. The SAP automation activities have been a particular strength: the dedicated SAP activities expose transaction-level controls that are more stable than generic UI automation, which has materially reduced selector fragility on SAP screens. Orchestrator has delivered the control-plane capabilities we expected from an enterprise RPA tool. Queues with SLA/priority handling, triggers, asset management for environment-specific configuration, and role-based access control line up well with our governance and audit requirements as a public-sector enterprise. Document Understanding has performed reasonably well on our invoice set, and combining the pre-trained invoice model with a validation station workflow for low-confidence extractions has given us an acceptable straight-through processing rate for structured invoices. On the less favorable side, licensing cost is a real planning constraint when sizing for enterprise-scale rollout. Version upgrades across Studio, activity packages, and Orchestrator require disciplined environment management. Debugging complex, multi-application workflows with dynamic selectors and transient exceptions has a steeper learning curve than the low-code positioning suggests. Even with a small production footprint, targeted processes have already reduced my team's manual effort by roughly 25-30%, and I expect that to grow significantly as we industrialize the pipeline and stand up a proper CoE. Overall, UiPath has been a capable foundation for our RPA journey, and my recommendation is to invest upfront in reusable frameworks, selector and exception-handling standards, Orchestrator governance, and disciplined license forecasting. Excellent to be precise.

it is a decent experience, while it lacks in providing certain features that would be helpful to do my job in a better way but its not that bad Afterall. The support team is great and helps with everything that i request.