Invoices, credits, and caps
How hard caps work, how the 7-day mismapped-credit window works, and how to download your invoices.
TL;DR
Invoices, credits, and caps
The billing mechanics that matter after your subscription is running — where to find invoices, how credits work, and what happens when you hit your limit.
Where to find invoices
Go to Settings → Billing. Once you have a paid subscription, your invoices appear in the billing page. Each invoice shows:
- Billing period (start and end dates)
- Plan tier and base subscription amount
- Mapped Bug count for the period
- Overage line (if any Mapped Bugs were billed above your included quota)
- Credits applied (from mismapped claims or other adjustments)
- Tax line (18% GST for INR billing; no sales tax for USD)
- Total amount and payment status
Click any invoice to download a PDF. The PDF includes your billing address, GSTIN if applicable, and a line-itemized breakdown.
What an invoice includes
| Line item | When it appears |
|---|---|
| Base subscription | Every invoice |
| Mapped Bug overage | When your usage exceeded the included quota and you had an overage cap set above the included count |
| Credits | When mismapped credits from a previous cycle are being applied |
| GST (18%) | INR billing only |
Bundled actions — PR generation, PR iteration, RCA, Slack and issue-tracker sync — never appear on an invoice. They are included in the base subscription at every tier.
Mismapped credit window
When a Mapped Bug was billed but the code mapping was wrong, you can flag it from the bug detail page. The credit window is 7 days from the bug's billed_at date — the timestamp at which the bug qualified and the meter fired.
The 7-day window is counted from billed_at, not from the ticket arrival date or the date you noticed the mapping error. After 7 days, the mismapped action is recorded but no credit is issued. This is a deliberate policy, not a technical limitation.
To file a mismapped claim:
Open the bug detail page from /tickets.
Click the Mismapped button. You'll see this button only while the credit window is open (within 7 days of billed_at).
Select the reason: wrong file, wrong function, not a bug, duplicate, or other. Optionally add a note.
Submit. The bug is marked mismapped, your Mapped Bug usage counter for the current period decrements, and a credit is queued.
Where the credit goes. Credits apply to your next invoice. Watari does not issue retroactive refunds through the payment processor — credits always apply to the next billing cycle. You'll see the credit as a line item on that invoice.
Self-serve credit limit. Credits up to 10% of your plan's included quota per billing cycle are processed automatically. Claims above that threshold are reviewed by the Watari team — you receive a confirmation and we follow up within 2 business days.
Hard cap behavior
When your Mapped Bug count for the cycle reaches your effective cap, Watari pauses ticket processing. In-flight pipelines (bugs already being mapped, PRs already open) complete normally. New tickets entering the queue receive a "paused — over allowance" status and are held until the next cycle.
When processing is paused:
- An in-app banner appears on the dashboard.
- Your billing admin receives an email notification.
- Processing resumes automatically at the start of the next billing cycle.
- Or you can raise your overage cap immediately to resume without waiting — see below.
Overage cap
By default, Watari pauses at your plan's included Mapped Bug count. You will not receive overage charges unless you explicitly raise the cap.
From Settings → Billing, find the Overage limit card. You'll see three numbers:
- Included quota — your plan's base allowance.
- Plan maximum — the highest overage cap your plan allows.
- Currently effective — the number Watari will pause at this cycle.
Set the "Pause processing at" field to any number between your included quota and your plan maximum. Setting it equal to your included quota disables overage entirely. Setting it higher allows Watari to continue processing past your quota, billing the per-bug overage rate for your plan up to the ceiling you set.
| Plan | Included | Max overage cap | Per-bug overage rate |
|---|---|---|---|
| Starter | 20 | 50 | $25 / ₹2,000 |
| Growth | 60 | 150 | $20 / ₹1,700 |
| Scale | 150 | 400 | $15 / ₹1,250 |
| Design Partner | 30 | 30 | No overage |
| Enterprise | Custom | Custom | Custom |
Design Partner plans don't show the overage cap control — the hard cap at 30 is fixed by the plan terms.
Currency change
Your billing currency is determined at your first checkout (India + GSTIN → INR; all other billing addresses → USD) and is locked afterward. Switching currency requires creating a new subscription. Contact us at /contact if your tax residency has changed.
Need more help? Visit /contact to reach the Watari team.