# Settyl — Lasya AI: full reference > Settyl builds Lasya AI, the System of Execution for supply chains, enabling organizations to move from fragmented coordination to Autonomous Supply Chain Execution across existing enterprise systems and external partners. Source: https://settyl.com. Company: Settyl (founded 2022; India, Middle East, North America). Founder: Gokulganth TM. Contact: support@settyl.com. ## Definitions ### Operational Fragmentation Operational Fragmentation is the condition in which supply chain work is distributed across disconnected systems, functions, companies and channels, forcing people to manually carry context, state and follow-through between them. Also called: Supply Chain Execution Fragmentation, Enterprise Execution Fragmentation. More: https://settyl.com/operational-fragmentation ### Multi-Enterprise Execution A framework for carrying a transaction across independent companies, systems and communication channels while maintaining its execution state, context and ownership until a verified outcome is reached. Also called: Cross-Enterprise Execution, Multi-Enterprise Transaction Execution. More: https://settyl.com/multi-enterprise-execution ### System of Execution The architectural layer responsible for carrying a business transaction from intent to verified outcome across enterprise systems, people, AI agents and external partners while authoritative Systems of Record retain official business state. Also called: System of Execution for Supply Chains, Supply Chain System of Execution, Execution Layer. More: https://settyl.com/system-of-execution ### Autonomous Supply Chain Execution The outcome in which supply-chain transactions continue across systems, functions and enterprise boundaries with minimal human relay until the required business outcome is verified. More: https://settyl.com/autonomous-supply-chain-execution ### Operational Memory Governed execution history created from transaction signals, context, decisions, actions, approvals, partner commitments, exceptions and verified outcomes so future supply-chain execution can reuse accumulated operational evidence. Also called: Transaction Memory, Supply Chain Operational Memory. More: https://settyl.com/lasya-ai ### AI Supply Chain Operating System A metaphor for the operating environment of a supply-chain System of Execution, where transaction state, actions, exceptions, partner interactions and operational memory are coordinated across systems and enterprise boundaries. Also called: AI Supply Chain OS. More: https://settyl.com/system-of-execution ### Execution Fragmentation Tax The hidden operational cost of manually relaying, reconciling, chasing and coordinating supply chain work across disconnected systems and enterprise boundaries. Also called: Coordination Tax. More: https://settyl.com/supply-chain-execution-fragmentation-calculator ### Autonomy Rate A supply-chain execution KPI measuring the share of eligible transactions and governed exceptions completed end-to-end without human relay. More: https://settyl.com/insights/autonomy-rate-supply-chain-kpi ### Exception Autonomy The ability of a supply-chain transaction to detect a deviation, understand its impact, recover under policy and escalate only when human authority is required. More: https://settyl.com/insights/exception-is-the-real-test-of-autonomy ### Transaction State The persistent record of a supply-chain transaction — intent, commitments, evidence, policy, authority, actions, exceptions and completion criteria — that execution acts against, rather than a single status field. Also called: Persistent Transaction State, Execution State. More: https://settyl.com/blogs/inside-an-autonomous-supply-chain-transaction-state-evidence-policy-and-memory ### System of Record The authoritative application, typically ERP, that preserves master data, governed transactions, inventory, financial state, controls and auditability. A System of Execution carries work between its records and writes verified outcomes back. More: https://settyl.com/blogs/system-of-record-vs-system-of-execution-in-supply-chain ## Lasya AI Lasya AI is the System of Execution for supply chains. It maintains transaction state and executes work across procurement, logistics, EXIM, finance, enterprise applications and external partners while ERP remains the System of Record. Capabilities: Persistent transaction state; Multi-Enterprise Execution; Operational Memory; Governed exception execution; Autonomous Sourcing and Procurement; Autonomous Freight, Logistics and EXIM; Autonomous Finance Operations; Email, WhatsApp, EDI, API, document and portal participation; ERP outcome synchronization. ### Lasya AI Autonomous Sourcing & Procurement A Lasya AI System of Execution capability that carries sourcing and procurement transactions across supplier discovery, RFQ, negotiation, approvals, PO creation and supplier acknowledgement to verified supplier commitment. Capabilities: Supplier discovery; RFQ / RFI and bid normalization; Negotiation; Approvals; PO creation; Supplier acknowledgement; Post-PO exception handling. More: https://settyl.com/products/autonomous-sourcing-procurement ### Lasya AI Autonomous Freight & Logistics A Lasya AI System of Execution capability for multimodal freight, carrier coordination, shipment exceptions, EXIM and verified delivery across enterprise systems and external partners. Capabilities: Shipment planning; Carrier and forwarder sourcing; Tendering and booking; Dispatch and tracking; Customs and EXIM; ePOD and freight evidence. More: https://settyl.com/products/autonomous-freight-logistics ### Lasya AI Autonomous Finance Operations A Lasya AI System of Execution capability for autonomous accounts payable, financial reconciliation, freight audit, governed exception handling, approvals, ERP posting and verified financial closure across procurement and logistics execution evidence. Capabilities: Invoice intake; PO, receipt and rate validation; Matching and variance resolution; Approvals and GL coding; Settlement workflow; ERP posting. More: https://settyl.com/products/autonomous-finance-operations ## Frequently asked questions ### About Lasya AI ### What is Lasya AI? Lasya AI is a System of Execution for supply chains. It carries transactions across systems, functions and enterprise boundaries from intent to verified outcome while ERP remains the System of Record. ### How is Lasya different from a copilot or standalone AI agent? A copilot recommends. A standalone agent can perform an individual task. Lasya is the System of Execution: specialized agents work against one shared transaction state while Lasya carries context, ownership, policy, exceptions and evidence across applications, enterprises and communication channels from intent to verified outcome. ### Do suppliers and carriers need to adopt Lasya? No. They can continue using email, WhatsApp, EDI, APIs, documents and existing portals while Lasya maintains the execution state. ### Does Lasya replace ERP? No. ERP remains authoritative for master, transactional and financial records. Lasya executes the work between those records and returns verified outcomes. ### What is Operational Memory? It is persistent execution context built from commitments, decisions, actions, exceptions, recoveries and outcomes across completed transactions. ### How does Lasya handle exceptions? Lasya can detect exceptions, assess impact and execute permitted recovery within policy. Decisions outside approved authority are escalated to the appropriate human owner. ### Settyl and Lasya AI (homepage) ### What is Lasya AI? Lasya AI is a System of Execution for supply chains. It runs procurement, freight and logistics, EXIM and finance transactions end to end across your ERP, suppliers and logistics partners. ### Does Lasya replace our ERP? No. SAP, Oracle or Dynamics 365 stays your system of record. Lasya runs the work between systems and partners and writes verified outcomes back to the ERP. ### What does Multi-Enterprise Execution mean? One transaction carries its context, owner and next action across every company it touches: buyers, suppliers, carriers, forwarders, customs, warehouses and finance. ### Do suppliers and carriers need a new portal? No. Partners keep transacting on the channels they already use: email, WhatsApp, Excel, PDF, EDI, existing portals or API. ### How are exceptions handled? Lasya detects the variance, assesses downstream impact, checks policy and authority, then executes governed recovery such as rebooking, rerouting, split sourcing or disputes. People are escalated only when policy requires it. ### How do we start? Pick one high-friction workflow, such as an RFQ, shipment, EXIM movement, invoice queue or exception. Measure cycle time, manual touches and exception recovery, then expand to adjacent transactions. ### What is Autonomous Supply Chain Execution? Transactions that complete across systems and partners within governed policy, without a person relaying state from one tool or company to the next. ### Autonomous Sourcing & Procurement ### What is Autonomous Sourcing & Procurement? Running sourcing and procurement from intent to verified supplier commitment with minimal manual relay, under governed policies. ### How is it different from sourcing software or eProcurement suites? Those tools optimize steps within one function. Lasya is the execution layer across suppliers, systems, approvals and exceptions, while the ERP stays the record. ### Do suppliers need a new portal? No. Suppliers can use email, WhatsApp, EDI, APIs, documents or their existing portal. ### What happens when quantity, price or dates change? Lasya updates the transaction, checks policy and impact, runs permitted recovery steps and escalates only when authority or judgment is needed. ### Where does Procurement end and Logistics begin? Procurement delivers a verified commitment. Logistics takes over the physical movement without resetting context. ### How does it work with SAP, Oracle or Dynamics? The ERP stays the system of record. Lasya carries the work between records and writes approved outcomes back. ### Autonomous Freight & Logistics ### What is Autonomous Freight & Logistics? The autonomous execution of physical movement - from verified supplier commitment through carriers, transport, customs, receipt and delivery - with minimal manual relay. ### How is Lasya different from a TMS? A TMS plans and optimizes transport within one workflow. Lasya runs the transaction across suppliers, partners, customs, exceptions and finance - existing ERP, TMS or specialist systems can stay in place. ### Do carriers need a new portal? No. Partners can keep using email, WhatsApp, APIs, EDI, documents or portals where relevant. ### How are exceptions handled? Lasya assesses impact, evaluates allowed recovery options, executes governed actions and escalates only when policy or authority requires it. ### How does EXIM fit in? Customs, documentation, broker coordination, duty and release events are part of the shipment transaction. ### What goes to Finance? Delivery proof, actual movement milestones, booked vs actual freight context, accessorial evidence, claims and the basis for reconciliation and settlement. ### Autonomous Finance Operations ### What is Autonomous Finance Operations? Turning procurement, shipment, receipt and invoice evidence into reconciled, approved and posted financial outcomes - with minimal manual reconciliation, under governed policy. ### What does autonomous AP mean? Invoices are ingested, matched against execution evidence, resolved, approved and posted by Lasya - people step in for real exceptions and authority decisions. ### Does Lasya replace ERP? No. SAP, Oracle or Dynamics stays the System of Record. Lasya does the work that makes the record complete and writes verified outcomes back. ### How are exceptions handled? Lasya detects the variance, investigates the evidence, then approves valid charges, disputes unsupported ones or escalates when authority requires it. ### How does freight data reach Finance? Freight & Logistics passes delivery proof, actual milestones, booked vs actual rates, accessorials and claims on the same transaction state. ### How are approvals governed? Three tiers: auto-execute within tolerance, request approval beyond delegated authority, and escalate on policy conflicts or missing evidence - every action keeps its audit trail. ### Operational Fragmentation (the problem) ### What is Operational Fragmentation? It is the condition where supply chain work is distributed across disconnected systems and channels, so people have to preserve context and carry each transaction between them by hand. ### Why doesn’t ERP solve it? ERP remains the system of record. The coordination that moves a transaction forward - chasing, relaying, reconciling - happens outside it, across email, spreadsheets, portals and partner systems. ### Isn’t this just an integration problem? No. Integration moves information between systems. Execution also needs persistent state, ownership, next-action logic, exception recovery and outcome verification. ### Why does it get worse across enterprises? Every additional company brings its own systems, policies and handoffs. Each boundary is another place where the transaction’s state can diverge. ### Multi-Enterprise Execution (the framework) ### What is Multi-Enterprise Execution? A framework for carrying one transaction across independent companies, systems and channels until its business outcome is verified. ### Does every partner need the same platform? No. Partners can keep using email, EDI, APIs, portals, documents and messaging. The execution layer keeps one state across all of them. ### Is this just a supply chain network? No. A network moves information between participants. Multi-Enterprise Execution carries the transaction itself - including next actions and exceptions. ### Does it replace ERP? No. ERP remains the System of Record. The execution layer manages the work and state between records and writes verified outcomes back. ### System of Execution (the architecture) ### What is a System of Execution? An architectural layer that carries a transaction from intent to verified outcome across systems, partners and channels - maintaining state, next actions, exceptions and verification. ### Does it replace ERP? No. ERP remains the authoritative System of Record. The System of Execution runs the work between records and writes verified outcomes back. ### How is it different from a control tower? A control tower observes and alerts. A System of Execution carries the work forward to completion. ### Do partners need a single supplier portal? No. Email, WhatsApp, EDI, APIs, portals, PDFs and voice act as I/O into one continuous transaction state. ### Why use AI Supply Chain Operating System as a metaphor? The metaphor explains the breadth of the execution environment. System of Execution is the architectural category underneath it. ### What role does Operational Memory play? It preserves context, decisions, partner behavior, exceptions and outcomes so later execution can reuse proven operational knowledge. ### Autonomous Supply Chain Execution (the outcome) ### What is Autonomous Supply Chain Execution? Transactions that continue across systems and company boundaries with minimal human relay until their business outcome is verified. ### How is it different from workflow automation? Automation runs predefined tasks on the happy path. Autonomous execution maintains transaction state, chooses next actions and handles governed exceptions. ### Does it replace ERP? No. ERP stays the System of Record. The System of Execution writes verified outcomes back to it. ### How is it measured? By Autonomy Rate, exception autonomy, cycle time and manual touches - not by how many AI actions were taken. ### System of Execution vs ERP, TMS, Procurement suites, control towers and AI agents ### Does Lasya AI replace ERP? No. ERP remains the system of record. Lasya AI runs the work between systems and partners and writes verified outcomes back to the ERP. ### Does Lasya AI replace planning suites? No. Planning creates the intent: forecasts, scenarios and the optimized plan. Lasya AI carries that approved intent into coordinated execution. ### Can Lasya AI replace procurement suites? Yes, where its native sourcing and procurement execution covers the scope you need. It also carries the transaction past the PO, through supplier commitment and physical execution. ### Can Lasya AI replace a TMS? For industrial supply chains, yes. Specialized transport environments can keep an existing TMS and interoperate with Lasya AI. ### How is Lasya AI different from a control tower? Control towers focus on visibility and intervention. Lasya AI owns the execution itself, through recovery, verification and evidence. ### How is Lasya AI different from AI agents? Agents perform tasks. Lasya AI keeps the shared transaction state, policy and completion criteria that agents work within. ### Does every supplier or logistics partner need to use Lasya AI? No. Partners take part through the channels they already use, such as email, WhatsApp, EDI, APIs and portals. ### What does Lasya AI consolidate? Depending on scope: sourcing, freight, EXIM, control-tower, exception, invoice, settlement and point AI workflows. ERP and planning remain. ### What is the main advantage of consolidating? Fewer internal handoffs, and execution that continues across company boundaries until a verified outcome is reached. ### Industrial Manufacturing ### Does Lasya AI work with our existing ERP? Yes. Lasya AI reads purchase orders and master data from your ERP and posts confirmed outcomes back. Your ERP stays the system of record. ### Do our suppliers need to log in to a new portal? No. Suppliers can keep replying by email, WhatsApp or spreadsheets. Lasya AI reads those updates and applies them to the right PO. ### Can it handle partial deliveries and split lots? Yes. Each lot is linked to the PO line, so open quantities and balances stay correct without manual tracking. ### How are rate contracts checked? Invoices are matched against the agreed rate, the PO and the goods receipt. Differences are routed to the right buyer with the evidence attached. ### How long does a first rollout take? Most teams start with one plant or one category of material, then expand once the first transactions run end to end. ### Pharma & Chemicals ### Can Lasya AI restrict sourcing to approved vendors? Yes. Sourcing and RFQs can be limited to your approved vendor list, with approvals recorded on each transaction. ### How are certificates and permits handled? Required documents are requested with the PO, collected from email or uploads and attached to the right batch and shipment. ### Does it replace our quality system? No. Quality decisions stay in your QMS. Lasya AI carries the release status into the transaction so invoices and payments follow it. ### Is there an audit trail? Every update, approval and document is time-stamped against the transaction, so you can show who did what and when. ### Is Settyl certified? Settyl is ISO 27001:2022 certified. Talk to us about your validation and data requirements. ### Telecom & Infrastructure ### Can we track materials by project and site? Yes. Every PO, shipment and invoice carries project and site references, so you can see status for each site. ### How is proof of delivery captured from remote sites? Site teams can confirm delivery by message, photo or upload. Lasya AI attaches it to the right shipment and PO. ### Can it work with our ERP and project tools? Yes. Lasya AI reads POs and project data from your ERP and posts confirmed receipts and invoices back. ### What happens when one vendor is late? The delay is flagged against every site that depends on that item, with an owner assigned to resolve it. ### Where should we start? Most teams start with one region or one rollout phase, then expand once the first sites run end to end. ### Logistics & 3PL ### Does Lasya AI replace our TMS? No. Your TMS can stay. Lasya AI coordinates the work around it, across carriers, partners and channels, and keeps one state for every shipment. ### Do carriers need to adopt a new system? No. Carriers can keep using email, WhatsApp, portals or APIs. Lasya AI reads their updates and applies them to the right shipment. ### How are exceptions handled? Each exception gets an owner, a next step and a deadline. Routine cases are resolved automatically and people handle the rest. ### Can it audit freight invoices? Yes. Invoices are checked against agreed rates, weights and proof of delivery. Differences are routed for approval before payment. ### How do we start? Most teams start with one lane or one carrier group, then expand once shipments run end to end. ### Procurement & Sourcing teams ### Do our suppliers need to log in to a new portal? No. Suppliers keep replying by email, WhatsApp, spreadsheets or their own portals. Lasya AI reads the reply and updates the right PO line. ### Will suppliers know they are talking to Lasya AI? Messages go out under your company’s name and tone, using templates your team approves. ### Can we still talk to suppliers ourselves? Yes. Buyers can step in on any conversation. Lasya AI keeps the record and picks up again when you are done. ### What happens when a supplier changes a date? The change is captured, compared with the PO and sent to the buyer and planning with a suggested next step. ### Does it work with our ERP? Yes. Lasya AI reads POs from SAP, Oracle or Dynamics 365 and writes confirmed commitments back. ### Logistics & Supply Chain teams ### Does Lasya AI replace our TMS? Not necessarily. Lasya AI can run freight execution end to end, or work alongside an existing TMS and coordinate the work around it. ### Do carriers need to adopt new software? No. Carriers and drivers keep using calls, WhatsApp, email or their portals. Lasya AI turns their updates into shipment status. ### How are exceptions handled? Each exception gets an owner and a next step. Routine cases are handled automatically, and people take the rest. ### Can we capture proof of delivery from drivers? Yes. Drivers can send a photo or signature by message, and it is attached to the shipment and the PO. ### Does it cover multimodal shipments? Yes. Road, ocean, air and rail legs can be tracked as one shipment with one timeline. ### Finance & Controllers ### Does Lasya AI replace our AP system? No. Your ERP and AP processes remain. Lasya AI gathers the evidence, does the matching and posts clean results back. ### What does Lasya AI match against? The PO, goods receipt, proof of delivery, contract rates and any agreed changes captured during execution. ### Who resolves discrepancies? The person who owns them. Price issues go to the buyer, quantity issues to the receiving team, each with the evidence attached. ### Is there an audit trail? Yes. Every match, change and approval is recorded against the transaction with time and owner. ### Can it handle freight invoices too? Yes. Freight charges are checked against agreed rates, weights and proof of delivery. ### Operations Leaders ### Is Lasya AI a replacement for our ERP? No. ERP stays the system of record. Lasya AI is the execution layer that carries work between teams and companies. ### How do we roll it out without disruption? Start with one flow, such as open POs or one freight lane, then extend as teams see results. ### Who owns exceptions? You decide. Ownership and escalation rules are set by team, site, category or value. ### Can we see performance by team and partner? Yes. Cycle times and exception rates can be viewed by team, site, supplier, carrier and lane. ### How does it help us scale? Routine coordination is handled automatically, so volume can grow without the same growth in coordinators. ### EXIM & Customs teams ### Does Lasya AI file customs declarations? Lasya AI prepares and tracks the documents and milestones. Filing stays with your broker or customs team, with everything they need in one place. ### Can our forwarders and brokers keep their own systems? Yes. They can share documents and updates by email, portal or API, and Lasya AI attaches them to the right shipment. ### How are document mismatches caught? Key fields such as values, quantities and descriptions are compared across documents before submission. ### Does it cover both imports and exports? Yes. Checklists and milestones are set per direction, lane and product. ### Is the record audit-ready? Yes. Every document version and approval is stored against the shipment with time and owner. ### IT & ERP teams ### Do we need to customise our ERP? No. Lasya AI runs outside the ERP core and writes verified outcomes back through standard interfaces. ### Which ERPs do you support? SAP, Oracle and Microsoft Dynamics 365. Talk to us about other systems in your landscape. ### How do partners connect? Through the channels they already use: email, WhatsApp, EDI, APIs or portals. No accounts needed on your side. ### How is data secured? Settyl is ISO 27001:2022 certified. Access is role-based and every change is logged. ### How long does integration take? Most teams start with read access to POs and master data, then add write-back once the first flow is live. ### Industries ### Which industries does Settyl work with? Lasya AI is used wherever goods are bought from suppliers, moved through carriers and paid against evidence. We have dedicated pages for industrial manufacturing, pharma and chemicals, telecom and infrastructure, and logistics, and we work across all the industries listed on this page. ### My industry has no deep dive page. Can you still help? Yes. The transaction model is the same across industries. Talk to us and we will map one of your real transactions from need to settlement. ### Do we need a separate product per industry? No. Procurement, freight and finance execution are the same products everywhere. Documents, partners, approval rules and ERP mappings are configured to your industry. ### Does Lasya AI replace our ERP? No. Your ERP stays the system of record. Lasya AI carries the work between systems, companies and channels, and posts outcomes back to the ERP. ### How do we start? Pick one transaction that causes the most follow-ups today. We map it with your team and show how it runs end to end on Lasya AI. ## Execution insights ### Your ERP Transaction Is Complete. Your Business Transaction Isn’t. Thesis: An ERP record can be complete while the business transaction is still open. Execution isn’t done until the intended outcome is verified. Key takeaway: Measure autonomous execution by verified business outcomes - not by whether every application shows Complete. More: https://settyl.com/insights/erp-complete-business-transaction-incomplete ### Five Internal AI Agents Can Become Five New Operational Silos Thesis: Separate agents for procurement, planning, logistics, EXIM and finance can each succeed locally - while the transaction between them still runs on people. Key takeaway: Without one governed transaction state, more autonomous agents mostly means more disconnected silos. More: https://settyl.com/insights/internal-ai-agents-operational-silos ### The Model Is Not the Moat. Execution Context Is. Thesis: Models are replaceable. Lasting advantage comes from governed context and verified transaction history. Key takeaway: Models will change. Build governed, verified transaction history that compounds over time. More: https://settyl.com/insights/model-is-not-the-moat-execution-context ### Operational Memory Is Earned, Not Imported Thesis: Operational memory grows from governed actions and verified results - it can’t be bulk-imported from documents or inboxes. Key takeaway: Operational memory accumulates from transactions whose outcomes were confirmed - it isn’t a data migration. More: https://settyl.com/insights/operational-memory-is-earned-not-imported ### Cross-Enterprise Execution Without Cross-Enterprise Control Thesis: A transaction can move across partners without any company gaining control over another. Key takeaway: Cross-enterprise execution means owning the transaction’s progress - not controlling the companies involved. More: https://settyl.com/insights/cross-enterprise-execution-without-cross-enterprise-control ### Shared Execution Without Shared Software Thesis: Partners don’t need to share an application. They need one transaction state that survives every channel. Key takeaway: What matters is one persistent transaction record across companies, systems and channels - not one shared app. More: https://settyl.com/insights/shared-execution-without-shared-software ### ERP Isn't Going Away. A System of Execution Is Emerging Thesis: ERP isn’t disappearing. The shift is a new layer for the work between ERP records. Key takeaway: Tomorrow’s platform leaders may be those who run the work that produces verified records - not those who store more records. More: https://settyl.com/insights/erp-needs-a-system-of-execution ### The Exception Is the Real Test of Autonomy Thesis: Autonomy is proven when a transaction keeps moving through disruption - without people becoming the link between steps. Key takeaway: Smooth workflows show software can follow a plan. Exceptions show whether the transaction can recover when the plan breaks. More: https://settyl.com/insights/exception-is-the-real-test-of-autonomy ### PO Created Is Not Procurement Completed Thesis: A purchase order records buyer intent. Procurement isn’t complete until the supplier’s commitment is verified. Key takeaway: A PO shows recorded intent. Real procurement progress is confirmed supplier commitment. More: https://settyl.com/insights/po-created-is-not-procurement-completed ### Autonomy Rate: The KPI That Tests Transaction Autonomy Thesis: Judge autonomy by completed, verified transactions - not by the number of agents or automated steps. Key takeaway: Measure supply-chain AI by how much eligible work finishes verified, with no human relay. More: https://settyl.com/insights/autonomy-rate-supply-chain-kpi ### Supply Chain Transaction Completion Thesis: Judge automation by whether the whole transaction succeeds - not whether each application finishes its step. Key takeaway: A finished task isn’t a finished transaction - only a verified business result is. More: https://settyl.com/insights/supply-chain-transaction-completion ### The Transaction Is the Unit of Autonomy Thesis: Lasting autonomy depends on the transaction - not on any single agent. Key takeaway: Agents are parts of autonomy. The transaction must stay coherent from intent to verified completion. More: https://settyl.com/insights/transaction-is-the-unit-of-autonomy ## Case studies ### AI-Powered Material Sourcing & Invoice Validation A leading industrial manufacturer used Lasya AI to automate the sourcing lifecycle across 20 global plants - improving speed, cost and the team’s strategic focus. Results: −75% sourcing cycle time (12 days → 3); 12% direct cost reduction - over $18M in annual savings; −87% invoice errors (mismatch rate 15% → under 2%); 85% of manager time refocused on strategic work; +20% vendor pool - 50+ new competitive suppliers in year one; 24/7 vendor engagement via autonomous chat and email. More: https://settyl.com/case-study/ai-powered-material-sourcing-invoice-validation ### Chemical Manufacturing Company Reduces Manual Effort & Enhances Efficiency with Lasya AI A mid-sized chemical manufacturer replaced manual data entry, invoice matching and PO follow-up with Lasya AI agents across procure-to-pay. Results: 98% accuracy for template-agnostic OCR invoice digitization; −45% manual administrative effort for PO management. More: https://settyl.com/case-study/chemical-manufacturing-company-reduces-manual-effort-enhances-efficiency-with-lasya-ai ### Lasya AI Agentic Sourcing Transformation How Lasya AI’s autonomous agents take sourcing beyond spreadsheets - running RFx, verification and supplier risk checks continuously. Results: Weeks → days sourcing cycles, down to hours for eligible events; Always-on supplier risk and ESG profiling. More: https://settyl.com/case-study/lasya-ai-agentic-sourcing-transformation