The multifamily month-end close checklist, AP section

Close is late for two reasons, and only one of them is about work remaining.

The first is that AP is still coding invoices that arrived in the last week of the month. The second is that nobody has a single view of what has not posted, so close becomes a search rather than a checklist.

The second one is worse, because it turns a known amount of work into an unknown amount.

Six things have to be true on the last day

Each of these should be answerable from a screen rather than by asking a person. If any of them requires a conversation, that is your bottleneck.

Every invoice received this month is captured and accounted for. Not approved, not posted. Accounted for. You need to know the population before you can know what is outstanding.

Nothing is sitting unapproved past its aging threshold. With the dollar value attached, because 40 invoices worth $3,000 and 4 invoices worth $180,000 are different problems.

The error queue is worked down, with the exposure known. A representative month at 24,000 units left 197 invoices in the error queue out of 2,665. That is normal. Not knowing the dollar value in those 197 is not.

Accruals reflect purchase orders received but not yet invoiced. This is where PO aging matters, and where most portfolios rely on somebody's memory.

Coding is consistent with prior months, per property. A property whose R&M jumped 40% either had an event or had a coding drift, and you want to know which before an owner asks.

The audit trail is complete without anyone assembling it. If producing it is a task, you will do it once a year under pressure instead of continuously for free.

Speed to submission is the number that predicts close

Most AP metrics measure volume. Volume tells you how busy the team was, not whether close will be on time.

Speed to submission measures time from invoice receipt to ERP submission. The reference portfolio runs 61.8 minutes on average.

That number predicts close because it measures the whole pipeline rather than one stage. A portfolio at 61.8 minutes has nothing queued at month-end. A portfolio at four days has a week of invoices in flight on the 31st, and every one of them is a decision somebody has to make while also closing.

Track it per property. The portfolio average hides the property where invoices sit.

Approval latency, not approval time, is what delays you

Worth separating, because the fix is different.

Approval time is how long an approver spends on an invoice. It is small, roughly 90 seconds of real attention.

Approval latency is how long the invoice waits. In multifamily that can be days, because the approver is a regional between property visits rather than someone at a desk.

Latency is what closes a discount window, prompts a vendor call, and delays close. And it is a routing and escalation problem rather than a diligence problem: an invoice sitting four days in the queue of somebody on vacation is not being carefully reviewed.

The useful diagnostic is bucketing approval time into under one day, one to three days, and over three days, per property and per approver. That distinguishes a routing gap from a staffing gap.

Multi-entity makes every one of these per-entity

For a third-party manager, none of the above is a portfolio question. Every property answers to a different owner with different reporting and its own close expectations.

That means configurable workflows per property, coding consistency checked per property, and reporting that rolls up without flattening. A portfolio-level close status is close to useless if three owners need their own.

What actually moved on the reference portfolio

40 hours a month returned to the team, more than $150,000 a year in cost, and a 98% automation rate, meaning 98% of invoices required no human touch.

Close ran days faster once approvals stopped bottlenecking. Being precise about the mechanism: capture and coding removed the volume, and approval routing removed the wait. Those are two different fixes and the second is the one most teams underinvest in.

The limit worth stating: none of this fixes an approver who does not open their queue. Routing is a technology problem. Urgency is a management one.

Do this before next close

Pick the last three closes and write down the date AP finished coding and the date close actually completed.

If those dates are the same, your bottleneck is upstream in capture and coding. If close trails coding by several days, your bottleneck is approvals and reporting, and no amount of faster extraction will help.

Which of the two is yours?