Intelligent document processing in Salesforce, and what it requires
Documents arrive as they already do. We build the extraction in a business day. It costs nothing until it runs.
Salesforce offers two document processing add-ons. Intelligent Document Reader and Intelligent Form Reader both need a paid add-on licence, and Salesforce Help lists them for industry clouds including Financial Services, Health and Public Sector. Neither is listed for Sales Cloud or Service Cloud, where the usual route is extracting outside Salesforce and writing the fields in over the API.
Fabrx builds the API. Landing it in a given system is done by partners, so the only requirement is a system that accepts an API call.
What moves, and what it becomes
Supplier invoices
The supplier, the number, the dates, the currency and the line totals, from several hundred senders who each format all five differently.
The fields your AP team keys in today
The record they open now
Signed contracts and order forms
Term, value, renewal date and the signature block, usually arriving as a scan of a printed copy of a document you generated.
Values on the opportunity or the contract record
Sales operations
Identity documents at onboarding
Name, number and expiry, photographed by the customer, at an angle, in a hurry, on whatever phone they had.
Verified fields on the person record
Onboarding
Certificates of insurance
Carrier, policy number, limits and the expiry that decides whether a supplier is allowed on site this week.
Compliance fields and a renewal date
Vendor and risk
Application and claim forms
Your own form, returned on paper, with boxes ticked, boxes missed and two corrections in the margin.
A case, populated instead of typed
Service
Purchase orders from customers
Issued by the buyer's system, in the buyer's layout, carrying the reference that has to match something in yours.
An order, matched against the account
Order management
What happens to one document
Your documents
A document arrives. Your documents
An inbox, a shared drive, an upload on an Experience Cloud site, or a phone camera in the field.
T+0
Fabrx
Identify what it is. Fabrx
A mixed inbox is sorted before anything is read, so an invoice and a certificate are not treated as the same document.
If A document type nobody described
Hold for review. Fabrx. Needs a person.
A named person on your side sees the document, the field in question and what the extraction read, before anything is written.
needs a person
Then it rejoins the path above.
Read the fields. Fabrx
Fields are read by what they are, wherever they sit, so a sender changing their layout does not need a rebuild.
If A value the document cannot settle
Hold for review. Fabrx. Needs a person.
A named person on your side sees the document, the field in question and what the extraction read, before anything is written.
needs a person
Then it rejoins the path above.
Send the payload. Fabrx
A structured record, the same shape every time, either written to Salesforce directly or posted to an endpoint you own.
Where we hand over
Two ways, settled on the call. We write to the Salesforce API against a connected app you authorise and can revoke at any time. Or we post the result to an endpoint you own and your side writes the record, through Make or your own middleware, in which case we hold no credentials to your org.
Salesforce
Fields on the record. Salesforce
Your objects, your validation rules, your automation. The team works where it already works.
What we do, and what stays yours
Fabrx builds and runs
- Reading the document, whatever shape it arrives in
- Identifying which document it is before anything is read out of it
- Pulling the fields, and checking what the document can confirm on its own
- Flagging anything that needs a person, with the document attached
- Building the connection, and rebuilding the extraction when you need a new field or a new document type
You keep
- Your org and its data model, including which object and which fields the values land on
- Authorising the connection, and the permissions it runs under
- What the document means for your process, which stays a decision inside Salesforce
- Somebody to look at the output and tell us whether it is right
When a document is wrong
A pipeline with no failure path is a diagram of a good day. These are the ones that happen.
The scan is unreadable
The document stops before extraction and is never guessed at.
Who sees it. Whoever sent it, by reply, with the page that failed.
- Rescanned and reprocessed
- Keyed in by hand, as it is today
The document is not a type we can identify
It is set aside at the classification step instead of being read as something it is not.
Who sees it. Your side, in the exception report, usually the same day.
- Added to the build as a new type
- Routed somewhere else entirely
A field you need is genuinely not on the document
The record arrives with that field empty and marked. Nothing is invented to fill it.
Who sees it. The person who owns the record in Salesforce.
- Filled from another source
- Chased with the sender
Salesforce refuses the write
A validation rule, a required field or a permission rejects the record, and the payload is held with the error Salesforce returned.
Who sees it. Your administrator, with the rule that fired.
- Mapping corrected and replayed
- Rule adjusted on your side
Intelligent document processing in Salesforce, four ways
The same document, four approaches, and what each one asks of you.
What it is
Intelligent Document Reader
Salesforce's own add-on for reading documents into records.
Intelligent Form Reader
Salesforce's own add-on for reading forms, built on Amazon Textract.
An IDP platform you configure
A third-party product you license and configure yourself.
Fabrx
An extraction built for your documents, landing fields on your records.
What you need before you can use it
Intelligent Document Reader
The Intelligent Document Reader add-on licence.
Intelligent Form Reader
The Intelligent Form Reader add-on licence, and your own Amazon Textract licence.
An IDP platform you configure
A licence, and an implementation before you know it reads yours.
Fabrx
A 30-minute call and about twenty sample documents.
Which Salesforce clouds it covers
Intelligent Document Reader
Industry clouds, including Financial Services, Health and Public Sector. Sales Cloud and Service Cloud are not on the list.
Intelligent Form Reader
Financial Services, Health Cloud and Public Sector Solutions. Sales Cloud and Service Cloud are not on the list.
An IDP platform you configure
Any, since it works outside Salesforce and writes in.
Fabrx
Any, for the same reason.
Who configures it
Intelligent Document Reader
Your admin, inside Salesforce.
Intelligent Form Reader
Your admin, inside Salesforce.
An IDP platform you configure
You do, in their builder.
Fabrx
We do. Adding a field is a request, not a procurement cycle.
Where the extraction runs
Intelligent Document Reader
Inside Salesforce, under the add-on licence.
Intelligent Form Reader
Amazon Textract, under your own AWS licence.
An IDP platform you configure
The vendor's platform, once you have configured it.
Fabrx
Ours, with the structured record written to your org.
What it costs to find out
Intelligent Document Reader
The add-on licence, before you have seen it read your documents.
Intelligent Form Reader
Two licences, before you have seen it read your documents.
An IDP platform you configure
A licence and an implementation.
Fabrx
Nothing. The build is free and you pay per document once it runs.
Someone has run this
They built solutions for any situation encountered along the way. For us, this type of partnership matters.
- 300+
- Field agents using it every working day
- 4,000+
- Documents processed every month
- 4 yrs
- In production, on the same workflow
Blitz is a real estate field agency network running identity documents into signed contracts. The figures are theirs and describe the pipeline on this page, not a Salesforce deployment.
What a pilot measures
Measured on your documents
Field-level accuracy
Every field on every sample document, scored against your correction.
Sample size
How many of your real documents we ran. You choose which.
Exception rate
The share that stopped for a person, and what stopped them.
Write success
How many records Salesforce accepted first time, and which rules rejected the rest.
Build time
Calendar time from your samples reaching us to the pipeline running.
What we ask you for
How long does one document take today, from arriving to being on the record?
It is the only honest denominator for any claim about time saved.
How many do you process in a month?
It sets the pricing band, because the rate depends on volume.
Which Salesforce clouds and editions are you on?
It decides whether the native add-ons are available to you at all.
Which object should these values land on, and who owns it?
The mapping and the permissions are the part that stays yours, and the build goes faster when the answer exists before the call.
What it costs
- 01
We build it
We build the extraction, usually within one business day of receiving your sample documents.
- 02
You check it
It costs you nothing until it runs on your real documents. If the accuracy is not good enough, nothing goes into production and nothing is charged.
- 03
Then you pay
A prepaid package priced per document, valid for a calendar year. The rate depends on the document type and your monthly volume.
- No subscription
- No per-seat charge
- No setup fee at any volume
Questions about document processing in Salesforce
Does Salesforce have intelligent document processing built in?
It has two separate add-ons. Intelligent Document Reader reads documents into records, and Intelligent Form Reader reads forms using Amazon Textract. Both need a licence on top of your existing Salesforce subscription. The details here come from Salesforce Help, checked in October 2026.
What is the difference between Intelligent Document Reader and Intelligent Form Reader?
They are two products with separate licences. Form Reader is the older of the two and runs on Amazon Textract, which is why your organisation needs its own Textract licence to use it. Document Reader is the broader document capability and is listed across more industry clouds. The names are close enough that the two are regularly confused.
Which Salesforce editions include intelligent document processing?
Salesforce Help lists Intelligent Document Reader for Automotive, Consumer Goods, Education, Financial Services, Health, Manufacturing, Media, Net Zero, Nonprofit and Public Sector, mostly in Enterprise and Unlimited editions. Intelligent Form Reader is listed for Financial Services, Health Cloud and Public Sector Solutions. The same documentation puts Document Reader at 5 MB and 20 pages per file.
Can I use Salesforce document processing on Sales Cloud or Service Cloud?
Neither add-on is listed for Sales Cloud or Service Cloud in the Salesforce documentation. Teams on those clouds generally extract the fields outside Salesforce and write them in over the API, which is the route this page describes.
Do I need an Amazon Textract licence as well?
For Intelligent Form Reader, yes. Salesforce Help states that your organisation must have an Amazon Textract licence to use it, and the Public Sector listing quotes a 1,000 page allowance. It is a separate licence from Amazon, bought alongside the Salesforce one.
How does extracted data get onto a Salesforce record?
Two ways, and the choice is made on the call. We write to the Salesforce API against a connected app you authorise and can revoke. Or we post the structured record to an endpoint you own and your side writes it, through Make or your own middleware. Either way your objects, validation rules and permissions stay as they are.
Related
- automatic document processing
The same work described by its five steps, from capture through to the system it lands in.
- automatic data extraction
What changes when the thing you are extracting from is a file instead of a page.
- how the build works
The call, the sample files, and what happens in the business day between them.
Send us twenty documents
We build the extraction and show you what it got right, field by field, before you pay anything.