Remote validation: document data checked against your master data
A PDF order carries the customer's company name, not the code you use in your ERP. A supplier invoice carries the VAT number, not the supplier code. With remote validation Data Alchemy connects a third-party source — typically your ERP — to verify the data read by the AI and retrieve the codes from your master data.
Availability: included in the Business and Enterprise licences. Not available on the Basic licence, and therefore not in the Demo either, which is its free trial.
What remote validation is
Remote validation is the checking of extracted data against a third-party source of the customer, such as the ERP. It does two things: it checks that a value read on the document really exists in your master data (for example an item code), and it derives a value that is not on the document (for example the customer or supplier code) from one that is, such as the company name or VAT number.
Unlike external fields, which compare the document with the external data the document itself refers to (the purchase order quoted on a delivery note), remote validation works on single values: it checks or resolves a field against master data. The two features are included in the same licences and are often used together.
How remote validation works while a document is read
Remote validation is configured in the document model: for the fields you specify, while reading, Data Alchemy queries the connected source and uses the result — the code it finds — or flags the field when the check does not succeed.
- 01AI readingThe model's AI engine reads the document and extracts the fields: company name, VAT number, item codes.
- 02Master data lookupFor the configured fields Data Alchemy queries the connected source, for example the ERP through the AI agent or via API.
- 03Code checked or retrievedThe item code is confirmed in master data; the customer or supplier code is retrieved from the company name or VAT number.
- 04Ready or flaggedThe document moves on with your ERP's codes; if the check finds no match, the field is flagged.
1. You configure the fields to validate
In the document model you specify the fields to check against the connected source: the item code on the lines, the company name or VAT number from which to derive the customer or supplier code.
2. You connect the third-party source
The source is usually the customer's ERP: the lookup goes through the AI agent, installed at your premises, which reads from a database, CSV, JSON or TXT files, or APIs with your ERP credentials kept in your perimeter, or via APIs your system exposes.
3. Data Alchemy queries the source while reading
On every document read, for the configured fields, the platform queries the master data: it looks up the item code and the customer or supplier matching the company name or VAT number.
4. It uses the result or flags it
The code found is used in the extracted data, so the record is already linked to the right master-data entry; if there is no match the field is flagged for review instead of entering your ERP wrongly.
Remote validation works on the fields of the document model; the connection with your ERP is described under ERP integration and on the AI agent page.
What it looks like in the platform
A remote validation field in a demo goods receipt model: the supplier code.
Real-world remote validation use cases
These are the cases where the document does not speak your ERP's language: the data is there, but not in the form needed to post it.
PDF customer order with only the company name
The order arrives with the customer's company name but without your customer code: Data Alchemy queries the ERP and retrieves the matching code, so the order enters already linked to the right master-data entry.
Supplier invoice: supplier code from the VAT number
From the VAT number read on the invoice, remote validation retrieves the supplier code from master data: posting no longer means looking it up by hand.
Delivery notes and orders: item codes checked in master data
On delivery note and order lines, remote validation checks that item codes exist in the ERP master data; a non-existent code is flagged before it reaches the ERP.
Fewer exceptions downstream
With your ERP codes already resolved, the following steps — posting, three-way matching, sending to the ERP or CRM — work on data consistent with master data.
Agribologna: customer codes checked against the AS400
At Agribologna, remote validation is connected to the AS400 ERP and checks customer codes starting from the company name read on the document. The document lines, mainly the item codes, are handled by external fields. Read the Agribologna case study.
Which licences include remote validation
Remote validation is included from the Business licence upwards, together with external fields and the Mail service.
Included
Included, with everything in the Business licence, the native Salesforce integration, Order Dispatcher and the AI agent.
Included
Included together with external fields and the Mail service; the AI agent is available as a separately quoted add-on.
Not available
The Basic licence covers document reading with 1 model and pay-as-you-go credits, with no checks against external master data.
Not included
The Demo is the trial Basic licence: 10 days, 10 documents, 1 predefined model. To see remote validation on your ERP, plan a call.
Compare the licences on the pricing and licences page or request a quote.
Related features and pages
- External fieldsThe document compared with the external data it refers to, such as the purchase order quoted on a delivery note.
- AI agentThe component installed at your premises that makes ERP data available for lookup and posts extracted data into the ERP or CRM.
- Sales order automationCustomer orders read by the AI and linked to the right master-data entry.
- Accounts payable automationSupplier invoices from receipt to posting.
Remote validation: frequently asked questions
What is Data Alchemy remote validation?
It is the checking of AI-read data against a third-party source of the customer, such as the ERP: Data Alchemy checks that item codes exist in master data and retrieves the customer or supplier code from the company name or VAT number. It is included in the Business and Enterprise licences.
How does Data Alchemy retrieve the customer code from a PDF order?
If the order only carries the company name, for the field configured in the model Data Alchemy queries the ERP while reading and retrieves the matching customer code. The order moves on already linked to the right master-data entry; if there is no match, the field is flagged.
What is the difference between remote validation and external fields?
Remote validation checks or resolves single values against master data (an item code, a customer or supplier code). External fields compare the document with the external data it refers to, such as the purchase order quoted on a delivery note, checked line by line. Both are included in the same licences.
How does remote validation connect to my ERP?
When the source is your ERP, the lookup goes through the AI agent or via API. The AI agent is installed at your premises, connects to Data Alchemy over websocket and APIs and reads master data from a database, CSV, JSON or TXT files, or APIs, with your ERP credentials kept in your perimeter. Alternatively, Data Alchemy queries the APIs your system exposes directly. The AI agent is included in Enterprise and available as a separately quoted add-on on Business.
Is remote validation available in the Demo?
No. The Demo is the trial Basic licence and lets you try document reading with 1 predefined model. Remote validation is included in the Business and Enterprise licences: to see it on your ERP, plan a call with a demo on your own documents.
Bring your ERP codes into the extracted data
Activate the free Demo to try AI reading on your documents, or plan a call to see remote validation connected to your master data.