C · Intake, extraction, and mapping
Validate, correct, and approve fields
After extraction, deterministic validators recheck dates, numbers, currencies, codes, required values, and allowed ranges. The same input yields the same validation result independently of any LLM explanation.
- Version
- 1.5.1
- Editions
- Standard · Pro
- Last verified build
1.5.1-private-commercial-r12
If the app is not installed, the link falls back to the safe download guide. It carries no file path, question, account, token, or evidence text.
WHEN TO USE IT
When this task is useful
After extraction, deterministic validators recheck dates, numbers, currencies, codes, required values, and allowed ranges. The same input yields the same validation result independently of any LLM explanation.
PREPARE
Check these items before you start
Define format, minimum/maximum, allowed units, and required status in the field schema.
STEP BY STEP
Complete these steps in order
Define format, minimum/maximum, allowed units, and required status in the field schema.
Run validation on extracted results and compare failed rules with source values.
Before saving a correction, confirm that source, user edit, and validation result are all visible.
Pass, fail, and review-needed states appear per field; failed values are not committed.
FOR EXAMPLE
Installed synthetic procurement-audit Demo
These files and values are automatically verified against the synthetic Demo shipped with Orbivell; they are not personal or company data.
- Files
- Approval_Log.csv, Purchase_Orders.xlsx, Invoices.pdf, Delivery_Confirmations.pdf
- Question
- Link the approval, invoice, and delivery evidence for PO-2026-014.
- Orbivell result
- Orbivell links PO-2026-014, INV-2026-032, and DC-2026-014 and shows the CSV row, Excel cell, and PDF page locations.
- User action
- Review extracted fields, correct only misread values, and approve them.
- Final result
- Only approved links are included in the audit draft and manifest.
CHECK THE RESULT
How to know the task is complete
- Before saving a correction, confirm that source, user edit, and validation result are all visible.
- Pass, fail, and review-needed states appear per field; failed values are not committed.
EVIDENCE STATE AND NEXT ACTION
Read the state, then make the decision
Even a source-confirmed item should be adopted only after opening its source location. Partial, conflicting, missing, and review-needed items are never silently finalized; choose the appropriate next action: open the source, correct a value, add a source, or exclude the item.
LOCAL/EXTERNAL AI AND COST
Review transfer and cost before execution
Local only
Indexing, keyword search, opening sources, and reviewing existing results can run without external requests or external-processing credits.
When external processing is selected
Orbivell shows the external-processing service, excerpt scope, estimated credits, and maximum, and sends only after one-time approval. Actual usage is reconciled with a tamper-evident usage history.
LIMITS AND ERRORS
What Orbivell does not silently finalize
Validators do not replace domain judgment when no business rule has been defined.
Error or state code: FIELD_VALIDATION_FAILED
If the state repeats, follow the next action shown in Status. Do not alter the source or delete failure records; request support with a redacted diagnostics bundle.