PROPOSED PROJECT
Fee Change Checker
Help bank teams find fees that differ between price lists, brochures, and website pages. Show the exact amounts and conditions that do not match, then prepare a list of changes for the product manager to approve.
Same account. Different promises.
Publication drafts under review
Changes to review
Across three example fees
What the terms say.
Waived when the average monthly balance is at least ₱25,000.
What customers would read.
Waived when the month-end balance is at least ₱25,000.
Same amount. Different condition.Find the mismatch
before a customer does.
A fictional Everyday account is preparing three fees for 1 November 2026. Approved terms list a ₱15 online transfer fee, while the website draft says ₱10. Both documents list a ₱200 monthly service fee, but the brochure replaces the required average monthly balance with a month-end balance. The ₱250 replacement-card fee agrees. Two corrections remain for product review.
WHAT IS USUALLY DONE
A product manager checks a price list against website pages and brochure PDFs by eye. A new amount may be corrected while an old waiver condition remains elsewhere. Documents with the same fee can still promise customers different terms.
WHAT SOVRUN CAN DO FOR YOU
Sovrun would build a comparison workspace for approved fee terms and the channels that publish them. Document models read the price table and draft pages, keeping the original passage and location. The system matches product, fee type, effective date, amount, and waiver condition before flagging a difference. It produces proposed corrections for the product manager and channel owners; it does not edit live pages automatically.
A matching price
can still be wrong.
Amounts, conditions, product versions, and effective dates must agree. The monthly fee below costs the same in both documents, but the waiver describes a different balance test.
Online transfer
Amount differs
Monthly service
Waiver differs
Replacement card
Terms agree
Average monthly balance₱24,500Below the approved threshold
≠Month-end balance₱26,000Above the draft’s threshold
The brochure would describe a waiver this balance record does not meet under the approved terms. Flag the wording for the product manager; do not decide or change a customer’s fee.
A correction list
people can act on.
The first version compares one account’s approved terms with supplied brochure and website drafts. Changes stay attached to their exact locations.
The condition changed.
Threshold stays ₱25,000.
Effective 1 Nov 2026.
Ready for owners.
- Website / transfers
- ₱10 → ₱15
- Brochure / p4
- Correct waiver
- Website / cards
- No change
Review, then verify.
- Product manager checks terms
- Channel owner updates copy
- Compare the published file
Current status: awaiting review.
How we’d make it happen.
Agree on the current terms
Identify the authoritative product record and effective date. Separate old versions and similarly named accounts before comparing their fees.
Compare the complete condition
Read amounts, units, waivers, and footnotes together. Link each flag to both the approved record and the conflicting document passage.
Approve and recheck
The product manager approves corrections and assigns channel owners. Check the supplied published versions afterward and keep unresolved differences visible.
Where AI helps
Document models extract fee tables and locate the passages in PDFs and supplied web snapshots. Language models compare conditions such as average monthly balance versus month-end balance. Exact amounts and effective dates are checked in code. We test the workflow on confusing page layouts, footnotes, old versions, and similarly named products before choosing models for the client.
What people approve
The product manager determines the authoritative terms and approves each correction. Channel owners check the final website or brochure, with the firm’s compliance reviewers involved where required. Unreadable pages, missing dates, and disputed source versions remain unresolved instead of becoming approved changes.
What we’d need to start
- The approved fee schedule, product identifiers, version dates, and effective dates
- Brochure PDFs and supplied website snapshots with their URLs or page numbers
- Waiver definitions, channel owners, and the approval process for publishing corrections
How we’d test it
Test changed amounts, equal prices with different conditions, missing footnotes, future effective dates, and products with similar names. Confirm that different valid dates are not treated as errors. Compare each suggested correction with the product team’s review and measure missed differences, false alarms, and review time.
Prepared for Financial services. We would agree on the work after reviewing your brief, materials, and requirements.
This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.
