Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.finwatch.finance/llms.txt

Use this file to discover all available pages before exploring further.

​
Operational Automation & Cost Saving

This is about automating manual, repetitive, and error-prone tasks that are common in finance operations. 

​
Use Case: Automated Treasury & Reconciliation.

Problem: Finance teams spend hours manually reconciling payments from gateways (like Stripe or Adyen) against internal ledgers. Discrepancies are often found hours or days later. How FinFlows Solves It: Create rules that monitor settlement reports and internal transaction states in real-time. Example Rule: 
rule AutoReconciliationAlert {
    description "Alert if Stripe settlement total doesn't match daily transaction sum"
    when metadata.source == "stripe_settlement_report" 
    and metadata.settled_amount != sum(amount where metadata.gateway == "stripe" and status == "cleared", "P1D")
    then alert
         reason "Stripe settlement mismatch detected"
}
Business Value: Turns a multi-hour manual process into an automated, real-time check, catching costly errors instantly.

​
Dynamic Pricing & Fee Management

This is about giving product and finance teams the power to implement and iterate on complex pricing strategies without needing engineering resources.  Use Case: Dynamic & Tiered Transaction Fees. Problem: Implementing tiered pricing (e.g., lower fees for high-volume customers) or promotional fee waivers is often hardcoded, making it slow and expensive to change. How FinFlows Solves It: Define pricing and fee logic directly in FinFlows rules. The then action can trigger a specific fee model to be applied downstream. Example Rule: 
rule PremiumTierFeeWaiver {
    description "Waive fees for premium customers after 100 transactions this month"
    when metadata.customer_tier == "premium" 
    and count(where source == $current.source, "P30D") > 100
    then approve
         reason "fee_model:premium_waiver" // Pass info in the reason
}
Business Value: Empowers the business team to launch and manage sophisticated pricing strategies on the fly, increasing revenue and customer retention.

​
Intelligent Payment Routing & SLA Monitoring

This is about optimizing payment flows for cost, speed, and reliability by monitoring the performance of payment partners. Use Case: Real-time Payment Partner SLA Monitoring. Problem: It’s difficult to know in real-time if a payment processor or bank partner is experiencing delays and violating their Service Level Agreements (SLAs). How FinFlows Solves It: Monitor the time difference between transaction states. If a partner is consistently slow, a rule can trigger an alert or even an automated routing change. Example Rule: 
rule ProcessorLatencyAlert {
    description "Alert if Partner Bank A takes more than 5 minutes to settle transactions"
    when status == "settled" 
    and (timestamp - metadata.initiated_at) > "PT5M" 
    and metadata.processor == "partner_bank_a"
    then alert
         score 0.3
         reason "SLA Breach: Partner Bank A settlement latency > 5m"
}
Business Value: Reduces failed transactions, improves customer experience, and provides the data needed to hold payment partners accountable.

​
Proactive Credit & Counterparty Risk Management

This is about using transaction patterns to manage credit risk for business customers (e.g., lending or B2B payments) before they default. Use Case: Early Warning System for Credit Risk. Problem: A business customer’s financial health can decline rapidly. Relying on monthly statements is too slow; you need to see warning signs in their daily transaction flow. How FinFlows Solves It: Create rules that look for patterns indicating financial distress, such as a sudden drop in average transaction volume, an increase in payment failures, or transactions to debt-collection agencies.  Example Rule: 
rule CreditRiskEarlyWarning {
    description "Flag account if avg daily volume drops by 50% over the last 7 days"
    when avg(amount where source == $current.source, "P1D") < (avg(amount where source == $current.source, "P7D") * 0.5)
    then review
         score 0.6
         reason "Potential Credit Risk: Significant drop in daily volume"
}
 Business Value: Allows you to proactively manage credit lines and engage with at-risk customers before they default, significantly reducing potential losses.