Outcome. A deal whose amount field disagrees with the sum of its actual line items gets flagged before it reaches a forecast or a quote, instead of a stale, manually-typed amount quietly overstating or understating what the deal is really worth.
flowchart TD
A[Deal created or Amount changed] --> B[Custom code: sum line items, compare to Amount]
B --> C{Mismatch beyond tolerance?}
C -->|yes| D[Flag Mismatch, add to list, create task]
C -->|no| E[Matches line items]

When to use it, when not to
- UseUse it on pipelines where deals carry line items, products with
quantity and price, and the deal
Amountfield is expected to reflect their total, but reps or an integration can still editAmountdirectly, independent of the line items. - UseUse it before a deal reaches a stage where the amount matters for a formal action, a quote generation, an approval, or a forecast roll-up.
- SkipDo not use it on deals that intentionally carry no line items and
use
Amountas a standalone manual estimate. This fiche assumes line items are the source of truth, which is not every deal's actual data model. - SkipDo not use it to auto-correct the mismatch. Overwriting
Amountsilently from the code removes the rep's ability to intentionally apply a manual discount or adjustment not reflected in the line items. Flag the mismatch, let a human decide which number is right.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





