GITNUXSOFTWARE ADVICE
Finance Financial ServicesTop 10 Best Automotive Lending Software of 2026
Top 10 ranking of automotive lending software tools with side-by-side criteria for lenders and auto finance teams, covering Byrdal, FundingShield.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Byrdal is the best pick if your lending teams need consistent decisioning to booking across many applications, while FundingShield fits when you prioritize controlled, API-driven automotive loan workflows with audit trails and Nortridge Software is the right alternative for configurable servicing on complex portfolios.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Byrdal
Policy configuration that turns underwriting decisions into downstream booking-ready workflow states.
Built for fits when lending teams need consistent decisioning-to-booking automation across many applications..
FundingShield
Editor pickEvent-driven loan stage updates that keep credit intake, contract booking, and funding milestones synchronized.
Built for fits when lenders need controlled automotive loan workflows with API-driven system integration and audit trails..
Nortridge Software
Editor pickNLS workflow configuration for custom fields, state transitions, approval queues, and staff actions.
Built for fits when automotive lenders need configurable servicing for complex portfolios and connected back-office systems..
Related reading
Comparison Table
Byrdal
SMBOffers an auto lending platform for dealerships and finance companies.
Policy configuration that turns underwriting decisions into downstream booking-ready workflow states.
Byrdal centers on credit application intake and downstream contract booking so underwriting outcomes propagate into the next operational steps without manual rekeying. The decision workflow supports structured inputs and deterministic policy rules that can be updated when lending guidelines change. Byrdal also fits indirect lending and dealer finance use cases where the process needs consistent controls across many submissions.
A tradeoff is that deep integration with existing servicing and document systems depends on the available integration surface and implementation effort. Byrdal fits teams that need configuration-driven decisioning for high volumes and want fewer operator touchpoints per file.
- +Config-driven decision rules reduce underwriting rework
- +Workflow handoffs speed contract booking after approvals
- +Built for multi-submission pipelines common in indirect lending
- +Operational controls help standardize file status transitions
- –External document and servicing integration can require project work
- –Complex risk policy changes may need governance time
- –VIN and collateral validation coverage may depend on connected components
- –Exception routing depth can lag highly custom underwriting desks
Dealer finance operations teams
Standardize approvals across dealer submissions
Fewer manual exceptions
Underwriting managers
Control rule updates and reruns
Lower policy drift
Show 2 more scenarios
Credit operations teams
Reduce touch time per application
Shorter cycle times
Structured intake and decision outputs cut rekeying between intake, decisioning, and booking.
Lending compliance stakeholders
Maintain consistent decision processes
More consistent outcomes
Workflow and governance around decisions supports repeatable handling of submissions.
Best for: Fits when lending teams need consistent decisioning-to-booking automation across many applications.
More related reading
FundingShield
enterpriseOffers automotive loan fraud prevention and validation tools.
Event-driven loan stage updates that keep credit intake, contract booking, and funding milestones synchronized.
FundingShield is a fit for organizations handling automotive lending at volume where credit application intake must move through consistent credit decisioning steps and then into contract booking and document handling. The platform’s automation emphasis shows up in how it sequences statuses, routes tasks, and records what changed during each stage, which supports governance around exceptions and rework. Integration depth is positioned around API connectivity for pulling credit data and exchanging loan and document events with adjacent systems.
A practical tradeoff is that teams typically need upfront process mapping to align FundingShield’s configured workflow to each lender channel and exception path. A common usage situation is an automotive lender consolidating direct-to-consumer and dealer finance pipelines while keeping consistent audit trails across the same funding workflow stages.
- +Configurable end-to-end funding workflow reduces manual status handoffs.
- +API-first integration support for credit pull and application event exchange.
- +Audit-oriented tracking of actions across loan lifecycle stages.
- +Document sequencing connects imaging to contract booking steps.
- –Requires careful workflow configuration to cover channel-specific exception paths.
- –Automation coverage depends on integrating adjacent underwriting and servicing systems.
Dealer finance ops teams
Standardize dealer intake to funding workflow
Fewer manual handoffs
Underwriting operations teams
Integrate bureau data into decisions
Faster credit decisioning
Show 2 more scenarios
Risk governance teams
Maintain action traceability on exceptions
Stronger audit readiness
Tracks changes across loan stages for accountability during rework and approvals.
Portfolio servicing integration teams
Send booked loan events onward
More consistent portfolio ingestion
Uses integration interfaces to emit loan and document milestones to downstream servicing systems.
Best for: Fits when lenders need controlled automotive loan workflows with API-driven system integration and audit trails.
Nortridge Software
enterpriseA configurable loan servicing platform used by automotive lenders.
NLS workflow configuration for custom fields, state transitions, approval queues, and staff actions.
NLS can represent borrowers, co-borrowers, collateral, references, transactions, and lender-defined attributes within configurable account records. Workflow rules organize queues, approvals, exceptions, payment events, and collections actions across active portfolios. Administrators can adapt forms, statuses, calculations, and permissions to match internal operating procedures.
Nortridge Software places more emphasis on servicing and portfolio administration than on native credit application intake or automated vehicle valuation. Automotive lenders may need connected specialist services for title processing, vehicle validation, and other front-end functions. A lender boarding purchased contracts can use NLS to centralize repayment schedules, account activity, collections work, and portfolio reporting.
- +Configurable fields and screens accommodate lender-specific borrower and collateral records.
- +Workflow rules support queues, approvals, and exception handling.
- +API integration supports connections to surrounding lending systems.
- +Portfolio accounting and collections support post-booking operations.
- –Origination depth is narrower than servicing and portfolio administration.
- –Automotive title and vehicle-validation work may require connected specialist services.
- –Implementation requires careful configuration of rules, fields, and permissions.
- –User experience varies across heavily customized screens.
Automotive finance companies
Managing multi-state repayment portfolios
Consistent account administration
Dealer finance operations
Boarding dealer-originated contracts
Fewer boarding exceptions
Show 2 more scenarios
Servicing operations teams
Handling delinquency and recoveries
Controlled collections workload
Queues, status rules, and staff permissions organize payment follow-up, promises, and escalation actions.
Integration architects
Connecting core lending systems
Connected operating workflows
NLS provides APIs and data import tools for customer, account, payment, and accounting records.
Best for: Fits when automotive lenders need configurable servicing for complex portfolios and connected back-office systems.
Lendscape
enterpriseA lending platform supporting automotive finance and point-of-sale lending.
Configurable funding and booking workflow rules that attach decisions and documents to the same application lifecycle.
Lendscape targets automotive lending workflows with dealer finance intake, credit decisioning hooks, and documentation routing that align to real origination steps. Core coverage centers on application intake, configurable underwriting inputs, and end-to-end contract booking workflows that connect to downstream funding and servicing operations.
Automation is driven through workflow configuration that moves files and decisions between roles without manual rekeying. Integration depth is expressed through an API-first approach that supports system-to-system moves for bureau pulls, asset data, and document lifecycle events.
- +Workflow configuration covers dealer intake through contract booking handoffs
- +API-first integration supports connecting credit, asset, and document services
- +Decisioning data stays attached to the application record for auditability
- +Role-based operational steps reduce manual status chasing
- –Heavier configuration is required to mirror specific dealer and lender policies
- –Document imaging and indexing depth can require add-on processes for complex packets
- –Limited native visibility into downstream funding states without extra integrations
- –Standard reporting may need customization to match portfolio servicing metrics
Best for: Fits when automotive lenders need workflow control across dealer intake, underwriting steps, and contract booking.
CDK Global
enterpriseProvides automotive retail technology including finance and insurance (F&I) solutions.
Dealer-lender workflow orchestration with end-to-end status propagation for contract booking and document readiness.
CDK Global supports automotive lending operations with workflows tied to dealer finance and downstream loan handling. Its scope focuses on loan processing tasks across origination-adjacent steps, including contract booking inputs, document handling, and coordination with lender partners.
The differentiator is integration depth into automotive ecosystems where dealer systems and lender operations need consistent status updates and auditability. Automation is geared toward reducing manual handoffs between intake, credit decision outputs, and contract-ready artifacts.
- +Integration paths for dealer and lender workflows reduce manual rekeying.
- +Workflow status tracking supports traceability from contract data to documents.
- +Document handling fits lending-grade requirements for contract-ready packages.
- +Automation supports lender partner handoffs with fewer exception queues.
- –Requires disciplined setup to match dealer and lender workflow variants.
- –Extensibility depends on integration work rather than self-serve configuration.
- –Limited transparency for non-CDK-connected dealer edge cases without add-ons.
- –UI workflows can feel process-heavy for small teams.
Best for: Fits when automotive lenders need tight dealer-to-loan processing integration across partner workflows.
DealerSocket
enterpriseOffers automotive CRM and finance tools for dealerships.
Workflow automation that ties credit application events to deal booking tasks, reducing manual state changes across lenders.
DealerSocket targets dealer-driven loan origination workflows by connecting credit application intake with downstream funding tasks used by automotive finance operations. Core capabilities center on credit processing, deal and contract handling, and document management used to move an application from submission to booking.
Automation and configuration focus on dealer finance teams that need consistent step-by-step processing across multiple stores and loan sources. Integration depth matters most when DealerSocket must exchange deal and application data with dealership systems and lending partners through its API and workflow hooks.
- +End-to-end automotive lending workflow from application to contract booking
- +Automation supports repeatable deal processing across dealer locations
- +Document and task handling reduces manual handoffs during funding workflow
- +API integration supports partner and dealership system data exchange
- –Complex setup required for multi-store configuration and workflow mapping
- –Best results depend on clean dealer data across products and lenders
- –Governance for roles and permissions needs deliberate configuration for scale
- –Some edge workflows require custom configuration rather than out-of-box templates
Best for: Fits when automotive finance teams need consistent deal processing with partner-facing integration and controlled workflows.
Open Lending
enterpriseProvides automated lending analytics and risk-based pricing for auto loans.
Vehicle-level provisioning that keeps VIN validation, document steps, and contract booking consistent across dealer intake to funding handoff.
Open Lending pairs automotive-focused loan origination workflows with dealer finance and credit application intake paths that map to real underwriting steps. The workflow engine supports staged document collection, credit bureau inquiry handling, contract booking, and handoffs into a funding workflow.
It also exposes an integration and automation surface designed for vehicle-level identifiers and lender operations where provenance and timing matter. Governance is handled through administrative configuration controls that separate operational roles across intake, underwriting, and contract processing.
- +Automotive workflow stages align to underwriting, booking, and funding handoffs
- +Automation supports credit inquiry sequencing tied to application state
- +API integration fits dealer and lender system-to-system provisioning
- +Configuration enables role separation across intake, decisioning, and document steps
- –Complex workflows require careful governance of configurations and rule ordering
- –Limited visibility tooling compared with platforms that provide deep servicing analytics
- –Adoption can be slower when mapping vehicle identifiers and document sets
Best for: Fits when auto lenders need configurable origination workflows with API-driven integrations and strict operational handoffs.
TurnKey Lender
enterpriseProvides an AI-driven lending platform supporting auto loan origination.
Lifecycle-driven automation that routes underwriting and contract booking tasks based on application decision outcomes.
TurnKey Lender targets automotive lending operations with an origination and contract workflow designed for dealer and lender teams. It supports end-to-end document and underwriting packet handling, then carries decisions into booking so files stay consistent from intake through funding readiness.
Automation rules help route applications, trigger required forms, and manage status changes across stakeholders. Integration depth is oriented around lender systems so credit checks, vehicle identifiers, and servicing touchpoints can map to each application lifecycle step.
- +Configurable underwriting packet flow keeps required documents aligned to decisions
- +Status and task automation reduces manual handoffs between intake, approval, and booking
- +Integration hooks support wiring credit inquiry and downstream contract activities
- +Audit-friendly activity trails support internal reviews of application lifecycle changes
- –Dealers and lenders need careful workflow configuration to avoid bottlenecks
- –Complex edge cases often require rule tuning for exceptions and overrides
- –Vehicle and lien data consistency depends on integration mapping quality
- –Reporting breadth for portfolio views may lag teams running large multi-channel operations
Best for: Fits when automotive lenders need automated underwriting packets and lifecycle handoffs across dealer and lender teams.
Gusto Auto
SMBProvides software for automotive loan origination and underwriting.
Guided intake flow with workflow checkpoints tailored to automotive contract booking steps.
Gusto Auto handles dealer lending workflows by collecting vehicle, borrower, and underwriting inputs into one guided intake flow. It supports configuration for underwriting rules and document steps so contract booking, funding workflow, and servicing handoffs can follow a consistent checklist. Gusto Auto also provides an integration surface for syncing application data and status updates with upstream and downstream systems used in automotive lending.
- +Configurable underwriting and document steps reduce manual follow-up
- +Guided application intake keeps VIN, credit inputs, and borrower fields consistent
- +Integration hooks support status synchronization across lending and servicing tools
- +Workflow checklists improve handoff consistency across funding stages
- –Less granular governance controls for multi-dealer teams than enterprise loan platforms
- –Automation depth depends on external integrations for bureau pulls and decisions
- –Document imaging workflows can be slower when handling large mixed media sets
- –Limited visibility into downstream servicing events without a tighter integration
Best for: Fits when lenders or dealers need structured intake plus configurable lending workflows with external integrations.
RouteOne
enterpriseA credit application and contract management platform connecting dealerships and lenders.
Dealer finance workflow tooling that ties credit decisions to contract booking and funding steps with consistent operational state tracking.
RouteOne targets automotive lenders that need consistent dealer finance processing across indirect and participation workflows. Core capabilities center on dealer application intake, credit bureau pulls, automated credit decisioning rules, and contract booking through a documented funding workflow.
It also covers document imaging and lifecycle steps tied to lien and title execution, which reduces manual handoffs between ops teams and downstream partners. The system is typically evaluated on integration depth through API and extensibility for loan origination system style orchestration.
- +Automation-focused funding workflow that connects approval to downstream contract steps
- +Dealer intake flow supports structured credit application handling for indirect deals
- +Document imaging supports operational tracking from booking through processing
- +API and integrations support connecting credit, imaging, and portfolio operations
- –Governance for multi-dealer configuration needs disciplined setup to avoid errors
- –Some lender-specific edge cases can require custom integration work
- –Admin configuration for workflow variations can be time-consuming for new lenders
- –Breadth across servicing steps depends on partner integration coverage
Best for: Fits when indirect lenders need consistent dealer intake, decisioning, and funding handoffs across many channels.
Conclusion
After evaluating 10 finance financial services, Byrdal 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 automotive lending software
The top differentiators across this set are integration depth and workflow control, especially when status changes must propagate across dealer intake, approvals, and document readiness. Byrdal leads with policy configuration that converts underwriting decisions into booking-ready workflow states, while FundingShield centers event-driven loan stage updates tied to credit intake and funding milestones.
Automotive lending software for origination, dealer intake, and contract booking automation
Automotive lending software orchestrates the end-to-end work between credit application intake and contract booking for direct-to-consumer and indirect lending channels. It manages workflow states and task handoffs so credit decisions, required documents, and funding steps stay synchronized across parties and systems.
Byrdal turns decision rules into downstream booking-ready workflow states so underwriting outcomes drive the next operational tasks. FundingShield keeps credit pull events, loan stage updates, and funding milestones in sync through API-driven integration and event-driven status propagation with audit trails.
Automotive lending workflow control and integration features that drive operational throughput
Automotive lending software lives or dies on workflow state control from credit intake through contract booking. The tools in this set treat those states as something the platform can compute, route, and audit, not just display.
Integration depth and automation surface determine whether credit pulls, underwriting decisions, and document handoffs move with minimal rekeying. Byrdal and FundingShield lead with decision and stage propagation that keeps booking tasks aligned to the same application lifecycle.
Decision rules that convert underwriting outcomes into booking-ready workflow states
Byrdal turns policy configuration into downstream booking-ready workflow states so underwriting decisions map to specific next steps. This reduces underwriting rework because workflow handoffs happen immediately after approvals.
Event-driven synchronization of loan stage updates across credit intake and funding milestones
FundingShield uses event-driven loan stage updates to keep credit intake, contract booking, and funding milestones synchronized. The platform also supports API-first exchange for credit pull and application events with audit trails.
Workflow configuration for custom fields, state transitions, and approval queues in servicing
Nortridge Software provides NLS workflow configuration for custom fields, state transitions, approval queues, and staff actions. It emphasizes configurable servicing and back-office workflows rather than origination depth.
Dealer-intake to contract-booking workflow rules that attach decisions and documents to one lifecycle
Lendscape covers workflow configuration from dealer intake through contract booking handoffs with decision and document attachment on the same application lifecycle. Its API-first integration support connects credit, asset, and document services.
Dealer-lender orchestration with end-to-end status tracking from contract data to document readiness
CDK Global orchestrates dealer-lender workflows and propagates status for contract booking and document readiness. Integration paths for dealer and lender workflows reduce manual rekeying while maintaining traceability.
Vehicle-level provisioning that keeps VIN validation, document steps, and contract booking consistent
Open Lending focuses on vehicle-level provisioning so VIN validation, document steps, and contract booking follow consistent workflow stages. The platform also sequences credit inquiry actions tied to application state.
Choose by workflow philosophy: decision-to-booking state automation versus lifecycle event orchestration
The fastest way to narrow the set is to match the product’s workflow philosophy to the organization’s routing complexity. Some tools compute next-step states directly from underwriting decisions, while others orchestrate loan stage changes as events across connected systems.
The second axis is whether the platform’s automation depends on self-serve configuration or integration work with adjacent systems. Tools that extend automation across underwriting, servicing, and document services reduce manual handling only when the connected systems publish compatible events and statuses.
Pick decision-to-booking automation when underwriting outcomes must drive the next operational task
Choose Byrdal when underwriting policy decisions must convert into booking-ready workflow states without manual status translation. Its config-driven decision rules reduce underwriting rework and speed contract booking after approvals.
Pick event-driven orchestration when loan stages must stay synchronized across systems and channels
Choose FundingShield when credit intake, contract booking, and funding milestones must move in lockstep via event updates. Its API-first integration support for credit pull and application event exchange helps keep audit trails consistent.
Choose dealer-intake workflow control when dealer intake variance drives the most exceptions
Choose Lendscape when the organization needs workflow control across dealer intake, underwriting steps, and contract booking while attaching decisions and documents to one lifecycle. Its heavier configuration can mirror specific dealer and lender policies when those variants drive exceptions.
Choose orchestration across partner workflows when dealer-to-loan processing spans multiple external steps
Choose CDK Global when dealer-lender processing requires end-to-end status propagation for document readiness. Its integration paths for dealer and lender workflows reduce manual rekeying but require disciplined setup to match workflow variants.
Choose provisioning-based consistency when VIN validation and document packets must align to the same vehicle record
Choose Open Lending when vehicle-level provisioning must keep VIN validation, document steps, and contract booking consistent from dealer intake through funding handoff. Its governance relies on careful configuration and rule ordering for complex workflows.
Who benefits from automotive lending workflow automation and integration-first orchestration
Automotive lenders with multiple handoff points across intake, underwriting, contract booking, and funding benefit from software that controls workflow state transitions. Those teams need fewer manual state changes and faster document readiness because downstream steps rely on upstream decisions.
The fit also depends on whether the lender’s biggest pain is inconsistent dealer intake routing, complex underwriting-to-booking mapping, or servicing workflow requirements for custom queues and exception handling.
Automotive lenders building consistent underwriting-to-booking automation across many applications
Byrdal fits when policy configuration must turn underwriting decisions into booking-ready workflow states with reduced underwriting rework. Workflow handoffs after approvals accelerate contract booking while keeping the application lifecycle coherent.
Indirect lenders and partner-heavy lenders that require API-driven event exchange and synchronized milestones
FundingShield fits when loan stage updates must be event-driven to keep credit intake, contract booking, and funding milestones synchronized. Its audit trails and API-first integration support reduce ambiguity in what stage drives the next task.
Automotive portfolio operators that need deep servicing workflow configuration with approval queues and exception handling
Nortridge Software fits when complex portfolio servicing and connected back-office systems require NLS workflow configuration for custom fields, state transitions, and staff actions. It prioritizes servicing configuration more than origination depth.
Lenders managing dealer intake variance where decisions and documents must remain attached to the same lifecycle
Lendscape fits when workflow control must span dealer intake, underwriting steps, and contract booking handoffs while attaching decisions and documents to one application lifecycle. Configuration effort increases when specific dealer and lender policies must be mirrored.
Teams prioritizing vehicle-level consistency where VIN validation and contract steps must follow strict operational handoffs
Open Lending fits when provisioning for a single vehicle record must keep VIN validation, document steps, and contract booking aligned across dealer intake to funding handoff. Automation depends on careful governance of workflow configuration and rule ordering.
Common mistakes that cause workflow breaks in automotive lending operations
Workflow failures usually happen when status propagation is treated as a UI problem instead of a computed, routed state. Another common failure mode is underestimating how many dealer or lender variants the workflow must represent to avoid bottlenecks.
A third mistake is assuming origination automation automatically covers servicing and document packet complexity without integrating adjacent systems. Several tools in this set highlight that automation depth depends on configuration discipline or integration work with external workflow participants.
Mapping underwriting outcomes to generic task names instead of workflow states that can drive contract booking steps
Use Byrdal to convert underwriting decisions into booking-ready workflow states so approvals route directly into contract booking tasks. This avoids rework caused by manual translation of outcomes into downstream steps.
Assuming event-driven stage updates will stay synchronized without integrating adjacent underwriting and servicing systems
Use FundingShield’s API-first integration support for credit pull and application event exchange to keep credit intake and funding milestones consistent. Add workflow exception paths deliberately because channel-specific exceptions require configuration.
Under-sizing configuration time when workflow rules must mirror dealer and lender policy variants
Plan for the configuration workload when selecting Lendscape because dealer intake through contract booking handoffs require mirrored dealer and lender policies. Build governance around document imaging and indexing depth when complex packets exceed default flows.
Trying to extend servicing complexity without ensuring the origination and servicing workflow coverage match
Avoid choosing Nortridge Software as a primary origination system when origination depth is narrower than servicing and portfolio administration. Connect specialist services for automotive title and vehicle-validation work when those capabilities must align to servicing workflows.
Neglecting rule ordering and governance for vehicle provisioning workflows that rely on strict VIN and document sequencing
Run a governance review for Open Lending configuration so vehicle-level provisioning aligns VIN validation, document steps, and contract booking. Complex workflows require careful governance to prevent rule ordering issues that lead to bottlenecks.
How We Selected and Ranked These Tools
We evaluated each automotive lending software option on workflow state control from credit intake through contract booking and on integration depth that supports dealer, lender, credit pull, and document services synchronization. Feature coverage was weighted at 40% and ease and value each made up 30%, since workflow automation only matters when teams can configure and operate it.
Byrdal ranked highest because policy configuration turns underwriting decisions into downstream booking-ready workflow states and because workflow handoffs speed contract booking after approvals with less rework. FundingShield placed near the top because event-driven loan stage updates keep credit intake, contract booking, and funding milestones synchronized with API-first integration support and audit trails.
Frequently Asked Questions About automotive lending software
How do these tools connect credit decisioning to contract booking without manual rekeying?
Which platforms provide an API surface for loan stage synchronization across intake, decisions, and funding?
When does each system pull credit bureau data, and how is the timing reflected in the application status?
What breaks if loan-stage updates are not event-driven for dealer and lender workflows?
How does SSO and RBAC typically show up in administrative control for lending operations?
How do teams migrate existing loan data models into a new loan servicing or origination workflow?
Which tool best supports configurable servicing after funding, including delinquency and collections workflows?
How is document imaging and lifecycle routing handled across lien and title steps?
What extensibility patterns help when a lender needs to adapt workflows without rewriting core logic?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
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
Finance Financial Services alternatives
See side-by-side comparisons of finance financial services tools and pick the right one for your stack.
Compare finance financial services tools→