Formula
NSF items across the period = sum of column 1 across all rows. Overdraft fee events = sum of column 2. Bank fees paid = sum of column 3.
Months breaching policy = count of rows where NSF count > Policy maximum NSFs per month. Worst month = the largest NSF count in any row.
Trend = NSF count in the last row − NSF count in the first row; a positive number means returned items are increasing.
Fees as share of deposits = Bank fees paid ÷ (Average monthly deposits × number of months).
Worked examples
Example 1: the default four months, rising but within policy
Inputs: four rows of NSF count, overdraft fee count and fees paid: 0 / 1 / $35; 2 / 3 / $175; 1 / 2 / $105; 3 / 4 / $245. Policy maximum NSFs per month 3; Average monthly deposits $60,000. NSF items across the period = 0 + 2 + 1 + 3 = 6. Months breaching policy: a breach requires a count above 3, and the highest month is exactly 3, so 0 of 4 months breach. Worst month = 3. Trend = 3 − 0 = +3, flagged because it is positive. Overdraft fee events = 1 + 3 + 2 + 4 = 10. Bank fees paid = 35 + 175 + 105 + 245 = $560. Fees as share of deposits = 560 ÷ (60,000 × 4) = 560 ÷ 240,000 = 0.23%. The file passes the policy count test in every month, yet the trend output is the one an underwriter should act on: zero returned items became three in four months while overdraft events rose each month. The fee drag is immaterial at a quarter of a percent of deposits; the direction is not.
Example 2: a bad quarter that is clearly over
Inputs: 4 / 5 / $300; 2 / 2 / $140; 1 / 1 / $70; 0 / 0 / $0. Policy maximum 3; deposits $45,000. Total NSF = 4 + 2 + 1 + 0 = 7, more than the default example. Months breaching: month 1 had 4, above 3, so 1 of 4. Worst month = 4. Trend = 0 − 4 = −4, which the tool shows in green because returned items are falling. Overdraft events = 5 + 2 + 1 + 0 = 8. Fees paid = 300 + 140 + 70 + 0 = $510. Fees share = 510 ÷ (45,000 × 4) = 510 ÷ 180,000 = 0.28%. By total count this file is worse than the default; by trend it is far better, since the most recent month is clean and the deterioration is three months old. A funder applying a rigid rule of no more than six NSFs in four months would decline this file and fund the default one; a funder reading the trend would do the opposite, and would ask what happened in month one and whether the cause, often a single large returned customer cheque, has been resolved.
Example 3: two clean months and a sudden spike
Inputs: 0 / 0 / $0; 0 / 0 / $0; 5 / 6 / $385. Policy maximum 2; deposits $90,000. Total NSF = 5. Months breaching: month 3 with 5 against a limit of 2, so 1 of 3. Worst month = 5. Trend = 5 − 0 = +5. Overdraft events = 6. Fees = $385. Fees share = 385 ÷ (90,000 × 3) = 385 ÷ 270,000 = 0.14%. The fee share is the lowest of the three examples and the total count is modest, but this is the most alarming pattern of the three: a well-run account with sizeable deposits suddenly returned five items in the latest month. That usually means a new fixed obligation began, typically a stacked advance, or a major customer stopped paying. The correct response is not to price the file but to ask for the current month's statement to date and a list of the returned items, because if those five returns include a financing debit, the merchant is already failing someone else's position.