Skip to content
Fabrx
FIG. 2Before you pay anything

The build is on us.

All of it happens before any money changes hands, and almost none of it needs your time.

  • A supplier invoice
    Invoicesupplier, number, VAT, dates, total
  • A service agreement
    Contractparties, term, value, effective date
  • An identity card, marked specimen
    IDname, document number, date of birth
  1. 01

    We talk for 30 minutes

    What documents you handle, what you need out of them, and where that data has to end up. If it is not a fit, we will say so on the call.

    30 minutes

  2. 02

    You send a few representative documents

    Whatever actually comes in. We need to see the scans that arrive crooked and the supplier who formats their invoices differently to everyone else.

    We sign an NDA if you want one, and redacted samples are fine. Your documents never train anything, and we do not keep them.

    A pile of mixed business paperwork: skewed sheets, a creased thermal receipt, a grey photocopy
  3. 03

    We build it

    The extraction, the output structure, the validation, and the connection into Make, your ERP or your own API. That part is ours to do.

    Usually one business day

  4. 04

    You look at the output

    Your documents, your fields, your team checking whether the values are right. That is the only part that asks anything of you, and it is reading results.

    Zero hours of setup on your side

  5. 05

    It goes live, and only then does it cost anything

    You pay per document processed. Nothing before that point, and nothing else after it.

It lands where your data already lives.

You do not adopt a new tool or move your team into somebody else's dashboard. The extraction runs behind whatever you already use.

The same path, whatever the page looks like

Pick a document type. The request in the middle is the same one every time. What changes is the page it reads and the record it writes.

Supplier invoice/v1/extractNetSuite vendor bill
A supplier invoice, the Fabrx extraction request and its response, and the vendor bill the values land in inside Oracle NetSuite.
Packing slip/v1/extractERP goods receipt
A supplier packing slip, the Fabrx extraction request and its response, and the goods receipt the values land in inside a manufacturing ERP.
Bill of lading/v1/extractShipment record
A bill of lading, the Fabrx extraction request and its response, and the shipment record the values land in inside a freight management system.
Auto claim form/v1/extractClaim record
A motor insurance claim form, the Fabrx extraction request and its response, and the claim record the values land in inside a claims management system.
Supply agreement/v1/extractMatter record
A master supply agreement, the Fabrx extraction request and its response, and the matter record the parties, dates and terms land in inside a legal workspace.
Commercial lease/v1/extractLease record
A commercial lease agreement, the Fabrx extraction request and its response, and the lease record the tenant, dates and rent land in inside a property management system.
Patient referral/v1/extractReferral record
A patient referral form, the Fabrx extraction request and its response, and the referral record the patient, provider and diagnosis code land in inside a care platform.

The documents and the destination screens are samples. Each one shows the kind of system the fields land in, not a named customer.

  1. Documents arrive from

    • An email inbox, including Gmail
    • A shared drive
    • An upload in your own interface
    • A scanner or a phone camera

  2. Fabrx does

    • Classification
    • Field extraction
    • Validation

  3. Data lands in

    • Make
    • Your own app, over our API
    • Your ERP
SalesforceMicrosoft Dynamics 365Oracle NetSuiteSAPHubSpotZohoWorkdaySageOdooQuickBooksXeroPipedriveFABRX
We build the API. It lands structured fields in any system that accepts an API call, so a new destination is one more endpoint.

What comes back

  • Structured fields, same shape every time
  • A webhook on every result
  • An exception when a value cannot be read
POSThttps://your-app.example/hooks/fabrx
{  "event": "document.processed",  "type": "invoice",  "fields": {    "supplier": "Meridian Supply SRL",    "number": "MS-2026-0416",    "vat_id": "RO99014288",    "date": "2026-07-27",    "due": "2026-08-26",    "currency": "EUR",    "total": 4182.60,    "pages": 2,  },  "exceptions": []}

Your documents stay yours.

We do not store them
Documents pass through and are gone. Fragments are kept only if you switch on data lineage, and that is your choice to make.
Never used for training
Your documents and the data we pull out of them never train a model, ours or anybody else's.
GDPR
PII detection and audit trails are included in the service.
Google and Gmail access
If you ask us to collect documents from your Gmail inbox, Fabrx requests read-only access (the gmail.readonly scope) and uses it only to find and import the messages and attachments you select for processing. Gmail data is never used for advertising and never trains a model, and you can revoke access at any time from your Google Account. The privacy policy sets out the full terms.