Finance agreement reductions — credits posted in the CRM

In the CRM, not on the staff log — 2026-09-07 → 2026-09-20

The staff log could not be read on this build, so NOTHING below has been checked against it. Treat this list as every reduction in the window, not as unlogged ones.

Credits posted against a finance agreement where the order reference appears nowhere on the Debt Reduction/Upsells sheet. Some will be studio-side reductions that were never the debt team's to log — but every one of them is money written off the book, so the list is the thing to work down.

Rows on the log the CRM doesn't agree with — 2026-09-07 → 2026-09-20

0 log rows in this window reconcile to a CRM credit on amount and date. The rest are below, each with the booking's complete finance schedule printed underneath so you can see exactly what the CRM holds. Upsell and No Sale rows are excluded — they are not credits, so they never appear in a finance schedule.

Every log row in this window matches the CRM.

How a reduction is recorded in the CRM — and how this report reads it

Worth reading before disputing a row: the CRM has no "reductions" screen and no reductions report. Everything below is read from the booking's own finance schedule.

Where it lives

Open the booking → Finance. That grid is the whole story of the agreement: Date · Type · Reference · Credit · Debit.

• The Order line at the top puts the package price in the Credit column — that is what they owe.
• Money coming in is a Debit row with Type Paid — deposit, card, then each monthly payment.
• A reduction is a line added with Type set to Credit (the dropdown is Debit / Credit / Declined). It lands in the Credit column and takes the balance down.
• The Reference box is free text. That is where "Discount", "Write Off - Bankruptcy", "Reduction to 15 Images", "Monterey Settlement" come from — typed by whoever posted it.

What this report counts

Every Type = Credit line on every finance agreement. Nothing is inferred and nothing is estimated. Two cross-checks that it is reading the right thing: the CRM's own Debtor Ledger carries a "Credits Applied" total per agreement, and the credit lines sum to it on 11,486 of 11,511 agreements — $19,696,908 of credit lines against $19,689,138 on the ledger, 0.04% apart.

The date

A credit's date is whatever the person posting it typed into the date box. The CRM stores no separate "created" timestamp for a finance line, so this is "when it was booked in", not an audit trail. That is why a log row is treated as matching if the dates are within three days.

The two ways a reduction hides from this count

• Posted as a payment. Some are typed in as a Debit / Paid row with "reduction" in the reference instead of a Credit line. The balance clears either way, but the books then read the write-off as money received — the sale looks fully collected and the discount disappears. These show up in the "Log vs CRM" tab, flagged in red.
• Never on finance. If the package was cut before the sale was written, or the client paid in full and was refunded, there is no finance agreement to credit — the CRM only ever saw the lower price. Those are flagged blue: nothing is wrong with the account, it just cannot be counted here.

By studio — 2026-09-07 → 2026-09-20

By reason — 2026-09-07 → 2026-09-20

By who posted it — 2026-09-07 → 2026-09-20

Taken from the CRM's own record of who keyed each finance line, not from any sheet. Read it with what each person is asked to do. Collections close uncollectable debt — write-offs, bankruptcies, Monterey — which is supposed to recover nothing, so a low return there is the job working. A booker discounting a live sale is a different measure entirely. Compare like with like using the reason breakdown, not this table alone. It is also who keyed it, not who authorised it — which is why "mb approved" keeps appearing in the typed reference.

Last 12 months — every reduction posted, by month

The whole book, not just the window above — so the last two weeks can be read against the run rate.