The scenarios no other platform
handles out of the box

The April document is a Proforma. No invoice number, no GST, no sequence number. On PO receipt (May 10th), it converts in-place to a Tax Invoice with a May sequence number and May date. Revenue recognised from April 1st via CFO-approved period close (Path A/B/C). No cancel-and-recreate workflow. Invoice date and recognition date are always independent. Works for both India GST and US ASC 606 customers.

Path A (<3% of period): catch-up in current period, auto-approved. Path B (3–10%): split entry, CFO approval required. Path C (>10%): reopen closed period, CFO + Controller dual approval. India: For Path C only, Fincelo checks whether the period being reopened has a filed GSTR-1. If filed, a mandatory amendment warning is raised and dual approval is required. Paths A and B are unaffected. US: GAAP exception log EX-YYYY-NNN generated automatically. Every decision immutably logged with name and timestamp.

View A: unconditional right to payment, revenue recognised through original end date. View B: recognition stops at exit, credit note issued. AI scans contract for no-refund clause before presenting the recommendation. ARR decrements on actual termination date regardless of which view the CFO selects. Both views are correct per ASC 606 and IFRS 15. The difference is the contract terms.

Fincelo links the Addendum as a child of the MSA. "All MSA terms incorporated" triggers full clause inheritance, payment terms, notice periods, PO requirements, ratchet clauses, all inherited automatically. ASC 606 prospective modification treatment applied. Expansion ARR tracked separately from original contract ARR. NRR calculation reflects both. Full parent-child audit trail.

Revenue is locked at invoice-date FX rate. Never re-translated. Payment FX difference → Other Income (realised gain/loss). Period-end unrealised gain/loss computed separately on all outstanding foreign-currency AR. Two completely independent engines. Correct for both US GAAP (ASC 830) and IFRS (IAS 21). Board-ready FX impact report generated separately from the revenue report.

If renewal intent is flagged, Fincelo holds the subscription in a Grace Period state. Never "Expired." CFO is presented three gap billing options: (1) bill the gap retroactively, (2) waive the gap as goodwill, (3) start new contract from April 14th. ARR shown as "At Risk, Grace Period" until signed. Renewal timeline preserved. No manual workaround needed.

Fincelo's AI scans every variation: minimum guarantee, committed to no less than X, floor quantity, base commitment, not fewer than X seats, minimum headcount. Extracts the exact floor number. Blocks any seat reduction below the floor and alerts the Account Manager. Works for India SaaS and US enterprise contracts in any language or formatting style.

Fincelo presents the CFO with 3 options every time: (1) Pro-rated co-terminus, charge for remaining period, end dates align. (2) Fresh 12-month, new contract starts today, end dates diverge. (3) Extended co-terminus, extend the original contract end date. ASC 606 treatment shown for each option. CFO selects one. The choice is logged with name and timestamp. Fincelo never decides unilaterally.

Fincelo runs a structured SLA escalation chain: T+42h → Manager (email + in-app), T+66h → Senior Manager, T+90h → CFO. Every alert shows the contract value, customer name, and exact revenue at risk. Escalation chain is configurable per deal size. Full log of every alert sent and every action taken, exported on demand for audit.

The core principle: Fincelo always generates invoices on the current date. Never backdated. So invoice date and GST liability are always current-period. No conflict there.

Where the conflict actually arises: When a finance team selects Path C (reopen a prior closed period to post a correcting entry), and that period's GSTR-1 has already been filed with the GST portal. The corrected books no longer match the filed return.

What Fincelo does: Paths A and B are always presented to the CFO with no GSTR-1 check. They post to the current open period and there is no conflict. Only when the CFO selects Path C does Fincelo check: "Has this period's GSTR-1 been filed?" If yes: a warning is raised, "January 2026 GSTR-1 was filed on Feb 11. Posting a correcting entry will create a mismatch. You may need to file a GSTR-1A amendment. Consult your tax advisor before proceeding." CFO + Controller dual approval is still required. The gstr1_resolution_note field becomes mandatory.

This check is India-only. No Western competitor files GSTR-1. Chargebee has no concept of this scenario. This is the India moat in one precisely-placed feature.

Fincelo calculates GST on the gross invoice value (₹1,00,000), not the TDS-net amount. Invoice: ₹1,00,000 + GST ₹18,000 = ₹1,18,000 total. Customer pays: ₹1,18,000 − ₹10,000 TDS = ₹1,08,000 net. TDS tracked under the customer's TAN (Section 194J). 26AS reconciliation run quarterly. CA-ready report generated. Correct per Indian tax law. Not a workaround.

Fincelo handles all 10 GST categories: Regular, Composition, Unregistered, Consumer, Overseas (LUT/bond), SEZ Unit, SEZ Developer, Deemed Export, Tax Deductor (TDS), and ISD. The correct treatment is auto-applied from KYC data, CGST+SGST vs IGST determined from place of supply, e-invoicing eligibility checked, GSTR-1 bucket assigned. Zero manual GST configuration per customer after KYC approval.

Fincelo tracks four independent ARR buckets: New ARR (new logos), Expansion ARR (upsells and upgrades. Never grouped with new), Contraction ARR (seat reductions and downgrades, tracked separately from churn), Churned ARR (terminations, decrements on actual exit date). NRR = (Beginning ARR + Expansion − Contraction − Churn) ÷ Beginning ARR. Board-ready waterfall chart in one click. Investor-grade metrics from day one.

Every customer has a Payment Score 0–100 across 5 tiers: Platinum (80+), Good (60–79), Average (40–59), Poor (20–39), Bad (<20). Score is based on payment history, days-to-pay trend, broken promises, and dispute history. Score determines dunning template (Standard/Enterprise/Aggressive), credit terms, suspension trigger date, and when the Account Manager is alerted. Platinum customers never receive a suspension notice. Bad-tier customers are escalated at Day 15 instead of Day 30.

Fincelo handles four metering models: Capped (hard stop at limit), PAYG (every call billed), Tiered (price per unit changes at thresholds), Rollover (unused credits carry forward). In this example: 100K rolled over → effective cap is 1.1M → overage is 100K calls. Billed on a single consolidated invoice: base subscription + rollover credit applied + overage amount. Customer gets a full usage breakdown on the invoice. Real-time balance visible in the customer portal throughout the month.