---
title: "Rate card"
description: "A rate card is the full price definition for a plan or customer — every fee, rate, tier and minimum — versioned so every invoice traces to its terms."
url: "/glossary/rate-card/"
updated: "2026-09-28"
aka: ["price book","pricing plan","tariff"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page defines “Rate card” — a term from payments, payouts and finance operations. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when someone needs this term defined, or wants to see how the mechanism runs in practice — the rule, the money movement and the ledger entry.

# Rate card

A **rate card** is the complete price definition that applies to a plan, a customer or a contract: the platform fee, each usage rate and its tiers, seat prices, percentage fees, included units, discounts, minimum commitments and caps. In billing systems it is a **versioned** object — every change is a new version with an effective date, so every invoice can be traced to the exact terms that produced it.

## What a rate card contains

- **Components** — each priced building block: platform fee, payment-volume fee, API-call fee, AI-usage fee, seat fee, payout fee, FX fee.
- **Models** per component — flat, per unit, percentage, tiered, volume, graduated or package.
- **Modifiers** — discounts and credits.
- **Country rules** — surcharges or overrides by buyer or processing country.
- **Tax policy** — tax-exclusive or inclusive, reverse charge.
- **Enterprise overrides** — negotiated rates, minimum commitments, ramps and caps.

## Why versioning matters

A price change should never rewrite a billed period. Without versioned rate cards, changing a rate on the 15th makes last month's invoices unreproducible — and a disputed invoice undefendable.

## How Fynex does it

Fynex prices each metric on a contract as a dated version and evaluates components in a fixed order — rate, allowance, caps, rounding, minimum — so the preview, the invoice and the audit trail agree. See [Usage-Based Billing](/features/usage-billing/).