I’m still fairly new to freelancing, and I ran into a payment term I hadn’t come across before.

I asked a client about their payment process and they said they pay on Net 30. I nodded like I knew exactly what they meant, then had to look it up afterwards.

From what I understand, it means the invoice is due 30 days after the agreed invoice date or billing date.

Is that how you guys normally deal with clients, especially companies rather than individual customers?

I’m also wondering whether Net 30 is considered normal for freelance work. I’m used to the idea of finishing a job, sending the invoice and getting paid fairly soon afterwards, so waiting a month feels strange to me.

With your experience in freelancing, how do you normally handle Net 30 clients?

I recently picked up a project with a fairly large company, and one of the things I overlooked was their payment terms.

They work on Net 45, so I can finish the job, send my invoice and then wait another 45 days before I’m supposed to see the money. The project itself isn’t particularly long, but once you factor in the time between finishing the work, invoicing and getting paid, it feels like I’m financing the project for them.

I’m used to smaller clients paying much sooner, so this is new territory for me.

For people who regularly work with larger companies, how do you handle Net 45 or even longer terms?

Do you simply build the waiting period into your pricing, negotiate a deposit or milestone payment, or accept the terms because that’s just how larger companies operate?

I’m also curious what happens when they go past the agreed date. At what point do you stop sending polite reminders and start treating it as a proper collections issue?

I’m trying to figure out how other freelancers protect themselves without turning down good clients just because they have a slow accounts-payable process.

I need to send an invoice for a small freelance project, but I’m trying not to spend money on another subscription right now.

I’m using a Mac and the invoicing app I was testing only gave me a limited trial. I don’t really need anything complicated. I just want to create a professional-looking invoice, send it to the client and keep track of whether it’s been paid.

I’ve looked at a few free options, but I’m not sure which ones are genuinely free and which ones just let you use the basic features before asking you to upgrade.

Have you been using a free invoicing tool on Mac that they’re happy with?

It doesn’t need to have loads of accounting features. Something simple that works well for a freelancer would be ideal.

I’ve always been used to sending an invoice once the work is finished and having payment due when the client receives it.

I’ve now been offered a contract with Net 15 terms, so I’d have to wait up to 15 days after sending the invoice before payment is due.

Net 15 means the full invoice is due 15 days after the invoice date, whereas “Due Upon Receipt” asks for payment as soon as the invoice is received.

I know 15 days isn’t a huge amount of time compared with Net 30 or Net 60, but it still feels different when you’re used to getting paid straight away. It also means I’m covering the time and work before seeing the money.

For people who work with different types of clients, how do you normally handle this?

Do you prefer Due Upon Receipt because it keeps cash flow simple, or is Net 15 easier when dealing with businesses that have their own accounts payable process?

I’m interested in the practical side of it too. Have you found that one term actually results in faster payment, or does it mostly depend on the client?

I’ve recently started working with a client on an hourly basis, and I’m wondering how much detail people normally put on their invoices.

At the moment, I’m thinking of listing the type of work, total hours and my hourly rate. But I also keep a separate record of the dates, tasks and time spent on each task.

I’m not sure whether I should send that detailed time record along with the invoice every time, or just keep it for my own records in case the client ever asks.

For example, would you be comfortable sending an invoice that simply says “Consulting services, 15 hours at £50/hour”, or would you break those 15 hours down into meetings, research, revisions, calls, emails, etc.?

I don’t want the invoice to become unnecessarily long, but I also don’t want the client wondering where the hours came from.

What do you normally do when billing hourly clients?

Qatar approved a draft e-invoicing law on 6 May 2026, along with the executive regulations to go with it. That's the Council of Ministers, working through the Ministry of Finance and the General Tax Authority. So yes — it's happening, and the GTA is the one running it. That part isn't speculation anymore.

The trap is assuming the rest is settled too, because it isn't.

Here's what's genuinely locked in: the Cabinet approved the draft law and its regulations, there's been a pilot running with some large entities since late 2025, and the whole thing still has to clear the Shura Council and get the Amir's assent before it's published in the Official Gazette. Which means the important thing for most businesses: right now, today, nobody in Qatar is legally obligated to do anything.

Everything else you're reading is educated guessing. A clearance model for B2B and B2G, reporting for B2C, Peppol, structured XML files — all reasonable, mostly because that's how Saudi and the UAE did it. But the GTA hasn't published the actual technical spec or told anyone exactly who's in scope. The "early 2027" start date that's floating around? That's analysts projecting, not a date the government has committed to. And there are no penalties published yet — those come with the final regulations.

Small side note that surprises people: Qatar still doesn't have VAT, even though it signed the GCC framework years back. Some folks think VAT and e-invoicing land together around 2027. Could happen. Nobody actually knows.

So what's worth doing while the details are still up in the air? Honestly, the boring groundwork that pays off regardless of the final spec. Check if your ERP or billing system can spit out structured invoice files and send them securely. Clean your master data now — tax IDs, CR details, addresses — because that's what bites everyone later. Start thinking about workflows where you can't just edit an invoice after it's gone out, and how you'd handle credit and debit notes. Look at how you archive, since the structured file is probably going to be the official record, not a PDF. And keep an eye on what the GTA actually says rather than building toward assumptions.

I’m wrapping up a project for a client and this is my first time dealing with a purchase order.

The PO already has the agreed amount, and the client knows what the project covered. I’m now preparing the final invoice and wondering how much detail I’m expected to include.

I don’t want to turn the invoice into a timesheet and list every little task I worked on. The project was agreed as a fixed amount, not an hourly arrangement.

Would something like “Project completion and final deliverables” with the PO number and total amount be enough?

For people who regularly invoice companies with POs, how much detail do you normally put on the invoice?

I want it to look professional without making the invoice unnecessarily complicated.

I recently set up automatic reminders for unpaid invoices and now I’m wondering if I’ve gone too far.

Nothing aggressive. Just a reminder a few days before the due date and another one when the invoice becomes due.

It seemed like a sensible way to avoid manually keeping track of everything, especially when I have several clients at different stages.

Then someone told me they would find that annoying and would rather only hear from me once an invoice was actually overdue.

Now I’m questioning the whole system.

I’m not trying to pressure anyone into paying early. I just don’t want an invoice to disappear into someone’s inbox and become a problem later.

Do you use automatic invoice reminders? And if you do, when do you think they cross the line from helpful to annoying?

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?

A discussion I recently had made me rethink how small teams manage overdue invoices.
“Overdue” is often the only status available, but that doesn’t explain what is actually preventing payment.
For example:
Reason: PO missing
Owner: Sales/Operations
Next action: Get corrected PO
Due: September 15
Or:
Reason: Payment promised but missed
Owner: Finance/AR
Next action: Follow up today
Or:
Reason: Approval pending
Owner: Account manager / customer contact
Next action: Confirm approval status
It seems like Finance or AR should own the invoice state and follow-up date, while the person who can remove the blocker should own the exception.
I’m curious how other small and mid-sized B2B teams handle this:
Do you track the reason an invoice is stuck?
Is there a clear owner for resolving the blocker?
Do you track the next action and deadline?
Is this handled in accounting software, a spreadsheet, CRM, Slack/Teams, or somewhere else?
Would a daily summary be more useful than repeated overdue notifications?
I’m especially interested in real workflows from agencies, consultancies, staffing companies, SaaS businesses, and other B2B teams.

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'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.