Resources · FAQ
Frequently Asked Questions
The questions buyers actually ask, answered without a sales call in the way.
Read this first
46 questions, seven topics
Short answers that agree with the longer pages. Where a topic has its own page, the answer links to it.
These are the questions buyers ask before a demo, and the ones security, finance and IT reviewers ask after it. The answers are deliberately plain. If a product, security or integration page says something more specific, that page is the one to trust, and we would like to hear about any answer here that disagrees with it.
If your question is not here, write to connect@ptasai.com. A person who works on the product answers.
01 · Company
About PTAS AI
Who we are, what we build, and the two things we are not.
What does PTAS AI do?
PTAS AI builds and runs AI automation for documents, finance and enterprise workflows. DocPro reads business documents and returns structured data with a confidence score on every field. FinSuite takes that data into payables, vendor checks, GST and reconciliation. Both run on the same Agentic AI Platform, and every workflow follows the same four moves: understand, decide, act, verify.
Who is behind PTAS AI?
PTAS AI is operated by Pritasha Solutions Private Limited, CIN U62091HR2024PTC121382, incorporated on 8 May 2024. The registered address is N.H. 11, Dohar Kalan, Narnaul, Haryana 123001, India. The leadership page names the people who run the company and what each one owns.
Is PTAS AI a chatbot company or a software agency?
Neither. Our agents read documents, apply rules and post entries; they do not hold conversations. And we do not start every project from nothing. When a process does not fit DocPro or FinSuite, we build on the platform, so the review queue, the audit trail and the integrations come with it.
How is this different from RPA?
RPA repeats clicks on a screen, so it breaks when the screen or the document changes. Our agents read the document, apply your rules, act through APIs and keep a record of why. When something does not fit a rule, it goes to a person with the reason attached instead of failing silently.
Will AI automation replace our finance team?
No. The agents take the typing, matching and chasing. People keep the judgement calls, the approvals above your thresholds and every exception. Human review is a control, and it is designed in from the first workflow.
How do we contact PTAS AI?
Email connect@ptasai.com or call +91-98963-36312. If you want to see the products on your own documents, request a demo and send a few samples ahead. Masked copies work.
02 · Products
DocPro, FinSuite and the platform underneath
DocPro understands documents. FinSuite executes finance workflows. Most product questions are about where one stops and the other starts.
How the pieces fit
Where agents are composed, given limits and audited. Every DocPro agent and every FinSuite workflow runs on it, so the review queue and the audit trail work the same way in both.
Reads invoices, receipts, bank statements, KYC packs and purchase orders. Every field it extracts carries its own confidence score, and anything below threshold goes to a person.
Takes validated fields into vendor checks, matching, GST validation, approval and ERP posting. The policy decides what runs alone and what waits for a sign-off.
One chain from the moment a document arrives to the moment the entry posts, with nobody retyping in between and the record kept at each step.
Either product works on its own. Together they remove the handoff between reading a document and acting on it, which is where most of the manual work hides.
What is the difference between DocPro and FinSuite?
DocPro reads the document and returns structured fields with a confidence score on each. FinSuite takes those fields and runs the finance work: vendor validation, matching, tax, approval, posting and reconciliation. On an invoice, DocPro's job is done when the fields are returned. Everything after that is FinSuite.
Which documents does DocPro handle?
Six agents cover invoices, receipts, bank statements, KYC and identity documents, purchase orders, and custom document types defined from a schema and a sample. Documents can arrive as PDFs, scans, phone photos or email attachments. Each agent carries its own schema, validation rules and review thresholds.
What does FinSuite cover?
Five modules: AP Automation, Vendor Management, GST Compliance, Bank Reconciliation, and Expense & Payment Operations. Each runs on its own. Together they share one vendor master, one rule set and one audit log, so adding a module later does not mean a second system.
Can we use one product without the other?
Yes, either works on its own. DocPro's output is JSON that can go to your own AP workflow or into an ERP import by a native, API, file or custom route. FinSuite does not read documents itself. When the two run together, DocPro reads and FinSuite acts, and nobody retypes anything in between.
Does FinSuite replace our ERP?
No. FinSuite runs the work in front of the system of record and writes the finished entry into it. Your chart of accounts, cost centres, vendor master and dimensions stay where they are, and each posted entry links back to its source document and the checks it passed.
Which FinSuite module do teams start with?
Usually AP Automation on one legal entity or one vendor group, because its output can be compared with postings you have already made. If the vendor master is known to be untidy, Vendor Management goes in first so the rollout does not inherit the duplicates.
What is the Agentic AI Platform?
The runtime under both products. It is where agents are composed, given limits and audited, which is why the review queue and the audit trail behave the same way in DocPro and FinSuite. It is also what we build on when a process needs a custom agent.
03 · Documents and accuracy
Reading documents, and what happens when the AI is unsure
Confidence is scored field by field, and anything below the threshold you set goes to a person.
How is DocPro different from OCR?
OCR converts pixels to characters and stops. DocPro settles what the document is, reads fields in context rather than from fixed coordinates, checks the values against your masters and the arithmetic, and flags what it is unsure about. What comes back is typed data with a score on every field.
Do we need a template for every supplier layout?
No. Fields are located by structure and context, so a supplier you have never sent us works on the first document, and one who redesigns their invoice keeps working. Where a change does lower confidence, those fields go to review and the log shows which supplier changed.
How accurate is the extraction?
It depends on the document, and the honest unit is the field. The DocPro page states the figure for supported standard formats, with its conditions. On degraded scans and unusual layouts it is lower, and the confidence scores say so field by field. The figure that should decide anything is the one measured on a set of your own documents.
What is a confidence score, and who sets the threshold?
It is the model's estimate for one field on one document, between 0 and 1. You set the threshold per field and per document type during onboarding, so a grand total can be held to a stricter bar than a remarks field. Fields below threshold go to review and the rest proceed. Moving a threshold changes how much a person sees. What the agent extracts stays the same.
What happens when a field falls below the threshold?
It is held with the reason, such as faded print, a handwritten amendment or a total that does not recompute, and goes to a review queue with the source image beside it. The reviewer settles that field, the correction is logged against it, and the record carries on. Sending a field to review is the control working as configured.
Does the AI ever guess a value it cannot read?
No. A value the agent cannot read confidently is left blank, flagged and sent for review. It is never filled in quietly, and the record shows which fields a person settled.
Does DocPro handle Indian GST invoices?
Yes. The Invoice Agent reads supplier and buyer GSTINs, the HSN or SAC code and tax split on each line, and the IRN and signed QR code where an e-invoice is required. FinSuite GST Compliance checks rates and registrations per line and reconciles the purchase register to GSTR-2B before the return is prepared. Your team or your tax agent files the return.
04 · Security and data
Where data lives, who sees it, and how long it stays
The full set of controls is on the Security page. These are the questions security teams tend to ask first.
Is PTAS AI ISO 27001 certified?
No. Our security practices are aligned with ISO/IEC 27001 and our delivery practices with ISO 9001, but we hold neither certification and do not claim to. We design for GDPR readiness where customers process EU personal data, and we are glad to walk your team through the controls themselves.
Can PTAS AI run in our own environment?
Yes, where supported. The options are cloud in the region you choose, a private cloud account you control, or on-premise, including air-gapped setups for regulated workloads. The products and controls are the same in each. What changes is whose infrastructure they run on and who holds the keys.
How long do you keep our documents?
For the period your retention policy sets. After that they are removed and the deletion is recorded. Field-level redaction on export is available for identity data and any other field you classify as sensitive, so two downstream systems can receive different versions of the same record.
Do you train AI models on our documents?
Customer documents are processed to do the work you have configured. Files uploaded to the public DocPro test are not used to train models. Any other use of your data is set out in your agreement, and we do not go beyond it.
What happens to a file uploaded to the DocPro test?
It goes to the DocPro extraction service for that one run and is stored on PTAS AI infrastructure for the test and quality review. It is not public, the preview comes back inside the response, so there is no file address to guess, and it is not used to train models. Use a document you are entitled to share, and mask anything you must.
Who can see documents and change rules?
Access is role-based: who can see a document, approve a payment or change a rule is set by role. Thresholds and rules are versioned with who changed them and when. Every agent decision is kept with the values it read, the rule it applied and the result it confirmed.
Can you complete our security questionnaire?
Yes. Send it to connect@ptasai.com with Security in the subject. An engineer who knows the platform answers it, for the deployment model you are considering.
05 · Integrations
Connecting to the systems you already run
Every connection is one of four methods, named per system and confirmed in discovery.
Which systems can PTAS AI connect to?
ERPs and accounting systems such as SAP, Oracle, Microsoft Dynamics, NetSuite, Tally, QuickBooks and Zoho, plus REST APIs, webhooks and file exchange. Naming a system is not a claim that a packaged connector exists. Each connection is built by one of four methods, and the method for your system is confirmed in discovery.
What do Native, API, File and Custom mean?
Native means a supported connector exists for your edition. API means we call the interfaces the system exposes. File means structured files exchanged on a schedule where there is no usable API. Custom means orchestration across several systems, or a process that needs its own build. Each integration page says which apply, because they are different amounts of work.
Do you have an SAP-certified connector or an SAP Store listing?
No. We do not claim an SAP certification, a partnership or a listing on SAP Store. The connection is built outside SAP against interfaces your basis team releases: OData APIs on S/4HANA, BAPIs over RFC on ECC, or IDoc and flat files where those are preferred.
Will invoices post into our ERP on their own?
Only after the checks and the approval your policy requires. FinSuite prepares the validated entry, posts it, and writes the document link and the status back. If your approval runs inside SAP, for example, FinSuite parks a complete document and leaves the approval there. One place approves, never both.
How do results reach systems we built ourselves?
Through the REST API and webhooks. You submit a document, then receive the record by webhook or by polling. A record that went to review arrives the same way once it is settled, so your system gets one final answer. Single documents and overnight batches run through the same extraction and the same rules.
What access do your agents need to our systems?
Only what the integration needs. Agents act with the permissions you grant, through the integration your IT team approved, and nothing more. For SAP that is one technical user authorised for the calls it makes, which your team can lock at any time.
06 · Engagement and pricing
Timelines, pricing and what we need from you
One workflow first, with the controls switched on from the first run.
How long does a first workflow take?
Typically 4 to 12 weeks, an indicative range that varies by document types, workflows, integrations and deployment. Discovery gives you a figure for your own case. A rollout normally starts on one entity or one queue and widens once the output has been checked against your records.
How is PTAS AI priced?
DocPro and FinSuite are quoted on your volume, the agents or modules in scope, the integrations and the deployment model, so the figure comes out of a scoping conversation. Tell us the process and the monthly volume, and we will come back with a figure.
What do you need from our team?
A process owner who can settle rules when they are unclear, about a month of real documents, access to the system the results post to, and an hour or two a week from someone who knows where the exceptions come from.
Where do you start?
With one workflow: the queue that waits longest on a person, run on a month of your real documents with the controls on from the first run. The second workflow is planned from what the first one measured.
Can we change rules and thresholds after go-live?
Yes. Rules and thresholds live in configuration your team can edit. Each change is versioned with who made it and when, so you can see which version of the policy any past decision followed.
What will you not automate?
Judgement calls nobody can write a rule for, payments above your approval thresholds, work nobody can describe yet, and any value below the confidence threshold. A change to a vendor's bank details always goes through a person, and your GST return is filed by your team or your tax agent.
Can we speak to an existing customer?
Where a customer has agreed to take reference calls, we arrange a direct conversation, without us on the line if you prefer. Tell us the process you are evaluating so we can look for a comparable deployment. No name is shared until that customer has said yes in writing.
07 · Evaluation
How to judge PTAS AI before you commit
Score, test, then demo. None of it needs an account.
What is the quickest way to evaluate PTAS AI?
Test one of your documents with DocPro. Then book a call for a demo on your own paperwork. In that order, the demo is about your process rather than a tour of ours.
What is the Automation Readiness Score?
A score out of 100 from fourteen questions across seven weighted dimensions: Process Automation 25, Document Automation 20, Data Quality 15, System Integration 15, Workflow Maturity 10, AI Adoption 10 and Governance 5. It places you in one of four bands (Emerging, Developing, Automation Ready or Advanced) and names two places to start. It is PTAS AI methodology, not an industry-standard benchmark.
Should we take the general or the finance assessment?
The general assessment if you have not settled on a first process. The finance assessment if payables is already the candidate: its fourteen questions cover intake, matching, approvals, exceptions, vendor data, GST and posting. Both use the same scorer and the same bands.
Do I need an account to use the tools?
No. The finance workflow assessment asks for a name, work email and company so the result can be sent to you. Research use and a sales follow-up are separate boxes, and both are optional. The document test asks for the file and the document type, and nothing else.
What can I test without talking to anyone?
An invoice or a UPI payment receipt, as a PDF, JPG or PNG up to 10 MB, one page at a time. The test shows the fields it read beside the page. Confidence scores and validation depend on thresholds set for your process, so they are shown in a demo, along with bank statements, purchase orders and KYC documents.
What happens in a demo?
A working session of about thirty minutes, an indicative length. You describe the process and where it waits, your documents go through DocPro or FinSuite, and the last part covers fit, scope and what should stay manual. Sessions run longer when there is more to look at.
Keep reading
Where the answers come from
Glossary
Plain definitions of the terms in these answers, from approval band to three-way match.
Read more →Guides
The long versions: agentic AI versus RPA, AP automation, IDP, GST, human review and readiness.
Read more →Security
Access, encryption, deployment, audit and retention, set out control by control.
Read more →Research and Evaluation
The benchmark, both assessments and the document test, and which to use when.
Read more →Still deciding
Ask the question on your own documents
Most of these answers are easier to check than to read. The assessment takes seven minutes and names the two places we would start; a demo puts your paperwork through the product.