Document intake for finance, procurement and legal teams

Incoming documents become trusted data - inside your perimeter.

Exceptions go to a human. Every value clicks through to the source page.

See how it works
Your perimeter01Document in02Fields by schema03Matched tocontract or order04To your systems04Exception cardfor a personCloud model, by policyYour perimeter01Document in02Fields by schema03Matched to contract or order04To your systems04Exception cardfor a personCloud model, by policy

Web Summit, Lisbon, 9-12 November 2026

The WislaSearch team is there all four days. Tell us when you are free and we will find a slot.

Book a meeting

How it works

We process the flow. Search is a side effect.

Every day your counterparties send invoices, delivery notes, acts, contracts and certificates. We classify each document, extract the fields your schema needs, resolve the parties, match the document to its order or contract, and pass it straight through to your systems. Anything that does not match becomes an exception card for a person.

  1. Classify
  2. Extract by schema
  3. Match
  4. Pass or hand over

Document types

  • Contracts and annexes
  • Cross-border invoices linked to a contract
  • Delivery notes and CMR
  • Acceptance acts
  • Price lists
  • Certificates
  • Contractor packs
  • Customs documents

Perimeter

Inside your perimeter, with a policy for models

Local models run in your contour. Cloud models are used by policy: who may send which data to which model, with quotas per department and a filter before anything leaves. The whole route stays inside: parsing, the exception queue and the trace back to the source.

  • Local models by default

  • Cloud by policy, with quotas

  • Filter before anything leaves

Traceability

Every value clicks through to the source page

We record the source and the exact position of each fragment at intake and carry it through the whole route. A reviewer sees where a number came from before approving it. This is what makes the exception queue work.

Extracted fieldsException queueDocumentService contractCounterpartyExample Trading LtdContract numberC-118Effective date14 Aug 2026Payment term30 daysContract value12,400.00ReviewSource pagePage 3 of 6Service contract3Contract value 12,400.00Extracted fieldsException queueDocumentService contractCounterpartyExample Trading LtdContract numberC-118Effective date14 Aug 2026Payment term30 daysContract value12,400.00ReviewSource pagePage 3 of 6Service contractContract value 12,400.00

Savings

Where the savings come from

Most companies pay an outside contractor or a BPO to process incoming documents. That budget line already exists. We replace it, document by document, without a conversation about headcount.

Three questions to start:

  1. how many counterparty documents arrive per month
  2. who processes them today
  3. what you pay for it

Pilot

A pilot on your documents

  1. You pick one document class and the fields you need. We bring the base axes for your domain.

  2. We run your real documents through, inside your perimeter or on a stand you control.

  3. Together we measure the direct-pass share and read the exceptions.

  4. You decide.

So we know who we are replying to.

Where the reply goes - a work address reaches us fastest.

or press Ctrl / Cmd + Enter

A named person replies to you.

We use your details only to answer this request. See our privacy notice.

FAQ

We give a number only on your documents and only after a run. The mechanics: part of the flow passes straight through, the rest goes to a person in the exception queue. The direct-pass share is what we measure and improve.

No. Keep it. Ask it what to do with the batch of invoices that arrived on the shared mailbox this morning. That is the part we cover.

Both, by policy. Local models run inside. Cloud models are used where your policy allows, with quotas and a filter before data leaves.

No. An expert sets the base axes of the domain once, and we supply them. The machine works under them, hands exceptions to a person and proposes new axes for a specialist to decide.

No. Documents that match pass through. Everything else goes to a human. We do not promise full automation.

The product is in development. We have a working extraction stand on real contracts and run results. We do not claim deployments we do not have.
Built by WislaCode

WislaCode is an engineering unit that owns client and partner integrations end to end for banks, payment providers, lenders and acquirers - delivered under your controls, your architecture and your standards. wislacode.com