# Getting paid safely as a freelance developer

> Get paid safely by never starting work that is not funded, splitting the project into short milestones, agreeing in writing what done means, and keeping payment and records in one place. On ErdiBuilds each milestone is funded first and paid out after approval.

Canonical: https://erdibuilds.app/guides/getting-paid-safely-as-a-freelance-developer
Last updated: 2026-11-06 (November 6, 2026)

## The core rules of safe payment

- Do not start before the money is committed. Unpaid work is a loan to a stranger.
- Keep each step small, so the amount at risk at any time is small.
- Write down the result and how it is approved before you begin.
- Keep the whole conversation, delivery and payment in one place, so you have a record.

These rules protect you from the most common problems: late payment, endless revisions and clients who vanish after a delivery.

## How the flow works on ErdiBuilds

Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. You start the work once it is funded. You deliver with a note and at least one attachment or a preview link. The client reviews and either approves or asks for changes. If the client does not react, the milestone is approved automatically after 14 days.

After approval, a short holding period runs and then your payout is released. New developers can have a part of the first payouts held back for a while as a safety reserve. Plan your cash flow with that delay in mind, and do not count on money the day after approval.

**From funding to payout**

|  | What happens | Why it helps you |
| --- | --- | --- |
| Funded | The client pays the milestone before work starts | You know the money exists |
| Delivered | You submit a note and files or a preview link | A record of what you handed over |
| Approved | The client approves, or it happens automatically | A clear end to the review |
| Released | Payout follows after the holding period | Predictable payment |

## When things go wrong

Clients can request changes within the deliverables you agreed. Work beyond the agreement is added as a new milestone. If both sides want out of a paid milestone, they can cancel together. If they cannot agree, an ErdiBuilds admin decides the dispute, and both sides can add evidence first. Delivery notes, approvals and messages are your evidence, which is another reason to keep everything on the platform.

## Invoices and records

Invoices are issued in your name, because you are the seller. You need to finish payout setup, tax details and the consent to invoicing in your name before you can be paid. Keep your own books too: record every milestone, the date, the currency and the amount.

> Developers pay a fee on paid work. Developers pay 8 percent plus payment processing. Include it when you set your prices.

## Tax and legal basics

As an independent professional you are usually responsible for your own taxes, social contributions and, where it applies, VAT. The rules depend on your country and your situation, so ask a local accountant before your first invoice. Set aside part of each payment for taxes right away. This is general information, not legal or tax advice.

## Habits that protect you

- Price with a buffer. See [pricing fixed-price milestones](https://erdibuilds.app/guides/how-to-price-fixed-price-milestones).
- Write clear deliverables. See [writing a winning proposal](https://erdibuilds.app/guides/how-to-write-a-proposal-that-wins).
- Share progress often, so approval holds no surprises.
- Never agree to start before the milestone is funded.

## Frequently asked questions

### When do I get paid?

After the client approves the milestone, or it is approved automatically after 14 days, a short holding period runs and then the payout is released.

### Should I start work before funding?

No. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Start after the funding is in place.

### Who issues the invoice?

Invoices are issued in the name of the developer, who is the seller. You complete the consent to invoicing in your name during payout setup.

### What if the client stops answering?

A delivered milestone is approved automatically after 14 days without a reaction, and then the payout process starts.

### What happens in a dispute?

Both sides can add evidence, then an ErdiBuilds admin decides. Keeping messages and delivery notes on the platform makes your case clear.

### Do I need to handle taxes myself?

Usually yes, as an independent professional. Talk to a local accountant. This is general information, not legal or tax advice.

## Related

- [How it works](https://erdibuilds.app/how-it-works): From idea to finished project, step by step.
- [How to Price Fixed-Price Milestones](https://erdibuilds.app/guides/how-to-price-fixed-price-milestones): A method for developers: turn your hourly rate and honest estimates into a fixed price per milestone, with buffer, scope limits and clear deliverables.
- [How to Write a Proposal That Wins](https://erdibuilds.app/guides/how-to-write-a-proposal-that-wins): How developers can write a proposal clients choose: read the brief, answer the real problem, split the work into clear milestones and show relevant proof.
- [Pricing](https://erdibuilds.app/pricing): What ErdiBuilds costs for clients and developers.
- [For developers](https://erdibuilds.app/developers): How independent developers join and get hired.
- [Guides for your project](https://erdibuilds.app/guides): Plain guides on planning, scoping and paying for apps, SaaS, websites and games, written for people who are not developers.