FeeProof
A fee-disclosure evidence layer that inventories fee sources, compares rendered totals across applicant surfaces, proposes corrections, and retains scoped display receipts with policy and version lineage.
Property-management software operators can display application, administrative, pet, utility, convenience and move-related fees differently across listings, lease flows and resident portals. FeeProof inventories fee sources, computes scenario-specific disclosure candidates, compares actual rendered surfaces, proposes changes and records what an applicant session was shown. The supplied research confirms a March 2026 FTC advance notice of proposed rulemaking and warning-letter activity, not a final rental-housing fee rule. It also confirms a direct competitor that monitors listing displays and captures timestamped screenshots. FeeProof's remaining wedge is internal fee-schedule reconciliation across lease and portal surfaces plus per-session evidence. Zero referenced APIs are verified. Qualified legal owners must decide which fees, totals, timing, prominence and jurisdictions apply. The product never rewrites a live surface without exact operator approval. A signed receipt proves captured content, policy version and integrity within an observation boundary; it does not prove compliance, applicant understanding or regulator acceptance. Fee source, calculation, legal interpretation, proposed copy, approval, deployment, rendered observation, applicant acknowledgement, charge, payment and dispute remain separate. Success is consistent disclosures and faster correction—not a compliance certificate or defense against enforcement.
A property-management software, compliance or operations leader responsible for consistent fee display across listing, application, lease and resident surfaces.
Operators want one total while lawful, accurate disclosure varies by scenario, timing and jurisdiction.
Current FTC attention supports urgency without a final-rule cliff.
One cross-reference and three inbound links support moderate convergence.
Regulatory attention, warning letters and a confirmed direct monitor validate the workflow while multi-surface reconciliation remains plausible.
The federal action is proposed rulemaking, no API is verified, a direct competitor exists and legal interpretation remains human work.
Discussion
No comments yet — be the first to weigh in.
