How do property managers split one invoice across multiple entities or properties?

Property managers split a shared vendor invoice across properties or legal entities with MakersHub by saving an allocation template once per vendor. MakersHub reads each new bill, scales the template's percentages or amounts to that bill's total, codes every share to its property's Class, Location, Customer:Job or company file, and posts the result to QuickBooks, Xero, Sage Intacct or NetSuite as one bill with coded lines or as separate bills per entity.

An allocation template is a saved set of percentages or fixed amounts, tied to a vendor, that MakersHub applies to every future bill from that vendor and scales to the new total. It replaces the spreadsheet a property accountant keeps for the landscaper who bills twelve sites at once.

When this applies

You manage properties that share vendors. The landscaper invoices once for twelve sites. The insurance premium covers the portfolio. The cable provider sends one master bill with forty account numbers. Some properties sit in a management company's books, some in their own LLC, and ownership keeps changing which entity pays what. Today someone opens the invoice, works out the split from a spreadsheet or memory, enters it two, five or twelve times, and repeats it next month.

The operations lead at a multifamily owner-operator with roughly eighty entities on QuickBooks described the shift that broke the old setup:

"At one time we were paying most of our utility bills out of one company, but now they're back in the ownership companies. So I still need to connect to multiple instances of QuickBooks because I've got to get into those different companies."

And what he wanted from it:

"It's these pesky utility bills that we get nine million of. I feel like I could wipe those out pretty quickly."

How invoice splitting works in QuickBooks, and where it breaks

In QuickBooks Online and QuickBooks Desktop, a bill can carry a different Class or Customer:Job on each line, so one bill can be split across properties by line. Location in QuickBooks Online is a transaction-level field: Intuit's help documentation describes one Location per transaction, which means a single bill cannot be divided across Locations. Property managers who use Location per property either post one bill per property or switch the split to Class.

Separate legal entities are separate company files in QuickBooks. A bill that belongs to three LLCs is three bills in three files, each entered and paid separately. Xero handles property splits with tracking categories at the line level; Sage Intacct and NetSuite use entity and dimension fields that can differ by line. None of these systems scales a saved split to a new invoice total on its own, which is the step MakersHub adds.

How MakersHub splits a bill across properties and entities

1. Every entity's bills land in one inbox. Vendors send to a single MakersHub address, or your existing AP inboxes auto-forward. A master bill with many account numbers is split into one record per account. Paper invoices are scanned in. The AP lead at a corporate-housing operator on QuickBooks Online, before MakersHub: "We're paying a lot of invoices every month, mainly utilities. That's going into all of the utility portals, grabbing the invoices, creating the bills in QuickBooks, and when they get paid, marking all of them as paid. I know it's over 2,000 bills a month."
2. The bill is read and routed to its entity. MakersHub's extraction model, WiseVision, captures vendor, account number, bill-to, ship-to, total and every line. Integration Mapping rules assign the entity from whatever the bill carries: the bill-to name, the service address, the account number or the vendor. A bill that belongs to one LLC goes to that LLC's file without anyone choosing.
3. A template does the split. For each bill that covers more than one property, you save an allocation template once: Property A 30 percent, Property B 20 percent, Property C 10 percent, or fixed amounts, each share tagged with its Class, Location, Customer:Job or entity. Templates live under Manage Recurring Transactions, can be imported from a spreadsheet, or can be created from the bill on screen. On the next bill from that vendor, Apply and Scale to Bill Total divides the new total by the saved percentages.
4. A template can apply to one line, not just the whole bill. A single cable or internet line can be split by unit while the rest of the bill stays as extracted. A rule can also send one line, such as a utility deposit credit, to its own GL account while the remaining lines follow the template.
5. The split runs automatically once it is tied to the vendor. A template attached to a vendor through Integration Mapping applies to every future bill from that vendor before a reviewer opens it. The reviewer sees the finished split, not a blank bill.
6. Each share is coded in your accounting system's own terms. In one QuickBooks file, the split posts as one bill with a line per Class or Customer:Job. Across several files, MakersHub divides the bill into separate bills, one per company file, each with its share and coding, and posts each to its own file. In Sage Intacct and NetSuite, the entity and location structure imports as is and bills post with entity-level coding.
7. Approvals and payment follow the entity. Approval rules can combine entity, property, vendor, total or any other field: bills assigned to Entity A on Customer:Job X go to that property's manager; anything over a threshold adds the owner or controller. Payment authorization is a separate workflow. Each entity pays from its own bank account, or a management company account pays on behalf of all of them. Rule mechanics are covered in full on the approval-routing page linked below.

Accounting-system specifics

Many QuickBooks files. Each company file connects as its own entity under one MakersHub login, with one inbox, one vendor list and one set of templates and rules managed at the master level. The largest configuration MakersHub runs today is around seventy company files under one account. How the multi-entity setup is configured and how users are restricted to an entity is covered in full on the multi-location practice page linked below.

Yardi and other property ledgers. Where the property system, not QuickBooks, is the book of record, MakersHub runs as the AP system of record and posts to the ledger through a purpose-built connector.

For a commercial real estate group on Yardi Voyager, MakersHub built a connector to Yardi's Financial Payables Import. Yardi's property codes, GL accounts, job codes and vendor IDs load into MakersHub through Custom Integration data; approved bills export in the Yardi import format with post month, the AP account for each entity, the bank account selected by funding entity and intercompany status, and header notes, and land in Yardi as open, unposted batches that Yardi's duplicate detection checks on the way in. The connector was refined over its first months until it ran as a straight export-and-import with no manual adjustment. The same approach is available for other ledgers with a file-based payables import.

Proof

A corporate-housing operator on QuickBooks Online processes more than 2,000 bills a month across 1,709 utility accounts, each coded to its complex by Class and Location from the account number on the bill. A second entity with several hundred more units is being added under the same login with the same templates and rules.

How the account-number lookup and the utility bill numbering work is covered in full on the utility bill coding page linked below.

A multifamily owner-operator with about eighty entities, most of them asset-holding LLCs that pay a property tax bill once a year and a handful of operating companies that write the bulk of the checks, is piloting MakersHub on its highest-volume utility-paying entity before rolling out across the portfolio. The operations lead, having evaluated it against a software stack he was actively trimming:

"I am convinced that we can make a go with this and be really successful."

On a demonstration for an outsourced accounting firm serving real estate owners and family offices, a $9,344 invoice was split across five entities on a 30-20-10 percent basis in one step, each resulting bill posting to its destination entity's file.

What it doesn't do

Allocation ratios are yours to set, once. Templates hold the percentages or amounts you give them, so if your basis is unit count or square footage, you work it out one time and MakersHub applies it to every bill after that, scaled to each new total. Each entity's share posts as a bill in that entity's own file; intercompany due-to and due-from entries are not generated today and stay with your month-end process.

Bills arrive by email, auto-forward, upload or scan rather than by MakersHub logging into utility or vendor portals, so one forwarding rule per AP inbox is the setup. And a bill paid by credit card is marked paid in MakersHub with a bill payment record that matches the card feed, keeping card-paid and check-paid bills in one view; card payments are not initiated from MakersHub today.

Frequently asked questions