Hi, this has happened to me a couple times now.
I set up a multi-milestone contract, and after the first is completed I "submit work for payment". The client pays, but I immediately get a message "client has ended the contract".
I don't think they did this intentionally - it seems to happen automatically even though there are further (unfunded) milestones. Is this a bug, are my clients hitting the wrong button, or do I need to set up the contract differently?
Are you doing a substantial amount of the work in the first milestone? If so, the customer might think (s)he can finish what you've started and save some money not paying you to complete the work.
I rarely use fixed pricing in the type of projects I work on, but if I do use fixed pricing I always use at least three milestones and frontload higher payment amounts, so if/when a client closes out the project early then I've been paid more of the total project value than if I'd structured the milestones more evenly or with higher payments on the back end.
No, these are all good clients and I've had no trouble arranging the rest of the payment so I don't think they are trying to get out of paying. It seems to be either accidental or a problem with the system.
I probably should insist on getting the full contract amount into escrow at the start though.