Why close delays start in AP, not in reporting
When a CAS engagement runs late, the conversation usually starts at the wrong end of the workflow. The client says reports are slow. The firm responds by adjusting reporting templates, refining commentary, or moving the management report deadline. The reports get faster. The close stays late. Six months later the same conversation repeats. For more context, see the accounting firm hub.
The reason the loop repeats is that reporting is the visible end of a sequence that fails earlier. By the time a controller is producing the management report, every bill has been coded, every approval logged, every accrual posted, every reconciliation cleared. If those upstream steps are slow, the report cannot be early. The fastest reporting template in the world cannot move a close forward by a day if AP is still chasing landlord backup on day eight.
I built CAMAudit partly because the most common close-week disruption I saw in my testing was an unusual landlord bill that arrived without warning and broke the AP queue. That single bill is a stand-in for a broader pattern. Close delays start in AP, and they get diagnosed in reporting. Fixing the diagnosis is where firms get their close speed back.
AP cutoff: The stated date or time before close starts by which all client-side bills must be received, coded, and approved for the period to be considered complete and ready for close. The cutoff is set by the controller, communicated to the client at engagement start, and enforced through the close calendar. Bills that miss the cutoff are either accrued by the firm based on best available information or pushed to the next period, depending on materiality and the firm's accrual policy. Without a cutoff, the AP queue is open-ended and the close timeline is dictated by the slowest client document.
Where the time actually goes
A close that runs ten business days has a typical shape. Day one through day three is bill entry and AP coding. Day four is bank reconciliation. Day five is payroll posting and accruals. Day six and seven are review, adjustments, and the controller's exception list. Day eight is reporting. Day nine and ten are the client meeting and follow-up.
When a close runs fifteen business days instead of ten, the extra five days are almost never on day eight. The reporting step is a constant. The slip is in days one through three: bills did not arrive on time, bills arrived without detail, an unusual bill landed and required review, an approval workflow stalled at the client. By the time reporting runs, the AP delay has propagated through every downstream step. The controller cannot review accruals on a P&L that does not yet have all its expenses. The bank rec cannot tie out against AP if AP is still entering bills.
The visibility problem is what makes this hard to diagnose. AP work is invisible. Reporting is what the client sees. The client experiences a late report and assumes the report is slow. The firm hears "the report was late" and adjusts the report. The pattern persists because nobody is measuring the AP cutoff slip that caused it.
The five AP failure modes that produce close delays
The five most common modes are predictable enough to design controls around.
Late client documents. Vendors send bills directly to the client. The client forwards them on a schedule that does not match the close calendar. By close week, half the recurring vendors have arrived and half have not. The bookkeeper waits, the controller waits, the close slips.
Bills with insufficient coding detail. A landlord invoice arrives with a single bundled line for "operating expenses" and no breakout. The bookkeeper cannot code it without context. The bill sits in the inbox while the controller decides whether to chase backup or post the bill to a temporary account.
Recurring bills that changed. A vendor that has billed $4,200 per month for the last fourteen months bills $7,800 this month. The bookkeeper notices the change but does not have a process for handling it. The bill stalls while someone decides whether to accept the new amount or query the vendor.
Duplicate bills. A landlord bills monthly through one channel and a property manager bills the same charges through another channel. The bookkeeper enters both in good faith. The duplicate is caught at variance review, which adds a correcting entry to close week.
Unusual non-routine bills. The annual CAM reconciliation, a one-time tax pass-through, a special assessment, a major repair allocation. These bills are not routine and require controller-level review before posting, but they arrive without scheduling and frequently land during close week itself.
Each of these is solvable with a process. None of them is a reporting issue.
"Every CAS firm I have spoken with about close speed describes a reporting problem when I ask about close timing. When I ask about AP cutoffs, exception processes, and unusual bill handling, the actual problem becomes clear within five minutes. Reporting is the symptom. AP is the cause." — Angel Campa, Founder of CAMAudit
What an AP exception process looks like
The AP exception process is a small set of rules applied at bill intake. It does not change the standard coding flow for routine bills. It pulls a defined subset of bills out of that flow for additional review.
A bill enters the exception lane if it meets any of the criteria the firm has set in advance: amount over a threshold relative to the client's run rate, vendor not seen before, vendor amount changed by more than a stated percentage from the prior month, bill contains a category the firm has flagged as non-routine (landlord reconciliations, real estate tax pass-throughs, insurance pass-throughs, major repair allocations), or bill missing an approval that the engagement requires.
The exception lane routes the bill to the controller or CAS manager. The reviewer either clears the bill back to the standard coding flow, requests backup before posting, accrues the bill at an estimated amount and pushes the actual posting to the following period, or escalates the bill to a specialist for further analysis. None of these decisions live with the bookkeeper.
The result is a close that runs on schedule because the routine bills move on the standard track and the exceptions are handled in a separate lane that does not block the queue. The cost of the exception process is the controller's time on a small subset of bills. The savings are the close-week hours that used to be spent rescuing the AP queue.
How to set an AP cutoff that holds
The cutoff fails when it is set in firm-only language and never communicated to the client. Most clients will respect a cutoff if they know it exists, why it exists, and what happens when they miss it. The conversation is short.
The cutoff is in the engagement letter and the close calendar. The client receives a pre-close request list at the start of close week with a stated deadline for bills, statements, and approvals. The deadline is a specific date and time, not "early in the week." Bills received after the deadline are accrued or pushed to the next period at the firm's discretion. The client meeting includes a brief review of which bills missed the deadline so the pattern is visible to the client over time.
After three or four cycles, the client behavior usually adjusts. The clients who do not adjust are surfaced as a scope conversation rather than a close-time conversation. That is a healthier framing for both sides.
Reporting is downstream
None of the above is about reporting. The reporting cadence comes from the AP cadence. A clean AP queue produces a clean trial balance, which produces a clean management report on schedule. A messy AP queue produces every downstream problem the client and the firm experience as a reporting issue.
The next time a close runs late and the conversation starts with the report, redirect to the AP cutoff. The diagnosis will be more accurate, the fix will be more durable, and the close will be faster the following month.