A distribution run is the batch process that pays every owner in a portfolio for a closed period. It happens after the statements are produced, it draws on a balance that has already been calculated, and it should be the least interesting part of the month.

For most operators it is not, because the run is assembled by hand: a list pulled from one system, payment details from another, a bank file built in a spreadsheet, and someone checking it twice because a mistake here moves real money to the wrong place.

This is the operational half of owner reporting. The terminology question of what to call the payment is separate and worth getting right, but it does not change the mechanics below.

Frequency

Three patterns are common, and the choice is usually set by the management agreement and operating policy.

• Monthly is common for residential portfolios. Rent arrives monthly, owners often expect regular income, and the shorter cycle limits the amount held between runs.

• Quarterly is also used in commercial portfolios and with some institutional owners, particularly where reporting is already quarterly or the amounts are larger.

• On request can turn a batch process into a series of one-offs, each needing its own balance check and payment review. If you allow it, define the conditions in the management agreement rather than handling them informally.

Whichever you use, set it per owner in the agreement rather than per run. An operator running monthly for most owners and quarterly for three commercial ones needs the system to know which is which, not a person to remember.

When in the Month

The run sits after the close, not alongside it.

Statements are produced from a period that has been reconciled, the checks have passed, and someone has reviewed the output. Only then does money move. Paying before the review means paying an amount you have not verified, and recovering an overpayment from an owner is far harder than delaying a payment by two days.

The gap between statement release and payment is a decision worth making explicitly. Some operators release both together, which is cleanest from the owner's perspective. Others release statements first and pay two or three days later, giving owners a chance to query before the money moves. Both work. A variable gap can create unnecessary uncertainty, because owners tend to form expectations around when payments normally arrive.

The cutoff and sign-off sequence covers what has to be true before either happens.

Deciding the Amount

The amount available for distribution is not necessarily the same as the net income for the period.

Work down in this order:

1. Opening balance held

2. Plus receipts for the period

3. Less disbursements made on the owner's behalf

4. Less fees earned under the agreement

5. Less any reserve requirement or holdback

6. Less any negative balance being recovered

7. Equals the amount available to pay

Two checks before the number is final.

1. Is the balance actually there?
   A calculated balance and cleared funds are different things. A rent payment that has not cleared may not be available to distribute, depending on the payment method, account structure and your funds-availability policy. Paying against uncleared funds is how an operator ends up temporarily funding one owner from money belonging to another.

2. Is it worth sending?
   Set a minimum. Below it, the balance carries to the next run. A small payment may cost more in payment and reconciliation effort than it is worth sending separately, and owners generally prefer one meaningful payment to two trivial ones.

Where the available amount is negative, nothing is paid and the balance carries. The handling of negative owner balances is a decision in its own right.

Payment Rails

Four options in practice, with different trade-offs.

ACH is the working default for routine distributions. Wires suit exceptions, typically a large commercial distribution or an owner who needs funds by a specific date. Cheques persist because some owners want them, and every one you send creates an uncashed-item problem to monitor.

Two things to settle whichever rail you use.

• Bank detail changes. A request to change payout details deserves particular scrutiny, because it can be used to redirect a payment. Verify it out of band, by calling a number you already hold rather than one supplied in the message, before anything changes. Record who verified it and when.

• Payment references. Use the same identifier on the payment as on the statement. An owner matching a bank line to a statement should not have to guess.

Running the Batch

The steps that matter at volume.

Build the list from the ledger, not from a spreadsheet maintained alongside it. Every balance in the run should be the closing balance of a ledger that has already passed its checks.

Exclude before you pay, not after. Owners on hold, owners with a negative balance, owners below the minimum, owners whose details are mid-verification. Each exclusion should have a reason recorded, because the question "why did this owner not get paid" arrives about a day later.

Review the totals. The sum of the batch should equal the sum of the distributions shown on the statements you released. A difference means something changed between the two, and finding out what is easier before the file goes to the bank than after.

Check the exceptions manually. New owners in their first run, owners whose amount is significantly different from usual, and anyone whose bank details changed this period. These are where the errors cluster.

Record the payment in a way that reflects its actual status, including pending, failed and returned transactions, so the ledger can be reconciled to the bank.

When a Payment Fails

Payment returns happen, and the handling is what separates a tidy process from a messy one.

An ACH return usually arrives one to several business days after the payment. If the ledger recorded the distribution when the original payment was released, the return now requires a reversal or other corrective entry so the owner's balance reflects the funds still held.

The sequence:

1. Reverse the distribution on the owner's ledger

2. Record the reason, usually a closed account or incorrect details

3. Contact the owner and verify new details out of band

4. Reissue as a separate transaction rather than editing the original

Do not simply amend the original entry. The payment was initiated, it failed, and both events are part of the record. Editing it away leaves a ledger that cannot be reconciled to the bank, which is the structural problem worth avoiding rather than creating.

The same applies to an uncashed cheque. It stays outstanding on the reconciliation until it clears or is voided, and voiding it is a posted transaction, not a deletion.

Owners Who Need Different Treatment

Four cases that break a straight batch.

1. New owners. The first distribution may cover a partial period and may include onboarding-related adjustments. Worth a manual look and a short note.

2. Owners leaving. A final distribution needs a decision on the reserve, any outstanding invoices expected, and how long you hold a residual balance before releasing it. Settle this at the point of termination rather than three months later.

3. Owners in dispute. Where an amount is contested, distribute the undisputed portion and hold the rest with a labelled line. Withholding the entire payment escalates a small disagreement.

4. Owners across several entities. Balances should generally be kept separate by owning entity rather than offsetting a surplus in one against a shortfall in another. Separate balances, separate runs, separate payments.

What to Keep

For each run: the batch list with amounts, the exclusions with reasons, the totals check, who approved release and when, the bank confirmation, and any returns with their resolution.

None of this is onerous if it is produced by the process rather than assembled afterwards. All of it is what you reach for when an owner asks, in March, why their January payment was what it was.

Frequently Asked Questions

1. How often should owner distributions be paid?
Monthly is common for residential portfolios, while quarterly schedules are also used in commercial and institutional settings where reporting runs on the same cycle. The frequency should be set per owner in the management agreement rather than decided per run.

2. How is the owner distribution amount calculated?
Opening balance held, plus receipts for the period, less disbursements made on the owner's behalf, less fees earned, less any reserve or holdback, less any negative balance being recovered. The result may differ materially from the net income shown for the period, because reserves, opening balances and prior-period items all affect what is available.

3. What is the best payment method for owner distributions?
ACH is the practical default for routine runs: low cost, with settlement ranging from same day to several business days depending on how it is sent. Wires suit exceptions where funds are needed on a specific date. Cheques persist where owners prefer them and create uncashed items to monitor on the bank reconciliation.

4. What happens if an owner distribution payment fails?
Reverse the distribution on the owner's ledger so the balance reflects funds still held, record the reason, verify new payment details out of band, and reissue as a separate transaction. Do not edit the original entry, because the failed payment is part of the record the bank reconciliation depends on.

5. Should there be a minimum distribution amount?
A minimum is worth setting. Below it, the balance carries to the next run rather than generating a payment that costs more in handling than it delivers. Document the threshold in the management agreement or owner payment policy so owners are not surprised by a month with no payment.

6. Can a distribution be paid before the month-end close is finished?
Generally, owner payments should follow the close and review process established for the portfolio. Paying before the checks have passed means paying an amount that has not been verified, and recovering an overpayment from an owner is considerably harder than delaying a payment by a day or two.

The Run Should Be Boring

Every difficult distribution run traces back to the same cause: the balance being paid was calculated somewhere other than where it is recorded. A list in a spreadsheet, a report exported and edited, payment details held in a separate file.

When the batch is built from the ledger that already passed its checks, the run stops being a reconstruction and becomes a release. The interesting work moves to where it belongs, which is the exceptions.

RIOO built on NetSuite, so owner balances and property accounting can be maintained within the same environment, with statements and reporting tied to the underlying financial records.

For what each figure on the resulting statement means, the line-by-line breakdown covers it.

Note: Guidance in this article is general. Distribution frequency, minimum thresholds, reserve requirements and trust account rules vary by management agreement and by state.