Email us an invoice. Get the data back, with a score on every field.
Your invoice is read in memory and discarded as soon as the reply is sent. It is never written to disk, and never used as training data or marketing content.
Send an invoice to
test@try.inlet-ap.comAttach a PDF invoice, or forward one you already have. The reply lands in the same inbox you sent it from, usually within a minute.
What comes back
- Vendor
- Rocky Mountain Plumbing97%
- Invoice no.
- RMP-200194%
- Invoice date
- 15 Aug 202696%
- Due date
- 14 Sep 202691%
- Total
- $1,009.3899%
- Tax
- $59.3888%
- PO number
- Not found42%
- Property
- Elm Street Apartments73%
An example, rendered with the same confidence chips your own result uses. 42% on the PO number is the point: a low score is information, not a failure.
How the test works
Three steps, and the third one is the invoice disappearing
- 01
You email the invoice
Send or forward a vendor invoice to test@try.inlet-ap.com. Attachments are read, and so is the body of the email when the invoice is written into it. Our mail server recognizes the address and holds the message in memory — it is never written to the database and never uploaded to storage.
- 02
We reply with the extraction
Usually inside a minute: the fields we read, the confidence on each one, and the line items. The email is the whole result — there is no results page and no link back to your document.
- 03
Everything is discarded
Once the reply is sent, the attachment, its text and the extracted fields are gone. Not deleted later by a scheduled job — never written down in the first place.
The privacy promise
What we do with the invoice you send — in plain terms
Read in memory, then discarded
We do not store your invoice. It is read in memory and discarded as soon as the reply is sent — the file, its text and the fields we read are never written to disk, and never used as training data or marketing content.
A third-party AI provider reads it
Extraction is performed by a third-party AI provider — the same one a paying customer's invoices go through. We say so here rather than in small print, because it is the fact a careful reader most wants and is least likely to be told.
We do keep your address
Your email address and display name are kept as a sales contact, so we can follow up about InletAP. That is the honest limit of the promise above. Every email we send you carries an unsubscribe link, and one click ends it.
Also true
- There is no retention period, because there is nothing retained: no stored invoice, no stored attachment, no stored extracted values, no stored subject or body.
- There is no shareable results link and no results page. The reply email is the result, and it is yours to forward.
- The mailbox answers 5 messages per sender per day, with per-domain and overall ceilings behind it. Past the limit your mail server gets a permanent refusal and you get a bounce that says so.
- Mail is received over TLS.
- The full policy is on the privacy page, and the controls behind it are on the security page.
- Please do not send an invoice you would not be comfortable emailing to a supplier — this is a public test address, not your workspace.
After the test
The same engine, with your own private address
- Your own *.inlet-ap.com intake address, or forward the mailbox you already publish.
- Coding to property, entity and GL account by rules you can read.
- Approval tiers with SLA timers, and an immutable audit trail.
- QuickBooks Online direct, or mapped CSV for Xero, AppFolio, Buildium and Yardi.
Reply in about a minute
Parse, extract, render the reply, discard. The same reading a customer's invoice gets before it reaches a person — minus the storing, coding and routing that only make sense inside a workspace.
One invoice at a time
The test mailbox answers 5 messages per sender per day. It is a demonstration, so it is rate limited rather than metered.
Questions about the test mailbox
Send one more — a messier one
Scanned, multi-page, or one bill covering three properties: the awkward invoices are the useful test. Email it to the address above and read the fields in the reply. Nothing is stored either way.