DocPro · Integrations
PTAS DocPro Integrations
Where the structured data goes next: ERP, accounting, storage and workflow systems, by API, webhook or file.
What moves
Documents in from four places, records out to wherever the work continues
DocPro sits between the places documents arrive and the systems that need what is on them. It reads, scores and checks; the systems on the right stay the systems of record.
Email inbox
Shared folder
Portal upload
API
DocPro
Structured JSON to your application
Typed fields, a score on each, the validation results and the review status, delivered when the record is final.
Entries into your ERP or accounting system
The fields your ledger needs, mapped to your chart of accounts, by a route agreed during assessment.
Events and files for everything else
A webhook when a record is final, or a scheduled file for a system that only accepts files.
These are routes, and none of them is a packaged connector. Which intake channels and which destinations apply to you, and the method for each system, are confirmed during assessment.
What the API sends and returnsIntake
Four ways documents arrive
Start with the channels your documents already use. Changing how suppliers send invoices is a project of its own, and rarely the one worth doing first.
Inbox
Suppliers keep sending to the address they already use. Attachments are classified and read; the body of the mail is ignored unless your process needs it. The mailbox stays yours, and the access DocPro needs to it is agreed with your mail administrator.
Folder
Shared folder
Scanners in a plant or a branch save to a folder they already write to, and DocPro collects from it on a schedule or as files land. Useful where paper still arrives at a site and nobody there should be keying it.
Portal
Upload page
Staff upload what arrived by hand or by courier, and suppliers can upload their own invoices. The person uploading can declare the type; classification still checks it.
API
Your application
An expense app, a procurement system or a line-of-business tool sends the document and its type, then takes the record back by waiting, polling or callback.
Illustrative example: one morning's intake, four channels
Illustrative data. A new channel does not mean a new pipeline: every route lands in the same queue, under the same rules and the same audit log.
Calling patterns for the API channel, single, batch or callback, are set out on DocPro API.
Outputs
Four places the record can go
One record per document, cut to suit each destination. A system gets the fields it needs, in the shape it accepts.
Illustrative example: one invoice record, four destinations
Illustrative data. Each destination gets the fields it needs and no more, because masking is set per field and per destination.
Integration methods
Native, API, file or custom, named per system
Four kinds of connection, and they are different amounts of work. We name the one that applies to each of your systems before anything is built.
Native
What the system ships itself
Some ERPs and accounting suites have their own capture or import. Where the DocPro record fits it, we say so for that system. We claim no packaged DocPro connector for any system, and none is assumed.
API
Your system has an API
The record is written through the receiving system's API by a user your IT team scopes, or your system calls DocPro and takes the record itself. The usual route wherever the system exposes one.
File
Your system takes files
A file in the format your system already imports, delivered on a schedule to a location your team chooses. Slower than an API and sometimes the only route an older system or a support contract allows.
Custom
Several systems, one record
The same document feeds an ERP, a document archive and a workflow tool, or the route needs logic of its own. Orchestration sits on top, with one record and one audit log.
A system's name on this site is a planning example. It is not a claim that a connector exists, or of a partnership or certification. The SAP, Oracle and QuickBooks pages describe the routes we would propose for those systems. For anything else, the method is confirmed in discovery against the version you run and the interfaces your IT team will release.
Where FinSuite takes over
Where DocPro stops and FinSuite starts
DocPro understands documents. FinSuite executes finance workflows. On an invoice, the handover is the moment the record is final.
Illustrative example: where DocPro hands over to FinSuite
Illustrative data. Without FinSuite, steps four to six belong to your own AP workflow, and the record reaches it by API, webhook or file.
With FinSuite in place, there is no integration to build between the two products. The record DocPro returns is the input FinSuite matches, routes for approval and posts, and both write to the same audit log. The integration work moves to the far end: how FinSuite reaches your ERP, which is the subject of FinSuite Integrations.
Without FinSuite, the record goes to whatever runs your finance process today, through one of the four methods above. That is a reasonable place to start. Some teams want the reading solved first and the workflow later, and the DocPro record is the same in both cases.
FAQ
Questions integration teams ask
Do you have a native connector for our ERP?
We claim none on this page. For each system the route is named as native, API, file or custom once we have seen your version and what your IT team will release. The SAP, Oracle and QuickBooks pages describe the routes for those systems in detail, and say plainly that none of them is a packaged connector.
Can we keep our current mailbox and scanners?
Yes. Suppliers keep sending to the address they use today and scanners keep saving where they save today. DocPro is pointed at those places, so nobody outside your team has to change anything.
Do we need FinSuite to get DocPro output into our ERP?
No. The record can go into your ERP through an API, a file import or a custom route without FinSuite. What FinSuite adds is the finance work in between: vendor verification, PO and goods receipt matching, GST checks, approval bands and posting with status written back.
What happens if the receiving system rejects a record?
The rejection is kept with the message the system returned and goes to a person. The record stays in DocPro, so once the cause is fixed, such as a vendor missing from the master, it can be sent again.
How long does an integration take?
An integration is built inside the DocPro rollout, which typically takes 4 to 12 weeks. That is an indicative range and it varies with the document types, workflows, integrations and deployment model in scope. A file route is usually the quickest to approve, an API route the quickest to run.
Keep reading
Where to go next
DocPro API
What goes in, what comes back, and how review fits into an API flow.
Read more →FinSuite Integrations
How FinSuite posts into SAP, Oracle, Tally and other systems of record.
Read more →Webhooks
Events sent to your systems when a record is final or a status changes.
Read more →All integrations
ERPs, accounting suites, the REST API and webhooks in one list.
Read more →Next step
Show us where your documents land today
The mailbox, the scan folder, the upload page. Send a sample from each and we will show you the record DocPro returns and where it could go next.