AI reads documents, extracts the information you need, categorizes and checks it. Staff do less data entry, know exactly what needs verifying, and data goes straight into the process you already use.
Already in the SAL software Discuss your needs Xem demoThe service below is for reading paper invoices, forms and specialised documents into the software; SAL - AI sets it up inside your own software.
Invoices, forms, emails and reports come from many sources in different layouts. Staff have to find information, re-enter it and check it before moving on. We help businesses organize these steps into a trackable process.
Data is copied from documents into spreadsheets or software.
Each source uses different naming, structure and layout.
Missing, conflicting or duplicate information slows down the next step.
Receives documents from supported sources and groups them by record type or business rules.
Reads the required fields from PDFs, scans, forms and documents within the tested scope.
Converts dates, field names and values into a consistent format following your business rules.
Detects missing fields, invalid values or data that needs verifying before use.
Compares data in documents against your reference sources, using agreed criteria.
Sends unusual cases to the responsible person. Results are only exported or updated in the system after being checked.
Document types, data fields and integrations are confirmed through assessment and testing on real samples.
Illustrative scenario: processing incoming invoices.
Original document
Extraction result
Field 4 (Total): 12,540,000 VND differs from the sum of line items, 12,450,000 VND. The system flags it and points to the location in the original document so staff can confirm or correct it.
The system captures the invoice number, date, seller details and amounts according to the agreed fields.
Flags missing fields or discrepancies that need verifying, with their location in the original document.
Staff check the flagged fields before exporting or updating the software.
Extract data, check required fields and prepare for system entry.
Capture item codes, quantities and dates and cross-check them with reference sources.
Categorize, check for missing information and forward to the responsible person.
Compile information into an output template, noting sources and items to check.
Each project starts with a specific group of documents. For contracts or specialist documents, AI assists with extraction; the responsible person still confirms the conclusions.
Review sample documents, fields to capture, validation rules and the system receiving the data.
Output: Scope, evaluation sample set and acceptance criteria.
Set up extraction, standardization, checking and review routing; evaluate on representative samples.
Output: Pilot process and results for each document type.
Controlled rollout, error monitoring and adjustment when formats or business rules change.
Output: An operating process with the agreed support scope.
We measure the time spent correcting errors too, not just how fast the AI reads documents.
The business processes repetitive documents, knows exactly which fields to capture and has someone to confirm results. The value of deployment depends on volume, complexity and current handling effort. Blurry, handwritten or highly variable documents need testing before the scope is confirmed.
Every extracted value links back to its location in the original document so staff can check it. Who has access, where data is stored, for how long and which provider's technology is used are clarified before deployment.
It can be deployed with supported formats. Image quality, language and layout affect results; the scope is confirmed through testing.
No. Accuracy varies by document type and by field, so the system is evaluated separately for each group and important information always goes through a checking step.
It depends on whether the software supports integration (API) and the access you can grant. If a direct connection isn't possible, data can be exported to a file for import into the software.
New formats need to be evaluated and the process may need adjusting. The update scope is agreed in the support package.
Representative sample documents, a list of fields to capture, validation rules, an output template and a person responsible for business requirements.
The quote separates deployment, integration, usage and maintenance. Document types, page count and processing volume are the factors to assess.
Tell us the document types, processing volume and the data you need to receive. We'll work with you to define a suitable pilot scope.
Thank you. We will get back to you to discuss a suitable scope.