DocxIntel home
DocxIntel, a product of BizfyLabs
DocxIntel, a product of BizfyLabs
by
BizfyLabs
  • Capabilities
    • Analyse

      Resolve layout, reading order, tables and handwriting

    • Identify

      Pull entities, fields and clauses with coordinates

    • Classify

      Sort document types and split multi-page packets

    • Map

      Link and reconcile entities across your estate

    • Modify

      Redact, mask and transform documents safely

    • Ask

      Query your documents and get cited answers

    • All six capabilities, one platform→
  • Deployment
  • Accuracy
  • Industries
    • Banking & Financial Services

      Statements, KYC files, and financial filings

    • Insurance

      Claims, policies, and underwriting documents

    • Government & Public Sector

      Records, correspondence, and regulatory filings

    • Healthcare

      Patient records, referrals, and lab reports

    • Legal & Compliance

      Contracts, filings, and case documentation

    • Energy & Utilities

      Engineering documents, contracts, and reports

    • Every regulated industry we serve→
  • Pricing
  • Docs
Book a Demo
Home
DocXIntel

Menu

    • All capabilities
    • Analyse
    • Identify
    • Classify
    • Map
    • Modify
    • Ask
    • All industries
    • Banking & Financial Services
    • Insurance
    • Government & Public Sector
    • Healthcare
    • Legal & Compliance
    • Energy & Utilities
    • Deployment models
    • Reference architectures
    • Sizing & throughput
    • What's in the box
    • Security posture
    • Documentation
    • Accuracy benchmark
    • Pricing
    • Proof of Value
    • Compare
    • About
    • FAQ
    • Contact Us
Industry — Banking

Banking document processing that keeps every page inside the bank.

KYC packs, trade finance presentations, credit files and statements are the documents a bank is least able to send anywhere. DocxIntel installs in your own data centre with the models in the bundle, so onboarding checks and document examination run without a third-party processor in the path.

  • No third-party processor
  • Trade finance examination
  • Arabic-native
  • No per-page charge
Book a technical walkthrough
Review the security architecture
A stamped and signed banking document with fields extracted from beneath the stamp and signature
0
Third-party processors
nothing to add to the register
99%
Field-level accuracy
on the published benchmark set
AR + EN
Native script support
including bilingual tables
Unmetered
Pages examined
fixed annual licence

Accuracy is measured field-by-field against a human-adjudicated ground truth, not character-by-character. The methodology and per-field breakdown are published in full on the accuracy page, and your own threshold is agreed in writing before the Proof of Value begins.

What it processes

The banking documents and workflows that hold up decisions

Onboarding, trade finance and credit all stall in the same place: a human has to read a stack of documents, check them against each other and confirm nothing is missing or expired.

KYC and onboarding packs

Emirates ID, passport and visa pages, trade licences, memoranda of association and address proofs are split out of a single scan and extracted document by document.

  • Page-level pack splitting
  • Identity and licence fields
  • Expiry date validation

Document-checklist completeness

The pack is checked against the checklist for that customer type, and the response names the specific document that is missing, expired or unsigned instead of returning a score.

  • Per-segment checklists
  • Named missing documents
  • Signature and stamp presence

Trade finance examination

Letters of credit, bills of lading, commercial invoices and packing lists are compared field by field, and discrepancies are raised as findings an examiner can act on.

  • LC terms against presentation
  • Goods, quantity and amount matching
  • Date and presentation-period checks

Credit file assembly

Loan applications, salary certificates, bank statements and financial statements are extracted and assembled into a credit file with the source of every figure recorded.

  • Salary and employment fields
  • Statement transaction tables
  • Income and obligation summaries

Bank statement extraction

Transaction tables are reconstructed as addressable grids across page breaks, including statements from other institutions arriving as scans rather than data feeds.

  • Multi-page table continuation
  • Balance and total reconciliation
  • Third-party statement formats

Board resolutions and authority documents

Signatory authority, mandates and board resolutions are read for the names, powers and limits that mandate management depends on, including stamped and wet-ink signed pages.

  • Authorised signatory extraction
  • Limits and mandate terms
  • Stamp-over-text separation
End to end

A trade finance presentation, examined against the letter of credit.

Document examination is where trade finance operations spend their day and where discrepancy disputes are born. Every step below happens inside the bank, on documents that were never transmitted anywhere.

  • The presentation arrives as one scanned bundle: bill of lading, commercial invoice, packing list, certificate of origin, insurance certificate
  • Pages are quality-corrected, classified and split, and stamps over printed totals are separated from the figures beneath them
  • Fields are extracted per document type and normalised — dates, currencies, quantities, incoterms, party names in Arabic and English
  • Each field is compared against the corresponding letter of credit term, and every disagreement becomes a named finding
  • Findings are presented with the page and bounding box on both sides, so the examiner reviews evidence instead of the whole file
  • The examined file and its structured fields are written back into your trade finance system with the audit trail intact

Discrepancy findings are advisory: the examination decision, and the liability for it, remain entirely with your own examiners.

See how cross-document mapping works
A stamped trade finance document with extracted terms compared against a letter of credit
Rollout

How a bank deployment actually starts

One workflow, one segment, measured on the bank's own files before anything is connected to a core system.

  1. 1
    Step 1

    Pick the workflow with the worst backlog

    Usually retail onboarding, corporate KYC refresh or trade finance examination. We ask for the files your team escalates — the poor-quality trade licence scan, the bilingual board resolution, the stamped invoice — because those set the real accuracy expectation.

  2. 2
    Step 2

    Clear it with risk, compliance and information security together

    Because processing stays inside the bank, the review is about internal segmentation, access control and audit logging rather than outsourcing and cross-border transfer. Deployment evidence and data-flow documentation are provided up front for your assessors.

  3. 3
    Step 3

    Install inside your own perimeter

    Containers and open-weight models are deployed on bank hardware in the network zone your policy requires — air-gapped, private cloud or managed single-tenant. Your team holds root, the keys and the change window.

  4. 4
    Step 4

    Configure schemas, checklists and examination rules

    Document types, field lists, checklist logic and letter-of-credit comparison rules are configured against your own procedures, then tuned on historical files where the outcome is already known.

  5. 5
    Step 5

    Measure against the written threshold

    Your own analysts adjudicate field-by-field, and the report shows per-field accuracy, confidence distribution and the exception rate you would staff for. Miss the agreed threshold and you keep the report and owe nothing further.

  6. 6
    Step 6

    Extend across segments and remediate the archive

    Adding corporate onboarding to a retail deployment, or reprocessing years of KYC files for a remediation exercise, is a configuration change and some GPU time rather than a new commercial negotiation.

Reference

Banking document types and the fields extracted from each

An indicative schema. The final field list is agreed against your own forms, checklists and procedures during the Proof of Value.

KYC and onboarding documents

Emirates ID
Full name in Arabic and English, ID number, nationality, date of birth, sex, issue and expiry dates, card number
Passport and visa pages
Passport number, machine-readable zone fields, nationality, date and place of birth, issue and expiry dates, visa type, sponsor, permit number
Trade licence
Licence number, legal name in Arabic and English, licensing authority, legal form, activities, issue and expiry dates, partners and shareholding
Account opening form
Applicant details, customer type, products requested, source of funds, expected turnover, declared tax residency, signatures and dates

Trade finance documents

Letter of credit
LC number, issuing and advising bank, applicant and beneficiary, amount and tolerance, incoterms, latest shipment date, expiry, presentation period, required documents
Bill of lading
B/L number, shipper, consignee and notify party, vessel and voyage, ports of loading and discharge, description of goods, container and seal numbers, freight terms, on-board date
Commercial invoice
Invoice number and date, seller and buyer, description of goods, HS codes, quantity, unit price, currency, total, incoterms, payment terms
Packing list
Package count and marks, gross and net weight, volume, per-carton contents, quantities reconciled against the invoice lines

Credit and authority documents

Salary certificate
Employee name, employer and trade licence, designation, joining date, basic salary, allowances, total monthly income, currency, issuing signatory and stamp
Bank statement
Account holder, account number and IBAN, statement period, opening and closing balances, transaction date, description, debit, credit and running balance per row
Board resolution
Company name, resolution date, resolved actions, authorised signatories, signing limits, quorum, directors present, company stamp
Attached to every field
Page number, bounding-box coordinates, confidence score and a stable element identifier that survives re-runs

Regulatory references on this page are evaluation context, not legal advice. Confirm the obligations that apply to your licence with your own compliance function.

Positioning

Banking document processing: on-premise against metered cloud IDP

Metered cloud IDP platforms are capable products, and several are sold through the same marketplaces your bank already buys from. The constraint is that the document has to reach the vendor to be read.

Banking document processing: on-premise against metered cloud IDP
CriterionMetered cloud IDPVendor BYOC tierDocxIntel
Where customer documents are readVendor cloudYour cloud tenantYour infrastructure, including bare metal
Adds a third-party processor to the registerYesYesNo — licensed software you operate
Residency evidence for a regulatorContractual commitmentYour cloud regionYour own network diagram
Works in an isolated network zoneNot availableRequires connectivitySupported by default
Illustrative cost at 1M pages a monthRoughly $150,000 to $3.6M a yearlist-rate arithmetic at $0.0125 to $0.30 per pageStill metered per pageFixed annual licencesized by deployment footprint
KYC remediation across the back bookCharged again per pageCharged again per pageNo incremental charge
Setup fees on top of subscriptionCharged on some platformsCustom quoteIncluded in the licence
Model weightsVendor-hostedVendor-controlled imagesShipped to you in the bundle

Where customer documents are read

Metered cloud IDP
Vendor cloud
Vendor BYOC tier
Your cloud tenant
DocxIntel
Your infrastructure, including bare metal

Adds a third-party processor to the register

Metered cloud IDP
Yes
Vendor BYOC tier
Yes
DocxIntel
No — licensed software you operate

Residency evidence for a regulator

Metered cloud IDP
Contractual commitment
Vendor BYOC tier
Your cloud region
DocxIntel
Your own network diagram

Works in an isolated network zone

Metered cloud IDP
Not available
Vendor BYOC tier
Requires connectivity
DocxIntel
Supported by default

Illustrative cost at 1M pages a month

Metered cloud IDP
Roughly $150,000 to $3.6M a yearlist-rate arithmetic at $0.0125 to $0.30 per page
Vendor BYOC tier
Still metered per page
DocxIntel
Fixed annual licencesized by deployment footprint

KYC remediation across the back book

Metered cloud IDP
Charged again per page
Vendor BYOC tier
Charged again per page
DocxIntel
No incremental charge

Setup fees on top of subscription

Metered cloud IDP
Charged on some platforms
Vendor BYOC tier
Custom quote
DocxIntel
Included in the licence

Model weights

Metered cloud IDP
Vendor-hosted
Vendor BYOC tier
Vendor-controlled images
DocxIntel
Shipped to you in the bundle

Cost figures are our own arithmetic on publicly published list rates as of 2026 — roughly $0.0125 per page for agentic cloud parsing and around $0.30 per page on a usage-based IDP growth plan — not vendor quotations. Setup-fee and self-hosting behaviour reflects publicly documented plan terms. Verify against current vendor documentation before making a decision.

Compare the options in detail

Questions bank risk and technology teams ask

The objections raised in every bank evaluation, answered without hedging.

DocxIntel is software you install and operate, not a service you send documents to. There is no third-party processor in the path, no cross-border transfer and nothing to add to your outsourcing register beyond a licensed software product. That converts a lengthy outsourcing approval into an internal change-management exercise your own teams already run.

Yes, and it is one of the strongest fits. The letter of credit terms, the bill of lading, the commercial invoice and the packing list are read as structured documents, then compared field by field: consignee, description of goods, quantities, amounts, incoterms, shipment and expiry dates, and presentation period. Discrepancies are raised as named findings with the page and coordinates of both sides, so an examiner reviews evidence rather than re-reading the file.

A KYC pack usually arrives as a single scan containing several identity documents, a trade licence, a visa page and an address proof. DocxIntel classifies page by page, splits the pack into its component documents, extracts the fields from each and checks the pack against your checklist — reporting exactly which document is missing or expired rather than returning a completeness score.

Every extracted value carries its page number, bounding-box coordinates and confidence score, and element identifiers stay stable across re-runs. An examiner or internal auditor can be shown the exact pixels behind a beneficial-ownership field years later, and the audit log records who accessed which document and when — inside your own logging estate, not a vendor portal.

Arabic is a first-class script, including right-to-left reading order, Arabic-Indic numerals, and pages that mix an Arabic trade licence header with English legal terms and Latin-script IBANs. Bilingual tables are resolved per block rather than flattened into one scrambled string, which is where most extraction tools lose the column alignment.

As a fixed annual licence sized by deployment footprint, never per page. At bank volumes the metering model is the whole cost: a million pages a month at published list rates works out somewhere between roughly $150,000 and $3.6 million a year on our own arithmetic. Reprocessing your archive for a remediation exercise adds nothing to a fixed licence.

Keep reading

All industries→The six regulated sectors DocxIntel is built for, and the constraint they share.Insurance→Claim packet auto-split, policy reconciliation and reimbursement processing.Legal→Clause extraction, obligation tracking and privilege-aware redaction.Map→How values are reconciled across a letter of credit, an invoice and a bill of lading.Security architecture→Isolation, audit logging and key handling — the controls your assessors will ask about.Pricing→Why a fixed annual licence beats per-page metering once bank volume is real.

Start with the onboarding packs sitting in your exceptions queue.

Thirty to forty-five days, fixed fee, deployed inside the bank on your own customer files. The accuracy threshold and the conversion price are both agreed in writing before we begin.

Talk to an engineer
How the Proof of Value works
  • No per-page metering
  • Runs in your environment
  • Written accuracy threshold
DocxIntel Logo

A product of BizfyLabs

Document intelligence that never leaves your building. Analyse, identify, classify, map, modify and ask — inside your own infrastructure.

BizfyLabs on LinkedInDocxIntel documentationBizfyLabs

Product

  • Capabilities
    • Analyse
    • Identify
    • Classify
    • Map
    • Modify
    • Ask
  • Accuracy benchmark
  • Pricing
  • Proof of Value

Technical

  • Deployment models
  • Reference architectures
  • Sizing & throughput
  • What's in the box
  • Security posture
  • Model licences
  • Documentation
  • API reference

Solutions

  • All industries
  • Insurance & TPAs
  • Healthcare
  • Banking & finance
  • Government
  • Legal
  • Energy & logistics

Compare

  • Compare approaches
  • LlamaParse alternative
  • Docsumo alternative
  • On-premise document AI

Company

  • About DocxIntel
  • FAQ
  • Partners
  • BizfyLabs
  • Careers
  • Contact

© 2026 BizfyLabs FZC LLC. All rights reserved.

DocxIntel™ is a product of BizfyLabs FZC LLC.

  • Privacy Policy·
  • Terms of Service·
  • Data Processing Addendum·
  • Acceptable Use·
  • Model Licences·
  • Security·
  • Cookies

Registered in the United Arab Emirates. Delivery partner: Bizfy Solutions LLP, Indore, India.

DocxIntel