# The Annual Escrow Analysis Under Reg X 1024.17: Aggregate Accounting, the Two-Month Cushion, and the Explanation the AI Servicing Agent Owes the Borrower

*July 3, 2026 · 13 min read · Pranay Shetty*

> Escrow analysis is where servicing math meets borrower incomprehension, and where a small computational error at the servicer produces a large volume of borrower calls the agent has to answer accurately. Reg X 1024.17 sets the aggregate-accounting method, the two-month cushion limit, and the shortage/surplus/deficiency rules the analysis has to produce. The intake the agent runs so a borrower gets the actual explanation the analysis warrants, and so the servicer does not create an error under its own rule.

## The Servicer's Most Predictable Call Surge

The mortgage servicer's most predictable call surge is the week after annual escrow statements go out. A borrower who has been paying $2,340 a month for two years opens a statement telling them the new payment is $2,617, and the reasoning is a paragraph of aggregate-accounting math the borrower did not go to school for. The call center fills up. The agent's job on those calls is not just to soothe the borrower; it is to explain the analysis in a way the borrower actually understands, and to catch the servicer's own errors when the analysis produced a number that will not survive review.

We build the agent that handles inbound servicing calls including the ones about the annual escrow statement. The escrow analysis rules at [12 CFR 1024.17](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) are among the most operationally consequential in the Reg X body, both because servicers get them wrong at a rate the CFPB has documented in multiple supervisory cycles and because the borrower-facing consequences of the errors are directly financial. The architecture below is what we run to answer borrower questions accurately, to catch servicer errors before they become findings, and to keep the audit file for the analysis in the form the examiner will ask for.

## Aggregate Accounting and Why the Method Matters

The rule at [1024.17(d)(2)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) requires servicers to use the aggregate accounting method for computing escrow account activity. The alternative single-item accounting method the rule allowed until 1998 is no longer permitted, and the aggregate method is the only method a modern servicer runs. What "aggregate" means operationally is that the analysis sums all anticipated disbursements from the escrow account over the computation year, calculates the monthly amount the borrower has to contribute to cover the disbursements plus the permissible cushion, projects the account balance month by month, and identifies the low point of the projected balance.

The projected low point is the anchor of the analysis. If the projected low point is above the target balance (typically two months of average escrow disbursements as the cushion), the account has a surplus. If it is below the target, the account has a shortage or a deficiency. The month-by-month projection is where the arithmetic gets dense, because a disbursement in March and a disbursement in December produce very different projected trajectories over the year.

The borrower does not need to be told about aggregate accounting to understand the analysis. What the borrower needs is a clear explanation of the total disbursements the servicer projected, the total contributions the borrower will make, and the target balance the analysis calibrated against. The agent's explanation converts the aggregate-accounting output into the borrower's mental model: "Your property taxes went up $180 a year. Your homeowners insurance went up $115 a year. That's $295 of increased annual escrow disbursements. Divided over twelve months, that's $24.58 a month. Your payment went up by $23, and the extra dollar and change is the servicer's cushion adjustment." The explanation is arithmetic the borrower can verify; the analysis's aggregate mechanics do not have to be explained for the borrower to trust the output.

## The Two-Month Cushion the Rule Caps and Servicers Often Overshoot

The cushion the servicer can maintain in the escrow account is limited at [1024.17(c)(1)(ii)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) to one-sixth of the estimated total annual escrow disbursements, or two months of average escrow. The two-month framing is easier to communicate but the rule's actual math is the one-sixth-of-annual computation, and the two figures produce the same result when the annual disbursements are evenly distributed.

Servicers overshoot the cushion regularly. The most common pattern is that a servicer's system computes the cushion against the historical disbursement amounts and does not adjust when the current year's projected disbursements are higher. The historical two-month cushion is now less than one-sixth of the projected annual, so the analysis increases the borrower's monthly payment more than the borrower's disbursement change alone would require. The borrower's call complains about the payment increase; the CSR agrees with the borrower that the increase seems high; the analysis is not corrected because the CSR does not have the tools to audit the analysis; and the borrower pays the higher amount for a year.

The agent's audit at intake compares the servicer's analysis's computed cushion against the two-month/one-sixth cap and flags any case where the cushion is above the cap. The flag routes the case for review by the servicer's escrow-analysis team, and if the flag is confirmed, the servicer produces a corrected analysis with the cushion at the cap and the corresponding lower payment. The correction produces a refund for any overpayment already collected in the computation year. The borrower's call, in this scenario, resolves in the borrower's favor with a corrected analysis and a payment adjustment; the servicer's exam-population posture improves because the incorrect analyses were caught pre-exam rather than at the exam.

## Shortage, Surplus, and Deficiency and What the Rule Requires Each One Look Like

The rule at [1024.17(f)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) sets specific rules for how the servicer handles each of the three conditions the analysis can produce.

A surplus of $50 or more requires the servicer to refund the surplus to the borrower within 30 days of the analysis, unless the borrower is currently in default on the loan (in which case the servicer may credit the surplus to the escrow account). A surplus of less than $50 can be refunded or credited to the escrow account at the servicer's option, and typical practice is to credit. The agent's explanation of the surplus tells the borrower which of the two paths applies and, if a refund is due, the specific date the borrower will receive it.

A shortage gives the servicer, not the borrower, the choice among the permitted treatments at [1024.17(f)(3)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/). If the shortage is less than one month's escrow payment, the servicer may allow the shortage to persist and do nothing, may require the borrower to repay the shortage within 30 days, or may require repayment in equal monthly payments over at least a twelve-month period. If the shortage is one month or more, the servicer may allow it to persist or require repayment in equal monthly payments over at least twelve months; the 30-day lump-sum option is not on the menu. The agent's explanation of the shortage tells the borrower which treatment the servicer elected and the specific monthly amount that treatment produces, with the reasoning documented for the case file.

A deficiency (negative escrow balance) also allocates the choice to the servicer at [1024.17(f)(4)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/), with a different spread window. If the deficiency is less than one month's escrow payment, the servicer may leave it, may require lump-sum repayment within 30 days, or may require repayment in two or more equal monthly payments. If the deficiency is one month or more, the servicer may leave it or require repayment in two or more equal monthly payments; the twelve-month floor that applies to shortages does not apply to deficiencies. The servicer that describes a lump-sum-or-spread choice to the borrower as if the borrower could elect between them is misdescribing the rule; the choice is the servicer's.

The three conditions have different remedies and different notice requirements, and the agent's classification of the analysis output into the correct condition is the first step in producing the right response. The classification is arithmetic against the rule's thresholds, and the classification is documented in the case file for the exam record.

## The Initial Escrow Statement and the 45-Day Clock

The rule distinguishes between the initial escrow analysis at loan closing (or at escrow-account establishment for a loan that adds escrow later) and the annual escrow analysis. The initial analysis under [1024.17(c)(2)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) produces the initial escrow account statement due to the borrower within 45 days of settlement, per [1024.17(g)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/). The initial statement has to itemize the estimated taxes, insurance premiums, and other charges the servicer expects to pay from the escrow account during the first twelve months, the amounts to be deposited by the borrower each month, and the disbursement dates.

The 45-day clock is often missed for loans that transferred between the origination servicer and a purchasing servicer within the initial 45-day window. The origination servicer's timing on the initial escrow statement can conflict with the transfer date, and the purchasing servicer inherits an incomplete file. The rule's expectation is that the initial statement is delivered within 45 days of settlement regardless of the transfer, and the servicing-transfer rules at [1024.33](https://www.consumerfinance.gov/rules-policy/regulations/1024/33/) require the transferring servicer to hand off the information the purchasing servicer needs to fulfill the obligation.

The agent's intake for a newly-boarded loan verifies that the initial escrow statement was produced within the 45-day window and, if not, flags the case for the servicer's compliance team to generate the statement now with a documented explanation of the timing. The examiner asking why a loan boarded in a specific month has no initial escrow statement in the file gets an answer that names the transfer, the timing, and the corrective statement the servicer produced. The examiner asking the same question with no answer in the file gets a finding.

## The Annual Statement's Content and the Explanation the Borrower Can Follow

The annual escrow account statement under [1024.17(i)](https://www.consumerfinance.gov/rules-policy/regulations/1024/17/) has to be provided within 30 days of the end of the servicer's computation year for the account. The statement's content requirements at 1024.17(i)(1) include the account balance at the beginning of the computation year, the amount of the borrower's monthly mortgage payment allocated to escrow, the amount paid into the escrow account during the year, the amount paid out of the escrow account for each item, the balance at the end of the year, and the specific information about any deficiency, shortage, or surplus.

The statement is a legally required document and often reads like one. Borrowers frequently call the servicer because the statement does not match what they think the analysis should have shown, or because the payment change the statement discloses is different from what the borrower had been anticipating from tax or insurance changes.

The agent's inbound handling reads the statement's content, cross-references the account activity, identifies any discrepancy between the borrower's understanding (typically anchored on the tax and insurance amounts they've seen) and the statement's computation, and produces the explanation that reconciles the two. If the reconciliation identifies an error in the statement, the case is routed for a corrected statement. If the reconciliation confirms the statement, the explanation the borrower receives is arithmetic-level and specific to their loan's situation.

The explanation the agent provides is generated per-call from the specific loan's data rather than delivered as a script. A borrower whose payment went up $47 and whose escrow disbursements went up $32 gets an explanation of where the other $15 came from (typically the cushion recalibration or a change to the loan's payment period), and the explanation cites the specific line items in the statement so the borrower can follow along. The borrower who ends the call understanding why the payment changed is less likely to call again, less likely to file a complaint with the CFPB or the state banking agency, and more likely to stay current on the new payment.

## The Payment Delinquency and Escrow Interaction

A borrower who becomes delinquent on the mortgage payment is a borrower whose escrow account activity often diverges from the escrow analysis's projections. The servicer's advances for tax and insurance disbursements from the escrow account, if the borrower's escrow contributions are behind, produce a deficiency the analysis will identify in the next annual statement. The borrower's cure of the delinquency has to include catching up on the escrow shortfall, and the servicer's handling of the cure has to conform to the escrow rules alongside the payment-application and delinquency rules.

We wrote separately on the [Regulation X 1024.35 Notice-of-Error and 1024.36 Request-for-Information processes](/blog/reg-x-1024-35-notice-of-error-request-for-information-ai-mortgage-servicing) and on the [1024.41 loss-mitigation servicer playbook](/blog/ai-agents-mortgage-loss-mitigation-regulation-x-servicer-playbook) that handle the delinquency-side of the borrower's relationship with the servicer. The escrow analysis interaction with the delinquency process is that a borrower entering loss mitigation has to have their escrow position accurately assessed as part of the workout, and the loss-mitigation option offered has to account for the escrow shortage or deficiency the analysis identified.

The agent's coordination between the escrow-analysis process and the loss-mitigation process is that the escrow-related components of a delinquent borrower's account are surfaced to the loss-mitigation reviewer with the analysis's specifics, and the workout's terms account for the escrow condition. A repayment plan that catches up on the mortgage payments but does not address the escrow shortage is a repayment plan that leaves the borrower in a position where the next annual analysis will show a large payment increase, which typically produces a new delinquency. The workout that addresses both the payment shortfall and the escrow shortage together is the workout that has a chance of holding.

## The Communication Timing That Reduces the Call Surge

The predictable call surge after annual escrow statements is expensive for the servicer and stressful for the borrowers, and both sides benefit from communication timing that reduces the surprise. Some servicers we work with have adopted a pre-statement communication pattern where borrowers receive a "your escrow analysis is being finalized" outreach two weeks before the annual statement is mailed, with a preview of the specific tax and insurance changes the analysis will reflect and an invitation to opt for a specific communication channel (secure message, phone call, or portal) to receive the statement and any follow-up.

The pre-statement outreach is not required by the rule, and it is not universally advisable (some servicers prefer to let the statement speak for itself), but for the borrower populations that respond well to it, the call volume after the statement drops meaningfully. The borrower who has already been introduced to the tax and insurance changes is less likely to react to the statement with a call, and the borrower who does call is more likely to have a specific and answerable question rather than a general "why did my payment go up" question.

The agent's role in the pre-statement outreach is to generate the tailored preview from the analysis's inputs, to schedule the outreach through the borrower's chosen channel, and to log the outreach for the case file. The audit trail of the outreach is part of the servicer's operational-quality record and is available if the examiner asks about the servicer's borrower-communication posture.

## The State-Level Escrow Variations the Program Has to Track

State law overlays Reg X's federal escrow rules in several jurisdictions. New York's Banking Law Section 6-l has specific escrow-interest requirements for certain loan types, requiring the servicer to pay a minimum interest rate on escrow balances. California's Civil Code Section 2954 and related provisions have specific interest and disclosure requirements. Massachusetts, Connecticut, and several other states have parallel requirements. The state variations do not displace Reg X; they add to it, and the servicer's escrow program has to run both layers simultaneously.

The agent's intake for a loan is aware of the property's state and the applicable state-law overlay, and the escrow analysis the servicer runs accounts for the state's interest-payment requirements, disclosure requirements, and any state-specific timing or content rules on the annual statement. The borrower asking why their statement in New York shows an interest credit that a friend's statement in Texas does not show is a borrower who gets an accurate explanation of the state-specific requirement rather than a confused CSR response.

## The Force-Placed Insurance Interaction

The [force-placed insurance rules at 1024.37](https://www.consumerfinance.gov/rules-policy/regulations/1024/37/) interact with the escrow analysis when a borrower's homeowners insurance lapses and the servicer places force-placed coverage. The force-placed premium is typically significantly higher than the borrower's prior insurance premium, and the escrow analysis for the following year reflects the higher disbursement. The borrower's monthly payment increases proportionally, and the borrower's call about the payment increase is often the borrower's first realization that force-placed insurance is on the loan.

We wrote separately on the [force-placed insurance architecture](/blog/force-placed-insurance-regulation-x-1024-37-ai-servicing) that runs the 1024.37 process. The escrow-analysis interaction is that the agent's explanation of the payment increase has to include the force-placed insurance context, and the borrower's options (reinstating their own insurance, disputing the force-placed placement, engaging with the workout) have to be presented alongside the analysis explanation. The two processes converge in the same borrower conversation, and the agent's coordination across them is the borrower-facing operational advantage.

## The Audit File the Analysis Produces

The audit artifact per loan per computation year that the examiner will ask for includes the analysis's specific inputs (the tax and insurance disbursement projections with their sources), the aggregate-accounting computation with the month-by-month projected balances, the identified low point and its comparison to the cushion cap, the classification of the account as surplus, shortage, or deficiency with the specific amount, the annual statement produced with the timestamp of delivery, any borrower response including questions or disputes with the servicer's response, and the analysis's outputs (the new monthly payment, the surplus refund if applicable, the shortage spread schedule if applicable).

The file supports the examiner's review of the servicer's Reg X 1024.17 compliance at the population level, and the file supports the individual borrower's access to information about their specific analysis. The rule at 1024.17(l) requires the servicer to maintain records for at least five years, and the servicer's records-management program applies the longer of the five-year rule and any state-law requirement.

## The Failure Mode We Engineer Against

The pattern that produces the worst outcomes is the servicer whose escrow-analysis system was set up years ago against the aggregate-accounting rules, has been running with the same computational logic since, and does not have the operational feedback loop from borrower calls that would catch the cases where the computation produced a wrong number. Borrower calls complain about the payment change; the CSR explains what the statement says; the borrower pays; and the analysis's error persists into the next year's inputs. Over time, the servicer's escrow-analysis population contains a meaningful number of loans where the analysis has been drifting incorrect, and the examiner review finds the drift.

The architecture we run against this is that borrower calls about the escrow analysis are treated as an operational signal in addition to a customer-service event. A pattern of borrower calls disputing specific components of an analysis is a signal that the servicer's computation may have a systematic error. The agent's classification of call patterns feeds an operational-quality dashboard that the servicer's escrow team reviews weekly, and the dashboard surfaces the specific loan populations, the specific components, and the specific error patterns that emerge from the call data. The servicer's escrow team investigates the flagged populations, identifies any computational error, and corrects both the errors and the underlying computation logic before the pattern grows.

The borrower call volume, in this operational model, is a source of quality data that improves the servicer's escrow analysis for all borrowers, not just for the borrowers who called. The servicer whose call volume feeds the quality process is the servicer whose exam finding on 1024.17 will be smaller than the servicer whose call volume is treated as a cost to minimize.

## The Honest Read

Reg X 1024.17 escrow analysis is one of the most computationally dense and operationally consequential rules in mortgage servicing. Servicers get it wrong at a rate the CFPB has documented, and the borrower-facing consequences of the errors are direct and specific: monthly payments too high, refunds not received, shortages not disclosed. The AI agent that handles borrower calls about the annual statement is the operational touch point that either explains the analysis correctly, catches the servicer's own errors, and produces the audit file the examiner will ask for, or that reads the statement to the borrower without meaningful comprehension of what the statement actually says.

The choice between the two operational modes is not primarily a technology choice; it is a program choice. The servicer whose agent has access to the analysis's inputs, understands the aggregate-accounting method well enough to explain it, and can flag computational anomalies is a servicer whose escrow program is stronger at the borrower level, at the exam level, and at the loss-mitigation-coordination level. The agent's job is not just to explain a statement; it is to be an effective quality-control layer on the servicer's escrow analysis, and the servicers we work with have found that this role is the most operationally valuable of the agent's contributions to the servicing program.

We have written separately on the [1024.35 Notice of Error and 1024.36 Request for Information processes](/blog/reg-x-1024-35-notice-of-error-request-for-information-ai-mortgage-servicing), on the [1024.37 force-placed insurance rules](/blog/force-placed-insurance-regulation-x-1024-37-ai-servicing), and on the [1024.41 loss-mitigation process](/blog/ai-agents-mortgage-loss-mitigation-regulation-x-servicer-playbook). The four Reg X rules together define the operational surface of the servicer's relationship with the borrower, and the agent that runs across all four with a consistent architecture is the agent whose contribution to the servicing program compounds across the borrower's lifecycle.

---

_Source: [https://www.seiright.com/blog/reg-x-1024-17-escrow-analysis-ai-mortgage-servicing](https://www.seiright.com/blog/reg-x-1024-17-escrow-analysis-ai-mortgage-servicing) · Sei AI_