Automate the AP inbox. Don't replace the system of record.
The free plan processes 25 invoices a month with unlimited users, takes no credit card and does not expire. You get your own intake address at the end of setup.
The observation the product is built on
Property technology is crowded, but almost all of it points outward: collecting rent, marketing units, sending notices, managing leases and work orders. The inbound half — the several hundred vendor invoices that arrive by email every month, from plumbers, landscapers, utilities and contractors — is handled by whichever member of staff opens the shared mailbox first.
The general AP automation platforms could solve it, but they are built for a different buyer. Their capture model assumes a supplier portal that a long tail of small trades will never adopt. Their coding model assumes one company with one ledger, rather than forty buildings and a dozen owners with separate books. And their commercial model assumes a procurement department with an implementation budget, which is why every one of them makes you book a call before you can find out what it costs.
So the gap is specific: an AP tool whose capture point is the email vendors already send, whose coding dimensions are property and entity rather than department, and which a two-person finance team can adopt on a Tuesday afternoon without a contract.
Who is behind it
This is the second time we have built document capture at scale
InletAP's founder was the founding engineer at Hubdoc — the document capture platform that pulled receipts, statements and bills out of inboxes and portals for hundreds of thousands of small businesses and their bookkeepers, and which was acquired by Xero and has since been folded into Xero itself.
That is where the thesis behind this product comes from. Hubdoc proved that email and forwarding beat every other capture mechanism on adoption, because they are the only ones a vendor is already using. It also made the ceiling obvious: capture hands you a document, and for anyone running accounts payable across a portfolio, the document is where the work starts rather than where it ends. Which building, which account, who approves it, has it already been paid — none of those are capture problems.
The same person also created Haraka, the open-source SMTP server, and maintained it for years before handing it on. InletAP's inbound mail runs on it. For a product whose entire capture path is email, that is not a trivia detail — it is the layer everything else depends on.
How we build
Four decisions that shape everything else
The mail infrastructure is ours
Inbound SMTP is served by our own Haraka mail servers rather than a third-party inbound-email relay — the same Haraka our founder created and maintained for years before handing it on. For a product whose entire capture path is email, owning that layer is the difference between controlling deliverability, duplicate handling and failure semantics and hoping a vendor does.
Scope discipline over feature breadth
No payment rails, no rent collection, no leasing, no attempt to become a property management suite. Every one of those would be a bigger market and a worse product. The wedge is the inbox, and staying inside it is a deliberate constraint rather than a stage we are passing through.
Attributable by default
Nothing changes without an actor, a timestamp and a before/after value, and no role can edit or delete the log. A controller should never have to reconstruct history from an email thread, and an auditor's question should be a filter rather than an afternoon.
Density over decoration
AP specialists live inside one queue all day. The interface is optimized for keyboard speed and information per pixel — a screen you can work down quickly, rather than one that photographs well.
Honesty policy
What you will not find on this site
- No invented customer statistics. There are no case-study percentages anywhere on this site, because we do not have a base of published customer results yet.
- Industry benchmarks are labeled as industry benchmarks, with a link to the source.
- No integration logos for connectors that do not exist — including the property management systems we get asked about most.
- No “SOC 2 ready” badge. We will tell you plainly which certifications we do not hold.
- Limitations are stated on the pages where they matter, not buried in a footnote.
The awkward one
Email routing has a limit worth repeating
InletAP cannot receive mail addressed to a domain you own. That routing is governed by your DNS and your mail provider, and no third party can intercept it — this is true of every vendor in the category, not just us.
What actually works: vendors send directly to an address on your InletAP subdomain, or you auto-forward the mailbox you use today into the InletAP mailbox that should handle it, which is what sets the routing. It takes a few minutes to set up in Google Workspace or Microsoft 365.
An earlier version of this site implied more than that. It was wrong, and it has been corrected — which is roughly the standard we would like to be held to.
Get in touch
We would rather hear a hard question than win an evaluation on a vague answer
Sales and evaluation
sales@inlet-ap.comSupport
support@inlet-ap.comPrivacy and data requests
privacy@inlet-ap.comOr read how it works, the security detail and the pricing, none of which are behind a form.
Start free and run your own invoices through it
25 processed invoices a month, unlimited users, no credit card. Point a few vendors at your intake address and see the extraction, the coding and the audit trail on your own documents.