Troubleshooting Billing
Symptoms you can hit with budgets, reports, exports and invoices, their causes, and the fix.
A budget says it is watching an empty set
Cause: Nothing carries the scope's tags, or the scope matches only resources of a kind that is not metered ("Matches … resources, none of a kind that is metered, so this budget can never be reached.").
Fix: Tag the resources, or change the scope. Check a scope before saving it (see Create a budget).
A budget says its project no longer exists
Cause: The project or saved view it watches was deleted ("The project this budget watches no longer exists. Nothing is being watched.").
Fix: Edit the budget and point it at another project, view or set of tags.
A budget never alerts
Cause: Every threshold is above the spend, or the alert already fired this period (each threshold fires once per period, even after you lower the amount).
Fix: Lower a threshold, or add a forecast threshold to a monthly budget.
An alert fired but no mail arrived
Cause: The budget has no notification addresses ("shown here only"), or sending failed.
Fix: Add an address to the budget. For a failed send, hover over the alert on Budgets for the reason.
A cost lands outside the team's budget
Cause: A budget counts a resource by its tags or its project now. Registry and Git storage is metered for the whole organization and is counted only by a budget for the whole organization.
Fix: Tag the resource, or move it into the project.
Sending the report answers already_sent
Cause: That month's report went out before; each month is sent once.
Fix: Send it with Send again ("again": true), at most every 10 minutes.
The DATEV export is refused for a range
Cause: The range crosses into another fiscal year.
Fix: Export the two parts separately, or check Fiscal year starts under Reports & DATEV.
DATEV refuses the file
Cause: The header has no Beraternummer or Mandantennummer.
Fix: Enter both under Reports & DATEV (see Export costs to DATEV).
Closing the organization is refused
Cause: Unpaid invoices, or resources still running or holding data.
Fix: Pay each listed invoice and remove each listed resource, then close again (see Close the organization).