In this post, we would be discussing the recent development wherein the YouTube Creator’s unpaid earnings are not displayed in the Adsense account. Uploading videos over to this streaming site was once just a side hobby for many users. However, over the past few years, it has become a full-time job for many as the revenue in this field is much higher than what you might get from your regular office jobs.
Granted it has its few risks as well, but the perks easily outweigh those concerns. Talking about the perks, the revenue for every creator is managed by the Google Adsense team. Moreover, you could easily access your Adsense account and view how your videos are performing as well as the total money that you have made from each uploaded video.
Likewise, you could also get a hold of the overall amount that you have accumulated to date for this month. And at the end of each month, if it reaches the minimum threshold of $100, you will get paid. But in the past few weeks, the Adsense account has undergone a change which is giving out a tough time to the end users.
Why are YouTube Creator’s Unpaid Earnings not displaying in Adsense?
In the Adsense dashboard, there was only the AdSense Payment till now. However, now the YouTube Payment section has been added as well. Up until now, all the payments were directly shown under the AdSense Payments section. But now the said section is blank and the amount accumulated is being displayed under the YouTube Payment section only. For others, the amounts have been segregated under both sections. So where lies the issue?
Taking a real-life example, a content creator has already accumulated the required amount of $100. However, only $70 is being displayed under AdSense Payments, the rest $30 is being shown under YouTube Payment. So even though he has met the required payment criteria [on the overall sum], he might not get paid as the AdSense amount is yet to reach the designated amount.
So is there a fix? Well, not as of now, but the good news is that the YouTube developers are aware of this issue and should rectify the bug at the earliest. As and when that happens, we will update this post accordingly. In the meantime, you may drop in your queries and opinions in the comments section.
