Skip to main content

Every format and method, in one place

You don't need to know the technical format. If it reaches you as a PDF, a spreadsheet, a scan or an email attachment, start with that. The details are here for whoever needs them.

Documents we read

Send the file as it is. We read every value and table on it, and there is no template to build first.

PDF (with a text layer)
The usual PDF: one made by a system or saved from an email, where you can select the text.
Scans and phone photos
A scanned page or a photo of one, as a PDF, PNG or JPG.
CSV
A table saved as plain text, the way most systems export it.
Excel
An .xlsx workbook.
Word
A .docx document.
Text
A plain .txt file.
XML
A structured .xml file exported by another system.
JSON
A structured .json file exported by another system.

Outputs

The file your system expects. You choose what goes in it and what each value is called.

CSV
Your columns and your names, separated by a comma, a semicolon or a tab.
Excel
An .xlsx file with your columns and your names.
JSON
For systems that take structured data, with the names your system expects.
XML
Structured data as XML, with the names your system expects.
PDF
A clean page with your title, your own text at the top and bottom, and your logo.
Text
A plain text file with a title and the values.
Fixed-width
Every value at a set width, for systems that read by position.
cXML
A purchase order as cXML 1.2, for suppliers and procurement networks that take it.
UBL Order
A purchase order as UBL 2.1, the XML order many European systems take.
EDIFACT ORDERS
A purchase order as an EDIFACT ORDERS message (D.96A).
ANSI X12 850
A purchase order as an X12 850 (version 4010), for EDI partners in North America.

Ways in

How a document reaches a flow. The people who send you documents don't need to change anything.

Upload
Drag a file into ProcuLink, or choose one.
A flow's own email address
Forward or send documents to it. Each attached file we can read becomes a document.
A mailbox
We collect new mail from a mailbox you already use.
SFTP, FTP or FTPS
We collect new files from a folder on your server.
An S3 bucket
We collect new files from a bucket, or from S3-compatible storage.
Our API
Your own system posts a file to a flow and fetches the result.

Collection runs every five minutes, takes each file once, and leaves it where it is.

Ways out

Where the finished file goes. One flow can send to several places at once.

Email
The file as an attachment, to one address or several.
A web address
We post the file to an address your system gives you.
SFTP or FTPS
Into a folder on your server.
An S3 bucket
Into a bucket, or S3-compatible storage.
Google Drive
Into a folder you choose.
Google Sheets
As new rows at the end of a sheet you choose.
Download
Download the file and send it on yourself.

Microsoft OneDrive and SharePoint: on request

Limits

How big a file can be, and how files are counted.

File size
Up to 10 MB a file.
What counts as a document
A document is one file of up to 10 pages. Longer files count once for every 10 pages, and we read up to 100 pages of a file.

Don't see yours?

Show us the file or the system on a short call and we'll tell you plainly whether it fits.

Talk to us

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.