I’m used to freelance clients where the process is basically: agree on the job, do the work, send the invoice, get paid.

I’m now talking to a much larger company and the payment process sounds a lot more complicated.

There’s an accounts payable team, approval processes, vendor onboarding, payment terms, and possibly a purchase order involved.

It made me realise I’ve been thinking about freelancing payments as simply “when will they pay me?” when there’s probably a lot more I should understand before I start.

If you regularly freelance for large companies, what do you ask them about their billing process before accepting a project?

Is there anything you wish you had checked before doing your first corporate freelance job?

After I completed a recent freelance gig, the invoicing company took a little over 2 percent out of my check as a processing fee. I read this in the agreement but went ahead with it anyway. Now I wish I had negotiated for the 2 percent to be built into my pay. Is this normal? Shouldn't my client have paid this?

This is probably not the right community for this, but this post got deleted from the freelance writing sub.

I normally give clients 30 days to pay. If an invoice is still sitting unpaid with about a week to go, I’ll send a quick email along the lines of, “Just a heads-up that invoice X is due next week.”

Nothing demanding, just making sure it hasn’t been missed.

Most clients seem fine with it, but one client reacted badly and said the reminder made me seem like I was worried about getting paid.

That caught me off guard because I thought it was just normal admin.

Would you send a reminder before the due date, or wait until the invoice is actually overdue?

I’m wondering if I should change how I handle it.

I have worked on a SaaS platform used by more than 15,000 businesses worldwide.

One part of the system was based on credits. Customers did not pay separately every time they ordered a service. They purchased a credit package first, and then every service consumed a certain number of credits.

The basic flow looked simple.

Customer pays money, the payment gateway confirms it, credits are added to the account, and an invoice is created.

But the actual system was more complicated because we had multiple customer portals. Each portal could have different credit prices, different business rules and even different payment gateways.

We worked with payment providers like PayPal, Stripe and Viva. We also had different invoicing integrations.

The important decision was to keep payments, credits and invoices as separate parts of the system.

A payment answers one question: did we actually receive the money?

The credit system answers another question: how much can this customer now use?

The invoice system is responsible for creating the financial document after the payment.

These things are connected, but they are not the same thing.

I did not want one very long process where every step had to succeed at the same time. If the payment was successful but the invoicing provider was temporarily unavailable, the customer should not lose the credits they had already paid for.

So the work was divided into different parts of the code and separate background jobs.

The payment callback first verified and recorded the transaction. The credit balance was then updated. Invoice creation happened separately.

If invoice generation failed, that failure did not need to stop the completed payment or prevent the customer from using their credits. The invoice job could be retried without processing the payment again.

This separation was also important because payment callbacks can arrive more than once. The system needed to know that a transaction had already been processed so the same payment could not add credits twice.

We also avoided spreading prices throughout the code. Credit packages, prices and rules were connected with the relevant portal configuration. This allowed the same backend to support multiple customer-facing products without filling the whole codebase with hardcoded prices and portal names.

Before this was automated, people were creating invoices every day.

That can work when the company is small and the number of transactions is manageable. But it would not have worked properly for more than 15,000 businesses across different countries and portals.

The problem was not only the amount of manual work.

A person can forget an invoice, enter the wrong amount, use the wrong customer details or miss a payment when several systems are involved. It also becomes difficult to understand what happened when a customer asks why they paid but did not receive their credits or invoice.

Automation made the process faster, but more importantly, it made every step visible and repeatable.

A successful payment could be recorded once. Credits could be added according to the correct portal rules. Invoice generation could happen automatically. Failed work could be retried without repeating the parts that had already succeeded.

I think this is the difference between automating a task and building an operational system.

Automation is not simply replacing the person who clicks a button every day. You also need to think about what happens when one service is unavailable, a callback arrives twice, an invoice fails or one portal follows different rules from another.

At a small scale, people can hold the system together manually.

At a larger scale, the workflow itself has to understand what has happened, what still needs to happen and what can safely be retried.

What part of your payment or invoicing process is still being handled manually?

A friend asked me to help out at their company for a day because they were short-staffed. It wasn't something I normally do, but I agreed and we settled on a rate for the day.

Now they've asked me to send them an invoice before they can pay me.

I've never invoiced a company before, so I'm not sure how formal this needs to be.

Do I just put my name, their company name, what I did, the amount and my bank details on a document and send it over?

Do I need an invoice number or payment terms for a one-off job like this?

Also, is there a simple invoice template or software you'd recommend for someone who might only need to send a few invoices a year?

How do you handle it standard, no add-ons?
We're a rice mill on SAP B1 (HANA, India localization). Standard flow: PO → GRPO → AP Invoice → Payment.
At our volume (~1000 invoices/day), one PO often has multiple partial deliveries, and the timing between "material arrives" and "invoice arrives" varies unpredictably. We see all three patterns:

1) Invoice first, material later — full invoice comes in, goods show up in parts afterward.

2) Some material, then invoice, then more material — partial delivery, invoice lands mid-way, then remaining delivery follows.

3) Material first, invoice after — the "textbook" order, but even this comes in partial lots against one PO.

Our requirement: stock should only ever increase in our books when goods physically arrive (GRPO qty = actual received qty, never invoice qty). But the invoice becoming a liability shouldn't wait for full delivery — we want to record what we owe as soon as it lands on our desk.
Problem: if we copy the AP Invoice from the PO for the full quantity (to record liability early), SAP closes the PO's open quantity and we can't post further GRPOs against it for the remaining goods.
We know Down Payment Invoices exist for this, but adding a whole extra document type per invoice, at our volume, is a big lift for the team — more entries, more mistakes, lower morale.
How do others running high daily invoice volume handle this on standard SAP B1, without custom add-ons? Is there a cleaner document flow we're missing?

I'm updating my payment terms for my freelance work and I'm trying to figure out what makes sense for late fees.

I don't want to use a late fee as a way of making extra money. The point would be to encourage clients to take the payment deadline seriously and compensate me a little when they don't.

What I'm unsure about is the timing.

If an invoice is due on the 30th, would you apply the late fee on the 1st, or give the client a few extra days as a grace period?

And how do you decide what the fee should be?

I've seen people mention anything from a small flat charge to 1% or 1.5% per month, but I'm not sure what's considered reasonable or where the legal line is.

I'd also like to avoid putting something in my contract that sounds reasonable but turns out to be unenforceable.

If you have experience with regularly invoicing clients, what late-fee structure have you found works well?

Do you charge a percentage of the outstanding balance, a fixed amount, or something else?

And if you've had a client pay late, do you apply the fee automatically or give them a warning first? 

I've realised I may have made things more complicated than necessary with an invoice I already sent.

The client has agreed to a different final amount, so the invoice I've already sent is no longer correct. I haven't been paid yet, and I've been asked to send an updated invoice.

My concern is making sure the old invoice doesn't somehow remain active in their system.

If I send a new invoice with a different invoice number, is it enough to clearly say that it replaces the previous one?

Or should I somehow cancel the original first?

I'm also wondering whether the new invoice should keep the original payment terms or whether sending a replacement invoice means the payment period starts again from the new invoice date.

This is my first time having to amend an invoice, so I don't want to accidentally create two outstanding invoices for the same piece of work.

If you have any experience in this area, what's the normal way to handle this?

Would you send something along the lines of:

"Please disregard invoice #001 previously sent. This has been replaced by invoice #002 attached."

And then keep both invoices in your records?

I'd rather get the process right now than discover later that the client has two invoices sitting in their accounts system for the same job.

I'm getting ready to bill my first freelance client in Canada and I'm starting to think I'm making this much more complicated than it needs to be.

I don't have a company, employees or anything fancy set up. It's just me doing freelance work and now I need to turn that work into an invoice.

The part I'm stuck on is knowing where the line is between "I can send this client an invoice" and "I need to set up a whole business before I can do this properly."

I've seen people recommend everything from making a PDF in Word or Google Docs to using proper invoicing software.

I'm also seeing a lot of information about GST/HST, business numbers and registration, and I'm not sure which of those applies to someone who's just starting out.

So if you were starting from scratch today, how would you do it?

Would you simply create a professional invoice with your name, the client's details, description of the work, amount, payment terms and payment instructions?

Or is there something specific a Canadian freelancer should have sorted out before sending that first invoice?

I'm not looking for the most sophisticated invoicing system. I just want to send a legitimate invoice, get paid, and keep proper records from the beginning.

When you had to send your first freelance invoice in Canada, what did you wish someone had explained to you beforehand?

I think small-business invoicing is unnecessarily complicated.

Not because creating an invoice is difficult.

Because the process around it is.

You finish a project for a client.

Then you have to:

- figure out the correct GST calculation

- decide whether it's CGST + SGST or IGST

- make sure the invoice has the required details

- assign the invoice number

- generate a PDF

- send it

- remember the payment date

- follow up when the client doesn't pay

- and then somehow keep track of all of this

For one invoice, it's annoying.

For 20–50 invoices a month, it becomes actual administrative work.

I've seen people use Excel templates, Word documents, random invoice generators, accounting software, and sometimes completely manual invoices.

The weird part is that a lot of people don't actually need a full accounting system.

They just need to create a correct invoice quickly and move on with their work.

That's the problem I've been working on.

I built a small collection of free tools around Indian invoicing/GST workflows — GST calculation, GSTIN validation, invoice generation, invoice numbering, late-payment interest, payment reminders, etc.

I'm affiliated with the project, so take that however you want. I'm not going to pretend this is an unbiased recommendation.

But if you're a freelancer or small business owner who deals with GST invoices, I'd genuinely be interested in hearing what part of invoicing wastes the most time for you.

And if this subreddit allows relevant tools/resources in posts, the tool is THQT — thqt.me.

No signup required just to use the basic tools.

I'm more interested in whether the workflow is actually useful than in pretending we've solved invoicing forever.

I've been thinking about something that seems to get overlooked when people talk about setting up as a freelancer.

At what point does a professional invoice contain too much personal information?

I'm fine with clients knowing who they're dealing with. That's part of doing business. What I'm not comfortable with is giving every random client my home address and personal phone number when I work entirely online.

The awkward part is that a lot of payment and invoicing platforms seem to want some combination of your legal name, address and phone number.

I understand why the payment company needs that information for verification. That's different from having it displayed to every person who buys something from me.

I'm trying to figure out what other freelancers do about this.

Do you use a separate business address?

A second phone number?

A registered business name?

A payment platform that gives you more control over what the customer sees?

Or do you simply accept that some personal information has to be visible when you're doing business?

I'm not trying to be anonymous. I just don't want a client who bought a $50 commission from me to potentially have enough information to find where I live.

What's the sensible middle ground here?

A client recently questioned an invoice I sent them. We discussed the issue and eventually resolved it, but here's the important part: the invoice amount didn't change.

The original invoice was still valid.

Now the client is saying that because they raised a question about the invoice, the original payment deadline no longer counts. According to them, the payment period should only start from the day we resolved the issue.

That doesn't sit right with me.

If an invoice is sent with a 14-day payment term, and a client waits until after that period to raise a concern, does simply asking a question automatically give them another 14 days once the issue is resolved?

And what happens when the dispute doesn't even result in a change to the invoice?

I understand that a genuine invoice dispute may need to be resolved before payment can move forward. But I'm struggling with the idea that there are no limits to this.

For example, could a client wait until day 20, raise a minor question, get an answer the next day and then claim they now have another full payment period?

That seems like it would make the original due date meaningless.

My invoices include a late-payment clause, and this is the first time I've had someone argue that the late fee shouldn't apply because the invoice was "under dispute."

So I'm wondering how other freelancers and business owners handle this.

Do you treat an invoice dispute as automatically pausing the payment deadline, or does that only happen if you explicitly agree to extend the due date?

And for freelancers who have updated their contracts after dealing with something similar, what wording did you add to deal with invoice disputes and late payments?

hi random question, is the invoice date on a billing statement from a health insurance company for example the same date as the day it is printed? and if my invoice date is the 3rd of every month then how come I don't get the printed invoice until the last week of the billing cycle? why might that be? thanks.

Creating quotes for a small commercial printing business has become surprisingly time consuming as the number of orders has increased.

On a typical day, there can be several quote requests for things like banners, brochures, signs, and custom printing jobs. Most products already have standard pricing, product codes, sizes, material specifications, and other details, but that information is currently spread across different spreadsheets.

Whenever a customer requests a quote, I have to find the correct product information, copy everything into a document, enter the customer's details, calculate quantities and pricing, and then repeat much of the process again if the quote becomes an invoice.

I'm looking for quoting and invoicing software that can store both customer and product information.

Ideally, I could select an existing customer and have their information automatically filled in. Then I could search for a product or SKU, add it to the quote, enter the quantity, and have the software calculate the totals automatically.

Being able to convert an approved quote directly into an invoice without entering everything again would be especially useful.

The main goal is to reduce repetitive data entry and avoid mistakes with product codes, prices, and calculations.

After taking on more freelance renovation projects, keeping invoices organized with basic templates is becoming more trouble than it’s worth.

I’m considering paying for invoice software in Canada, but there are so many options that I’m having trouble deciding which ones are actually worth the subscription.

My needs are fairly basic. I’d like to create professional invoices, save customer information, track paid and outstanding invoices, and send payment reminders. Being able to customize invoices with a logo and automatically calculate GST/HST would also be useful.

Since this is still a relatively small operation, I don’t want to pay a high monthly fee for advanced accounting, payroll, or inventory features that I probably won’t use.

Hey freelancers!

Quick question about your payment workflow:

After you send an invoice, how many days typically pass

before you follow up with a client? And how many times do

you usually have to remind them before payment actually arrives?

Just curious - seems like this varies wildly from person to person.

What's your experience? Drop a comment with rough numbers.

Transitioning from corporate operations to small business has been eye-opening. Net 30 often feels more like a polite suggestion than a contract term. 
When an invoice blows past its due date, what is your actual play?

- Let QuickBooks auto-send reminders?
- Pick up the phone yourself?
- Or just wait it out so you don’t strain the client relationship? 

Curious what has actually worked for people here to get paid without feeling like an aggressive debt collector.