How to Write a Payment Contract (Without Losing a Weekend to It)

The first time I had to chase down a client for an unpaid invoice, I learned something the hard way: a friendly email and a PDF invoice don't really hold up when someone decides to stop paying. What does hold up is a signed payment contract. Even a one-page one.

I had done about six weeks of work for a marketing agency. Good rapport, friendly Slack channel, the kind of client where you stop bothering to pin down the legal side because the energy is good. Then their CFO left, a new one came in, and suddenly my invoice was "under review." It stayed under review for four months. I didn't have a contract. Just an email thread, a Notion doc with the scope, and a stack of invoices. I eventually got paid, but only because they wanted to keep the relationship, not because I had any real leverage.

The next client got a payment contract. Two pages. Took me twenty minutes. It's been five years and I've never had to fight for an invoice again.

If you're a freelancer, a small business owner, a contractor, a landlord working out a back-rent plan, or you've just lent money to a friend and want to be smart about it, this guide walks you through what actually goes into a payment contract, what tends to go wrong, and how to put one together without spending half a Saturday on it.

TL;DR: A payment contract is a written agreement that defines who pays whom, how much, when, by what method, and what happens if a payment is missed. To be enforceable it needs identified parties, a clear amount, agreed terms, consideration on both sides, and signatures. Skip any of those and you weaken your ability to collect. If you'd rather not draft one from scratch, you can generate a tailored payment contract in under two minutes with the LegesGPT AI Document Generator.

So what is a payment contract, really?

It's a written agreement between two people (or two companies) that says: "You're going to pay me this much, by this date, in this way, and here's what happens if you don't." That's it. It can be one page or ten. The format matters less than the fact that it exists and that both sides signed it.

You'll see it called a few different things depending on who you ask: payment agreement, installment agreement, promise to pay, payment plan agreement, deferred payment agreement. They're all variations of the same idea. The legal weight comes from the structure, not the label at the top of the document.

A payment contract is different from an invoice, different from a promissory note, and different from a master services agreement, even though all four of them touch the same area. I'll come back to those distinctions later because they matter more than people realize.

When you actually need one

Anytime real money is changing hands and there's any gap at all between the work and the payment, write it down. The bigger the gap, the more important the contract.

The usual situations:

• Freelance gigs where you invoice after delivery
• Service work on a monthly retainer
• Selling something on a payment plan (a car, a piece of equipment, a course)
• Lending money to a friend, family member, or another business
• Settling a debt someone already owes you
• Construction or renovation work paid in stages
• Subscription-style B2B arrangements where the contract isn't already a master agreement
• Repayment plans you offer to a customer who can't pay a full invoice at once
• Partner buyouts, where someone is being paid out over time
• Rent arrears arrangements between a landlord and tenant

If the deal is bigger than a few thousand dollars, you don't really have a choice. Most jurisdictions require contracts above a certain threshold to be in writing if you ever want to enforce them in court. In the U.S. it's called the Statute of Frauds, and the threshold varies by state and by type of transaction. In the EU and the UK, similar rules apply for consumer credit and any sale of goods above modest sums. The general rule: if the number has commas in it, get it on paper.

There's also a softer reason to write it down. It forces both sides to actually agree. Half the disputes I see in unpaid contracts aren't really disputes about money. They're disputes about what was supposed to be delivered, by when, and whether it was good enough. Writing the payment terms forces you to also write the scope, and writing the scope kills 80% of the arguments before they start.

What to put in it

I'll skip the legal-treatise version and just walk through what I actually include when I draft one. There are eight things you really can't leave out, and a handful of "boilerplate" clauses that look like filler but pull a lot of weight when something goes wrong.

The parties

Full legal names. Not "John" or "the client," but John Smith, residing at this address, or Acme LLC, a Delaware company with this registered office. If you're dealing with a business, name the entity, not the person you've been emailing. This is the single most common reason payment contracts fall apart in court.

If the entity is a sole proprietorship, put the owner's name and add "doing business as [trade name]." If you're contracting with someone individually but a company is paying, make sure the company is the named party. I've seen people sue the wrong entity and lose simply because the company on the contract didn't exist or had a slightly different name registered with the state.

If there's a personal guarantor (say, an owner personally backing their company's promise to pay), name them separately and make sure they sign as guarantor. Without that, the corporate veil protects them and you're stuck chasing an empty LLC.

Why the payment is owed

A short paragraph is enough. "Payer purchased web design services from Payee between March and April 2026, as outlined in the attached scope of work." Context protects you later if anyone tries to claim the contract was about something else, or that the underlying work was never agreed to.

If you can, attach the scope as an exhibit and reference it. Then there's no ambiguity about what was bought.

The amount

Write it twice. Once in numbers, once in words. "Five Thousand U.S. Dollars ($5,000)." Sounds redundant, but if anyone types $50,000 by mistake, the spelled-out version is what controls.

Specify the currency. Don't write "$5,000" if you're in a cross-border deal where the other party assumes Australian dollars. Use "USD," "EUR," "GBP" explicitly.

Decide upfront whether the amount is gross of taxes, net of taxes, or tax-inclusive. In the U.S. this matters less for B2B services. In the EU it matters a lot because of VAT. State it clearly: "The total amount is inclusive of all applicable taxes" or "The Payer shall pay all applicable VAT in addition to the stated amount."

When and how it gets paid

Spell out specific dates, not "end of the month." Pick a structure that fits the deal:

• One lump sum on a specific date
• Monthly installments (state the day of the month and the start month)
• Milestone-based payments tied to deliverables ("30% at signing, 40% at first draft approval, 30% at final delivery")
• Net terms ("Net 30 from the invoice date")

Each has a tradeoff. Lump sums are simplest but give the payer all the leverage if they decide to push back. Installments smooth your cash flow but multiply the number of times you can be paid late. Milestone-based works well for projects but requires you to clearly define what triggers each milestone, otherwise you'll be arguing about whether the "first draft" was really a first draft.

And say how the money moves. ACH, wire transfer, check, Stripe, PayPal, crypto if you're into that. If wire fees apply, decide upfront who eats them. International wires can chew 1-2% off the top, and that's an argument waiting to happen.

If you're invoicing rather than billing on a fixed schedule, set a clear invoice cadence: "Payee will issue invoices on the first business day of each month. Payment is due within 15 calendar days of invoice receipt."

What happens if a payment is late

This is the clause people skip and regret. You need three things: a grace period (something like 5 business days), a late fee, and the right to send a default notice.

The late fee can be a flat amount or a percentage. A flat $50 after 10 days is enforceable almost everywhere. A percentage works too (typically 1.5% per month, which annualizes to 18%), but you have to be careful with state usury caps. California, New York, and a handful of others restrict how high you can go. If you're not sure, stick with a modest flat fee plus the ability to suspend services.

Suspension is underrated. If you're providing an ongoing service (consulting, hosting, software, anything recurring), the right to pause the service is far more effective than a late fee. The fee is a number on paper. The suspension stops their business.

What you can do if they stop paying entirely

This is your acceleration clause and your remedies. The big one: if two payments get missed, or if any payment is more than 30 days late, the entire remaining balance becomes due immediately. Without that, you're stuck suing for each installment separately, which is a nightmare.

Other remedies to consider:

• Repossession (if you're financing the sale of equipment or a vehicle, and you have a properly perfected security interest)
• Recovery of attorneys' fees and collection costs (only enforceable if it's in the contract)
• Interest on the unpaid balance at a default rate
• Right to report to credit bureaus, where applicable
• Right to refer the account to a collections agency

Attorneys' fees clauses are worth their weight in gold. Without one, even if you win a lawsuit, you usually eat your own legal costs. With one, the defaulting party pays them. Which often turns "should I bother suing?" into "I should obviously sue."

Where disputes get handled

Pick a state (or country) whose law governs the contract, and a venue where lawsuits get filed. This sounds nitpicky until you're trying to file a small-claims case in your own city and finding out the contract requires you to fly to Texas.

The general rule: pick somewhere you can realistically litigate. For most small businesses, that's your home state. For international contracts, consider arbitration in a neutral forum like London, Singapore, or Paris. But only if the amounts justify it. Arbitration costs five figures to start. Small claims court costs fifty bucks.

You should also think about mandatory arbitration vs. court. Arbitration is faster and private but more expensive upfront, harder to appeal, and discovery is limited. Small claims court is cheaper and friendlier to non-lawyers but caps the amount you can recover. For most freelancers and small businesses, I'd default to small claims court in the seller's home state.

Signatures

Both parties, dated. E-signatures are fine. DocuSign, Adobe Sign, Dropbox Sign, anything with an audit trail. They've been legally valid in the U.S. since 2000 under the ESIGN Act, and in the EU under eIDAS. The audit trail is what matters: timestamp, IP address, the order signatures were applied, and the version of the document each party signed.

A few quick rules of thumb:

• For B2B contracts, have the person signing represent that they have authority to bind the entity. A "By: ___ Title: ___" block usually does it.
• If a guarantor is signing, make sure they sign in their personal capacity, not as an officer of the company.
• Don't email back and forth with marked-up versions and expect a clean signature at the end. Use a signing platform that locks the version once it's sent for signature.

The boilerplate that actually matters

Lawyers love their boilerplate, and most of it really is filler. But three or four of these clauses do real work and you shouldn't skip them.

Entire agreement. Says the written contract supersedes every prior verbal promise, email, and Slack message. Without it, the other side can argue you "really agreed" to something different in a phone call.

Notice. Says how official communications (default notices, termination, amendments) must be sent. Email is fine if you specify it. Don't leave it ambiguous, or you'll deliver a default notice via Slack and have it ignored.

Severability. If one clause turns out to be unenforceable, the rest of the contract survives. Cheap insurance.

Amendment in writing. Any changes have to be signed by both parties. Kills the "we agreed by phone to extend the deadline" argument.

No waiver. Just because you let one late payment slide doesn't mean you've given up the right to enforce future ones.

Assignment. Says whether either party can hand the contract off to someone else. For a payment contract, you typically don't want the payer to be able to assign their obligation without your consent. You probably do want the right to assign your receivable (so you can factor it or sell it later).

A short example

To make this concrete, here's roughly what the meat of a freelance payment contract looks like in practice:

This Payment Agreement is entered into on June 8, 2026 between Acme Consulting LLC ("Payee"), a Delaware limited liability company with offices at 123 Main St., Wilmington, DE, and Northwind Trading Inc. ("Payer"), a New York corporation with offices at 456 Broadway, New York, NY.

Payer agrees to pay Payee Twelve Thousand U.S. Dollars ($12,000) for consulting services delivered between April 1 and May 31, 2026, as described in Exhibit A.

Payment will be made in three equal monthly installments of $4,000 via ACH transfer to the account designated by Payee, due on the first of each month beginning July 1, 2026.

A late fee of $75 applies to any installment more than five (5) business days late. If two consecutive installments are missed, or if any installment is more than thirty (30) days late, the full remaining balance becomes immediately due and payable.

In the event of default, Payer shall reimburse Payee for all reasonable costs of collection, including attorneys' fees.

This Agreement is governed by the laws of the State of New York. Any disputes shall be resolved in the state or federal courts located in New York County, New York.

That's the skeleton. A real contract would add notice provisions, dispute resolution, signature blocks, and anything specific to the deal. But if you have the pieces above, you have something enforceable.

How a payment contract holds up in court

A payment contract is binding when it has four ingredients: an offer, an acceptance, consideration (something of value exchanged on both sides), and the intent of both parties to be legally bound. Both signers need to be legally competent, meaning of legal age and not under duress, fraud, or significant mental impairment.

That last part matters more than it sounds. If you can show that the other party signed under pressure (you threatened them, lied about a material fact, or rushed them into signing without time to read), the contract can be voided. So don't get cute. Give them time to review. If they ask for changes, negotiate them in writing.

The four-element test is what a judge looks for. If you've got all four and the contract isn't asking anyone to do something illegal, you're in good shape.

How payment contracts compare to similar documents

People mix these three up constantly, and the difference matters when you're trying to enforce one:

If you're issuing repeat invoices, back them with a payment contract or master services agreement. Invoices alone are easy to dispute. If you're lending pure cash with no underlying transaction, a promissory note can stand on its own. For everything else, a payment contract is the right tool.

The mistakes I keep seeing

After looking at a lot of these (both well-drafted and not), the same problems show up over and over:

Dates like "by next month" or "as soon as possible." Use real calendar dates. Always.

No late-fee mechanism. If there's no consequence for paying late, payers will pay late. Behavior follows incentives.

Generic templates pulled off the internet that were written for a different state, a different country, or for a 1998 transaction. The clauses look right but they cite laws that don't apply to your situation.

Verbal amendments. "We talked and agreed to push it back two weeks" doesn't override what's in writing. If something changes, sign a one-line amendment.

Forgetting to say whether taxes are included in the amount. This causes more disputes than you'd think, especially with VAT.

Missing the jurisdiction clause, then realizing nobody can agree on where to sue.

Skipping the attorneys' fees clause because it feels aggressive. It's not aggressive. It's how you make sure suing for $8,000 doesn't cost you $9,000 in legal fees.

Using a personal name when the actual payer is an LLC, or vice versa. If you sue the wrong party, you lose.

Letting late payments slide without sending notice. If you tolerate the behavior for six months and then suddenly try to enforce, courts may treat your tolerance as a de facto modification of the contract.

Storing the only copy in someone's email. If a co-founder leaves or your inbox gets compromised, you've lost your enforcement document. Save executed copies in a shared drive both parties can access for years.

Doing this faster

Drafting a payment contract from scratch, even a simple one, usually takes me 30 to 45 minutes if I'm being careful. Pulling from a template is faster, but then you spend time cutting out clauses that don't apply and second-guessing whether you missed one that does.

That's why we built the AI Document Generator into LegesGPT. You answer a handful of plain-English questions about the deal (who's paying who, how much, what schedule, what state) and it puts together a contract with all the clauses I just walked through, written in language that actually holds up. You can edit any clause, swap "Net 30" for "Net 15," add a personal guarantee, drop something you don't need. Then export to PDF or Word and send it for e-signature.

It's not just for payment contracts either. The same tool handles NDAs, service agreements, promissory notes, bills of sale, independent contractor agreements, and most of the documents a small business cycles through. If your deal is unusual (a partner buyout paid out over five years, an earnout tied to revenue, a structured settlement), you can describe it in your own words and the generator drafts something tailored to it rather than forcing you into a generic form.

What I like about the AI approach over picking a template is the jurisdiction handling. A New York template doesn't know it's a New York template. It just has New York clauses. The generator asks where the contract will be enforced and writes the right clauses for that jurisdiction. Same goes for industry-specific quirks. Construction contracts have different mechanics' liens, consumer contracts have different disclosure requirements, and so on.

If you'd rather skip ahead and just see what comes out, the same logic powers our free contract generator. It's a good way to feel out the output before committing to a full document.

For business owners who cycle through payment terms with new clients every week, automating the first draft is the difference between getting it written and having it sit in a "to-do" tab for months.

Wrapping up

A payment contract is the cheapest piece of legal infrastructure you can put around a deal. It takes minutes to write, costs nothing to sign, and turns a "they said they'd pay" situation into something you can actually act on if things go sideways.

If you've been operating on handshakes and invoices and it's mostly worked out, great. But the one time it doesn't, you'll wish you had a paragraph or two on paper. The cost of writing the contract is twenty minutes. The cost of not writing it is whatever the deal is worth, multiplied by the probability that the other side decides to be difficult. Over a career, that's not a coin flip you want to keep taking.

Write one today for your next deal, or generate it in a couple of minutes with AI and move on with your day. Either way: write it down.

FAQ

Do I need a lawyer to write a payment contract? Not for most situations. If the amount is small to moderate and the deal is straightforward, a clean self-drafted contract or one generated by a decent AI tool is fine. Above $10,000, or if there's collateral, guarantors, or anything cross-border, get a lawyer to look at it. Most attorneys will review a draft for a flat fee, which is far cheaper than litigation.

Is a signed PDF enough, or do I need a notary? For most payment contracts a PDF with both signatures is enough. Notarization is required mainly when you're transferring real estate, executing certain affidavits, or recording a document with a government office. For everyday business contracts, e-signatures with audit trails are the standard.

What's the difference between a payment contract and a promissory note? A promissory note is a one-sided written promise from a borrower to repay a specific sum, usually with interest. A payment contract is two-sided. Both people have obligations and rights. If someone owes you money for goods or services, a payment contract gives you more leverage. If you're purely lending money with no underlying transaction, a promissory note can be enough on its own.

Is an invoice the same thing as a payment contract? No. An invoice is a request for payment. A payment contract is the agreement that makes that payment enforceable. Invoices on their own are easy to dispute. The better setup is a payment contract or services agreement up front, then invoices issued under it.

Can the other party back out after signing a payment contract? Generally no, unless the contract has a termination clause that allows it, or there was fraud, duress, or a mistake about a material term. Some consumer contracts also have a statutory cooling-off period. For typical B2B deals a signed contract is binding.

How do I enforce a payment contract if the other party stops paying? Send a written demand letter that cites the contract's default clause. If they still don't pay, you can sue for the full balance under the acceleration clause, or take them to small claims court if the amount is below your state's small-claims cap. An attorneys' fees clause in the contract makes this far more cost-effective.

How long should a payment contract be? As long as it needs to be. A well-drafted one-page contract often beats a sloppy ten-page one. The point isn't length, it's coverage. If you've handled the essentials (parties, amount, schedule, late fees, default, jurisdiction, signatures), you're done.

Are e-signatures legally valid on a payment contract? Yes. E-signatures have been legally valid in the U.S. since 2000 under the ESIGN Act, and in the EU under eIDAS. The audit trail is what matters: timestamp, IP address, the order signatures were applied, and the version of the document each party signed.

Can I write a payment contract with AI? Yes. Tools like the LegesGPT AI Document Generator ask plain-English questions about your deal and produce a jurisdiction-aware payment contract in under two minutes, with all the essential clauses, ready to export to PDF or Word and send for e-signature.