Plans and checkout
Plans with GST, trials and setup fees, a plans page and a checkout.
Recurring revenue, invoiced and collected every cycle
Sell plans and subscriptions, send GST invoices every cycle, and collect through Payments.
Each domain sets plans with a price in INR, GST from 0 to 28% inclusive or exclusive, a monthly, quarterly, half-yearly or yearly interval, trial days, a setup fee, SAC and features, shown on /plans in the brand. Subscriptions are created by the team, the API or /checkout/<plan> (with a live GST quote and an optional Coupons code) and move through trialing, active, past due, paused, and cancelled or expired, with plan changes at the next cycle and cycles that keep their anchor day. Every cycle makes a GST invoice numbered INV/<financial year>/0001: CGST+SGST within the seller's state, IGST across states, the amount in words, UPI and bank details, printable at /invoice/<token>. Money is collected only through APPNEURAL Payments (a payment request per invoice, read back on return, on notify and every 30 minutes) or marked paid with a UPI or bank reference. Dunning at 10:00 IST reminds 3 days before, on, and 3, 7 and 14 days after the due date, marks past due and expires after the domain's set days. Customers manage their plans, invoices and details through a 7-day /account/<token> link. MRR, ARR, churn and MRR movements, CSV, an API, webhooks, and Claude for dunning email drafts and MRR explanations.
What Billing does for you.
Plans with GST, trials and setup fees, a plans page and a checkout.
A GST invoice every cycle, collected through Payments or marked paid with a reference.
Reminders before and after the due date, past-due handling, MRR and churn.
A suggested path for Billing. What you can do depends on your access in the app.
Legal name, GSTIN, address and UPI or bank details.
Price, interval, trial and features.
Through the checkout, or add subscriptions yourself.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain sets plans with a price in INR, GST from 0 to 28% inclusive or exclusive, a monthly, quarterly, half-yearly or yearly interval, trial days, a setup fee, SAC and features, shown on /plans in the brand. Subscriptions are created by the team, the API or /checkout/<plan> (with a live GST quote and an optional Coupons code) and move through trialing, active, past due, paused, and cancelled or expired, with plan changes at the next cycle and cycles that keep their anchor day. Every cycle makes a GST invoice numbered INV/<financial year>/0001: CGST+SGST within the seller's state, IGST across states, the amount in words, UPI and bank details, printable at /invoice/<token>. Money is collected only through APPNEURAL Payments (a payment request per invoice, read back on return, on notify and every 30 minutes) or marked paid with a UPI or bank reference. Dunning at 10:00 IST reminds 3 days before, on, and 3, 7 and 14 days after the due date, marks past due and expires after the domain's set days. Customers manage their plans, invoices and details through a 7-day /account/<token> link. MRR, ARR, churn and MRR movements, CSV, an API, webhooks, and Claude for dunning email drafts and MRR explanations.
Collecting the money belongs to Payments; coupon codes belong to Coupons; newsletter sign-ups belong to Subscriptions.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
billings.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.