10 Related
What this sits between
The model reads. These decide what happens to what it produces.
| Field | Measured accuracy | Cost of an error | Threshold we set |
|---|---|---|---|
| Invoice amount | 99.2% | A wrong payment | High, plus a rules cross-check on the arithmetic |
| GSTIN | 97.4% | A blocked input tax credit | High, plus a format and checksum validation |
| Vendor name | 71.8% | A misposted ledger, easily spotted | Always review, until the accuracy improves |
| Invoice date | 98.6% | A wrong ageing bucket | Medium, with a sanity range check |
| Line description | 88% | Almost none | Permissive, no review |
- The thresholds are set from the cost of an error, which is a business judgement and yours to make. We supply the measured accuracy and the review load each choice implies.
- A rules layer sits after the model for anything checkable: format validation, checksum tests, arithmetic that must tie, and range sanity checks. A model should never be the thing that adds up a column.
- The review queue is a real queue, with a named owner, a service level and escalation, exactly as an approval workflow would have.
- Where the accepted output posts into the books, the Anything writing into the books inherits the logging control an external audit already tests: an unalterable, timestamped record of each entry and each later change, which is control A.8.15 of ISO/IEC 27001. An automated posting is part of that record.
10 Related
What this sits between
The model reads. These decide what happens to what it produces.
Step 1: Check it is not a rules job
If every document arrives in one template, rules are cheaper, faster and more reliable. We will send you to rules-based automation where that is the honest answer.
Week 1Step 2: Pilot on your own documents
50 to 200 real items, correct answers defined by your team, accuracy reported per field. The build decision is made here, on a number.
Weeks 1 to 2Step 3: Set thresholds per field
From the cost of an error rather than from the accuracy alone. Expensive fields get conservative thresholds and cheap ones get permissive ones.
Week 3Step 4: Wire the queue and the write-back
Review queue with a named owner and a service level, a rules layer for validation and arithmetic, then the write into your ERP or ticketing system.
Weeks 3 to 6Step 5: Monitor for drift
Accuracy on a rotating sample, review rate, cost per item and failure rate. A rising review share is the earliest warning that something upstream has changed.
Ongoing
Two people were keying invoices from about three hundred suppliers. They now review the exceptions and handle the difficult vendors, and month-end closes four days earlier.
10 Related
What this sits between
The model reads. These decide what happens to what it produces.
- Personal data. Documents contain names, phone numbers, addresses and bank details, and sending them to a model is processing them, so the General Data Protection Regulation and its equivalents apply. We map the fields, redact what the task does not need, and record where the rest goes.
- The accounting record. Anything posting entries is part of the accounting system and inherits the logging control an external audit already tests, retained for as long as the record-keeping rules where you are incorporated require.
- What we put in writing before a pilot. Which provider, which region, whether inputs are used for training, what retention applies, and what never leaves your systems at all.
10 Related
What this sits between
The model reads. These decide what happens to what it produces.
The savings figure in the report is measured, not modelled. The same team produces the before number and the after number.
-
P J Divya
Co-Founder, CTO and CMO
Builds the automation and the human review step, and instruments both so the saving is auditable.
-
Chetan Ravi
Founder and CEO
Counts the hours before, agrees the task inventory, and signs off the number afterwards.
-
Harith
Compliance Expert
Checks the record the automation leaves and whether it satisfies the books it feeds.
-
Harsh Jain
Legal Expert
Sets what the model may read, and reviews accountability when an automated step gets it wrong.
10 Related
What this sits between
The model reads. These decide what happens to what it produces.
Working hours
Our day runs on UTC+5:30. The overlap window with your team is written into the scope rather than assumed, and everything outside it runs asynchronously.
How we communicate
One written update a day on the channel you already use, a standing weekly call inside the overlap window, and a named person to escalate to. Nothing important is agreed only on a call.
Who you contract with
ProTax Consultancy, the company behind ProTax, named in the agreement with its registration number. The governing law and the forum are agreed before you sign, not after a dispute.
Currency and payment
Invoiced in your currency or in ours, your choice, and settled by bank transfer. Milestones are tied to deliverables you can see, never to elapsed time.
What you own
Copyright in everything built for you is assigned on final payment: source code, design files, prompts, configuration and documentation. Third-party licences are listed by name so nothing is a surprise later.
Where data sits
You choose the region your data is stored and processed in, and the answer is written down before the build starts, with who at ProTax can reach it and for how long.
Offset from our working day standard time
- London-5:30
- Dubai-1:30
- Singapore+2:30
- Sydney+4:30
- New York-10:30
- San Francisco-13:30
ProTax is a brand of ProTax Consultancy. The contracting entity, the governing law and the invoicing currency are all named in the proposal before you sign anything.
09 Questions
What this sits between
- Intelligent document processing
- Written IDP: extracting structured fields from documents that arrive in no fixed layout.
- Confidence threshold
- The level below which an output is sent for human review instead of being accepted. Set per field, from the cost of an error.
- Review queue
- Where below-threshold output goes, with a named owner, a service level and escalation.
- Straight-through rate
- The share of items processed with no human touch. The number that decides whether the automation pays back.
- Schema validation
- Checking output has the expected shape and types before it is accepted, so a malformed answer fails loudly.
- Drift
- Behaviour changing over time, either because the provider updated the model or because the incoming documents changed.
- Audit trail
- A non-erasable log of each entry and each later change with its date. Control A.8.15 of ISO/IEC 27001, and the first thing an external audit asks to see.
- GDPR
- The EU and UK data protection regime. Article 83 sets administrative fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, which is why consent, retention and access control are build decisions here rather than paperwork.
09 Questions
What this sits between
Next step
Name the job your team does by reading and retyping.
We will pilot it on your own documents and come back with a measured accuracy figure per field, a cost per item, and the review load it implies.
Read by P J Divya, our CTO, not a form queue. Reply usually within one working day, in your time zone.

