One invoice. Five buildings. No spreadsheet in the middle.

Yes — as one bill per company. A QuickBooks bill is scoped to a single company file and there is no cross-company posting anywhere in the QuickBooks Online accounting API, so an invoice whose properties keep separate books becomes two bills, each carrying only that company's share and each linked back to the same original document. The export preview tells you how many bills you are about to create, and in which companies, before you press Export. What it is not is an intercompany journal: inletAP posts no due-to / due-from entries and does not attempt consolidation.

Then this feature cannot work for you as things stand, and you should know that now rather than after a failed export. 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. Moving properties from locations to classes is a change to your chart of accounts that only you can make. If you make it, everything on this page applies; if you do not, inletAP still codes and posts one property per bill.

Exactly, every time. Money is held as integer cents from the moment the split is computed to the moment the bill is written, and the odd cent left by splitting three ways is handed to a specific row by the largest-remainder method rather than dropped or spread. Nothing can be saved while the remaining amount is anything other than zero — not a cent of tolerance, because twelve allocations each half a cent out is six cents of real money and a tolerance wide enough to absorb it is wide enough to absorb a genuine mis-coding.

From the invoice itself. Property aliases — the service addresses and building names you already keep against each property — are matched against the text of the document, and each suggested row carries a confidence and the line of text it was read from. Nothing is saved from a suggestion until a person accepts it, and that evidence is written into the audit trail, so the answer to “why did Elm Terrace get this line?” is a record rather than a recollection.

Yes. Any split saves as a named allocation template, optionally tied to a vendor, and applying it to next month's invoice from the same vendor is one action. Templates computed from unit counts or square footage record the figures they were built on, so when a building's square footage changes the template tells you it has drifted instead of quietly allocating on last year's numbers.

By whoever your policy says approves that building's spend. An approval can be scoped to one property's share, so a property manager signs for their own slice rather than for a $12,000 invoice that is mostly somebody else's, and you choose whether approvers see the whole document or only their own slice. Auto-approval is evaluated against the document total by default and not against each slice — a $60,000 invoice cut into twelve $4,999 slices would otherwise clear a $5,000 threshold twelve times with nobody looking at it.

150 allocations on a single printed line and 200 across the whole document. Those are our limits, not QuickBooks limits, and they exist because somebody eventually pastes a spreadsheet into the grid. A portfolio-sized split is nowhere near either number.

No. inletAP does not move money — there are no ACH or check disbursement rails in the product — so a split invoice produces correctly coded, approved bills and payment continues to happen wherever it happens today. If what you actually need is three cheques from three bank accounts, that is a payments feature and this is not it.