استخراج بيانات المستندات

المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.

1. document_intake_channel

   مطلوبقراءةحدث

   Where documents arrive for processing. Most clients have several channels feeding the same workflow.

   شكل البيانات

   Document files in common formats (PDF, image, sometimes Word or HTML email) with arrival metadata: source, timestamp, sender if known.
   يُملأ عادةً بواسطة

   • email inbox where suppliers send invoices
   • shared drive folder where scanned documents land
   • upload portal for customers or partners
   • vendor portal that pushes documents via API
   • OCR feed from a multi-function printer
2. extraction_schema_definitions

   مطلوبقراءةمجموعة

   What fields to extract per document type. Different document types have different schemas; the pattern needs explicit definitions, not guessing.

   شكل البيانات

   Per-document-type field definitions: name, type, required-or-optional, validation rules, example values.
   يُملأ عادةً بواسطة

   • configuration maintained per document type by the engagement team
   • small admin UI for the operations team to manage schemas
   • templates derived from sample documents during build phase
3. reference_data_for_validation

   مطلوبقراءةطلب

   Known-good data the extracted values get checked against: supplier list, product catalog, customer roster, GL codes.

   شكل البيانات

   Reference tables with the canonical entities and their identifiers. Lets the pattern check that 'Acme Corp' on an invoice matches the supplier record and isn't a new supplier.
   يُملأ عادةً بواسطة

   • supplier master in the ERP or accounting system
   • product catalog with SKUs
   • customer database keyed by name and tax ID
   • chart of accounts
4. structured_output_destination

   مطلوبكتابةحدث

   Where the extracted, validated records land. Usually the system of record the documents would have been keyed into by hand.

   شكل البيانات

   Structured records matching the destination system's schema, with a reference back to the source document.
   يُملأ عادةً بواسطة

   • bill or invoice created in the accounting system
   • purchase order record in the ERP
   • claim record in the operations platform
   • structured entry in the workflow management tool
5. human_review_queue

   مطلوبقراءة + كتابةطلب

   Where low-confidence extractions go for human verification. Reviewer sees the source document and the proposed values side by side, with the uncertain fields highlighted.

   شكل البيانات

   Document + extracted fields + per-field confidence + reviewer actions (confirm, edit, reject).
   يُملأ عادةً بواسطة

   • review UI built for the engagement showing document and fields side by side
   • queue inside the accounting or ERP system
   • dedicated app for the operations reviewers
6. exception_workflow

   مطلوبكتابةحدث

   Where documents that fundamentally can't be processed go: unknown supplier, malformed document, suspected duplicate, suspected fraud.

   شكل البيانات

   Document with exception classification, evidence, and routing suggestion.
   يُملأ عادةً بواسطة

   • exception queue in the accounting system
   • ticket created for finance operations
   • dedicated investigation folder with notifications
7. source_document_archive

   موصى بهكتابةمجموعة

   Long-term storage of original documents, linked from the structured records for audit and reference.

   شكل البيانات

   Original files preserved with metadata: extraction date, links to created records, retention schedule.
   إذا مفقود

   Compliance and audit trail are weaker; in regulated industries this is effectively required. Strongly recommend in any client with audit obligations.
   يُملأ عادةً بواسطة

   • document management system with retention policies
   • archived folder in the file store with structured naming
   • attachment field on the destination record