Purchase Order vs Invoice: What Is the Difference?

A purchase order comes from the buyer, before the work. An invoice comes from the seller, after it. The PO says "please supply this at this price." The invoice says "here is what I supplied, please pay." Same transaction, opposite ends, opposite directions.

That's the difference in full. But the reason people search for it is usually more specific: an invoice has gone unpaid, and somebody has mentioned a PO number you don't have. So here's how the two documents actually interact, and where payments get stuck.

What is a purchase order?

A purchase order is a document the buyer sends to a supplier saying exactly what they want to buy, at what price, and on what terms. It carries a unique PO number, and that number is the thread everything else hangs off.

A typical PO includes the PO number and date, the buyer's and supplier's details, a line-by-line list of goods or services with quantities and unit prices, the total, delivery details, and the payment terms.

Two things about POs surprise people. First, it's a control document before it's a commercial one. Its main job inside a company is making sure spending was authorised by somebody with authority to authorise it. Second, on its own it's an offer to buy, not a contract. It becomes binding when the seller accepts it, whether by countersigning, confirming by email, or simply starting the work. Sending a PO into silence is not a deal.

What is an invoice, and how is it different?

An invoice is the seller's request for payment after goods or services have been delivered. Where the PO looks forward at what will happen, the invoice looks back at what did.

That last row matters more than the rest. A purchase order is never a tax document. Only a proper tax invoice supports a GST input tax claim, which is covered in our GST invoice guide. If you're wondering where receipts fit into this, our receipt vs invoice guide handles that pair.

Which side issues each one, and when?

The full sequence in a business that uses POs runs like this:

1. The buyer requests a quote. You send a quotation with your price and terms.
2. The buyer raises a purchase order. Internally approved, then sent to you with a PO number.
3. You accept it. Confirm in writing. This is the moment it becomes binding, and the moment most freelancers skip.
4. You deliver. Goods arrive or work completes.
5. The buyer records receipt. A goods receipt note or a sign-off that the work was done.
6. You invoice, quoting the PO number. Leave the number off and you've made your invoice hard to match.
7. Accounts payable matches and pays.

Step 6 is where most avoidable delays start. If a client gave you a PO number, it belongs on the invoice, usually near the top. Their system may literally have no way to route an invoice without one.

What if the buyer issues the invoice instead of you?

Then you have run into self-billing, and nothing has gone wrong. It inverts the rule the section above just set out, which is why it throws people the first time a client says do not send us an invoice, we raise it ourselves.

The arrangement is exactly what it sounds like. The buyer creates the invoice on your behalf, using their own record of what you supplied, and sends it to you along with the payment. It is common wherever the buyer knows the final figure better than the supplier does: construction subcontracting where the value depends on a measured site survey, agriculture priced on weight at delivery, recruitment agencies paying contractors on approved timesheets, and marketplaces or royalty payers handling thousands of small suppliers.

It is also properly regulated rather than an informal habit, because an invoice is a tax document and the tax authority cares who wrote it. The United Kingdom is a good worked example. HMRC's guidance on self-billing sets out the conditions, and its internal manual traces the legal basis back to Regulation 13(3) of the VAT Regulations 1995, under which a self-billed invoice stands in for the VAT invoice you would otherwise have issued.

Four conditions are worth knowing before you sign anything:

• There has to be a written agreement. Paper or electronic, and it has to record that you accept the buyer raising invoices for your supplies.
• You agree to stop invoicing for that work. The agreement must state that you will not raise your own VAT invoices for anything it covers. This is the part that bites, and the next paragraph explains why.
• It has a start and an expiry date, and HMRC recommends reviewing the arrangement every twelve months to confirm you are still VAT registered and still willing. You also have to tell the buyer if your registration lapses or your number changes.
• The document has to say SELF-BILLING on it. HMRC also suggests wording noting that the VAT shown is your output tax due.

Worth knowing that nobody needs permission for any of this. HMRC states plainly that you do not need its authorisation to operate self-billing, so a buyer proposing it is not doing anything unusual or requiring approval.

Now the trap, and it is the one that causes real damage. If you forget the arrangement and send your own invoice for work already self-billed, you have created a second tax document for a single supply. Depending on how both sides post it, that is a duplicate in the accounts and an overstated VAT position, and it surfaces at exactly the wrong moment, which is during an audit rather than during the month it happened. Keep a clear list of which clients self-bill and treat it as a rule rather than something you will remember.

The other thing to hold onto is that the document is still your tax position even though someone else typed it. Check every self-bill the way you would check a payment: quantities, rate, the VAT treatment, and whether the total matches what you actually delivered. An error in a self-bill is not the buyer's problem to notice, and the returns filed against it are yours.

Terminology varies once you leave the UK, so search the right phrase for where you are. Australia calls the same document a recipient-created tax invoice, usually shortened to RCTI, with its own written-agreement rules. The EU VAT rules permit self-billing across member states subject to prior agreement and an acceptance procedure. The shape of the arrangement travels; the specific conditions do not, so check your own authority before you rely on another country's version.

Do you legally need a purchase order?

No. There's no law in Singapore or anywhere else requiring a buyer to issue a PO or a seller to demand one. It's a business control, chosen by the buyer.

Which means the honest answer for most readers is: probably not yet. If you're a sole proprietor or a two-person outfit, a written quotation your client accepts by email does nearly the same job with a fraction of the admin. Our free quotation template guide covers that route.

POs start earning their place when one of these is true:

• Someone other than you can commit money. The moment a second person can order things, you need a record of who approved what.
• A single wrong order would actually hurt. If your typical purchase is large enough that a mistake is painful, the paperwork is cheap insurance.
• Your clients demand one. Large companies and government agencies usually will, and that's not negotiable.
• You're arguing about scope. A PO fixes what was agreed before the work, which is much easier than reconstructing it after.

Below that threshold, it's overhead. Above it, skipping POs is how businesses end up paying for things nobody remembers ordering.

Why does your invoice get held up by matching?

Because your invoice is being checked against two other documents before anyone releases money, and any disagreement stops the clock.

The process is called three-way matching, and it's a standard accounts payable control. Before approving payment, the AP team compares three things:

1. The purchase order, which says what was authorised.
2. The goods receipt, which says what actually arrived or was completed.
3. The invoice, which says what you're billing for.

They check quantity, unit price, total, and the PO number. All three agree, the invoice goes for payment. Anything disagrees, it gets flagged and sits in a queue until a human resolves it. The control exists to catch duplicate payments, pricing errors, and billing for things that never turned up, which is exactly why nobody in AP is willing to wave a mismatch through.

Not every client runs all three checks, though, and knowing which version you're dealing with tells you what will trip you up.

Two-way matching is the friendlier one for freelancers and service businesses, because there's no delivery note for a design job or a month of consulting. If you're selling services and your invoice is stuck, the culprit is almost always the PO number or the amount, not a missing receipt. If you're shipping physical goods, the receipt is the piece most likely to be missing, and it's the piece you have least control over.

Plenty of larger buyers set a value threshold: below it, two-way; above it, three-way. So the same client can pay one of your invoices in a week and sit on the next one for a month, purely because the second crossed a number in their policy that nobody told you about. Asking which threshold applies is a fair question to put to accounts payable, and they'll usually answer it.

From your side, the practical consequences:

• Quote the PO number exactly. One transposed digit and your invoice is unmatched.
• Bill what the PO says. If the job changed mid-way, get a revised PO before invoicing. Do not just invoice the higher figure and hope.
• Match the line structure. If the PO has three lines, three lines on the invoice is safer than one lump sum.
• Chase the goods receipt, not just the invoice. If nobody at the client has confirmed delivery, your invoice can't match no matter how correct it is. This is a surprisingly common cause of "we never got your invoice."

If an invoice has gone quiet, a matching problem is the first thing to rule out. Our late payment follow-up guide covers what to do next.

What if the work changes after the PO is issued?

Get the PO amended before you invoice. That's the whole answer, and it's the single most useful habit in this article, because almost every stuck invoice traces back to somebody skipping it.

Here's why it bites so hard. The matching check above compares your invoice against the authorised amount. If the PO says S$4,000 and you bill S$5,200 because the job grew, nothing in that system cares that the extra work was real, or that your contact approved it in a Slack message. The numbers don't agree, so it flags. And a flagged invoice becomes an invoice dispute, which is one of the two causes of late payment Atradius names for Singapore. The dispute isn't about whether you did the work. It's about a number that no longer matches.

Three versions of this come up, and they need different handling.

The scope grew. Stop before you bill. Ask for a revised PO or a second PO covering the extra, and get the number in writing. Written approval from the person you deal with is not the same thing as an amended PO, because the approval and the payment run through different people. Your contact can genuinely mean it and still be unable to make accounts payable release the money.

The scope shrank, or you delivered part of it. Invoice what you actually delivered and reference the PO. Billing the full PO value for partial delivery fails matching just as reliably as overbilling, and it's a worse look.

You're billing in stages. Several invoices against one PO number is completely normal and no buyer will object. Number them clearly, say which stage each covers, and state the running total against the PO so whoever opens it can see at a glance what's left. That saves them a calculation and saves you a query.

If you already sent the invoice and the value has to change, don't edit and resend it. Reissuing an invoice under the same number breaks your own audit trail and the buyer's. The correct instrument is a credit note, and our credit note guide covers what one needs on it.

Now the case the standard PO sequence handles badly: retainers and recurring work. One PO per job doesn't fit a monthly retainer, and raising twelve POs a year is exactly the admin nobody wants. Ask for a blanket PO instead, sometimes called a standing order. It covers a period or a value ceiling, and your monthly invoices draw down against it.

Two things to pin down when you agree one, because both are quiet failure modes:

• The ceiling. Once your cumulative invoices hit it, further invoices stop matching, and the failure looks identical to having no PO at all. Track your running total yourself rather than assuming someone will warn you.
• The expiry date. Blanket POs are usually issued for a financial year. A lapsed one blocks payment just as hard as a missing one, and the lapse tends to land in the first week of the new year when nobody has renewed it yet. Put the renewal in your calendar a month early.

There's a development here worth knowing about, because it's moving this whole problem onto the same infrastructure as invoicing. Singapore's InvoiceNow network doesn't only carry invoices. The Singapore Peppol Guide, published by IMDA, sets out what Access Points and InvoiceNow-Ready Solution Providers must support, and alongside Invoice and Credit Note the list includes Order documents under several profiles (Order Only, Ordering, Advanced Ordering and Order Agreement), plus Order Balance and Invoice Response.

Two of those matter directly for this section. Order Balance tracks how much of an order is still outstanding, which is the partial-delivery and blanket-PO problem handled by the network rather than by your spreadsheet. And Invoice Response is the buyer telling you electronically that your invoice was accepted, rejected or is under query, instead of the silence most of us currently get and have to chase.

None of this is compulsory for you today. The GST InvoiceNow requirement covers invoice data, not procurement documents, as the e-invoicing section below explains. But if your buyer is large enough to run POs, they're likely to be early on that timetable, and the practical upside is real: a rejected invoice that tells you why beats an invoice that just never gets paid.

The rule underneath all of it fits in one sentence. Bill what was authorised, and when the two stop matching, fix the authorisation before you send the bill.

What if the buyer won't give you a PO number?

Don't invoice yet. An invoice sent into a PO-driven accounts payable system without a PO number on it is not an early invoice, it's a rejected one, and rejection usually resets your payment clock rather than pausing it.

This trips up small suppliers constantly. You've done the work, the person who hired you is happy, and they tell you to just send the invoice over. But the person who hired you and the person who pays you are rarely the same person, and AP has no authority to release money against a PO that doesn't exist. Your invoice arrives, fails the match described above, and sits in an exceptions queue where nobody owns it.

So the useful move is to get the PO sorted before you start, or at minimum before you bill. A few situations and what actually works in each:

• They forgot to raise it. Most common by far. Ask your contact directly for the PO number and, if you can, the name of whoever raises POs in their team. Getting that second name is what stops this recurring on every job.
• The PO exists but nobody sent it to you. Also common. Ask them to forward the PO document itself, not just read you the number, so you can check the description, quantity, unit price and validity dates match what you agreed. Catching a wrong line item now is far cheaper than after you've invoiced against it.
• They say they don't use POs. Sometimes true, especially with smaller firms. Get the agreement in writing anyway, by email if nothing else, covering scope, price and payment terms. That written trail is what you'll rely on if the invoice is later queried.
• The work grew past the PO value. The PO needs amending or a second one raising before you bill the extra. Invoicing over the authorised amount is one of the most reliable ways to get an invoice stuck, and the section above on scope changes covers how to handle it.
• They want you to start before the PO is issued. This is a commercial risk decision, not an admin one. If you proceed, get written confirmation that the work is authorised and a PO will follow. Verbal go-aheads are worth very little once an invoice is disputed.

One habit worth building: put the PO number on the invoice itself, in its own clearly labelled field, not buried in a description line. Matching is often partly automated, and a number the system can't find in the field it's looking at is functionally a missing number. Same goes for quoting it in your email subject line when you send the invoice across.

And if you're regularly billing a client who keeps promising a PO that never materialises, treat that as the payment risk signal it usually is. Our guide to invoice payment terms covers setting terms that give you somewhere to stand when this happens.

What if the invoice still doesn't get paid?

Then you're in the situation most readers of this page are actually in, and it's more common than the tidy PO-to-payment sequence above suggests.

Atradius Collections publishes an annual payment practices survey for Singapore. Its 2025 edition, published in July 2025, found that roughly 35 percent of B2B invoices in Singapore are overdue on average, and about 6 percent end up as bad debt. It puts average payment terms at 46 days, with 54 percent of B2B sales made on credit. The two causes it names for late payment are customer liquidity problems and invoice disputes.

That second cause is this whole article in one phrase. An invoice dispute is very often just a matching problem nobody has picked up the phone about. Worth treating as a caveat, though: Atradius is a trade credit insurer surveying its own market, not a government statistics agency, so read the numbers as a well-informed industry estimate rather than an official figure.

Atradius has since published a regional edition, and it puts Singapore in useful context. The B2B Payment Practices Trends in Asia 2026 report, out on 8 July 2026, found that Singapore has the highest share of B2B sales made on credit anywhere in Asia, at 51 percent, against a regional average of 43 percent. Across Asia as a whole, close to a third of B2B receivables were overdue.

That top ranking is not a compliment, exactly. Selling on credit is what a trade hub does, and Singapore does more of it than anyone else in the region. But every credit sale is an invoice waiting to be matched, queried, or quietly parked, which is precisely the machinery this article is about. More of your revenue sits in that queue here than it would almost anywhere else nearby.

One figure in the regional report is worth flagging if you are a subcontractor. Overdue receivables climb to roughly 40 percent among smaller firms in construction and trade, well above the Asia-wide third. Which is a decent argument for reading the next few paragraphs carefully, because construction is the one sector with a statutory way out.

Your first move is boring and it works: confirm the PO number, the quantities, and the goods receipt before you escalate anything. Most stuck invoices come unstuck there.

But if you work in construction, you have a statutory route the rest of us don't, and a surprising number of subcontractors never use it.

Singapore's Building and Construction Industry Security of Payment Act, introduced in 2005, gives contractors and suppliers a fast adjudication process for payment disputes instead of going to court. The Building and Construction Authority describes it as a simple, fast and low-cost mechanism, and says that by the end of 2018 it had already facilitated roughly S$1 billion in payments. Adjudication is administered by the Singapore Mediation Centre. The Act also sets a minimum late payment interest rate of 5.33 percent a year, applied where that beats whatever your contract says.

Two limits worth knowing before you get excited. It applies to written construction contracts, and it excludes residential work that doesn't need a Building Plan submission, so an HDB flat renovation is outside it. And the process runs on short deadlines at each step, which is exactly why people miss their window. BCA publishes a Security of Payment Act information kit with the current timings, and if a serious claim is on the line that's the document to read rather than a blog.

Outside construction there's no equivalent fast track, so your bargaining power is contractual: clear payment terms agreed up front, and a follow-up sequence you actually run. Our invoice payment terms guide covers setting them, and the chasing late payments guide covers the rest.

What changes when the buyer is in another country?

The two documents don't change at all. A PO is still the buyer's order and an invoice is still your bill. What changes is how unforgiving the matching gets, because three fields that rarely cause trouble domestically become the most common reasons a cross-border invoice gets rejected.

Work through them in this order.

Currency. If the PO is raised in the buyer's currency and you invoice in yours, the match fails on amount even when every line item is correct. And the deeper question is who carries the movement between order date and payment date, which on a 60-day term is a real number rather than a rounding issue. Agree the invoicing currency before the PO is raised, get it written on the PO itself, and invoice in exactly that currency. If you need to be paid in something else, that's a bank instruction, not an invoice change.

Tax identifiers. Domestically you can often get away with a thin tax block. Across a border you usually can't. Depending on the countries involved, the invoice may need the buyer's tax registration number, a statement about where the supply is treated as taking place, and wording covering who accounts for the tax. Get the buyer's registration number at PO stage. Asking for it after you've invoiced means reissuing.

The PO reference itself. Different systems format and truncate references differently, and a reference that arrives clipped or reformatted won't match. Copy it exactly as issued, in the field the buyer tells you to use, and don't tidy it up.

Why the standards work matters to a small supplier

This is where the plumbing has quietly improved, and it's worth knowing even if you never touch it directly.

Peppol, run by the non-profit OpenPeppol AISBL and going since 2008, is the network a growing number of countries have standardised on for exchanging business documents between organisations. The detail that matters for this article: it carries purchase orders as well as invoices. Both sit on the same rails, in the same structured format, which is what lets a buyer's system match them without a human retyping anything.

The European rules show what that looks like once it's mandatory. Under Directive 2014/55/EU, adopted on 16 April 2014, all public authorities have had to be able to receive and process invoices meeting the EN 16931 European standard since the April 2020 deadline, for contracts above the EU procurement thresholds. So a supplier can send one standard-compliant invoice to a public body in any member state rather than learning a different portal for each.

Two honest caveats. That obligation is on the buyer to receive, not on every business to send. And the Commission's own 2024 review reports limited adoption among EU businesses and low uptake of the standard, so plenty of cross-border invoicing is still PDFs by email. The direction is set. The arrival is uneven.

What to do before you start the work

• Get the PO before you invoice, not after. The advice earlier on this page applies harder here, because chasing a missing reference across a time zone costs days rather than an afternoon.
• Confirm invoicing currency and payment currency separately. They're allowed to differ, but only if both sides know it in advance.
• Ask which format they want. A structured e-invoice, a portal upload, or a PDF. Sending the wrong one is a rejection, not a preference.
• Collect the tax registration number at order stage. Along with the exact legal entity name and billing address, which are often not the same as the trading name you've been dealing with.
• Ask who the invoice goes to. Cross-border, the person who briefed you and the accounts payable inbox are almost never in the same office or country.
• Write bank charges into the terms. International transfers carry fees, and if nobody agreed who absorbs them you'll be short-paid and calling it a dispute.

None of this is exotic. It's the same PO-to-invoice discipline described throughout this guide, applied where the cost of getting a field wrong is a fortnight instead of a phone call.

Do you need a PO to sell to the Singapore government?

Yes, in effect, and this is the clearest real-world example of everything above. Government agencies don't do informal. If you're selling to one, the paperwork sequence isn't optional and the invoice route isn't email.

How you get the work depends entirely on the value. The Ministry of Finance sets out four procurement approaches by contract size:

That S$6,000 line is the one small suppliers should know. Below it an agency can simply place the order, which is why a one-off job for a government department can feel refreshingly quick. Above it you're bidding through GeBIZ, the government's e-procurement portal, where quotation notices, tender notices and awards are all published. GeBIZ also publishes indicative procurement opportunities above S$200,000 once a year, which is a free pipeline of what agencies expect to buy.

Now the part that catches people out. Once you've won the work, you don't email a PDF invoice to your contact. Government suppliers submit e-invoices through Vendors@Gov, run by the Accountant-General's Department, or from within GeBIZ itself.

And the PO equivalent has a different name here. Your client agency issues an Invoicing Instruction, usually shortened to II, at GeBIZ. Per the Vendors@Gov Invoicing Instruction user guide, selecting the II ID is mandatory when you create an e-invoice if your agency has issued you one. If they haven't, you pick the "No Invoicing Instruction / Direct Invoice" option instead.

Which is the three-way matching logic from earlier, just with the government's vocabulary and no room to improvise. Same principle: the reference number is what connects your bill to an authorised commitment, and without it the invoice has nowhere to land.

Three things worth doing before you invoice a government client:

• Ask whether an II was issued, and get the ID. Do this when the work is awarded, not when you're ready to bill.
• Register on Vendors@Gov early. Sorting out your entity details and bank account after you've finished the job just delays your own payment.
• Keep the II reference with the invoice. It's part of the same evidence trail as a PO, and the retention rules below apply to it.

How long must you keep both in Singapore?

At least five years, and the rule covers both sides of the transaction.

The Inland Revenue Authority of Singapore requires businesses to keep proper records and accounts of transactions for a minimum of 5 years from the relevant Year of Assessment. That includes source documents like invoices and receipts, and it covers tax invoices you issue to customers as well as those your suppliers issue to you. Records can be kept physically or electronically, so a tidy folder of PDFs is fine.

The consequences of not keeping them are specific. IRAS notes that failure to maintain proper records can mean disallowed expense claims, capital allowances, or GST input tax claims, plus penalties of up to $5,000 and, in default of payment, imprisonment of up to 6 months.

If you run a Pte Ltd rather than a sole proprietorship, there's a second duty on top of the tax one, and the two clocks don't start at the same moment. The Accounting and Corporate Regulatory Authority sets out directors' duties under sections 199(1) and 199(2A) of the Companies Act, and its guidance is blunt: keep records for at least five years after the end of the financial year in which the transactions were completed, and make sure those records can actually be used to prepare true and fair financial statements. IRAS counts from the Year of Assessment. ACRA counts from the financial year end. In practice that means the safe answer is to keep everything until the later of the two dates, which for most companies is a shade over six years.

Purchase orders aren't tax documents in their own right, but they're part of the evidence trail explaining a transaction. If IRAS queries an expense, a PO showing what was ordered and approved is exactly the sort of supporting record that makes the answer easy. Keep them with the matching invoices rather than in a separate system nobody opens.

How long must you keep them in other major markets?

There's no single answer, the spread runs from three years to forever, and one major market doesn't work in fixed years at all. If you sell across borders, the retention rule that matters is rarely the one where you're sitting.

The United Kingdom works on a statutory maximum. HMRC's compliance handbook, citing the Value Added Tax Act 1994, Schedule 11, paragraphs 6 and 6A, states that the specified period "is not to exceed 6 years". A shorter period can be specified in particular cases, and different periods can apply to different cases.

One detail there is easy to miss and expensive to get wrong. The obligation holds regardless of whether you remain registered. Deregistering for VAT does not wipe the clock, so closing a business or dropping below a threshold doesn't let you clear the filing cabinet.

Australia works on a fixed five years, counted from an unusual point. The Australian government's business record-keeping guidance says you need to keep most business records for 5 years, and that the period "starts from when you either got the records or completed the transactions or actions they relate to, whichever is later." Company records and some employee records run to 7 years.

That "whichever is later" is doing real work. A late-arriving document can push the clock past where you assumed it ended.

The United States doesn't really give you a number. This is the one that surprises people. The IRS ties retention to what it calls the period of limitations, which it describes as the window in which you can amend a return to claim a credit or refund, or the IRS can assess additional tax.

The baseline is three years. But it stretches depending on what happened:

• Six years if you don't report income you should have, and it's more than 25 percent of the gross income shown on your return.
• Seven years if you file a claim for a loss from worthless securities or a bad debt deduction.
• Indefinitely if you don't file a return, or if you file a fraudulent one.
• At least four years for employment tax records, from when the tax becomes due or is paid, whichever is later.

Read that list again and notice the awkward part. Several of those triggers depend on facts that may only surface after you've filed. You cannot always know at filing time which bucket you're in, which is why the practical answer in the US is usually to keep things longer than the three year baseline rather than to calculate precisely.

So what do you actually do with a customer base spread across markets?

• Keep to the longest period that touches you, not your local one. If you invoice UK and Australian customers from anywhere, you're effectively running a six or seven year policy. Running three different retention schedules to save filing cabinet space is a false economy.
• Watch where each clock starts. Transaction date, filing date, and end of accounting period are three different starting guns, and the gap between them can be a full year. When in doubt, count from the latest plausible one.
• Store the purchase order with the invoice. When a query arrives years later, the question is almost always whether the amount billed matched what was ordered. That's the matching problem covered earlier on this page, and the PO is half the answer.
• Digital is generally fine, retrievable is the requirement. The common thread across these regimes is that records must remain legible and accessible for the whole period. A file format nobody can open in year six is not a kept record.
• Closing the business doesn't end it. The UK position is explicit on this, and it's the safe assumption everywhere.

None of this replaces advice for your own situation, and thresholds do change. But the shape holds: retention rules are set where your customer and your tax obligations are, they rarely run shorter than five years once you're trading internationally, and the clock is usually longer than people assume.

Is e-invoicing becoming mandatory everywhere?

Close to it, and the direction of travel is the same in most places even though the deadlines aren't. If you sell across borders, this is worth understanding once rather than country by country as each one lands on you.

The short version: tax authorities have worked out that if invoices reach them in a structured format as they're issued, VAT and GST fraud gets much harder. So the invoice is quietly turning from a document you send a customer into a filing you also send a government. The PO side of the process is largely untouched. Nobody is mandating how you raise a purchase order. It's the invoice that's being standardised.

Two examples worth knowing, because between them they cover a lot of the world's trade.

The European Union. The VAT in the Digital Age package, usually shortened to ViDA, was adopted on 11 March 2025 and entered into force on 14 April 2025. Two dates matter after that. From 1 July 2030, digital reporting becomes mandatory for cross-border B2B transactions inside the EU. By 1 January 2035, member states that already run their own domestic real-time reporting systems have to bring them into line with the common standard. The immediate effect, though, started on the day it came into force: member states can now require domestic e-invoicing without first asking Brussels for permission, which is why several have moved quickly.

India. Further along than most people realise. E-invoicing under GST has been phased in by turnover since 2020, and the current threshold is low. A CBIC trade notice records that under Notification No. 10/2023-Central Tax dated 10 May 2023, from 1 August 2023 e-invoicing became mandatory for taxpayers with aggregate turnover above 5 crore rupees in any financial year from 2017 to 2018 onward. That's the sixth phase, down from a 500 crore threshold when it started. It applies to B2B and export supplies, with some categories exempt.

Put those next to each other and the pattern is clear enough to plan around:

• Thresholds fall over time. Every mandate so far has started with the largest businesses and worked downward. If you're under the threshold today, assume you're inside it eventually rather than exempt forever.
• It's the invoice, not the PO. Your purchase order process stays yours. What changes is the format, timing and destination of the bill you issue.
• Cross-border rules arrive after domestic ones. Countries digitise their own trade first and harmonise later, which is exactly the shape of the EU timeline above.
• The buyer's country can pull you in. Selling into a mandate market can mean meeting its format requirements even when your own country has no rule yet. Check the buyer's obligations, not just your own.

The practical move if none of this applies to you yet is unglamorous. Make sure your invoices already carry the things every regime asks for, a unique sequential number, both parties' registration details, clear tax treatment and line-level detail, because that's the data these systems want and a tidy invoice today is most of the work. Our guide on what to include on an invoice covers the full list.

The next two sections work through Singapore and Malaysia in detail, as two mandates already running to a published timetable. If you're somewhere else, read them as a worked example of how these rollouts tend to go, because the shape repeats.

Does e-invoicing change any of this?

It changes the invoice side considerably, and if you're GST-registered in Singapore it's arriving on a published timetable.

IRAS is phasing in the GST InvoiceNow requirement, under which GST-registered businesses transmit invoice data to IRAS through the InvoiceNow network, which runs on the international Peppol standard. The rollout so far:

That last row is the one most business owners haven't registered yet, and it's now official rather than proposed. IRAS confirmed at Committee of Supply 2026 that the requirement extends to all GST-registered businesses by April 2031. So if you're GST-registered today, this reaches you eventually. It's a question of which year, not whether.

IRAS has said it will inform businesses registered before 2026 of their individual implementation date by mid-2026. Transitional funding is available to offset onboarding costs, up to $1,000 for SMEs and up to $5,000 for larger businesses. The full technical detail sits in the IRAS e-Tax Guide on adopting the GST InvoiceNow requirement if you need to brief an accountant or a software vendor.

You can also work out your own year right now without any tooling, because the phases are banded by turnover and IRAS has published them. From section 5.5 of the e-Tax Guide:

The number that decides your row is specific, so use the right one. IRAS goes by your total annual supplies across all prescribed accounting periods ending in calendar year 2025, which is Box 4 on your GST return: standard-rated, zero-rated and exempt supplies added together. Not your profit, and not just your standard-rated sales. If your 2025 periods don't add up to a full 365 days, IRAS lets you extrapolate.

If your 2025 figures sit close to a band boundary, or you'd rather have the answer confirmed than work it out yourself, IRAS publishes a GST InvoiceNow implementation date calculator, a spreadsheet you fill in yourself to work out your own mandatory date. IRAS describes it as a self-help option for existing GST-registered businesses in the meantime, so it isn't a guess or a third-party estimate. It's the same schedule the notification will eventually confirm.

Worth doing sooner rather than later. If your date lands in the first wave from April 2028, you have roughly a year and a half of runway to pick a Peppol-ready system, migrate, and get your invoice numbering and PO references lining up cleanly before anything is compulsory. Find out in 2031 and you're onboarding under a deadline. Five minutes with a spreadsheet now is a much better trade.

What this means for the PO question: purchase orders aren't part of the GST InvoiceNow requirement, since IRAS wants invoice data, not procurement documents. But Peppol carries POs as a document type too, so plenty of businesses adopting e-invoicing end up moving both onto the same rails. If your clients are large enough to insist on POs, they're also likely to be early on the InvoiceNow timetable, which is worth knowing before they ask.

There's money on the table for the switch, and a lot of small businesses don't know about it. IMDA runs a GST InvoiceNow Transition Grant worth S$1,000 in cash, aimed squarely at smaller GST-registered businesses making the move. The headline conditions, per IMDA's own published grant FAQs, are worth reading before you assume you don't qualify:

• You're GST-registered and operating in Singapore.
• Your total annual supplies don't exceed S$4 million, measured across prescribed accounting periods ending in calendar year 2025. That's the same Box 4 figure you just used to find your implementation date.
• You onboard through an IMDA-accredited InvoiceNow-Ready Solution Provider, or connect your existing accounting system through an accredited Access Point, with the onboarding happening after 26 February 2026.
• You weren't already connected to InvoiceNow, and haven't used an accredited provider's solution in the three months before onboarding.
• You actually activate GST InvoiceNow and start transmitting invoice data to IRAS before your own compliance deadline.

The window runs from 1 July 2026 to 31 March 2030, or until the funding runs out, whichever comes first. That last clause is the one to pay attention to. Grants with a fixed pot and a four-year window tend to get quieter long before the end date.

The practical read: if your mandatory date is somewhere in the 2028 to 2031 range and you were planning to deal with it later anyway, moving early is currently worth S$1,000 more than moving late. Check your eligibility on IMDA's grant portal rather than taking a vendor's word for it, since solution providers have an obvious interest in telling you that you qualify.

If you're not GST-registered, none of this applies to you yet. A clean PDF invoice with the right details on it remains perfectly valid, and our guide to what to include on an invoice covers those details.

What about Malaysia's e-invoice mandate?

Malaysia moved faster than Singapore, and if you invoice Malaysian clients this is already live rather than coming.

The Inland Revenue Board of Malaysia runs e-Invoicing through the MyInvois system, and unlike Singapore's phased InvoiceNow rollout it's been mandatory in waves since 2024, sorted by annual turnover. LHDN's official implementation timeline sets it out like this:

Now the line that matters most to anyone reading a free invoice generator's blog. There's an exemption floor, and LHDN has now raised it twice in under a year. A December 2025 revision lifted it to RM1 million. Then Prime Minister Anwar Ibrahim announced a further increase in the 2026 National Day address, and LHDN published it in e-Invoice Guideline version 4.8 on 30 August 2026. Businesses with annual turnover below RM3 million are now excluded, effective 1 September 2026. The Inland Revenue Board said the higher floor takes more than 1.1 million businesses out of scope.

So Phase 4 still reads as "up to RM5 million" on the timeline, but in practice it now bites from RM3 million upward. If you're a freelancer or a small sole proprietor turning over less than that, you're outside the mandate and a normal PDF invoice is still fine. Check your own turnover against the current threshold rather than assuming, because this floor has already moved twice and could move again.

Two things follow for the PO question specifically. First, MyInvois validates invoices, not purchase orders, exactly like InvoiceNow in Singapore. Your client's PO process sits upstream of it and is unaffected. Second, a validated e-invoice carries a unique identifier from LHDN, so if a Malaysian client is in scope they may need that reference alongside the PO number before they can pay you. Ask which system they're on before you send the first bill.

If you invoice into Malaysia regularly, our Malaysia SST invoice guide covers what a valid SST invoice needs on it, and the Singapore vs Malaysia invoicing comparison covers the differences side by side.

What else do people ask?

For the numbers behind your tax and GST obligations, try the free Singapore and Malaysia calculators at AsiaCalc.

Sources: European Commission, Directorate-General for Taxation and Customs Union, VAT in the Digital Age (ViDA), for the 11 March 2025 adoption, the 14 April 2025 entry into force, the 1 July 2030 cross-border digital reporting date and the 1 January 2035 alignment deadline for existing domestic reporting systems. Central Board of Indirect Taxes and Customs (CBIC), Trade Notice 01/2024, citing Notification No. 10/2023-Central Tax dated 10 May 2023, for India's sixth-phase e-invoicing threshold of aggregate turnover above 5 crore rupees with effect from 1 August 2023. OpenPeppol AISBL, peppol.org, for the network carrying purchase orders alongside invoices and other business documents, and for OpenPeppol being a non-profit operating since 2008. European Commission, eInvoicing, for Directive 2014/55/EU adopted 16 April 2014, the EN 16931 European standard, the April 2020 deadline for public authorities to receive and process standard-compliant invoices above EU procurement thresholds, and the 2024 review finding limited adoption among EU businesses and low uptake of the standard. Inland Revenue Authority of Singapore, Record Keeping Requirements, for the 5-year retention rule and the penalties for failing to keep records. Accounting and Corporate Regulatory Authority, Directors' Duties in relation to Financial Reporting, for the sections 199(1) and 199(2A) duty to keep records for at least five years after the end of the financial year. Inland Revenue Authority of Singapore, GST InvoiceNow Requirement, for the phased implementation dates and transitional funding amounts. Building and Construction Authority, Enhancing payment practices in the sector, for the Security of Payment Act adjudication mechanism, the S$1 billion facilitated by end-2018, the 5.33 percent minimum late payment interest rate, and the exclusion of residential work not requiring a Building Plan submission. Singapore Ministry of Finance, Procurement processes, for the Small Value Purchase, Quotation, Tender and Tender Lite thresholds. GeBIZ, Guide to Singapore Procurement, for the publication of quotation and tender notices and the annual indicative opportunities above S$200,000. Accountant-General's Department, Vendors@Gov Invoicing Instruction user guide, for the requirement to select the Invoicing Instruction ID when an agency has issued one, and the Direct Invoice option when it has not. Atradius Collections, B2B Payment Practices Trends, Singapore 2025, published 23 July 2025, for the 35 percent overdue, 6 percent bad debt, 46-day terms and 54 percent on-credit figures. Atradius, B2B Payment Practices Trends in Asia 2026, published 8 July 2026, for Singapore's 51 percent share of B2B sales on credit, the highest in Asia against a 43 percent regional average, the roughly one third of Asian B2B receivables overdue, and the roughly 40 percent overdue among smaller construction and trade firms. Both are a trade credit insurer's industry surveys, not official statistics. Inland Revenue Board of Malaysia, e-Invoice Implementation Timeline and e-Invoice Guideline version 4.8 dated 30 August 2026, for the four MyInvois phases by annual turnover and for the exemption floor rising from RM1 million to RM3 million with effect from 1 September 2026, announced in the 2026 National Day address and reported by LHDN as taking more than 1.1 million businesses out of scope. Singapore Peppol Guide, published by IMDA at peppolguide.sg, for the document types Access Points and InvoiceNow-Ready Solution Providers are required to support, including Invoice and Credit Note, Invoice Response, the Order profiles (Order Only, Ordering, Advanced Ordering and Order Agreement) and Order Balance. Three-way matching, PO amendment practice and blanket purchase orders are described as they are practised in standard accounts payable procedure rather than as legal requirements. This article is general information, not tax or legal advice. Confirm your own position with IRAS or a qualified adviser.