How to Invoice a Startup or Tech Company as a Freelancer

Startups and tech companies have their own billing quirks that catch freelancers off guard. The founder who hired you may have zero authority over accounts payable. Payment might require a purchase order number you do not have. Net 60 terms might show up in a contract when you expected Net 15. Knowing how these companies actually process invoices saves you weeks of payment delays and awkward follow-ups.

This is not about being suspicious of startup clients. Most of them pay fine. But their internal processes are often more bureaucratic than a small business, and their cash position can be more volatile. A startup burning through a Series A round may have plenty of money today and none in six months. How you invoice and when you get paid matters more than it does with an established company that has been around for 20 years.

Find the Right Billing Contact Before You Start

The most common reason invoices get stuck at a startup is that they were sent to the wrong person. You built a relationship with the design lead, the marketing manager, or a co-founder. That person hired you, approved the work, and loves everything you delivered. But they do not cut checks.

Before you even send the first invoice, ask: "Who should invoices go to, and is there a specific format or PO number required?" This one question solves half the problems. At a 10-person startup the answer is usually "just email it to our ops person at finance@company.com." At a 200-person Series B company, the answer might be "you need to submit through our vendor portal and reference PO #12847."

If the company uses a vendor or AP portal like Coupa, Tipalti, or Bill.com, get yourself set up in that system before the first invoice is due. Some of these portals take a few days to verify you. Finding out after you deliver the work that you cannot get paid until you complete a vendor onboarding form is a frustrating delay you can avoid with one email at the start of the engagement.

Purchase Orders: What They Are and When You Need One

A purchase order, or PO, is a document a company issues to a vendor that authorizes a specific purchase. It has a PO number, a description of what is being bought, and the approved amount. When the company's accounting team gets your invoice, they match it to the PO in their system before they pay it. If the PO does not exist or the numbers do not match, your invoice sits in a hold queue.

Smaller startups, under maybe 30 to 50 people, often skip POs entirely. The founder says "go ahead," you do the work, you invoice, they pay. Bigger companies and later-stage startups almost always require a PO. When you ask about billing contacts, also ask: "Do you issue purchase orders for contractor work?" If yes, do not start work until you have the PO number in hand and can reference it on your invoice.

Your invoice should list the PO number prominently, usually in the header near the invoice number. Something like: "PO Number: 2026-4821." If a PO is required and your invoice does not reference it, the AP team will either reject it or email you asking for it, adding days or weeks to the payment timeline.

Net Terms With Startups

Tech companies often try to push Net 30 or Net 60 payment terms on freelancers, especially if they have a standard vendor agreement they ask everyone to sign. Net 60 means they have two months to pay you. That is a long time to float a project, and it is longer than most freelancers can comfortably wait.

Net terms are often negotiable, especially for smaller engagements. If a startup offers you Net 60, counter with Net 30 or Net 15. Most will agree, particularly for project amounts under a few thousand dollars. The AP team does not particularly care when they pay you as long as it is within the contracted window. Only the finance team cares, and they are usually flexible unless cash is tight.

If they insist on Net 60, price your work accordingly. The carrying cost of waiting two months for payment is real, particularly if you turned down other work to take the project. Some freelancers add a financing buffer of five to ten percent to their rate when clients require long payment terms. That is entirely reasonable, and the client's AP team will never notice it because it is baked into the line item prices, not called out separately. For more on setting terms that protect you, see our guide on payment terms for freelancers.

Always Get a Deposit From an Early-Stage Startup

Seed-stage and early Series A startups are the highest-risk billing clients in the freelance world. Not because they are dishonest, but because their financial position can change fast. A startup that had runway for 18 months in January might be doing emergency cuts by September. If you delivered 8,000 dollars of work in August and they run out of cash before they pay you, you have a very hard time collecting from a company that is dissolving.

For any startup under Series B, get a deposit before you start. Fifty percent upfront is standard. The founders might push back a little, especially if they are first-time startup operators who are used to paying on delivery. Explain simply that it is your standard terms for new clients, and that it protects both sides. If they are truly not willing to pay any deposit, treat that as a signal and factor the risk into your rate.

For ongoing monthly work with a startup, set up monthly invoicing with payment due within two weeks, not at the end of a long engagement. Monthly invoices for smaller amounts get paid more reliably than one big invoice at project completion. If they miss a monthly payment, you know quickly and can pause work before you are owed 20,000 dollars instead of 2,000.

What to Put on an Invoice for a Tech Company

Tech companies, especially bigger ones, want invoices that match their internal record-keeping. A professional, complete invoice processes faster than a vague one. Include:

• Your legal name or business name, matching whatever name they have in their vendor system
• Your address and EIN or SSN if they are going to issue you a 1099 at year end, which they will for payments over 600 dollars
• Their company's legal name and billing address
• The PO number, if applicable, in a prominent location
• Invoice number and invoice date
• Due date as a calendar date, not just "Net 30"
• Line items that match the statement of work or contract description exactly. If the SOW says "UX audit and wireframes," your invoice line should say "UX audit and wireframes," not "consulting services."
• Payment instructions: bank wire details, ACH info, or a link to pay online

That last point about matching the SOW description matters more than people realize. AP teams match invoices to contracts before approving payment. If your invoice says something different from what the contract authorized, it can get kicked back. Copy the language from the contract or statement of work directly.

You can build a clean invoice like this in minutes using WaffleInvoice's free invoice generator. Fill in the fields, add your line items, and send or download a PDF. It handles the formatting so your invoice looks professional on the first try.

Following Up With a Tech Company's AP Team

Corporate AP teams are not ignoring you on purpose. They deal with hundreds of invoices and the most common reason a freelancer's invoice is late is that it got lost in the inbox, submitted incorrectly to the portal, or is waiting on an internal approval the AP team cannot push through on their own.

If an invoice is three to five days past due, a short email directly to the AP or finance contact (not the person who hired you) usually resolves it. Something like: "Following up on invoice #2026-014 for 4,500 dollars, due June 15. Can you confirm it was received and processed? Happy to resend or provide any additional information." Friendly, specific, and gives them a clear action.

If that does not work within a few days, loop in your main contact at the company, the person who hired you. They often have more authority to push things through internally than you do. Most tech companies do not want to have a reputation for stiffing contractors, and a well-placed internal nudge from the project owner resolves most stuck invoices quickly.

Contracts and Paper Trails With Startup Clients

Startups move fast and sometimes treat written agreements as optional. Do not. Even a short email chain confirming the scope, rate, and timeline is better than a verbal agreement. If the company offers you a contractor agreement or MSA (master services agreement) to sign, read it before you sign, especially the payment terms, intellectual property assignment, and non-compete clauses.

Some startup MSAs include clauses that transfer all IP to the company immediately upon creation, before you are paid. That is standard for work-for-hire arrangements, but make sure you understand what you are agreeing to. Others include non-solicitation clauses that restrict your ability to work for their competitors. These clauses are often negotiable, especially for short engagements.

Whatever you agree to, make sure the payment terms are written down. If you negotiated Net 30 instead of their standard Net 60, that needs to be in the signed agreement or at least in a clear email exchange. Your invoice can reference the agreed terms, but you need documentation that those terms were agreed to.

For more on what to include and what to watch out for in your billing relationship, the guide on the difference between an invoice and an estimate covers when to lock in scope before billing and how to handle scope changes mid-project.

Billing startups well comes down to preparation: find the right contact, confirm the process before you start, use a professional invoice, and track every payment. WaffleInvoice is free for unlimited invoices with no per-invoice fees, so you can send clean, professional invoices to every client without paying for software.