Read it. Check it. Transform it. Send it.
ProcuLink reads the files you receive, shows what it read beside the original, and sends the data on in the format your system needs. Scans and phone photos are read too.
Send it
Upload a file, forward an email to the address your flow gives you, or let ProcuLink collect files for you.
We can collect from a mailbox, an SFTP, FTP or FTPS server, an S3 bucket, or our API. PDFs with a text layer, CSV and Excel files are read, and so are Word, text, XML and JSON files.
We read it
We read every value and every table on the first document, row by row.
There is no template to build first, so a new sender with a new layout does not mean new setup. Scans and phone photos are read too.
You check it
The original stays on screen beside what we read. Fix a value that is wrong, or draw a box around it on the page so we find it in the same place next time.
We flag a value that is missing, in the wrong shape or hard to read, and we hold a document we have already seen instead of sending it twice.
We send it
Choose CSV, JSON, XML, Excel, PDF, text or fixed-width, then send the result where it needs to go.
Send it by email, to a web address, to an SFTP or FTPS server, an S3 bucket, Google Drive or Google Sheets, or download it. Microsoft OneDrive and SharePoint are available on request.
Have your receiving system's documentation? Upload it and we propose the output for you to check.
The second document is easier.
We remember where each sender puts each value, so the next document from them needs less checking.
- Every flow starts in Review before delivery. Each document waits for you, and nothing goes out until you press Send.
- The flow tells you how many documents in a row went out without a correction.
- When you trust it, switch that flow to Automatic delivery. You can switch back at any time.
- A document with a number we have already received always waits for you, so nothing is sent twice.
- The first document from a new email address waits for you too. Send it once and later documents from that address go by themselves.
For technical readers: the pipeline.
Every document goes through the same five stages. What happened at each one is kept on the document, so you can open it later and read its history.
In
A file arrives by upload, email, a pickup or the API, and becomes a document in its flow.
Read
Every value and table is read, with where on the page it was found and how sure we are.
Check
Built-in checks mark a value that is missing, in the wrong shape or hard to read. A repeated document number is held, and so is the first document from a new email address.
Transform
Each output file is built from the read values, with your column names and any lookups applied.
Send
The file goes to each destination. Each delivery keeps its attempts, the destination's answer where it gives one and, when it fails, the error.
Try it on your own documents
Upload one and see what comes back. It takes a few minutes, and nothing is sent on until you say so.