UAE E-Commerce Firm Cuts Invoice Cycle Time 60% with On-Premise AI Pilot

Background: A 30-Person E-Commerce Firm in Dubai

This case study is a composite based on patterns observed in the field. We do not fake named customers. The details are drawn from multiple engagements with e-commerce and retail firms in the UAE and Gulf region, and the metrics are realistic ranges, not made-up precision.

The company in question is a 30-person e-commerce firm based in Dubai, operating in the UAE and serving customers in the Gulf region. The firm sells consumer electronics and home goods through its own website and marketplaces like Amazon.ae and Noon. The company is in a growth stage, with revenue of approximately USD 12 million annually and a team of 30 employees. The tech stack includes a custom e-commerce platform, SAP Business One as the ERP, and a mix of manual and semi-automated back-office processes. The company has no AI in production yet, and the operations team is stretched thin, handling invoice processing, order fulfillment, and customer support with a small team of five back-office staff.

Challenge: Scaling Operations Without New Hires

The company’s primary challenge was scaling operations without adding new hires. The back-office team of five was handling 1,200 invoices per month, with a cycle time of 48 hours from receipt to entry in SAP Business One. The error rate was 8%, with most errors stemming from manual data entry and misclassification of vendor invoices. The company was also facing a compliance pressure: as a merchant, it was subject to PCI DSS, and the manual handling of invoice data (which sometimes included cardholder data) was a risk. The operations director had a hard deadline: the company was planning to expand into Saudi Arabia and Kuwait in Q3, and the back-office team needed to be able to handle a 40% increase in invoice volume without adding headcount. The challenge was to automate the invoice processing workflow, reduce the cycle time, and ensure PCI DSS compliance, all within a 3-month timeline.

Approach: Fixed-Scope Pilot with On-Premise Open-Weight Models

The company engaged Forfis, a product studio with eight years of delivery experience, to run an AI process audit and a fixed-scope pilot. The audit identified invoice processing as the highest-impact workflow, with a clear success metric: reduce the cycle time from 48 hours to 12 hours and cut the error rate from 8% to 2%. The pilot was scoped to cover the invoice processing workflow, with a 3-month timeline. The architecture was model-agnostic: the company used an open-weight model (Llama 3) on-premise for processing sensitive data, and a commercial API (OpenAI) for high-accuracy multilingual processing. The system was integrated with SAP Business One through its API, and the human-in-the-loop workflow was designed so that low-risk invoices were auto-approved, while high-risk invoices were routed to a human for review. The pilot included a multilingual accuracy benchmark to validate the routing strategy for Arabic, Hindi, and Mandarin invoices.

Outcome: 60% Cycle Time Reduction and 75% Error Rate Cut

The pilot achieved a 60% reduction in cycle time, from 48 hours to 19 hours, and a 75% reduction in error rate, from 8% to 2%. The system processed 1,200 invoices per month with a straight-through processing rate of 82%, meaning that 82% of invoices were auto-approved without human intervention. The remaining 18% were routed to a human for review, which took an average of 4 minutes per invoice. The system was able to handle multilingual invoices (Arabic, Hindi, Mandarin) with an accuracy of 91%, which was sufficient for the company’s needs. The on-premise deployment ensured that no data left the company’s infrastructure, which simplified the PCI DSS scope. The company’s QSA reviewed the AI system’s data flow during the annual PCI DSS assessment and confirmed that the system met the requirements. The operations team was able to handle a 40% increase in invoice volume without adding headcount, and the company was able to proceed with its expansion into Saudi Arabia and Kuwait.

Lessons: What Similar Teams Should Take Away

• Start with a process audit, not a model. The audit identified the highest-impact workflow and the data flow, which was critical for the integration phase. Teams that skip the audit and jump straight to model selection often end up with a system that does not fit their existing workflows.
• Use a model-agnostic architecture. The company used an open-weight model for sensitive data and a commercial API for high-accuracy multilingual processing. This routing strategy was critical for meeting both the compliance and accuracy requirements. Teams that force a single model to handle all cases often end up with a system that is either too slow or too inaccurate.
• Design the human-in-the-loop workflow to minimize manual approvals. The system classified invoices by risk, and only high-risk invoices were routed to a human. This reduced the number of manual approvals by 82%, which was critical for scaling operations without adding headcount.
• Include a multilingual accuracy benchmark in the pilot. The company’s customers were in the Gulf region, and the invoices were in multiple languages. The benchmark validated the routing strategy and ensured that the system could handle the multilingual workload.
• Ensure the on-premise deployment is included in the PCI DSS scope. The company’s QSA reviewed the AI system’s data flow, access controls, and logging during the annual PCI DSS assessment. This ensured that the system met the compliance requirements and simplified the PCI DSS scope.