fincarna

Benefits that follow the whole relationship

Waivers, entitlements, rewards, and fee schedules that reflect everything a customer does with you, executed exactly as your policy is written, every cycle.

The challenge

Customers expect to be recognized for the relationship they bring, and regulators expect every fee to be fair and explainable. Most institutions already want to move from flat fees to pricing that reflects the depth of the relationship.

What stops them is the billing layer inside a core banking system was built when products changed once a year, promotional pricing was a rare exception, and a fee schedule was something you printed.

So pricing that the business designed gets simplified down to what the system can do. Waivers become permanent flags because there is no lifecycle. Tier thresholds get approximated because the calculation is not expressible. Every genuinely relationship aware idea becomes a manual process, and manual processes are where customers stop getting what the policy promised them.

How Fincarna solves it

Fincarna adds the layer your core is missing. Fee schedules, entitlements, waivers, rewards, and promotions are configured objects with lifecycles, not exceptions handled by hand each cycle.

The catalog is built for this. One product can carry several pricing variants. Variants group into bundles. Rewards and promotions sit on top. Everything is versioned and effective dated, so you can schedule a change, run a campaign, and answer precisely what the pricing was on any given day.

Every cycle the engine executes those rules and records how it reached each number. Your core keeps the ledger and the regulatory reporting. Fincarna decides what to charge and can always show its work.

Layer 1ProductMirrors what exists in your coreYour core has products. So does Fincarna.Chequing, savings, LOC, mortgage. One-to-one with your core.Layer 2VariantsMultiple pricing models per productOne product, many pricing options.A LOC can have Standard and Premium variants, each with itsown fees, rates, entitlements, and billing cycle.Layer 3aBundlesGroup variants, price as oneGroup variants across products into asingle offering with shared pricing.Layer 3bRewardsConditional, behavior-drivenWaive fees or discount rates whenconditions are met. Encourage behavior.Layer 4aPromotionsTime-limited, rule-drivenTake any variant or bundle to market.Set a window. Everything reverts on expiry.Layer 4bDealsNegotiated, per clientBespoke terms for one relationship.Approved before they ever reach a bill.Your core todayProductflexibilityRelationshippricingCompetitiveadvantageEach layer adds capability your core doesn't have. No migration required.WHAT IT ENABLES ↑

What the relationship can earn

  • Balance aware fees

    Not flat subscriptions

    Waive the monthly fee above an average balance, charge it below one, and define precisely which average you mean. Daily, monthly, minimum, or a formula of your own. The ambiguity in the phrase average monthly balance is where similar customers end up treated differently.

  • Entitlements and overage

    Free, then billed

    Give an account a number of free transfers, withdrawals, or ATM transactions per cycle and bill automatically once they are used up. The counter resets with the cycle without anyone driving it.

  • Waivers with a lifecycle

    Lifecycle, not a flag

    A waiver has a start, an end, and a reason, so it applies for exactly as long as the relationship warrants and is renewed on purpose rather than by default. A waiver granted once and never revisited tells nobody why it exists.

  • Relationship and bundle pricing

    Priced as a relationship

    Price on everything a customer holds: group accounts into bundles and households, share benefits across them, and control how charges and waivers are distributed across the relationship rather than pretending each account exists alone.

Key capabilities

  • A catalog with room for pricing

    Products mirror what your core already knows. Variants let one product carry several pricing models. Bundles group variants into relationship packages. Rewards and promotions layer on top. Each layer adds something your core was never asked to do.

  • Variants versioned and effective dated

    Change a fee schedule without rewriting the product. Every variant revision carries its own effective date, so you can schedule a change in advance and answer later what the pricing was at any point in time.

  • Promotions with a real lifecycle

    Eligibility, enrollment, stacking rules, and automatic expiry are part of the promotion rather than manual steps around it. When a campaign ends, the pricing reverts on its own.

  • Rewards driven by behavior

    Discount a rate or waive a fee when conditions are met, and recalculate tier status each cycle as the relationship changes. Benefits follow what the customer actually does rather than what they qualified for a year ago.

  • Custom logic where you need it

    Most pricing is configuration. For the genuine edge cases, write a rule in JavaScript that runs inside the billing engine, with your own custom fields available as first class properties on the customer and account.

  • An audit trail on every charge

    For any amount on a statement you can retrieve the inputs, the rule that fired, the output, and the account it applied to. Not a log line saying a fee was charged, but the full calculation.

Your pricing logic, your vocabulary

Fincarna ships with core objects: accounts, customers, events, and products. Every institution is different, so you can extend any of them with your own properties through the dashboard, the API, or a column in a file.

Those extensions are not just metadata. The pricing engine has full access to every custom field you define. Extend the customer object with a loyaltyTier property and it is immediately available as customer.loyaltyTier in your billing rules.

Most pricing never needs code at all. When an edge case genuinely does, it reads like the business rule it represents.

A customer template in Fincarna adding custom attributes such as date of birth, accessibility eligibility and first-time home buyer

Where pricing drifts from policy

  • Waivers nobody reviews

    Fee waivers granted at account opening with no end date or reason on record, so nobody can say whether they still reflect the relationship. Fincarna gives every waiver an explicit lifecycle and flags any without an expiry, so each one is renewed or ended on purpose.

  • Tier miscalculation

    "Average monthly balance" can mean different things depending on who configured it. Fincarna calculates balances using your exact rules (daily average, monthly average, minimum, or any custom formula) and applies the correct tier assignment consistently across every account.

  • Stale fee schedules

    Fee schedules change, but configurations don't always keep up. Fincarna maintains a single source of truth for your fee schedules. Every charge is calculated from the current rules, delivered in real time or on your billing cycle.

  • Promotions that never end

    A promotional rate was supposed to end after 90 days. The marketing campaign stopped, but the billing adjustment is still active. Fincarna manages all promotional rates with hard expiry dates. When the promotion ends, the rate reverts.

  • Services priced by accident

    Wire transfers, certified cheques, and foreign currency conversions priced one way for one customer and another way for the next, because each billing event was configured by hand. Fincarna maps every billable event to a rule and flags the gaps, so similar customers are treated the same and every exception is deliberate.

What changes

Every cycle
Billing enforcementEvery account, every charge, calculated automatically from your current rules
Full
Audit trailEvery pricing decision is auditable: the rule, the account, the amount, and why it was applied

The benefit your core cannot run today

The relationship pricing it cannot express, so it never shipped. We will model it with you live.

or email us at hello@fincarna.com