fincarna

Know what the rate was, and who changed it

A rate change touches every product, channel, and disclosure that quotes it. Rate Governance puts every publish, every correction, and every approval on the record.

The challenge

Treasury sets the rate. Then it has to reach every product, every channel, and every system that quotes it, and that part rarely goes as planned.

A change to prime becomes a manual sweep across a rate sheet spreadsheet, a core banking ticket, and a disclosure update, done separately and usually out of sync for a few hours or days. The rate a customer was quoted, the rate that was disclosed, and the rate the core accrued against agree most of the time, which is exactly the kind of gap that's hard to catch.

And when an examiner or an auditor asks the obvious question, what was this rate on this date and who approved it, the honest answer takes a week of digging through email and spreadsheet version history.

How Fincarna solves it

Fincarna gives Treasury one place to publish a rate change, with an effective date, an author, and a reason attached. Draft values are never billable, so nothing goes live before it's meant to.

Every product that references the rate resolves to the correct value automatically, on the date it takes effect. No sweep, no ticket queue, no waiting on another team to catch up.

Corrections supersede rather than overwrite, so the record of what was published, when, and by whom stays intact. When an examiner asks what the rate was on a given day, the answer is already on the record.

Mortgage rate gridOne rate priced across two dimensions. Every cell versioned independently.Credit scoreGood660 to 719Prime720 to 779Super prime780 and upLoan to valueUp to 65% LTV5.12%4.86%4.54%65% to 80% LTV5.44%5.18%4.91%Over 80% LTV5.98%5.72%5.39%Resolved rate62% LTV, score 791Treasury authors the grid in Excel or the dashboard. Every cell carries its own version history and effective date.

Where rate governance breaks down today

  • Prime moves, nothing else does

    Manual sweep required

    The index changes and now every product that references it has to be updated by hand, product by product, before the disclosed rate and the accrued rate drift apart.

  • Disclosed rate, actual rate

    Two numbers, one gap

    What the customer was quoted, what was disclosed, and what the core accrued against are three systems of record, and nothing checks that they agree.

  • The examiner's question

    What was it, and when?

    What was this rate on this date, and who approved it, is a routine question from a regulator or auditor. Answering it today means reconstructing the story from email and file history.

  • The spreadsheet nobody fully trusts

    rate_sheet_final_v2.xlsx

    The rate sheet lives in a file that gets emailed around and edited by more than one person. Nobody is fully sure the copy they are looking at is the one that is actually live.

What changes

  • One place to publish a change

    Treasury publishes a rate value with an effective date, an author, and a reason attached. Draft and in-review values are never billable, so nothing goes live before it is meant to.

  • No sweep required

    Every product that references a rate or an index resolves to the correct value automatically, on the date it takes effect. Change the index once and it propagates on its own.

  • Corrections that don't erase history

    When a published value was wrong, a correction supersedes it rather than overwriting it. The original stays on the record with its lineage intact.

  • Guardrails before publication

    Set floors, ceilings, and a maximum change per period on a rate. A publication that would breach them is caught before it reaches a customer, not after.

  • What was it on any given day

    Every value carries a version, an effective date, and who published it. Who published a value, when it took effect, and why are part of the record.

  • Your core keeps accruing

    Fincarna is the authority on what the rate is and when it applied. Your core still does the accrual. Nothing about how you book interest has to change.

Expected outcomes

One
System of recordFor what the rate is, when it changed, and why
0
Manual sweepsRates propagate to every product that references them automatically
Minutes
To answer an audit questionDown from days spent reconstructing history from email

Walk a rate change through end to end

Pick one with an index, a guardrail, and a disclosure requirement, and we'll show you how it publishes.

or email us at hello@fincarna.com