The 18-Minute Contract Review That Eats a Finance Team’s Week
A 15-person fintech in the UAE processes 300 to 500 contracts per month. Each contract requires a finance analyst to open the document, locate the payment terms, extract the amounts, and enter them into SAP. The average cycle time is 18 minutes per contract, with a 7% error rate on data entry. The analyst spends 40% of their week on this task, which means they are not doing the reconciliation, forecasting, or vendor management that actually requires judgment. The pain is not that the work is hard; it is that it is repetitive, error-prone, and it consumes the time of the person who should be doing higher-value work. The metric that matters is not the cost of the analyst’s salary; it is the opportunity cost of the 40% of their week that is spent on data entry.
Why Hiring More Analysts and Buying RPA Both Fail
The first approach is to hire more analysts. This works until the volume grows, and then the problem scales with the headcount. The second approach is to use a commercial RPA tool to automate the data entry. RPA works for structured data in fixed formats, but contracts are semi-structured. The payment terms might be in a table, a paragraph, or a footnote. The RPA bot breaks when the format changes, and the maintenance cost of keeping the bot working across 500 different contract templates is higher than the cost of the analyst. The third approach is to use a commercial AI API to extract the data. This works, but the contract data leaves the building. For a fintech in the UAE, where the data includes payment terms, vendor names, and amounts, sending that data to a third-party API is a risk that the compliance team will flag. The problem is not that the technology is unavailable; it is that the available options do not fit the constraints of a small team with sensitive data and no dedicated compliance function.
On-Premise RAG With a Human Approval Gate
The approach that fits is a retrieval-augmented knowledge assistant built on open-weight models running on the company’s own hardware. The system ingests the contract, retrieves the relevant clauses, and extracts the payment terms, amounts, and dates. The output is a structured form that the finance analyst reviews and approves before it enters SAP. The model is model-agnostic: the pilot uses an open-weight model on-premise because the data cannot leave the building, but the architecture allows switching to a commercial API for workflows where the data is less sensitive. The integration is through the SAP API, not a replacement of SAP. The human-in-the-loop step is not a limitation; it is the design. The analyst sees the AI’s output, can edit it, and clicks approve. The system logs every approval and rejection, which creates an audit trail. The pilot is fixed-scope: one workflow, one integration, one measured baseline, 8 weeks.
Eight Weeks From Audit to Measured Baseline
Week 1: run the process audit. Map the contract review workflow step by step. Measure the current cycle time and error rate. Identify where the data enters and leaves the system. Check whether SAP has an API that can be used for integration. The output is a one-page recommendation with a projected ROI calculation. Week 2: select the model. For a fintech in the UAE where the data is sensitive, an open-weight model on the company’s own hardware is the right choice. The model should be capable of extracting structured data from semi-structured text. Week 3 to 4: build the RAG pipeline. Ingest the contract, retrieve the relevant clauses, extract the data, and populate the form. Week 5 to 6: build the approval interface. The analyst sees the AI’s output, can edit it, and clicks approve. The system logs every action. Week 7: integrate with SAP. The approved data enters the ERP through the API. Week 8: measure the baseline. Compare the cycle time and error rate against the pre-pilot numbers. The deliverable is a working system with documented metrics, not a proof of concept.
Leave a Reply