Why is my Firebase billing reporting a different number than Google Cloud billing for non-firebase services?

Viewed 51

I'm creating a Firebase project which isn't live yet, so I'm mostly in the free tier, but I have Blaze enabled.

In my Firebase billing console, I see a small charge for "Non-Firebase services":

enter image description here

Besides the standard Firebase services, I'm using pub/sub and Google places autocomplete.

My billing in the Google Cloud Console shows a different story:

enter image description here

It seems like Google Places Autocomplete got rid of their free-tier, and instead reimburses up to $200/mo in credit. I can see that if I look in billing reports:

enter image description here

So it seems like the Places API usage is being offset, though I'd like to see more details.

So, for my main question, why is the Firebase billing amount different? Is it maybe lagging behind in credits being applied? It also seems like the credits in the report are lagging $0.03 behind the cost.

I want to understand whats happening.

1 Answers

I think this is completely normal. Quoting from Google's Firebase docs and assuming you have your Firebase project under the Google Cloud account that you show on the screenshot :

Depending on the Google Cloud or Firebase service, sometimes there's a slight delay (up to a few days) in usage reporting to Cloud Billing. This reporting delay impacts the calculated spend during the budget period and can cause a delay in the generation of budget alert notifications.

Edit: If any of the above isn't your case (for example a few days have passed) you can notify me to update my answer.

Related