Your contracts already say what to bill. Your billing system doesn't know it.
For SaaS, fintech, telecom and energy companies billing negotiated, usage-linked B2B contracts.
Verdix reads the signed agreement, pulls the usage it requires, and turns both into approved, clause-linked billing instructions. Keep your existing billing stack, with live integrations to Remembill and Stripe.
From signed agreement to paid invoice
Verdix turns the commercial terms and usage in the agreement into approved billing. Remembill takes the invoice from delivery to payment, including recovery when a payment fails.
- Fixed + variable billing logic configured
- Required usage pulled
- Clause-linked review & approval
Remembill- Invoice delivered
- Simple payment without login
- Failed-payment recovery
Commercial terms + usage → approved billing
Approved invoice data sent automatically
Invoice delivery → payment → failed-payment recovery
Live Remembill design-partner pilot using a real enterprise agreement. Customer identifiers are redacted and commercial figures shown are illustrative.
Live Remembill design-partner pilot using a real enterprise agreement. Customer identifiers are redacted and commercial figures shown are illustrative.
Bespoke contracts move faster than billing systems
Commercial terms get negotiated in the agreement. Someone still has to translate them into billing logic, every cycle, by hand.
Terms live in the agreement
Rates, tiers, commitments and exceptions never make it cleanly into billing configuration.
Usage lives somewhere else
Transactions, sessions, seats and consumption sit in operational systems, outside the billing workflow.
People connect them manually
Teams interpret the contract, retrieve usage and rebuild the calculation every cycle.
Built for companies whose agreements are negotiated, not configured
Verdix is built for B2B companies where customer-specific rates, tiers, commitments, credits and amendments live in signed agreements — while the usage needed to bill them lives somewhere else.
You already have a billing, ERP or payment system worth keeping. The problem is the manual work in between: RevOps and billing teams still have to interpret what was agreed, retrieve the required usage and translate both into the right billing logic.
Best fit: negotiated B2B contracts · recurring or usage-linked pricing · operational data accessible from existing systems · manual contract-to-billing workflows.
Different industries. The same contract-to-billing problem.
Enterprise SaaS & AI
Bespoke pricing schedules, minimum commitments, usage tiers, ramp discounts, overages, credits, annual escalators and amendments.
Usage tiers · minimums · ramp discounts · credits
Payments & fintech
Merchant-specific transaction rates, volume tiers, minimum fees, platform charges, revenue shares and negotiated pricing exceptions.
Transaction rates · volume tiers · minimum fees · revenue shares
EV charging & energy
Customer-specific tariffs, subscription and usage charges, site-specific pricing, energy pass-through rules and contract amendments.
Tariffs · usage charges · site-specific pricing · pass-through rules
Telecom & connectivity
Customer-specific messaging, voice, data and IoT rates, volume tiers, minimum commitments, reseller pricing and negotiated contract amendments.
Messaging & data rates · volume tiers · minimums · reseller pricing
From signed agreement to approved billing instruction — in four steps
The signed agreement
Rates, tiers, commitments, escalators, discounts and amendments are extracted and structured from the signed agreement.
Only the required usage
Transactions, sessions, seats, orders or consumption are retrieved from the systems you already use. No new usage pipeline.
The billing instruction
Agreed rates, tiers and billing rules are applied to the actual usage, with every figure linked back to its source.
Your billing owner approves
Verdix flags exceptions and ambiguous terms for review. Nothing is sent downstream until your team approves it.
Approved billing instructions flow into the systems you already use
No billing migration. Keep the systems you already run.
Remembill
StripeFrom signed agreement to configured billing — in the actual platform
This is a live Remembill design-partner pilot shown with illustrative commercial figures: a 12-month base subscription, a one-time integration fee, tiered SMS pricing, a quarterly commercial rule and an escalation clause — including terms Verdix surfaces for human interpretation before they affect billing.
12-month contract with Fenix Försäkring AB, running 11 Aug 2026 to 10 Aug 2027 — SEK 6,900.00/month base subscription plus a SEK 12,000.00 one-time integration fee.
Base fee billed monthly in advance · SMS usage billed quarterly in arrears · 30 days net from invoice date · auto-renews (90-day notice required).
AI extraction complete · human review required for 4 commercial decisions.
Click any rate. Land on the clause that set it.
Every calculation keeps its evidence — the contract term, source usage and applied logic. So your team can see exactly why something was billed, and trace it back to the signed agreement.
4.2 SMS-påminnelser — volymbaserad prissättning
SMS-påminnelser mäts och faktureras kvartalsvis, i efterskott — till skillnad från grundavgiften, som faktureras månadsvis i förskott enligt punkt 4.1. Volymen nollställs vid varje kalenderkvartals början (kvartal: jan–mar, apr–jun, jul–sep, okt–dec).
| Volym per kvartal | Pris per SMS-påminnelse |
|---|---|
| 0 – 500 | Ingår i grundavgift |
| 501 – 2 000 | 1,10 SEK |
| Över 2 000 | 0,85 SEK |
Garanterad minimiavgift: Kunden betalar lägst 5 000 SEK per kalenderkvartal för SMS-påminnelser, oavsett faktisk volym under kvartalet.
The base fee bills monthly in advance. SMS usage bills quarterly in arrears, with volume resetting each calendar quarter. Verdix preserves these component-level billing rules rather than flattening them into a single contract-wide cadence.
Verdix surfaced the SEK 5,000 quarterly minimum because its interaction with the included allowance required interpretation. The billing owner confirmed the treatment, and Verdix retained both the source clause and the approved rule.
Verdix can also use the same agreement logic to verify incoming supplier, reseller and partner invoices.
Catches: wrong rates · expired discounts · unsupported fees · missed rebates · incorrect indexation
Designed around European data requirements
Your contracts contain commercially sensitive pricing, customer and operational information. Verdix is designed to minimise what reaches the model layer and keep the processing path controlled and traceable.
EU-based architecture
Customer data is processed within European infrastructure.
Masked before AI processing
Personal identifiers such as names, email addresses, phone numbers and other direct identifiers are masked before contract text reaches the model layer.
No training on your contracts
Your agreements and customer data are not used to train AI models.
Traceable by design
Extracted terms, source clauses and billing calculations remain linked throughout the workflow.
Pricing aligned to completed agreement workflows
No percentage of revenue. No charge for every raw usage event. No requirement to replace your billing or payment infrastructure.
Not with the revenue flowing through them.
Test Verdix on a historical contract and the usage behind it before committing to a production integration.
- Complimentary first audit
- Read-only validation
- Early product access
- Direct roadmap input
- Preferred commercial terms
For RevOps, Billing and Finance teams running recurring agreement-to-billing workflows.
- Customer agreement-to-billing
- Automated usage retrieval
- Clause-linked calculations
- Live integrations with Remembill and Stripe
- Team review and approval
For higher volumes, multiple entities or additional deployment, security and support requirements.
- Custom workflow volumes
- Multiple integrations and data sources
- Enterprise access controls
- Configurable retention and audit requirements
- Support and commercial SLA options
Bring us one difficult agreement. We'll show you what it should have billed.
Start with one historical agreement and the usage behind it. Verdix reconstructs the billing logic and shows the evidence behind every result.
30-minute fit check → complimentary first audit → read-only pilot
Early access · Direct roadmap input · Preferred commercial terms