Rate tables start in an underwriting platform. This platform keeps track of base premiums, location costs, and classification codes in set areas. Each time a rate changes, there’s a date it starts being used and a reference number tied to a filing with regulators. The underwriting system saves old rate versions as locked files, which you can see by looking at the version history. This history shows when the rates were approved and who approved them.
Start dates divide pricing inside the same product line. Policies made before a change stay with the old rate tables, which are saved as they were. New policies and renewals that happen on or after the start date use the new rates without anyone having to do it themselves. Old and new pricing exist in the same space, set apart by dates and version numbers.
Regulatory filings go through a separate online area. Actuarial reports, policy forms, and proof are uploaded to a web page that’s not part of the main policy system. This page gives a tracking number that’s different from the rate numbers inside the company. Status updates—like filed, being looked at, or approved—show up in the compliance area, and staff watch these updates in-house too.
The filing process follows a regulatory schedule that doesn’t always match when the product is put into action. A rate can be filed and waiting for approval while the company gets ready to change settings for the new rate. Until the approval is official in the compliance area, start dates are just planned. There are two processes happening at the same time: filing review and internal prep.
Once approved, rate updates are put into the policy system through scheduled data uploads. The spots for figuring out premiums update automatically for policies made on or after the start date. Policies made before that date keep the old rates, which are saved and can be seen in the policy record.
Scheduled data uploads make times when things are in sync. Between when a rate is approved and when the system is updated, the company might look at approved rate tables stored in special areas. The live production area shows the new rates only after the upload is complete, which is when pricing changes happen.
Outside parties can see premium info through a portal that shows basic coverage and pricing. This portal asks the insurance company’s database for premium amounts and classification codes. Some rate factors, like location costs tied to city records, might not be in the outside party’s view and stay inside the underwriting system.
What you can see depends on the location. An outside party sees total premium numbers and summaries, while the details are in company tables. Matching the summary and details depends on having shared policy numbers and start dates, not on having the same setup.
City records affect pricing through location-based modules. Address info from policies goes to a mapping service that gives risk scores and zoning types. These types change rate factors in underwriting tables. The mapping service has its own database that is updated on its own schedule, separate from the company’s records.
Risk score updates cause changes that the company can’t control. A change in zoning or risk can change rates when a policy is renewed. The underwriting platform saves the score and when it was pulled, keeping the outside data that was used for the rate.
Repair groups see pricing when looking at payment schedules. Agreed rates with contractors are in a vendor system separate from underwriting. When a bill comes in, billing codes are checked against agreed prices in the vendor portal. The approved amounts go into the claim payment system, with the claim number and vendor contract ID.
Vendor payment tolerances are different from underwriting tolerances. Premium factors control policy pricing, while contract matrices control claim payments. Both use set tables with start dates and revision histories, but they are separate systems.
Legal work is separate from premium figuring but uses pricing during disagreements. A legal application saves policy forms as static files tied to case records. Lawyers get premium details from the underwriting system and upload them into the legal file as proof. The legal platform gives its own case number, tied to policy and claim numbers.
Static files show the pricing at the time of policy setup or renewal. Rate changes later on don’t change these files. Versioned rate tables are still in underwriting archives to compare against pricing questions.
Set times in inspection processes connect pricing changes to operations. When an inspection is scheduled, it can cause a re-evaluation of risk type. Updated inspection results go into underwriting through a compliance module, which saves changes in building status. Revised risk types then change rates for future policies.
Inspection results change future pricing, not past premium. Start dates on revised types decide when new rates apply. Claims and underwriting changes happen at the same time but don’t become one event.
Billing codes move between repair groups and accounting platforms. An approved invoice makes a payment instruction in the claims system. The accounting platform gets the transaction, noting the rate agreement at the time of service. Accounting gives its own tracking number and payment date, creating matching numbers tied to the pricing structure.
Batch processing adds another time layer. Vendor approval might happen fast, while accounting records the payment later. Transaction numbers connect the time between approval and posting.
Regulatory checks include saving data. Filing documents stay online for set times. The underwriting system keeps its own schedule for rate tables and models. A link in the underwriting platform goes to the regulatory filing number, so staff can look up the related filing from the outside portal.
Saving times change depending on the platform and rules. A filing might stay in the compliance area longer than some underwriting logs. Cross-referencing keeps track of things despite different schedules.
Outside parties might make changes that change premium during the policy. The change in the administrator’s portal asks the underwriting system to recalculate. The new premium appears in both systems, but the administrator’s portal might show just the change, while the underwriting system keeps all the rate details.
Changes during a policy split the premium into segments. The change date separates old and new premium parts. Accounting systems split amounts correctly, recording changes linked to both the original and new numbers.
City permit data sometimes affect pricing. A permit in a city database goes into the insurance company’s compliance module. The compliance module flags policies at the changed address, causing underwriting to check. New risk factors go into the underwriting system, and new rates apply when the policy is renewed.
Permit-driven changes go through check thresholds. Not every permit changes a rate; rules decide which ones cause underwriting to look into it. These rules are stored in compliance modules with their own change logs.
Document systems save policy forms and rate books separately from databases. Rate books have details and rate tables. Underwriting areas link to these books, and the compliance portal saves the same books as part of filings.
Book references support databases. Rate figuring uses coded tables, and books explain. Access logs record each time a book is looked at.
Legal mail in rate fights moves between systems. Emails with regulators are saved in the compliance portal, with a timestamp and sender name. Underwriting staff might add summaries to internal notes in the policy system, linking the systems.
Summaries are reference points, not duplicates. The compliance portal keeps all mail; underwriting keeps notes tied to policy numbers.
Data warehouses collect pricing data from underwriting, claims, and accounting. Extraction scripts line up premium spots that are named differently. A base premium in underwriting might have a different name in accounting. Transformation rules change these spots for reporting without changing the source systems.
Extraction happens on set schedules, making reporting snapshots separate from live data. Changes after extraction happen in the next reporting cycle, causing small time differences between operations and reporting.
Outside parties have reporting dashboards that show total premium coming through their portal. These dashboards use policy numbers and dates but don’t show rate details. Comparing administrator reports and company totals happens through file transfers with shared numbers.
Comparison tolerances decide how much difference is okay between the report and company totals. Differences that are too big cause follow-up, which is saved in shared logs.
Repair network contracts have clauses tied to cost indexes. The vendor system updates payment schedules based on index numbers from outside data providers. These updates are saved in vendor tables and used when checking invoices. The underwriting system stays separate, keeping premium rate tables that are not changed by vendor costs.
Index updates follow released schedules. Vendor payments change when new index numbers load, while underwriting premiums stay the same until filing and approval happen. Pricing systems change on different schedules.
System migrations bring old pricing data into new platforms. Rate tables from old systems might be brought in as static records that can’t be edited much. Underwriting staff look at old rates and enter new rates into the current system.
Static entries keep old pricing without being part of the current math. Staff look at archived tables for reference, not for making rates.
Regulatory reviews cause extra data exchanges. Auditors ask for extracts of rate tables, filing mail, and premium logs. Extract files are made from underwriting databases and uploaded to secure portals. Receipts from these portals are saved in compliance logs separate from underwriting.
Reviews put outside time on things, separated from policy schedules. Extract timestamps are different from rate timestamps, forming audit trails.
Schedule overlaps go to renewals. Renewal batches in the policy system figure out premiums using current rate tables. The batch file goes to a billing system that makes invoices with its own numbers. Payment receipts are saved in accounting and linked to the policy record through numbers.
Renewal math, invoice making, and payment receipt each have different numbers and times. Premium numbers move through these steps without changing database structures.
Pricing data moves between underwriting screens, compliance portals, vendor systems, city data, legal platforms, and accounting through saved numbers. A rate change in underwriting shows up in renewal notices, filings, vendor payments, and records with different numbers and times. Statuses, payments, authorizations, and batch references are stored in their places. Shared policy numbers and dates appear across files. Records add new lines.
