The integration is a file you own.
Procurea does not plug into your ERP, your CRM or your accounting system. A run ends in a spreadsheet you download: one row per supplier, eight columns, loaded by you into whatever you already run. That is the entire surface today, and this is a short page because it is a short truth.
suppliers.csv · 8 columns · one row per supplier · no connector, no sync, no record written on your side
Eight columns, and none of them guessed.
Every row is a company the engine read and scored against your brief. Blanks are real blanks: a supplier with no published email address is exported with that column empty rather than filled in with something plausible.
| Column | What is in it |
|---|---|
| Name | The company as the engine read it off its own site, not as a directory listed it. |
| Country | Where the supplier is, when the engine could place it. A few rows come back unplaced and say so. |
| City | The site or head office, where the pages named one. |
| Website | The page that was screened. This is the field to match on: a domain is the only identifier in the file a machine can trust. |
| ContactEmails | A published address, where one was found. Not every row has one, and the file never pretends otherwise. |
| Score | The match against your brief, out of 100, as the engine recorded it. |
| Specialization | What the supplier says it makes or does, in one line. |
| Certificates | Standards named on the supplier pages themselves, ISO 9001 and the rest of them. |
Name,Country,City,Website,ContactEmails,Score,Specialization,CertificatesAcross the 8 runs we have published, 300 of 472 shortlisted suppliers came out carrying an address in the ContactEmails column.
Four steps, all of them on your side.
Filter before you download
The export takes the filters you set in front of it: country, a minimum score, whether the row carries an email, and a text search. Pull the rows you will act on rather than everything the run touched.
Map eight fields onto your vendor record
Most of the mapping is obvious and done once. The only judgement call is what you do with Score and Certificates, which usually land in a note field or a custom field rather than anywhere structural.
Match against the suppliers you already hold
Procurea does not read your vendor master, so nothing on our side knows who you already buy from. Dedupe on your side: domain first, company name second, and expect a handful of judgement calls.
Load it, and keep the file
Your own import brings the rows in. Keep the download afterwards: it is the record of what the run returned on the day it ran, which is the thing an approval or an audit asks for later.
Named honestly, not connected.
These are the systems buyers name when they land on this page. Procurea is not connected to any of them: nothing syncs, nothing is created on your side, nothing links back. What each one does have is an import of its own, and a supplier spreadsheet is exactly the kind of file those imports were built to take.
| System | Kind | Where the file goes in, run by you |
|---|---|---|
| SAP S/4HANA | ERP | Business partner load through the migration cockpit, run by your own Basis or data team. |
| SAP ECC, on premise | ERP | The vendor master upload your team already uses, LSMW or an equivalent. |
| Oracle NetSuite | ERP | The CSV import assistant, against the vendor record. |
| Oracle Fusion Cloud | ERP | The file based supplier import your Oracle team runs. |
| Microsoft Dynamics 365 Business Central | ERP | A configuration package, which is the spreadsheet route into vendor cards. |
| Microsoft Dynamics 365 Finance and Operations | ERP | The data management framework, vendor entity. |
| Salesforce | CRM | The data import wizard or the data loader, as accounts and contacts. |
| QuickBooks Online | Accounting | Import vendors from a spreadsheet. |
| Xero | Accounting | Import contacts from CSV. |
| Sage Intacct | Accounting | The vendor import template. |
| Odoo | ERP | Import into contacts, res.partner. |
If one of these were built, this page would name the version it was tested against and the date it last ran. None are.
Read only, key scoped, undocumented.
There is a read only interface behind an API key: campaigns, and the supplier rows behind them, over HTTPS. It returns the same data the export carries. There is no OAuth flow, no client library, no event you can subscribe to and no published reference, so a key is a conversation rather than a signup. Ask, and say what you want to read.
Then the agents move to your side.
A download is fine for a shortlist a person reads. It stops being fine when one enquiry carries a hundred line items and the first question is always whether you already buy this from someone. Pointing the agents at your own supplier database first, and teaching them your qualification rules, is real work that we scope on a call rather than sell from a page.
Or bring one enquiry to a call: talk to us
Platform, monthly: Starter $69 · Growth $159 · Scale $299