Numeric fees in consistent format
Why it matters
Mixed fee formats — $0.50 on pricing, .5 USD at checkout, 0.50 on statements — make users second-guess the amount and erode trust at the exact moments they are deciding whether to pay. Inconsistent decimal precision is also a reconciliation hazard: a fee rendered $10 on the pricing page and $10.00 on the invoice looks fine to humans but breaks downstream CSV parsers and accounting imports. The content-integrity taxon captures both the user-facing confusion and the data-quality drift across surfaces.
Severity rationale
Low because the dollar amounts themselves are correct, but the inconsistency costs trust and breaks downstream parsers.
Remediation
Centralize every fee render through a single Intl.NumberFormat helper so currency symbol, decimals, and thousands separators are locked site-wide. Create src/lib/formatters.ts and import it anywhere money is displayed:
export function formatFee(amount: number, currency = 'USD') {
return new Intl.NumberFormat('en-US', {
style: 'currency',
currency,
minimumFractionDigits: 2,
}).format(amount);
}
Then grep the repo for $ and .toFixed( and replace each with formatFee().
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Regulatory Disclosure Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from finserv-disclosure·automated