Plans and limits
InletAP charges for documents, not for people. This page sets out what each plan includes, what counts as a processed invoice, and what happens when you go past your allowance — which, on the free plan, is a state you can see in the inbox rather than a surprise on a bill.
The plans
| Plan | Price a month | Included documents | Extra documents |
|---|---|---|---|
| Free | $0 | 25 | Not charged — held instead |
| Starter | $39 | 150 | $0.35 each |
| Growth | $99 | 500 | $0.25 each |
| Pro | $249 | 1,500 | $0.18 each |
Annual billing saves 17%, which is two months. Every plan, the free one included, has unlimited users, properties, vendors and legal entities.
Prices are in US dollars and exclude sales tax, which is added where it applies. Some US states tax software subscriptions and some do not, so the amount follows the billing address you enter at checkout and is shown there before anything is charged.
That last point is deliberate rather than generous. Per-seat pricing makes companies ration approvers, and the approver you leave out to save a license is usually the property manager who knows whether the work was done. Per-entity pricing punishes exactly the customer we are built for, the one running a company per building.
There is no contract, no minimum term and no implementation fee. Plans change or cancel from billing settings.
What counts as a processed invoice
One invoice document that InletAP extracted fields from. Per document, not per email.
| Arrives | Counts as |
|---|---|
| An email with one invoice attached | 1 |
| An email with three invoices attached | 3 |
| An invoice typed into the body with no attachment | 1 |
| A newsletter, an auto-reply, a bounce, a calendar invite | 0 |
| The same invoice forwarded twice and caught as a duplicate | 1 |
| An invoice you correct and re-correct in review | 1 |
The count happens at extraction, which is the expensive step, and it happens once per document. A document that bounces back through review, gets re-extracted, or is retried after a failure is still counted once.
Mail that is judged not to be an invoice is diverted to the filtered view before extraction, so it never touches the allowance. This is why the not-an-invoice check sits where it does: moving it one step later would mean charging you for your own newsletters.
One case is easy to miss. An invoice the model could not read at all — a photograph of a handwritten docket, say — is counted when a person finishes keying it in and sends it on. The alternative is that the documents costing your team the most effort are the only free ones, which would be an odd incentive to build.
Going over the allowance
On a paid plan, nothing stops. Extra documents are processed and billed at the plan's overage rate, and usage is visible in settings before the invoice arrives.
The free plan is a hard cap instead of a bill. Nothing is charged, and documents beyond the twenty-fifth are parked in the held_quota status.
Held is not lost
A held document has already been received, stored and parsed. What has not happened is the extraction. The source text is on file, so releasing one costs only the reading.
The inbox shows a banner counting the held documents. They are released in two ways:
- You upgrade. Everything held is released, because a paid plan has no hard cap to hold it against.
- The period rolls over. A new calendar month brings a new allowance, and held documents are released into it, up to whatever is left of it.
The second case is worth stating plainly: if you are twenty documents over on a 25-document plan, the roll-over releases what fits and holds the rest. The cap would be decoration if it worked any other way.
Held documents stay listed the whole time. Nothing is deleted, and nothing is quietly dropped on your behalf.
What else differs between plans
Volume is the main axis, but not the only one.
| Capability | Free | Starter | Growth | Pro |
|---|---|---|---|---|
| QuickBooks Online sync and CSV export | Yes | Yes | Yes | Yes |
| Intake mailboxes | 1 | Unlimited | Unlimited | Unlimited |
| Rules engine and approval tiers | — | Yes | Yes | Yes |
| Nightly QuickBooks reconciliation | — | Yes | Yes | Yes |
| SFTP delivery | — | — | — | Yes |
| SSO | — | — | — | Yes |
| Unlimited users, properties, vendors, entities | Yes | Yes | Yes | Yes |
Accuracy is not a plan feature and neither is export. A free workspace gets the same extraction and the same QuickBooks connector as a paid one. Gating the part that proves whether the product works would tell you nothing useful about it.
Enterprise exists for custom volume, SSO/SAML, a DPA and a support agreement, and is priced by conversation rather than by table.
Split coding limits
Splitting one invoice across several properties has three caps. They are guard rails against a pasted spreadsheet rather than accounting limits, and no real portfolio split comes near them.
| Limit | Value |
|---|---|
| Allocations on one printed line | 150 |
| Allocations on one invoice | 200 |
| Saved allocation templates | 200 |
The per-invoice cap is deliberately lower than 150 multiplied by however many lines an invoice has. Every allocation becomes a bill line in your ledger, an approval slice to route and a row to read back later, and a four-thousand-line bill is not a feature anybody asked for. See splitting an invoice.
Limits your ledger imposes, which we do not control
Two QuickBooks Online limits shape how a portfolio can be modeled, and they are worth knowing before you design your books rather than after.
QuickBooks Plus allows 40 classes and locations combined. Not 40 of each — 40 in total. QuickBooks Advanced removes the limit.
The consequence is blunt: a portfolio of 41 or more buildings cannot model property-as-class on QuickBooks Plus. Since property splitting reaches the ledger through the class on each bill line, that is a fact a customer needs before they hit it. The routes past it are sub-customers, which are unlimited and also per line, or QuickBooks Advanced.
QuickBooks Plus also caps the chart of accounts at 250 accounts, which portfolios reach for a different reason — a GL structure that carries the property in the account name rather than in a dimension.
A parent customer may hold sub-customers up to four levels deep, so entity, property and unit fit comfortably as a hierarchy. A customer that is a QuickBooks Project cannot contain sub-customers at all.
These are Intuit's limits on Intuit's product. InletAP reads what the connected company supports and says what it can and cannot do with it, rather than posting coding the ledger will drop. See multi-entity QuickBooks.
Billing periods and usage
Usage is counted per calendar month in UTC, and the current figure is shown in settings. Upgrading mid-month changes the allowance you are measured against from that point; it does not retroactively re-price documents already processed.
If a payment fails, the workspace keeps working while the card is retried and you are told about it in the app. We would rather chase a card than stop reading a customer's invoices in the middle of a close.
Where to go next
- Invoice statuses — including
held_quotaandfilteredin context. - Why hasn't my invoice appeared? — the quota check is one of the six things to rule out.
- Security and data — what happens to the documents you are being charged for.
- Quickstart — if you have not yet run one invoice through.