Invoices and receipts
Arabic-English line items, totals, taxes, discounts, and stamps, with the scan quality and layout variation your system encounters.
Bayanat Documents
Arabic documents with the labels your model needs.
Build a dataset for the documents your product reads, from bilingual invoices to handwritten forms. Get text, layout, extracted fields, and evidence for the answers you need.
اقرأ بالعربيةIs Bayanat Documents the right fit?
A good fit if
- Your model reads Arabic or bilingual invoices, receipts, forms or contracts.
- You need more than OCR text: reading order, layout, extracted fields and the evidence behind them.
- You need test splits by issuer, template or writer, so you can measure performance on unfamiliar documents.
Choose something else if
- You want a ready-made document image library. This family is built to order.
- You need OCR software. We build the training and evaluation data, not the OCR tool.
What you can check before you commission
We separate what is confirmed on this page, what we send on request, and what is agreed for each project.
| Item | Status | Details |
|---|---|---|
| Volume | Per project | Built to order. Page count and template coverage are agreed with you. |
| Label types | Per project | Transcription, coordinates, reading order, layout, normalized fields, evidence locations and validation checks; choose what your model needs. |
| Source handling | Confirmed | Genuine, de-identified and synthetic documents remain distinguishable. Template diversity is reported separately from page count. |
| Evaluation splits | Per project | Separate issuers, templates, sources and writers for testing. |
| Example of the label format | On request | Ask for it when you scope your pilot. |
What we can build together
Forms and records
Printed fields, handwriting, checkboxes, corrections, and missing entries in applications, delivery documents, or service reports.
Contracts and procurement
Clauses, tables, attachments, and cross-references, with questions answered from specific supporting passages.
Labels beyond transcription
Choose reading order, layout, normalized fields, evidence locations, and checks for missing information or inconsistent totals.
How the license covers each use
Training rights do not automatically include display, retrieval or redistribution. Each use is set in the agreement.
Source documents
Source permissions are defined with you before collection.
Delivered data
Use and delivery rights are set in the agreement.
How we put the data together
Start with one document type
We define source permissions, layout diversity, capture conditions, and page count around the problem you need to solve.
Keep sources identifiable
Genuine, de-identified, and synthetic documents remain distinguishable. Template diversity is reported separately from page count.
Test unfamiliar documents
Evaluation splits can separate issuers, templates, sources, and writers to check performance on documents the model has not seen.
For example: Checking an invoice total
A bilingual invoice has a discount and a handwritten correction. Labels locate both amounts so the system can extract them, recompute the total, and flag a mismatch.
Scope your request
Tell us these details. We come back with a fixed-scope pilot plan.
- Document types
- Languages and scripts
- Labels you need
- Sources you can authorize
- Volume and timeline
Common questions
Can I order OCR labels without extraction labels?
Yes. You can request transcription, coordinates, and reading order on their own, or add layout, field extraction, document questions, and validation checks. The labels should match the model you are building.
How do you handle repeated invoice or form layouts?
For a custom collection, we agree the template coverage and evaluation splits with you. Variations of one template remain identifiable, so page count does not get mistaken for the number of independent layouts.