This should not be the behaviour.
The way IdentityNow provisioning works is if provisioning plan is committed it reflects the changes on idn side. e.g. If enable provisioning plan comes as successful then it marks account as enabled on idn side. In WS source, response code plays important role so if your end system is returning different response code then what you have configured then identitynow would not consider operation as committed.
Check provisioning logs from search and see if it’s actually successful or failing.