whats-best.ai
Search Sign in

Billing & Invoicing

Fenerum

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Fenerum ApS · www.fenerum.com

Report an error on this page Is this your product? →

Link to this page

Fenerum: AI-assisted analysis on whats-best.ai Fenerum: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Fenerum at a glance

Vendor
Fenerum ApS
Headquarters
Not stated on the vendor’s pages as of 26 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 26 Oct 2026
Free plan
Yes, per the vendor’s own page source, captured 26 Oct 2026
Panel verdict
The AI panel rates Fenerum 3/5, the mean of 6 judges. Fenerum, from Fenerum ApS of Denmark (CVR 40430989), is subscription billing for B2B SaaS with automatic booking into the accounting system. how scores are made
As of
Vendor pages captured 26 Oct 2026; evaluated by the panel 28 Oct 2026. all sources

Fenerum alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Billing Engineer

Weighted verdict

Wires billing into the product and gets paged when a webhook goes missing. Wants a documented API for usage events, idempotent webhooks, entitlements the app can read, a sandbox that behaves like production, and a migration path that moves subscriptions and payment tokens out again if the company outgrows the tool.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Billing Engineer

Panel median The Billing Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Billing Engineer
Plans, pricing models & subscription lifecycle 3 of 5 3 of 5
Invoices & e-invoicing compliance 3 of 5 3 of 5
Cross-border VAT & tax handling 2 of 5 2 of 5
Payment collection, dunning & portability 3 of 5 3.5 of 5
Revenue reporting & accounting handoff 3.5 of 5 3.5 of 5
European sovereignty 3.5 of 5 3.5 of 5
Pricing transparency 3 of 5 3.5 of 5

Plans, pricing models & subscription lifecycle

How this is scored

How the product models what is sold and to whom: plans, add-ons and price points, trials, upgrades and downgrades with proration, usage-based and seat-based pricing, contract terms and renewals, quotes, and a self-service portal where the customer changes or cancels their own subscription.

0 — No subscription model; recurring charges are set up by hand per customer or per invoice.

3 — A recurring invoice or a fixed plan that repeats on a schedule, but no proration, no trials, no add-ons and no usage component.

5 — Plans with add-ons and trials, upgrades and downgrades with proration, renewals and cancellations handled by the system, and a customer portal for viewing and changing the subscription.

8 — Usage-based, tiered, volume and seat-based pricing with metering through an API, contracts with minimum terms, ramps and notice periods, quotes that convert into subscriptions, multiple currencies and price books, and the subscription history kept per customer.

10 — The commercial model lives in the product: hybrid pricing (commitments, prepaid credits, overage) without custom code, price changes rolled out to existing customers with grandfathering, entitlements exposed to the selling application, and every change to a subscription versioned and attributed.

Report an error

The Billing Engineer

Renewals, cancellations and reactivations are handled by the system and a self-service portal lets customers create, change and upgrade subscriptions, with contracts supporting binding commitment lengths and quantity-based tiers and discounts per seat or as a flat percentage. What holds me back: I found no public information on trials, proration on mid-cycle changes, usage-based metering through an API, or quotes that convert into subscriptions. 5 6 13

Report an error

Invoices & e-invoicing compliance

How this is scored

Whether the invoices the product issues are legally valid where the customer is: mandatory invoice content, sequential numbering, credit notes and cancellations instead of edits, retention and archiving to GoBD, and structured e-invoices (XRechnung, ZUGFeRD/Factur-X, Peppol) for business customers and public bodies.

0 — No invoices; the product charges cards or sends payment requests and the seller writes invoices elsewhere.

3 — PDF invoices from a template, but numbering, mandatory content, corrections and retention are not described.

5 — Invoices with sequential numbering and the mandatory content stated, credit notes and cancellations instead of edits, invoices in several languages and currencies, and a documented archive.

8 — Structured e-invoices to EN 16931 issued as XRechnung or ZUGFeRD/Factur-X and sent through Peppol, GoBD-compliant numbering and unalterable archiving stated, invoice data exportable for a tax audit, and the e-invoicing mandates in named EU countries addressed.

10 — Invoicing that stands up in any audit it may face: e-invoicing to public bodies and businesses in several EU countries with the channels named, clearance and reporting models (France, Italy, Poland) supported where they apply, a Verfahrensdokumentation or equivalent offered, and every invoice traceable to the subscription event that produced it.

Report an error

The Billing Engineer

Credit notes are applied through the API on an invoice in chargeback status and refunds return a credit note rather than an edit, invoices are language-versioned, and Peppol and EAN e-invoice sending run through named subprocessors alongside a VAT report export by country and period. I found no public information on sequential numbering rules, retention or archiving standards, or XRechnung and ZUGFeRD formats. 4 5 8

Report an error

Cross-border VAT & tax handling

How this is scored

How the product gets tax right when the seller sells across borders: VAT rates per country and product type, reverse charge for business customers with VAT ID validation (VIES), the EU One-Stop-Shop, US sales tax — or, for a merchant of record, which tax liability it takes on in its contract and which it leaves with the seller.

0 — No tax handling; the seller types the rate on every invoice.

3 — One configurable VAT rate or a manual rate table, with no customer-location logic and no VAT ID check.

5 — Tax rates applied by customer country and status, reverse charge for business customers with a VAT ID field, and tax shown correctly on invoices and in reports.

8 — Automatic VAT per country and product type, VIES validation of VAT IDs, OSS reporting data, evidence of customer location kept, US sales tax through a named engine — or a merchant-of-record contract that states the tax liability it assumes and in which countries.

10 — Tax is discharged and evidenced: filings or filing data for OSS and the countries sold into, rate changes maintained by the vendor with a stated process, tax decisions per invoice explainable, and the division of liability between seller and vendor written into the terms.

Report an error

The Billing Engineer

VAT rates live in codes synced from the connected accounting system and are assigned to invoice lines when posting, with a VAT report export available by country, period and granularity. I found no public information on reverse charge for business customers, VAT ID validation against VIES, One-Stop-Shop reporting, or US sales tax. 8 9

Report an error

Payment collection, dunning & portability

How this is scored

How invoices turn into money: which payment providers and methods the product works with, SEPA direct-debit mandates, automatic retries and dunning sequences, payment reconciliation, collections handover — and whether the seller can move subscriptions and stored payment details to another provider.

0 — No collection; invoices are sent and payment is chased by hand.

3 — One built-in payment provider with card payments, and failed payments reported but not retried or chased.

5 — Several payment providers or methods including SEPA direct debit with mandates, automatic retries of failed payments, dunning emails with configurable steps, and payments matched to invoices.

8 — Gateway-agnostic collection across named providers, smart retries and card updaters, dunning with escalation and service suspension rules, bank-transfer reconciliation, a handover to a collection agency, and recovery reported.

10 — Collection is portable and measurable: subscriptions and payment tokens importable and exportable with a documented migration path, routing across providers per country or method, recovered revenue reported per dunning step, and no lock-in to the vendor's own payment service stated in the terms.

Report an error

The Billing Engineer

Collection spans named gateways — Stripe on the free tier plus Nets and QuickPay above — with SEPA direct debit across all 36 SEPA countries via Stripe, automated dunning, and a documented API call that hands a nonpaying invoice to a debt collector after onboarding. Card expiry triggers a customer notice 30 days ahead and payment webhooks cover declines and authentication; I found no public information on automatic retries, a documented path for exporting subscriptions and payment tokens, or recovery reported per dunning step. 2 5 8 10 13

Report an error

Revenue reporting & accounting handoff

How this is scored

What finance gets out of billing: MRR, ARR, churn and cohort reporting, revenue recognition and deferred revenue, the export or sync to the accounting system and to DATEV, CRM and data-warehouse integrations, an API and webhooks, and a complete export of customer and subscription data.

0 — No reporting and no export beyond downloading individual invoices.

3 — A revenue overview and a CSV export of invoices, with no subscription metrics and no accounting integration.

5 — Subscription metrics (MRR, churn) on a dashboard, an export or sync to at least one named accounting tool, and a documented API with webhooks.

8 — Revenue recognition with deferred revenue schedules, a DATEV export or booking-ready journal for the ledger, native CRM and accounting integrations named, MRR movements explainable per customer, and a full data export documented.

10 — Billing is the system of record for revenue: recognition to IFRS 15 / ASC 606 stated, month-end close supported with reconciled reports, data-warehouse sync, audit trail of every financial event, and a complete export of customers, subscriptions and invoices that a successor system can import.

Report an error

The Billing Engineer

Subscription metrics, churn and retention cohorts, profit & loss, month-end close and two deferred revenue schedules are in the product, with real-time automatic booking into the accounting system and an API exposing 16 webhook events across the subscription and payment lifecycle. Data leaves through Excel exports of receivables, active subscriptions and contacts; I found no public information on a named accounting target such as DATEV, revenue recognition stated to a named accounting standard, or a complete export a successor system could import. 1 12 13

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where customer, invoice and payment data are hosted, and who the subprocessors are (hosting, payment providers, tax engines, email delivery). Independently sourced by the sovereignty pipeline; billing data is personal and financial at once, so the whole chain counts, not only the database.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (tax engine, email, analytics, support) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Billing Engineer

The contracting entity is a Danish company covered by the EU GDPR with the data processing agreement inside the master service agreement, application and database hosting sits on Scaleway processing in France and the Netherlands, and a public subprocessor list names each provider with its registration and processing countries — Datadog is registered in the USA though it processes in Germany. I found no public information on security certifications, ownership structure, or documented data export and deletion. 1 3 4

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: platform fee, percentage of billed revenue or per-invoice fees, which modules (revenue recognition, e-invoicing, tax, extra gateways) cost extra, overage above a revenue band, setup and minimum term, and the merchant-of-record fee where it applies.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with billed revenue, invoices or modules is unclear.

5 — Tiers are public with their main inclusions and revenue bands, but at least one commonly needed piece (e-invoicing, revenue recognition, extra gateways, overage) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (revenue percentage, per invoice, per subscriber), overage and add-ons listed, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given billed revenue, invoice volume and module set, with every add-on, setup, support and payment or merchant-of-record fee and the cancellation and data-return terms published.

Report an error

The Billing Engineer

Tiers are public with their MRR caps — free up to 50.000 DKK MRR, Plus at 1.149 DKK per month up to 100.000 DKK MRR — a stated 12-month minimum commitment, and an explicit statement that they do not charge a percentage of revenue or per invoice, with add-ons priced (Bank Integration From DKK 199, Expense Management DKK 399, HubSpot Integration DKK 149) and onboarding from DKK 10.000. The Enterprise tier is contact-us from 8.000.000+ MRR and the VAT treatment of prices isn't stated, so the full annual cost isn't computable from public pages alone. 2

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 4 Report an error

Questions about Fenerum

Is Fenerum European?

Yes. whats-best.ai classifies Fenerum as EU-Made.

Where does Fenerum store data?

Not stated on the vendor’s pages as of 26 Oct 2026.

Does Fenerum have a free plan?

Yes. Fenerum has a free plan, per the vendor’s page captured 26 Oct 2026.

What are the best alternatives to Fenerum?

As of 28 Oct 2026, the panel rates Chargebee (3.5/5), Younium (3.5/5) and Stripe Billing (3.5/5) highest among the other 12 Billing & Invoicing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Younium (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Fenerum alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Fenerum? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.fenerum.com Checked 26 Oct 2026 Details →
  2. 2 Pricing page www.fenerum.com Checked 26 Oct 2026 Details →
  3. 3 Legal notice www.fenerum.com Checked 26 Oct 2026 Details →
  4. 4 Subprocessor list www.fenerum.com Checked 26 Oct 2026 Details →
  5. 5 Plans, pricing models & subscription lifecycle — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  6. 6 Plans, pricing models & subscription lifecycle — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  7. 7 Invoices & e-invoicing compliance — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  8. 8 Invoices & e-invoicing compliance — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  9. 9 Cross-border VAT & tax handling — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  10. 10 Payment collection, dunning & portability — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  11. 11 Payment collection, dunning & portability — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  12. 12 Revenue reporting & accounting handoff — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →
  13. 13 Revenue reporting & accounting handoff — found from sitemap www.fenerum.com Checked 26 Oct 2026 Details →