1
00:00:01,000 --> 00:00:03,393
Supplier certificates arrive as documents,

2
00:00:04,000 --> 00:00:06,927
but receiving teams need clear inspection data.

3
00:00:07,533 --> 00:00:09,580
Foxit IDP turns those certificates

4
00:00:09,600 --> 00:00:12,638
into structured information for faster review.

5
00:00:13,289 --> 00:00:15,913
In this example, we use a certificate of analysis

6
00:00:15,933 --> 00:00:17,749
for a batch of silica filler.

7
00:00:18,422 --> 00:00:20,682
The extraction schema defines the certificate,

8
00:00:21,289 --> 00:00:25,616
supplier, material, batch, issue date, and test results.

9
00:00:26,333 --> 00:00:27,624
You define the fields you need

10
00:00:27,644 --> 00:00:29,860
without marking their position on the page.

11
00:00:30,533 --> 00:00:32,824
A simple workflow connects document intake,

12
00:00:32,844 --> 00:00:35,082
data extraction, and completion.

13
00:00:35,911 --> 00:00:37,216
We upload the sample certificate

14
00:00:37,444 --> 00:00:40,238
and open the results beside the original document.

15
00:00:40,911 --> 00:00:43,860
The certificate and batch details are filled in automatically.

16
00:00:44,667 --> 00:00:48,047
The tests include lead, moisture, and bulk density

17
00:00:48,067 --> 00:00:49,882
with their values and units.

18
00:00:50,400 --> 00:00:53,371
Notice that the lead result preserves the less-than sign,

19
00:00:53,756 --> 00:00:55,149
an important part of the measurement.

20
00:00:55,778 --> 00:00:58,304
Now consider a certificate with a missing test.

21
00:00:58,956 --> 00:01:00,402
Reviewing the extracted list

22
00:01:00,422 --> 00:01:02,069
against the receiving requirements

23
00:01:02,089 --> 00:01:04,616
helps the team see what needs follow up.

24
00:01:04,844 --> 00:01:08,882
With Foxit IDP, teams spend less time retyping certificates

25
00:01:09,178 --> 00:01:11,971
and more time reviewing the information that matters.