Mango Billing
Invoicing, collections, revenue recognition, commissions, and tax — the finance motion for the revenue stack.
MangoApps
Meet the agent
This app ships with a production AI agent — permission-aware, tenant-scoped, audit-logged, and governed by the Agent Development Lifecycle.
Mango Billing AI
AR aging, dunning, revenue recognition, commissions, Stripe sync.
Overview
Mango Billing owns the finance / AR surface for the revenue stack. AR aging dashboard, automated dunning sequences (day 7/14/30/45), ASC 606 revenue recognition with period close + GL export, tiered-accelerator commission plans with per-rep attainment tracking, Anrok tax integration, and an Ask AI agent for finance questions. Built on the existing Billing::* domain layer (Invoice, Subscription, Stripe, Refund, CreditTransaction). Replaces the sysadmin BillingInvoicesController + CustomerBillingController with a workflow-aware, tenant-scoped surface.
Highlights
Capabilities
Invoices & Collections
-
Tenant-scoped invoice list, filterable by status, date, and invoice number
-
Invoice detail with live Stripe line items
-
Mark paid out-of-band (offline, check, wire), void, or send a reminder email
-
Create manual invoices for non-Stripe billing
-
Download invoice PDFs
-
One-click overdue-invoice view with month-to-date collection stats
Customer Billing & Subscriptions
-
One billing account per tenant with pricing, payment, and credit views
-
Set a customer discount percentage with an optional expiry date
-
Custom per-package price overrides
-
Store card and ACH payment methods (Stripe-backed)
-
Assign, upgrade, or cancel plan bundles with seat and billing-term control
-
Grant free-trial days when assigning a subscription
-
Manual resource-credit adjustments with an audit trail
Automated Dunning
-
Per-invoice dunning sequence with day 7 / 14 / 30 / 45 stages
-
Cron job advances sequences and sends reminder emails automatically
-
Pause or resume a sequence (e.g., customer in dispute)
-
Full event audit trail per sequence
-
Filter sequences by state (active / paused / completed) or stage
Revenue Recognition (ASC 606)
-
Straight-line or point-in-time recognition schedules
-
Monthly recognized-vs-deferred revenue rollup
-
Drill into any month's underlying schedule entries
-
Close a period to lock recognition (async, atomic)
-
CSV export for NetSuite / QuickBooks import
Sales Commissions
-
Commission plans with tiered accelerators per event type
-
Tiers for new-logo, renewal, and expansion deals
-
Earnings auto-generate when a proposal is marked won
-
Tier-boundary splits handled automatically on large deals
-
Approve, mark paid, or reverse an earning (reversal rolls back attainment)
-
Payout CSV export with per-rep attainment
Tax, Refunds & GL Export
-
Automatic tax sync to Anrok on every invoice
-
Jurisdiction + year-to-date tax summary with per-invoice re-sync
-
Full or partial refunds against a paid invoice (Stripe-backed)
-
Refund reconciliation CSV
-
Balanced journal-entry export for NetSuite / QuickBooks
Analytics & AI Agent
-
AR aging dashboard (0–30 / 31–60 / 61–90 / 90+ buckets)
-
MRR / ARR with year-over-year growth trend
-
Logo churn and net revenue retention (trailing twelve months)
-
Revenue mix by type and package, plus top customers by revenue
-
Unbilled metered-usage visibility with projected close totals
-
Ask AI: aging, dunning, revenue, commissions, and customer summaries in chat
Limits & Specs
-
Default payment terms: Net 30 (configurable)
-
Default dunning cadence: Day 7 / 14 / 30 / 45 (configurable)
-
Revenue recognition: Straight-line or point-in-time, monthly
-
Tax provider: Anrok (optional)
-
Payment rail: Stripe
-
Access: Admin / Super Admin (finance-gated)
Use cases
Resources
FAQ
Mango Billing requires a license and is disabled by default — the license comes through your MangoApps account team, and an administrator then enables it per-tenant in the Apps Marketplace. Individual modules (invoices, dunning, revenue recognition, commissions, tax) each have their own toggle in Settings.
No. Mango Billing reads the existing Billing::* tables in place — Invoice, Subscription, Customer, Refund, CreditTransaction. New tables only back dunning, revenue recognition, and commissions; your billing history stays where it is.
Stripe is the payment rail (webhooks keep local invoices in sync, and card/ACH methods are stored via Stripe). Anrok handles tax sync when enabled. Revenue-recognition and GL journal-entry exports produce NetSuite / QuickBooks-compatible CSVs.
No. Stripe remains the payment rail. Mango Billing sits on top of the existing Stripe integration — webhook events keep updating local invoice records as they always have. Mango Billing adds the workflow layers finance owns: dunning, revenue recognition, commissions, refunds, and GL export.
Every surface is finance-gated to Admin and Super Admin roles — invoice amounts, pricing, payouts, and the revenue book are never exposed to ordinary members. The Ask AI agent applies the same admin gate, so it won't return restricted financial data to non-admins.
No. Tax is off by default. Flip the tax toggle and paste an Anrok API key to sync tax automatically on each invoice. Without Anrok, invoices still flow and finance can add tax manually on manual invoices.
Turn off commissions in Settings. The rest of the app — invoices, customer billing, dunning, revenue recognition, tax, refunds, and analytics — still works, and commission plans and earnings stay hidden from the nav.
No — the agent is read-only. It answers questions about aging, dunning, revenue recognition, commissions owed, customer balances, and Stripe sync health, and points you to the right screen. Every state change (pause a sequence, approve an earning, issue a refund, close a period) is performed in the app so it's authorized and audited.