M15

File & Data Extraction

Allows platforms to receive PDF files and extract key bits of data to populate either an assessment or any number of server-side use cases. Users can upload PDF files, and the system can attempt to extract data and map it against your own custom data model or predefined requirements.

See it in action

The File & Data Extraction module, on screen.

The following visual animation videos demonstrate possible use cases of the File and Data Extraction module. These are only imaginary examples of receipt uploads. Actual user implementations would vary widely.

Single file data extraction
Batch file data extraction

Admin Template Setup

Admins define extraction templates before any user uploads occur. A PDF sample is uploaded and parsed to surface candidate field labels. The admin confirms which labels to keep, saves them to the database, and optionally maps each field to an assessment question or other server-side entity. The activated template is then available for live document processing.

Admin Template Setup Flow

End-to-end document ingestion pipeline: users upload PDF files, the system extracts structured data from document content, and the extracted fields are mapped against a configurable data model or predefined requirement set. Extracted data can flow directly into assessment population, workflow triggers, or any server-side use case. Batch job support handles multi-file processing at scale.

Capabilities

  • PDF file upload and ingestion to blob storage
  • Automated data extraction from document content
  • Custom data model mapping and field resolution
  • Predefined requirement matching and validation
  • Assessment population from extracted fields
  • Batch extraction job management and status tracking
  • Extraction result storage, retrieval, and review

Benefits

  • Eliminates manual data entry from PDF documents
  • Feeds assessment and workflow engines automatically
  • Scales to batch processing without custom infrastructure

Flow of work

  1. 01Upload PDF file
  2. 02Trigger extraction job
  3. 03Parse and extract document content
  4. 04Map fields to data model or requirements
  5. 05Validate mapped data
  6. 06Populate assessment or target system
  7. 07Review and store results

Subfeatures

  • PDF upload
  • Extraction job trigger
  • Content parsing
  • Field mapping
  • Requirement matching
  • Assessment population
  • Batch job management
  • Result retrieval
  • Extraction review
Source surfaces (technical reference)

Internal code areas in the licensed Full-Stack codebase that back this module.

  • ApiFileExtraction
  • Background extraction job workers
In the stack

Where it lives. What it exposes.

A quick visual of how File & Data Extraction participates across the CleenUI stack, alongside the named operations it adds to the API surface.

M15 · architecture
Frontend
React · TailwindCSS · 60+ components
File upload UIExtraction status viewerField mapping editorBatch job dashboardResult review panel
API
C# Web API · production-ready · role-aware
File upload endpointExtraction triggerStatus pollingResult retrievalMapping config
Database
AzureSQL · 300+ tables · 700+ procedures
ExtractionJobsExtractionResultsFieldMappingsExtractedDocuments
Async Services and Batch Jobs
WebJobs & Functions · queue-backed
PDF extractorField mapperBatch job workerBlob storage client
All four layers ship together as the Full-Stack license. M15 blocks are highlighted.
API operations

Named operations on this surface

9
Try these in Postman
  • POSTPDF upload/file-extraction/pdf-upload
  • POSTExtraction job trigger/file-extraction/job-trigger
  • POSTContent parsing/file-extraction/content-parsing
  • POSTField mapping/file-extraction/field-mapping
  • POSTRequirement matching/file-extraction/requirement-matching
  • POSTAssessment population/file-extraction/assessment-population
  • POSTBatch job management/file-extraction/batch-job-management
  • POSTResult retrieval/file-extraction/result-retrieval
  • POSTExtraction review/file-extraction/review

Each operation maps to an endpoint in the licensed C# Web API surface.