Misunderstanding, aritrixa, my fault - not 'stupid' at all to ask. Most of us spent years trying to work out the finer points of FS, it's fun to help people make quicker progress. My problem is with people who ask, but don't bother to come back on to say whether the advice given was any use or not. You're fine, keep on asking.
It triggered me to the question who has the right to decide descending, Pilot or ATC?
Flying IFR, DEFINITELY ATC. They'll tell you when to start your descent, and what courses to follow. Do what they say; don't start your descent until ATC tells you to..
Is it also what happen to real pilot in real life?
Same or worse. There are very complicated rules for real pilots. I've never flown jets, but I understand that they are bound by their airlines' rules to follow very strict procedures as to which of the many available autopilot 'modes' they are allowed to use in a descent; and they also get told by ATC to be down to a certain height by the time they reach a given beacon, whether or not that's possible without spilling the drinks in First Class, or maybe even tearing the wings off....but thankfully that's not our problem as simmers.

I think I see what the problem may be - airspeed. Flight Simulator ATC is programmed on the assumption that you're not flying too fast. If you are, there'll be a tendency for FS ATC instructions to be 'too little, too late.' Approach too fast, and you may find the FS 'controllers' not turning you on to your final course to intercept the localiser beam/glideslope until you're within 3 miles of the airport.
My solution to that possible problem, when flying the default 737, is to switch to IAS, and set the speed hold to 250 knots, as soon as I'm told to start the descent. And I usually 'accept' the default rate of descent (1,800 feet per minute). With the 737, that usually means that you're down to the mandated height in plenty of time for ATC to begin vectoring you on to final approach at a sensible distance from the airport.
If you're having problems, it could very well be that you're descending at too high an airspeed, and therefore getting too far ahead of where the FS programmers expected you to be when you got down to the ordered height.
Try that '250-knot IAS' idea of mine - see if that solves your problem.