One invoice. Five buildings. No spreadsheet in the middle.
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.
Why one invoice for five buildings is a manual job today
Coding an invoice to a property is a solved problem. Coding one invoice to five properties, in the right proportions, to the cent, is where every AP process in property management quietly falls back to a human and a spreadsheet.
The work is real and it is repetitive. Read five service addresses out of the line-item text. Decide the basis — square footage this month, unit count for the pest control contract, an even split for the shared dumpster. Compute the shares. Check the total. Fix the rounding, because a three-way split of an odd number never lands on its own. Then key it into the ledger as five lines, or as three bills if those buildings are owned by three partnerships with three sets of books. None of that is judgment. All of it is typing, and every keystroke is a chance to put a building's money on another building's owner statement.
InletAP does the same job on the document. The properties are read off the invoice, with the text they were read from attached to each one. The split is computed on a basis you pick and the amounts are held as integer cents, so the five rows add to $12,480.00 and not to $12,479.98 — the row that takes the odd cent is chosen deliberately and marked. And when the split crosses ownership entities that keep separate books, the export preview says so before you press the button: one invoice, three bills, three QuickBooks companies, each linked back to the same original email.
That third part is the one worth being precise about. Splitting an invoice across properties is table stakes — AppFolio, Yardi, Nexus and Propertyware all do it, and we are not going to pretend otherwise. Splitting one invoice across separate QuickBooks companies is the part the SMB tier does not do: Ramp's help center answers its own question with “Not at this time”, and Buildium, DoorLoop and TenantCloud have nothing. Only Yardi and Sage Intacct do it natively, and neither publishes a price.
One QuickBooks constraint decides whether any of this works for you, and it is better learned here than at export time. A QuickBooks bill carries one Location for the whole document, and classes and customers on each line. So properties tracked as QuickBooks Locations cannot be split across a single bill at all — only properties tracked as classes can. InletAP checks which one your company uses and says so before the export runs, not after it.
Capabilities
What happens when a five-property invoice arrives
The addresses come off the invoice
Property aliases are matched against the document text, so five buildings named in the line items arrive as five pre-filled rows, each with a confidence and the exact text it was read from. A suggestion saves nothing until you accept it, and the evidence goes into the audit log.
The pennies are exact
Integer cents end to end, and the odd cent from a three-way split is handed to a specific row by largest remainder rather than dropped. The remaining amount has to read $0.00 before anything can be saved — no tolerance, not one cent.
Three companies, three bills
Where the properties on one invoice keep separate books, the document posts as one bill per connected QuickBooks company, each carrying only that company's share. The export preview names the companies and the amounts before you press Export.
Five ways to compute the split
By amount, by percentage, evenly, by unit count or by square footage — the last two read from the property records you already keep, and record the figures they used so a stale basis can be spotted later.
Save it, then stop doing it
Any split saves as a named allocation template, optionally tied to a vendor. Next month's invoice from the same vendor is one action, already balanced. Templates built on square footage or unit counts report their own drift when the underlying numbers move.
Approvals scoped to one building's share
An approval can cover one property's slice rather than the whole invoice, so a property manager signs for their own building. Auto-approval is measured against the document total by default, because a $50,000 invoice cut into twelve $4,999 slices must not clear a $5,000 threshold twelve times.
Why this one
The parts that are genuinely different, and the parts that are not
- One document posts as several QuickBooks bills, one per connected company — the thing the SMB tier does not do, and the reason the fan-out matters more than the grid.
- The unit of fan-out is the company, not the ownership entity. Three partnerships that share one set of books stay on one bill, told apart by the class on each line, because that is what the accounting actually is.
- A keyboard grid, not drag-and-drop. Nobody in this market markets drag-and-drop for allocations; Yardi's documented workflow is about tab order, and so is ours.
- Every allocation records its basis and the figures it was computed from, so an auditor asking why one building took 33.33% is answered from the event log rather than from memory.
- No intercompany due-to / due-from posting. Consolidation is a general-ledger job and InletAP is not a general ledger.
- No occupancy-based or rental-income-based allocation. InletAP holds neither figure, and a basis that computes nothing is worse than no basis at all — AppFolio has rental income because AppFolio has the rent roll.
- No splitting of payments. InletAP does not move money; it produces coded, approved bills.
Compare
Who else splits an invoice, and how far
| InletAP | AppFolio | Yardi Voyager | Ramp | Buildium / DoorLoop / TenantCloud | |
|---|---|---|---|---|---|
| Split across properties | Yes | Yes — one expense across up to 400 properties in the same group, portfolio or owner | Yes — property lists and a distribute function on the payable | Yes — line-item splits across departments, locations and custom fields | No published bill-level allocation |
| Split across separate companies | Yes — one bill per connected QuickBooks company | Within one AppFolio database | Yes — cross-entity transactions | No — “Is splitting across entities supported? Not at this time.” | No |
| Saved allocation template | Yes — named, optionally per vendor, with drift reporting | Implicit, through property group, portfolio or owner | Yes — Distribution AP templates | Yes — allocation templates, importable by CSV | No |
| Basis options | Amount, percent, even, unit count, square footage | Unit count, square footage, rental income, even spread | Predefined percentage lists | Percent and amount | — |
| Published price | Yes — free plan upward, this feature included | Quote-based; a partner analysis puts Core near $1.40 per unit with a $280/month minimum | Quote-based, enterprise | Included in Ramp Plus, a paid tier | Published, roughly $58–$479 a month |
Competitor rows checked 2026-08-30 against vendor help documentation and, for AppFolio and Buildium pricing, third-party partner analyses — treat those two price cells as indicative rather than as a quote. Sage Intacct and Yardi are the only two products found that split across separate ledgers natively, and neither publishes a price.
Pricing
Included, not an add-on
Prices are in US dollars and exclude sales tax, which is added where it applies.
Paid plans renew automatically at the price shown — every month, or every 12 months on annual billing — until you cancel. Cancel any time in billing settings: the next renewal stops and you keep the period you have already paid for.
Splitting invoices — common questions
Try it on the invoice that annoys you most
Pick the vendor whose invoice gets retyped into a spreadsheet every month, forward one to your intake address, and split it. The free plan covers 25 invoices a month with no credit card, which is enough to find out whether the totals and the templates hold up on your own numbers.