What EDI is and who it is for
Electronic Data Interchange — EDI — is the established standard for computer-to-computer exchange of business documents. When a large retailer receives a purchase order from a major supplier, that transaction is almost certainly handled by EDI. The data flows directly from one system to another with no human touching it.
EDI works well in the right context. Large trading volumes, standardised document types, established supplier relationships, and IT teams capable of maintaining the integration. A major supermarket processing ten thousand supplier transactions a day needs something like EDI. The economics and the infrastructure make sense.
Why EDI is not the answer for most businesses
Most businesses are not large supermarkets. They have twenty suppliers, not two thousand. Their suppliers include a local manufacturer, a sole trader who emails handwritten PDFs, and a mid-sized distributor with their own idiosyncratic invoicing software. None of these suppliers are going to implement EDI.
EDI implementations typically cost between £10,000 and £100,000 to set up, require ongoing maintenance, need both parties to agree on a message standard, and require IT involvement to manage. For the vast majority of SMEs, EDI is not a realistic option — not because they could not benefit from it, but because the cost and complexity are entirely out of proportion to the problem.
The gap EDI leaves
The gap is this: EDI handles structured electronic exchange between large organisations. Manual keying handles everything else. There is very little in between.
The "everything else" category is enormous. Most supplier-to-buyer document exchange — across most businesses, across most industries — still happens via PDF email attachments processed by humans. The volume is massive, the inefficiency is significant, and the market has largely accepted it as unavoidable.
Harold's position in that gap
Harold sits in that gap. Not as a replacement for EDI — if you genuinely need EDI, Harold is not EDI. But as a practical alternative for the 95% of business document workflows where EDI is not happening and is not going to happen.
The model is: supplier sends a document in whatever format they already use (PDF, scanned image, emailed invoice). Harold receives it, understands it, and produces structured data. No supplier change required. No integration project. No IT team needed.
This is what makes Harold fundamentally different from both EDI and from generic OCR tools. EDI requires both sides to change. Generic OCR extracts text without understanding structure. Harold understands documents the way a person does — it knows what an invoice number is, what a line item is, what a payment term is — and it learns your suppliers' specific layouts so that over time the accuracy improves without anyone doing extra work.
What Harold does not do that EDI does
EDI provides guaranteed delivery, automated acknowledgement, and compliance audit trails. Harold does not provide these. Harold is a document extraction and processing tool, not an electronic trading platform.
If you have compliance requirements around document interchange (regulatory, contractual, or audit-related), you need to evaluate whether Harold meets those requirements specifically. For most SME finance and operations workflows, the requirements are simpler: get the right data out of the document accurately, and do it without manual effort.
The practical argument
The practical argument for Harold as an EDI alternative is not that it is better than EDI. It is that it is vastly better than doing nothing — which is the realistic alternative for most businesses.
A business implementing Harold takes one afternoon to train their first document type. After that, documents are processed automatically. The data is clean, structured, and ready to go wherever it needs to go — into a spreadsheet, via Zapier into their ERP, into a CSV import file.
Compared to the status quo of manual entry: faster, more accurate, and far cheaper. Compared to EDI: simpler, quicker to deploy, and practical for the supplier relationships that most businesses actually have.
That is the position. Not a technology statement. A practical one.