How to split one invoice across several properties in Xero

Yes, one Xero bill can be coded to several properties. The dimension that carries a property in Xero is a tracking option, tracking sits on each line of a bill rather than on the bill as a whole, and a bill can hold as many lines as the invoice has shares. The ceiling is Xero's, not your software's: a Xero organization defines at most two tracking categories in total, so your properties have to be one of the two you already use. The work that is actually hard is not the entry — it is making the shares add up to the invoice exactly, every month, and being able to explain a year later why one building took a cent more than another.

This page is about coding one supplier bill to several buildings. It is not about splitting a payment between two bank accounts, and it is not about part-paying a bill during bank reconciliation. Those are different jobs and most of what search engines return for this question answers one of them instead.

Where a property can live on a Xero bill

A Xero bill (an ACCPAY invoice, in Xero's own vocabulary) puts some things on the header and some things on each line, and the difference decides whether a split is possible at all.

That last row is the whole answer. Because tracking is a line-level field, one bill can carry Maple Court on line 1 and Elm Terrace on line 2 without any workaround, any journal, or any second bill.

It is worth knowing what the other ledger does here, because the advice you find for one is frequently repeated for the other and it does not port. In QuickBooks Online a class is also a line-level field, so a class-based property split behaves much like Xero's. A Location, however, is a bill header field — one per bill, never one per line — so a company that models its properties as Locations cannot split a bill across them at line level at all. And coding a line to a unit as a sub-customer is a QuickBooks-only idea; Xero has no equivalent and inventing one would quietly spend a tracking slot you only have two of.

The two-category ceiling, and what it forces you to choose

Xero allows two tracking categories per organization. Not two options — two categories, each of which may hold many options. So an organization that already tracks, say, Region and Department has no slot left for Property, and something has to give.

The three honest ways out, none of which is a trick:

1. Spend one of the two slots on the property. The most common answer for a property manager, because the building is the dimension every report is cut by.
2. Use the account code as the second dimension. A chart of accounts that already separates the work (repairs, grounds, utilities) does not need a tracking category to say the same thing twice.
3. Keep separate books per ownership entity. Where owners genuinely require separate books, the property split partly disappears into the organization split — and one invoice then becomes one bill in each set of books rather than one bill with many lines.

What you cannot do is have three tracking categories. Any page that offers you a way around that number is describing something other than Xero.

The arithmetic, which is where the real errors live

Splitting $1,000.00 three ways gives each share $333.3333…, which is not a number of cents. Somebody has to decide who takes the odd penny, and "the spreadsheet rounded it" is not an answer you can give an owner.

The rule worth adopting — the one inletAP implements, and the one to reproduce by hand if you are doing this in a spreadsheet — is the largest remainder method, also called Hamilton's method:

1. Work out each row's exact share.
2. Give every row its whole cents.
3. Hand out the leftover cents one at a time, largest fractional part first.

Three equal shares of $1,000.00:

And a case where the fractions do not tie — $9,600.00 split by unit count across buildings of 48, 40 and 30 units:

Two cents were left over, and they went to the two rows whose exact shares sat furthest past a whole cent. The rejected alternative is the one most spreadsheets use: round everything down and dump the whole remainder on one row. It is visibly unfair on a bill that recurs monthly, because the same building carries the entire rounding error twelve times a year.

Three rules go with it, and they are worth writing into your own procedure whatever software you use:

• Work in whole cents, never in percentages multiplied back out. A percentage is a description of the split. The cents are the split. Show the percentage to four decimal places if you show it at all — 33.33% three times is not a hundred.
• Balance exactly, not "within a cent". Twelve rows each half a cent out is six cents of real money, and a tolerance wide enough to absorb that is wide enough to absorb a genuine mis-coding.
• Record which row took the extra penny. Recomputing it later agrees with the original answer until the day somebody edits a unit count, and then it quietly does not.

Doing it by hand, and what it costs

Entering the split directly in Xero is one bill with one line per building, each line carrying that building's amount, its account code and its tracking option, and the lines adding to the invoice. For a two-way split of a roofing bill, that is a perfectly reasonable five minutes.

The cost is not the first invoice. It is the landscaper who bills the same five buildings on one page every month, on a distribution the owners agreed in writing two years ago — and the person keying it re-derives that distribution by hand, from memory, twelve times a year, with the rounding decided freshly each time. That is where the errors that survive an audit come from, and it is the case worth automating.

What inletAP does with the same invoice

inletAP reads the invoice, splits it, and posts the finished bill into Xero. The mechanism, stated plainly:

• Five ways to divide the money: by percent, evenly, by unit count, by square footage, or by typed amounts. The unit and square-footage bases read the figure off each property record, and a building with no square footage on it makes that button unavailable and names the building, rather than treating the missing figure as zero.
• Nothing saves until it balances. A chip above the grid reads Balanced, Remaining $X or Over by $X, and the check is at zero drift. Typed amounts are stored as typed and never re-rounded; every computed basis uses the largest-remainder rule above and marks the row that took the extra cent.
• A saved split is a template. Save the distribution once and the next invoice from that vendor is offered it as a one-click button with its shares printed on it. Templates hold fixed percentages, so next month's $9,742.15 distributes on the same shares as this month's $9,600.00.
• It posts as one Xero bill. One line per share, each line carrying its account code, its tax rate and the property as a tracking option, with the supplier's own invoice number as the reference and the source PDF attached where the invoice arrived with one.
• Every save is in the audit trail with the actor, the time, and the before and after totals — including which template was applied and the weights it computed. "Where did this 40 / 30 / 30 come from?" has a written answer.

Split coding, the five bases and saved templates are included on every plan, including the free one, which is 25 documents a month with no card.

The limits, stated out loud

• inletAP matches a property to a tracking option that already exists in your Xero organization. It does not create tracking categories or options in Xero, and it cannot raise Xero's ceiling of two categories.
• inletAP is not a Xero certified app and is not listed on the Xero App Store. You connect it from inside inletAP. Bills travel one way, into your books; nothing in Xero is edited or overwritten, and there is no such thing as a sync here.
• It pays nothing. There are no ACH or check rails in the product at all, so nothing on this page stops, releases or schedules a payment.
• One printed line can be split up to 150 ways, one invoice can carry 200 allocations, and a workspace holds 200 templates. Those are guard rails against a pasted spreadsheet, and they are the same on every plan.
• Once a bill has posted, the coding cannot be re-cut in inletAP. Edit the bill in Xero, or void it and export again.
• QuickBooks Online is the other shipped connector, and it is not the same mechanism: a class is per line, a Location is a header field and cannot be split at line level, and one invoice cannot span two QuickBooks companies — it fans out into one bill in each.

Common questions

Can one Xero bill be coded to more than one property?

Yes. Xero puts tracking on each line of a bill rather than on the bill header, so a single bill can carry a different property on every line, with its own account code and its own tax rate.

How many tracking categories can a Xero organization have?

Two in total. That is Xero's own ceiling rather than a limit imposed by any third-party product, so a property manager who wants to track buildings has to make the property one of the two.

Is splitting an invoice across properties the same as splitting a payment?

No. Splitting an invoice is coding one supplier bill to several buildings before it is approved. Splitting a payment is settling one bill from more than one source, which happens later and is a separate job.

What happens when the shares do not divide evenly?

Use the largest remainder method: give every row its whole cents, then hand out the leftover cents one at a time, largest fractional part first. The split then adds up to the invoice exactly, and the row that took the extra penny is a recorded fact rather than an accident of rounding.

Can inletAP create a tracking category in Xero for me?

No. inletAP matches a property to a tracking option that already exists in the organization, and it never creates or renames anything in your chart of accounts or your tracking categories.

Does this work the same way in QuickBooks Online?

Only partly. A QuickBooks class sits on the line and behaves much like Xero tracking, but a Location is a bill header field and cannot be split at line level, coding a line to a unit as a sub-customer is QuickBooks-only, and one invoice cannot span two QuickBooks companies — it becomes one bill in each.

Where to go next

• Connecting Xero — the mapping, what a posted bill carries, and what happens when Xero refuses one.
• Splitting an invoice across properties — the full procedure, screen by screen.
• Allocation rounding — the exact rule for the odd cent, and who takes it.
• Allocation templates — saving a distribution so next month costs one click.
• Xero — what the connector does, in one page.
• Splitting one invoice across properties — the product page, including what happens when the buildings keep separate books.