GWS & Gcloud User

Singapore

Reviews

Review of Google


Rated 1 out of 5 stars

1 star.

1 star.

Extremely poor billing experience across both Google Cloud and Google Workspace.

I have dealt with recurring payment issues caused by Google’s own billing systems, not by my card, bank, or refusal to pay. My payment method is valid and has successfully been charged by Google before.

For Google Cloud, Google successfully deducted SGD 20.22 on 1 June 2026, proving the card works. Google Cloud support later confirmed in writing that when the balance is below the minimum automatic transaction threshold, Google may not even attempt to charge the card. Despite that, a separate automated system can still mark the account as past due, send payment warnings, and create suspension risk for linked projects.

In plain terms: a valid low-usage customer can be punished because the bill is too small for Google’s own billing system to charge.

Their “solution” was not to fix the billing behavior. Their solution was basically to ask me to preload SGD 50 or SGD 100, or use a reseller. That is not a fix. That is asking the customer to overpay in advance to work around Google’s own system limitation.

Google Workspace support was even worse.

Workspace is handled by a separate department from Google Cloud, with different support personnel and different billing amounts, but the same kind of billing chaos happened. Google showed me an amount of SGD 37.13, and I paid that amount in full on 30 May because that was the amount Google presented to me at the time. Then on 1 June, Google suddenly requested an additional SGD 1.24 and began flagging payment issues again.

Workspace support kept avoiding the actual issue. Instead of explaining why Google showed me a lower payable amount the day before, they kept implying that I should have paid the full amount. But I paid the full amount Google displayed to me at the time. The remaining SGD 1.24 was not clearly calculated or presented when I made the payment. I had to investigate and work out myself that this mysterious SGD 1.24 likely related to the final day of their prorated cycle.

This is unacceptable.

Google Workspace support came across as clueless, evasive, and more interested in pushing the blame back onto the customer than actually solving the billing issue. They could not provide a proper explanation, could not provide a real solution, and their only practical suggestion was for me to dump extra money into Google as overpayment.

That is not customer support. That is asking customers to lock up money with Google just to avoid Google’s own broken billing behavior. That money could have been kept in my own account or used elsewhere instead of being parked with Google as a workaround for their system limitation.

Meanwhile, the system floods customers with reminders and threatens suspension of services and domain access over tiny residual amounts that were not clearly presented at the time of payment.

A business customer should not have to investigate Google’s billing calculations themselves while support gives generic answers, avoids the actual facts, and the system threatens service suspension.

A valid customer with a valid payment method should not have to worry that Google Cloud projects, Firebase billing, Workspace services, or domains may be suspended because of tiny residual balances, unclear prorated charges, or minimum transaction thresholds.

The support staff may sound polite, but the billing systems and support process are deeply flawed. Google Cloud confirmed the issue and offered no direct fix. Google Workspace support failed to properly explain the SGD 1.24 until I traced the likely cause myself, while continuing to push the burden back onto me.

For small businesses, low-usage apps, Firebase projects, and Workspace users, this is a serious service continuity risk. I no longer feel confident using Google Cloud or Google Workspace billing for business-critical services.

24 June 2026
Unprompted review