I'm going to be brutally honest. You have 2 options: lawyer up and sue to get your money or walk away and treat this as a very expensive lesson learned.<p>Lessons for next time:
1. <i>Never</i> cap invoices. Instead, cap your work. If there's 80 hours of work, and the company is only willing to pay for 40, guess what? You should only do 40 hours of work (and bill for it).<p>2. Don't worry about bleeding the company. What's the worst they can do? Not pay you? Hell, that's what they're doing right now!<p>3. If there's a change in the work timeline, the contract should be renegotiated. You mentioned earlier that one of the other developers quit a few days in. That, right there, would have been grounds for a renegotiation. I mean, unless the departure of this dev. was explicitly planned for, it constitutes a fairly radical change in the terms of the contract — you now have to do 50% more work than anticipated.<p>4. "I've met with my manager and the owner of the company on three separate occasions and I've always felt like they listened and the financial situation would be taken care of. Each time I find myself grabbing my own ankles on pay day again."<p>Whoa, this should have been a gigantic, enormous red flag. Words are cheap, especially if you're of the sociopathic type that heads all too many companies. What counts is action. I mean, even if the company is in financial trouble, they still have a contractual obligation to pay you. Out and out missing a payment is unacceptable. At the very least, I'd expect a clear warning in advance and a concrete set of steps detailing how and when the make-up payment will be delivered. And even then, if they consistently miss paying you, fire them.