Resources ยท Research

Research and Evaluation

The benchmark, the finance assessment and the document test. Three ways to see where you stand before you buy anything.

Overhead view of four colleagues reviewing printed pie and bar charts around a wooden table

What this section is for

Evidence before a sales conversation

Every tool here returns something you can show your own team the same day: a score, a breakdown or a set of extracted fields.

Most automation evaluations start with a vendor demo on the vendor's sample documents. That tells you the product works on paperwork chosen to make it look good. The tools on this page work the other way round. They start from how your work runs today and from a document you actually received, so that when you do ask for a demo, you already know which process, which documents and which controls you want to see.

There are two kinds of tool, and it helps to keep them apart. The Automation Benchmark is a method: seven dimensions, weighted to add up to 100, with four bands. The finance workflow assessment is where you take it for payables; for any other process, book a call. The DocPro document test is different again. It asks nothing about your process and reads one file instead.

None of them replaces a pilot on a month of your own documents. They tell you whether a pilot is worth setting up, and what it should measure.

Which tool, when

Start from the question you have

Each tool answers one question well and the others badly. Pick by the question, not by the tool that sounds most thorough.

Four ways to evaluate, and what each one hands back

The question you haveUseYou get back
Which part of the operation is ready to automate first?A call with the teamThe first process to automate, agreed
Is our payables process ready on its own?Finance assessmentThe same score, for AP
Can DocPro read the paperwork we actually receive?Document testFields beside the page
How would it run on our rules, thresholds and ERP?DemoYour documents, end to end
Before a demoScore, then testA specific agenda
No account needed The assessments ask for a name, work email and company so the result has somewhere to go. The document test asks for the file and the document type.

The benchmark is the method behind both assessments. Read it once, then take whichever track fits the process you own.

If this is where you areUse this
You want to know what the score means before you take it Automation Benchmark, the method
Several processes are candidates and nobody agrees which goes first Book a call to compare them with the team
Payables is the candidate and you want to know what will fight you Assess Your Finance Workflow, finance track
The process is fine; the doubt is whether your invoices or receipts can be read Test Your Document, one file
You have a score and a test result and want to see your rules applied Request a Demo on your documents
You are building the internal case and need something to read Insights and the guides

Answers and documents

Why the assessment and the document test are both worth doing

They look at different things. A process can score well and still run on paperwork nobody can read, and the reverse happens just as often.

Two kinds of evidence · Illustrative example

Assessment14 answers
Documents enter byScanned, then keyed
Master dataClean in places
Reaching the ERPFile exports and imports
ReturnsScore, band, two next steps
Document test1 invoice, 1 page
Seller GSTINRead
Line table11 of 12 rows read
TotalBlank, stamp across it
ReturnsFields beside the page
Both, then a demo The answers say how work moves. The file says whether the paperwork can be read. Neither sees your rules, and that is what the demo is for.

Illustrative data. A blank total is a useful result: the agent did not settle the value, and it did not invent one.

The assessment hears how work moves: who keys what, how clean the master data is, how a result would reach the ERP. It cannot see a single document. The document test sees one document closely and knows nothing about your process. Run both and you can tell a process problem from a paperwork problem, which decides whether the first project is a DocPro deployment, a FinSuite workflow, or a clean-up of the vendor master before either.

The public test reads invoices and UPI payment receipts only, one page at a time, and does not display confidence scores or run validation. Those depend on thresholds and masters set for your process, so they are shown in a demo. Bank statements, purchase orders and KYC documents have their own agents and are shown the same way.

How we handle research

What we label, what we hold back, and what we keep apart

On every page that scores

The method, labelled as ours

The benchmark page and both assessments say the same thing in so many words: PTAS AI methodology, not an industry-standard benchmark, and not scientifically validated.

Not on this site yet

Aggregate results

We do not publish averages, peer comparisons or industry figures from assessment responses. If we publish benchmark research later, it will state its sample and method.

Kept separate

Research and marketing consent

The assessment asks for each separately and both are optional. Only responses with the research box ticked may be included in aggregated research.

Start with the score

Get one number to argue about, in seven minutes

The assessment scores seven dimensions and names the two places we would start. Take it before the document test, and both before a demo.