MuleSoft IDP

The document is the intake. The record is the work.

IDP turns files into fields. Anypoint writes them where the process already lives. A person reviews what the model should not sign.

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

Five problems

Document work is five jobs, not one model.

  1. 01

    Classification

    What type of document is this

  2. 02

    Extraction

    Which fields · How they relate

  3. 03

    Validation

    Totals · Allowed items · Required parties

  4. 04

    Human review

    Exceptions · Low confidence · Policy holds

  5. 05

    Integration

    Salesforce · ERP · Case or invoice

  6. 06

    Insights

    What failed · What a person had to touch

MuleSoft IDP covers the document lifecycle. Integration and insights belong next to Anypoint and the system of record, not inside the PDF.
Mermaid source
flowchart TD
  A["Classification: what is this file?"] --> B["Extraction: which fields, how related"]
  B --> C["Validation: do the totals hold"]
  C --> D["Human review: exceptions only"]
  D --> E["Integration: write to Salesforce or ERP"]
  E --> F["Insights: what the trail shows"]

Who this is for

Three desks that stopped re-keying documents.

Start with the document you actually receive. One type first.

  • Example

    Accounts payable lead at a Dubai trading house

    Today: Supplier invoices arrive as PDFs and scans and are typed into the ERP.

    After: Totals and lines are extracted and matched to the PO; only mismatches reach a person.

    Invoice processing
  • Example

    Onboarding manager at an Abu Dhabi corporate-services firm

    Today: Trade licences and passports are checked by eye and typed into the account.

    After: Fields land on the account with the expiry date; low-confidence pages go to a reviewer.

  • Example

    Claims supervisor at a Houston property insurer

    Today: Repair estimates arrive in a dozen formats.

    After: Each estimate is classified and extracted to the claim; money fields stay with a person until the evals say otherwise.

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

The desk

A person sees only the field to sign.

An accounts clerk with a stack of supplier invoices and a scanner, reviewing one field highlighted in amber on her screen.

Illustration

The model reads the invoice. The clerk reviews only the field it should not sign.

Personas

Business user, developer, reviewer.

IDP is not a data-science project. It is an operations desk with a model underneath.

Trust

Einstein for IDP. Trust Layer still applies.

Prompt-based extraction sits behind the same controls as the rest of the Salesforce AI stack. We will not skip that because a demo extracted an invoice.

Adjacent

Composer and RPA are not IDP.

A click-path robot and a document action are different jobs. We will not sell one as the other.

A click-path robot (RPA, Composer)

A document action (IDP)

Repeats the clicks a clerk already does
Reads the file and returns fields
Breaks when the screen changes
Writes through Anypoint to the system of record
A bridge when there is no API
Sends exceptions to a person

Questions

What we actually say.

Is IDP the same as an agent?
No. IDP structures a document. An agent may call IDP as a tool. Governance still sits on the gateway and the reviewer queue.
Do you skip human review in production?
No. High-confidence fields can auto-post. Money, identity, and policy holds stay on a person until the evals say otherwise.

The brief · one email

Send one document type.

We will tell you whether IDP earns the seat, or whether the file should stay a person. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.