GITNUXSOFTWARE ADVICE
Business FinanceTop 10 Best Call Billing Software of 2026
Top 10 call billing software for carriers and VoIP teams, ranked by features and pricing. Includes MOR and Telgoo5 telecom billing.
How we ranked these tools
Gitnux editors write the brief first: the topic, the inclusion rules, and the frame for what belongs.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
MOR is the best pick for teams that need repeatable call rating and reruns to produce consistent invoices across destinations, while PortaBilling fits carriers or resellers needing tariff-governed CDR mediation and governed invoicing, and Call Accounting Mate is the cheaper entry if you just need invoice-ready chargeback exports.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
MOR
Rate-comparison driven rating that evaluates alternative tariff outcomes consistently from the same mediated CDR inputs.
Best for: Fits when teams need repeatable call rating, reruns, and rate comparisons across carrier and destination scenarios.
Telgoo5 Telecom Billing
Editor pickRating configuration ties call attributes to charge outcomes while keeping the CDR-to-invoice workflow operationally repeatable.
Best for: Fits when telecom billing teams need repeatable CDR-to-invoice rating across many destinations.
PortaBilling
Editor pickMulti-tenant account operations with fine-grained RBAC plus auditable charging and billing actions.
Best for: Fits when carriers or resellers need governed CDR mediation, tariff-based rating, and repeatable invoices across multiple upstreams.
Comparison Table
MOR
SMBMOR is a VoIP billing and management platform with prepaid, postpaid, rating, and invoicing features.
Rate-comparison driven rating that evaluates alternative tariff outcomes consistently from the same mediated CDR inputs.
MOR turns call events into billable charges by applying per-destination tariff logic to CDR fields and producing invoice-ready totals. It supports rate comparison workflows that help teams validate least-cost outcomes before routing or carrier changes. It also handles recurring reconciliation by re-rating mediated CDR sets and carrying results into account balance movements.
A tradeoff appears in the setup depth needed for correct tariff and normalization rules, especially when jurisdictions and destination prefixes differ across regions. MOR fits teams that already own CDR ingestion and want a controlled rating and settlement layer that can be rerun when rate decks change.
- +Deterministic rating runs from CDR fields to charge outputs
- +Rate comparison workflows across destinations and carrier scenarios
- +Re-rating and reconciliation support for mediated CDR sets
- +Account ledger movements for prepaid and postpaid settlement
- –Tariff setup requires careful mapping of CDR fields and prefixes
- –Operational overhead increases when rate-deck changes need frequent reruns
- –Advanced mediation workflows depend on well-formed input CDRs
- –Automation depth relies on integration fit with existing ingestion
Carrier operations teams
Compare tariff outcomes per routing choice
Lower termination cost visibility
Billing ops teams
Reconcile balances after CDR mediation
Faster dispute resolution
Show 1 more scenario
Telecom finance teams
Maintain prepaid and postpaid ledgers
Cleaner settlements
Apply rating results into prepaid consumption tracking or postpaid invoice totals and reconciliation.
Best for: Fits when teams need repeatable call rating, reruns, and rate comparisons across carrier and destination scenarios.
Telgoo5 Telecom Billing
SMBTelgoo5 provides telecom billing, rating, provisioning, and subscriber management software.
Rating configuration ties call attributes to charge outcomes while keeping the CDR-to-invoice workflow operationally repeatable.
Telgoo5 Telecom Billing fits organizations that already manage call detail records and need consistent rating, rounding behavior, and invoice-ready outputs. The system is built around usage-based charging workflows, with rule configuration that maps call attributes to charge outcomes. It can be used for prepaid account control and for postpaid reconciliation cycles when CDR mediation and reporting are part of the operations plan.
A clear tradeoff is that deeper automation depends on how CDR fields are normalized before ingestion, since rating outcomes rely on the available call attributes. The best usage situation is when a telecom team must standardize rating across multiple destinations and then feed invoices, dispute handling inputs, or accounting exports on a predictable schedule.
- +Configurable rating rules align charges to destination and call attributes
- +Account-based flows support both prepaid control and postpaid reconciliation
- +Repeatable CDR-to-invoice workflow reduces manual reconciliation work
- +Reporting outputs support operational audits of charge calculations
- –Correct rating depends on clean and consistently mapped CDR fields
- –Complex rule sets can require disciplined configuration management
Revenue operations teams
Standardize multi-destination invoice calculations
Fewer billing adjustments
Carrier billing operations
Prepaid usage balance enforcement
Tighter spend control
Show 2 more scenarios
Accounting and reconciliation teams
Postpaid reconciliation from CDRs
Cleaner month-end close
Teams use the rating workflow to support month-end reconciliation and invoice generation.
Dispute management teams
Trace charge computation inputs
Faster dispute resolution
Teams pull charge-relevant call data and computed outcomes for dispute investigations.
Best for: Fits when telecom billing teams need repeatable CDR-to-invoice rating across many destinations.
PortaBilling
enterprisePortaBilling provides rating, charging, invoicing, and account management for communications providers.
Multi-tenant account operations with fine-grained RBAC plus auditable charging and billing actions.
PortaBilling is designed for high-throughput call detail record flows where mediation, rating, and charging must be consistent across prepaid and postpaid accounts. It processes CDRs into billable outcomes using tariff table logic that can reflect destination rules and jurisdiction-based outcomes, then feeds results into reconciliation and invoice generation workflows. For teams comparing routes across Twilio, Vonage, and Plivo, the operational focus is on metering inputs and keeping rating results reproducible across source formats.
A key tradeoff is configuration complexity, because route logic, account structures, and mediation mappings require careful setup to match each upstream carrier feed. It fits best when call routing, rate deck changes, and dispute handling need controlled governance rather than ad-hoc reporting. Teams that rely on rapid experimentation often spend more time tuning mediation and rating behaviors than teams that run stable carrier feeds.
- +Carrier-style CDR mediation and normalization for repeatable rating outcomes
- +Prepaid and postpaid account workflows with controlled enforcement and reconciliation
- +Strong operational governance with RBAC and audit trails
- +Automation support for provisioning and integration across telephony systems
- –Initial setup requires deep configuration of routing, mediation, and account structures
- –Rate deck changes can create operational overhead for large reseller hierarchies
Telecom billing engineering teams
Standardize multi-carrier CDR mediation
Lower rating discrepancies
Reseller operations teams
Prepaid enforcement across child accounts
Better spend control
Show 1 more scenario
Finance and billing analysts
Reconcile usage into invoices
Faster close cycles
Use mediation outputs to drive invoice generation and month-end reconciliation workflows.
Best for: Fits when carriers or resellers need governed CDR mediation, tariff-based rating, and repeatable invoices across multiple upstreams.
Azure Billing for Telecom
enterpriseAzure-hosted telecom billing reference architecture for call usage rating and invoicing.
Azure-native governance and audit integration around telecom billing workflows and billing-run automation.
Azure Billing for Telecom targets telco usage charging with billing workflows built around usage inputs, rating, and account-level outputs. It fits teams that need integration depth into Microsoft cloud operations through Azure services, identity controls, and configurable automation around metering, rating rules, and invoice-ready outputs.
- +Azure-native identity and audit logging for controlled billing operations
- +Configurable rating workflows that map usage inputs to billing outputs
- +Integration patterns that fit Microsoft cloud governance and automation
- +Operational support for end-to-end billing runs with reconciliation steps
- –Rate and tariff configuration requires disciplined setup and validation
- –Telephony-specific integration depth depends on how CDR inputs are produced
- –Operational complexity increases when multiple account and invoice scenarios exist
- –Requires Azure-side integration work for end-user portals or disputes
Best for: Fits when telecom billing teams already run Azure and need controlled rating-to-invoice automation.
Rev.io Telecom Billing
SMBRev.io combines telecom billing, subscriber management, payments, and operational workflows.
Jurisdiction-based rating combined with configurable tariff tables for consistent reruns across changed rate decks.
Rev.io Telecom Billing processes call records into rated usage for voice and SIP trunk related traffic, then produces invoice-ready results for usage-based charging. It supports rate deck style tariff tables and jurisdiction-aware rating decisions while handling per-call billable duration rules.
- +Supports jurisdiction-based rating logic for destination and billing rules
- +Provides configurable tariff table inputs for rate comparisons across markets
- +Automates recurring rating and re-rating cycles for operational control
- +Exports CDR outputs that fit finance reconciliation workflows
- –Requires careful configuration to keep billable duration rules consistent
- –API coverage can be uneven across administrative and operational workflows
- –Complex rate decks add governance work for ongoing changes
- –Operational reporting depth depends on the chosen export and reconciliation path
Best for: Fits when teams need repeatable call-rating automation with jurisdiction-aware rules and controlled tariff updates.
Alepo Charging and Billing
enterpriseAlepo provides real-time charging, policy control, and billing systems for communications providers.
Tariff-table rule evaluation that applies destination and jurisdiction logic during charging computation.
Alepo Charging and Billing targets carriers and VoIP operators that need usage-based rating and invoicing built around call event streams. It supports tariff-table style rating workflows that apply jurisdiction and destination rules to CDR-like inputs.
- +Tariff-table rating workflows support destination and jurisdiction rule application
- +API-first ingestion supports automation for call events and billing runs
- +Prepaid and postpaid control paths cover common telecom account styles
- +Invoice generation ties rating output to accounting artifacts
- –Configuration depth can require careful governance for rate and rule changes
- –CDR mediation and CSV handling are not positioned as the primary workflow
Best for: Fits when teams need automated rating runs and invoice outputs with rule-driven telecom controls.
Telarix
enterpriseInterconnect billing and traffic management software for telecom carriers.
Telarix supports carrier-style CDR mediation with rerunnable rating jobs tied to structured rating outputs for reconciliation.
Telarix is a call billing and rating system designed around carrier-grade mediation and rating workflows. It provides support for CDR ingestion, rate deck and tariff table based rating, and invoice-oriented output for ongoing reconciliation.
- +API-first integration surface for CDR mediation, rating, and downstream posting
- +Configurable rate decks and tariff table logic for destination and jurisdiction rating
- +Operational tooling for high-volume batch rating and reruns
- +Supports dispute workflows through auditable rating outputs
- –Complex rule configuration can require strong governance to avoid rating drift
- –Feature depth favors mediation and rating teams over pure self-serve UI users
- –CDR mapping and normalization effort depends on source format consistency
- –Advanced scenarios may require additional implementation work for edge cases
Best for: Fits when carriers or call centers need API-driven rating, reruns, and controlled rule changes across multiple routing sources.
Call Accounting Mate
vertical specialistCall Accounting Mate tracks telephone usage and assigns call costs to users, departments, or accounts.
Destination and jurisdiction-aware rating driven by configurable rate tables and dial plan attributes.
Call Accounting Mate focuses on turning telephony CDR feeds into bill-ready outputs with a rate deck workflow and repeatable rating runs. It supports rate comparisons across destinations and jurisdictions, then produces invoices and usage exports for accounting reconciliation.
- +Rate table workflow supports destination and jurisdiction-based charge differences
- +Invoice generation plus CDR export supports accounting and dispute workflows
- +Automation runs rating and reporting on schedules for consistent outputs
- +Admin configuration ties charge rules to dial plan attributes
- –Setup requires careful configuration of dial plan matching and rate selection
- –API depth for external systems and provisioning is limited compared with top tiers
- –Real-time enforcement style controls are not emphasized for prepaid use cases
- –SIP and RTP analytics are not a primary focus for operational troubleshooting
Best for: Fits when telecom ops need repeatable rating runs, rate comparisons, and invoice-ready exports.
A2Billing
API-firstOpen-source telecom billing and calling card platform built on Asterisk PBX.
CDR mediation and normalization before rating lets A2Billing handle imperfect upstream call records.
A2Billing generates VoIP call ratings and invoices by turning SIP trunk usage into rated call detail records. It supports a tariff table workflow for per-destination pricing, plus CDR mediation steps before postpaid reconciliation or prepaid balance enforcement.
- +Tariff table model supports destination-based per-minute rating workflows
- +CDR mediation pipeline helps normalize and prepare records for rating
- +Self-hosted deployment fits environments needing control over accounting logic
- +Operational exports support downstream reconciliation and reporting
- –Admin workflows can require technical setup for rate decks and routing
- –API coverage for real-time balance enforcement is not as direct as modern SaaS stacks
- –Complex rating edge cases can increase configuration and troubleshooting time
- –Front-end tooling for dispute workflows is thinner than fully managed billing suites
Best for: Fits when teams need self-hosted call accounting with strong tariff control and CDR processing for multiple trunks.
Telnyx
API-firstTelecom API and platform with usage reporting and billing practices for voice calling traffic.
Telnyx provides an API-driven rated-usage workflow that ties call detail records to automated charging outcomes.
Telnyx is a call billing option built around programmatic voice and communications connectivity, with billing and rating exposed through its API-first operations. It supports usage-based charging workflows that map call detail records into rated events, covering common carrier and termination use cases.
- +API-first call rating and usage event handling fits telecom automation workflows
- +Supports per-destination rating patterns using configurable rate logic and routing inputs
- +Handles CDR to rated usage flows for mediation and charging operations
- +Extensible provisioning patterns help integrate voice circuits and metering pipelines
- –Operational setup requires telecom-grade discipline for correct rating inputs
- –Administration UI coverage can feel thin compared with API-based configuration workflows
- –Complex international and jurisdiction rule sets take time to validate end-to-end
- –Dispute and mediation workflows depend on consistent CDR field quality
Best for: Fits when telecom teams need API-driven call charging workflows with rate comparisons across carriers and destinations.
Conclusion
After evaluating 10 call billing software, MOR stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Call Billing Software
Call billing software turns call detail records into rated usage and invoice-ready charges using tariff tables, mediation rules, and repeatable rating runs. This guide covers MOR, PortaBilling, Telarix, Telnyx, and the other listed systems used to compare rate outcomes across carrier and destination scenarios.
The tools in this list differ in how they map CDR fields into rating inputs, how they rerun rating to validate changed rate decks, and how they govern billing actions across prepaid control and postpaid reconciliation workflows. The next sections focus on integration depth, automation and API surface, and admin controls that matter when rate comparisons must stay deterministic across reruns.
Call Billing Software: CDR mediation, call rating engines, and usage-to-invoice charging
Call billing software ingests call events or call detail records, applies tariff and jurisdiction logic, and produces charge outputs that can feed invoice generation and reconciliation workflows. Systems like PortaBilling and Telarix emphasize carrier-style CDR mediation and rerunnable rating jobs that help teams reproduce the same charging results when rate decks change.
In rate comparison use cases across Twilio, Vonage, and Plivo, the practical differentiator is how each platform evaluates rating rules against the same mediated inputs and how it manages configuration changes without rating drift. MOR focuses on deterministic reruns that compare alternative tariff outcomes from the same mediated CDR inputs, while Telnyx leans on an API-driven rated-usage workflow that ties call detail records to automated charging outcomes.
Call billing capabilities that change rate-comparison accuracy
Rate comparisons only hold up when the system maps the same mediated CDR inputs into rating outputs with deterministic reruns. The cards below show major differences in how tools handle CDR mediation, rule evaluation, and repeatable charging outcomes.
For teams comparing rates across Twilio, Vonage, and Plivo, the practical needs are consistent CDR-to-charge mapping, controlled rate-deck updates, and governance over billing actions that feed invoices and reconciliation workflows.
Deterministic reruns for rate-deck comparisons
MOR is built around rate-comparison-driven rating runs that evaluate alternative tariff outcomes from the same mediated CDR inputs. Telgoo5 Telecom Billing ties rating configuration to charge outcomes while keeping the CDR-to-invoice workflow operationally repeatable.
CDR mediation and normalization before rating
PortaBilling supports carrier-style CDR mediation and normalization so rating reruns use consistent inputs across upstreams. A2Billing uses a CDR mediation pipeline to normalize imperfect upstream call records before tariff-table rating.
Jurisdiction logic tied to tariff table evaluation
Rev.io Telecom Billing combines jurisdiction-based rating with configurable tariff tables so rate-deck changes can be rerun consistently. Alepo Charging and Billing applies destination and jurisdiction rules during tariff-table rule evaluation inside the charging computation.
Automation-first integration surface for rated usage workflows
Telnyx provides an API-driven rated-usage workflow that ties call detail records to automated charging outcomes for telecom automation stacks. Telarix emphasizes an API-first integration surface for CDR mediation, rating, and downstream posting so reruns stay controllable.
Governed admin operations for charging and billing actions
PortaBilling adds multi-tenant account operations with fine-grained RBAC plus auditable charging and billing actions. Azure Billing for Telecom adds Azure-native governance and audit integration around telecom billing workflows and billing-run automation.
Choose call billing based on rerun determinism, integration shape, and governance
The right call billing software depends on how each system turns CDR fields into rating inputs and how reruns behave when rate decks change. The selection steps below force forks between deterministic comparison workflows, carrier-style mediation approaches, and API-first rated-usage stacks.
These steps also reflect operational constraints shown in the tool cards, like tariff mapping overhead in MOR and Telgoo5, deep setup requirements in PortaBilling, and configuration governance needs in Telarix.
Start from the rate-comparison workflow outcome, not the UI
If the requirement is comparing alternative tariff outcomes from the same mediated inputs, prioritize MOR because it evaluates alternative tariff outcomes consistently from the same mediated CDR inputs. If the requirement is keeping a CDR-to-invoice workflow repeatable across many destinations, use Telgoo5 Telecom Billing because its rating configuration is designed to keep CDR-to-invoice operationally repeatable.
Validate how CDR normalization affects repeatability
If upstream records are inconsistent across carriers and resellers, check PortaBilling and its carrier-style CDR mediation and normalization so rating reruns use consistent inputs. If imperfect upstream call records are the main problem and the workflow needs to be self-hosted, A2Billing’s CDR mediation pipeline is designed to normalize records before rating.
Pick the rule engine philosophy: tariff-table rating versus mediation-first rating jobs
If tariff-table rule evaluation must apply destination and jurisdiction logic during charging computation, Alepo Charging and Billing is positioned around tariff-table rule evaluation with destination and jurisdiction logic. If rating jobs must be rerunnable and tied to structured rating outputs for reconciliation, Telarix focuses on carrier-style CDR mediation with rerunnable rating jobs tied to structured rating outputs.
Choose the integration shape based on where charging automation runs
If telecom automation must be API-first and rated usage must be driven programmatically, Telnyx is built around API-driven rated-usage workflows that tie call detail records to automated charging outcomes. If the environment already uses Azure identity and audit needs to govern billing runs, Azure Billing for Telecom centers on Azure-native governance and audit integration around billing-run automation.
Confirm governance depth for multi-entity billing operations
If multiple upstreams, tenants, or resellers require governed billing actions, select PortaBilling for RBAC plus auditable charging and billing actions. If governance requirements are specifically tied to Azure audit and controlled billing operations, Azure Billing for Telecom is built to map telecom workflows into Azure-native identity and audit logging.
Who benefits from these Call Billing Software design choices
Call billing software fits teams that must turn CDRs into rated charges that stand up to reruns, rate-deck changes, and reconciliation. The tool cards show different strengths based on mediation depth, rule evaluation control, and automation surfaces.
The audience fit below maps directly to the categories of work that appear in rate-comparison projects across Twilio, Vonage, and Plivo.
Telecom billing teams running repeatable CDR-to-invoice rating at scale
Telgoo5 Telecom Billing is designed to keep the CDR-to-invoice workflow operationally repeatable while rating rules align charges to destination and call attributes. MOR is built for deterministic rating runs that support repeatable reruns and rate comparisons.
Carriers, resellers, and mediation teams with upstream variance
PortaBilling provides carrier-style CDR mediation and normalization so rating outcomes stay consistent across upstream differences. Telarix also supports carrier-style CDR mediation with rerunnable rating jobs tied to structured rating outputs for reconciliation.
Teams requiring jurisdiction-aware tariff-table rating
Rev.io Telecom Billing includes jurisdiction-based rating combined with configurable tariff tables for controlled reruns across changed rate decks. Alepo Charging and Billing applies destination and jurisdiction logic during tariff-table rule evaluation for charging computation.
Engineering teams that need API-driven charging workflows
Telnyx focuses on an API-driven rated-usage workflow that ties call detail records to automated charging outcomes. Telarix provides an API-first integration surface for CDR mediation, rating, and downstream posting.
Enterprises with Azure identity and audit governance requirements
Azure Billing for Telecom emphasizes Azure-native identity and audit logging tied to controlled billing operations and billing-run automation. This fits organizations that want rating-to-invoice automation governed through Azure controls.
Common failure modes in Call Billing Software evaluation
Misalignment between CDR fields and rating configuration breaks determinism and makes reruns disagree. Operational governance gaps can also turn rate-deck updates into uncontrolled changes that affect invoicing and reconciliation.
The pitfalls below connect to the specific configuration and operational constraints called out in the tool cards.
Assuming any CDR import format produces comparable rating outcomes
MOR and Telgoo5 both depend on correct mapping of CDR fields and prefixes into rating logic so tariff comparisons remain consistent. Clean, consistent CDR inputs are a prerequisite for correct rating in Telgoo5 and a mapping requirement in MOR.
Overlooking how rate-deck changes add operational overhead for large hierarchies
MOR notes operational overhead when rate-deck changes require frequent reruns. PortaBilling warns that rate deck changes can create operational overhead for large reseller hierarchies.
Skipping governance and audit requirements for multi-tenant billing actions
PortaBilling includes multi-tenant operations with fine-grained RBAC and auditable charging and billing actions, which is designed to support governed billing operations. Azure Billing for Telecom concentrates governance through Azure-native identity and audit logging around billing-run automation.
Choosing mediation tooling without confirming reconciliation-grade outputs
Telarix is positioned for reconciliation-grade reruns because rating jobs are tied to structured rating outputs. If reconciliation-grade outputs are needed, Telarix’s mediation and rerunnable rating job design is more directly aligned than lighter admin workflows.
Treating API-first charging as a substitute for disciplined telecom input handling
Telnyx is API-first for rated usage, but its operational setup requires telecom-grade discipline for correct rating inputs. Teams that cannot enforce correct routing and rating inputs will see rating drift regardless of API availability.
How We Selected and Ranked These Tools
We evaluated call billing software on a weights-first scoring model where features account for 40%, and ease and value each account for 30%. MOR ranked highest because its rating runs are deterministic for repeatable reruns and it supports rate comparisons from the same mediated CDR inputs.
Telgoo5 Telecom Billing scored strongly for repeatable CDR-to-invoice workflow behavior tied to configurable rating rules. PortaBilling rated highly for governed multi-tenant operations with fine-grained RBAC and auditable charging and billing actions.
Frequently Asked Questions About Call Billing Software
How do teams run repeatable rate comparisons across carriers and destinations?
Which products support API-first integration for feeding call detail records and receiving rated usage outputs?
How is identity and access control handled for multi-tenant billing operations?
How does call billing software handle CDR mediation when upstream call records are inconsistent?
When should teams choose per-call billable duration rules versus minimum-duration billing and rounding increments?
What breaks if CDR mediation and rating jobs use different data schemas or rating attributes?
How are jurisdiction-based and international call rating decisions applied during charging?
How do dispute workflows connect rated usage or invoices back to the underlying call records?
Where does setup and governance complexity tend to fall short across common call billing workflows?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
- Business FinanceTop 10 Best Call Center Billing Software of 2026
- Business FinanceTop 10 Best Cloud Based Billing Software of 2026
- Business Process OutsourcingTop 10 Best Credit Card Billing Software of 2026
- Finance Financial ServicesTop 10 Best Billing Services of 2026
- Customer Experience In IndustryTop 10 Best Business Call Center Services of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Business Finance alternatives
See side-by-side comparisons of business finance tools and pick the right one for your stack.
Compare business finance tools→