Due Upon Receipt on an Invoice

Due upon receipt means an invoice is payable immediately, on the day the customer receives it. There is no credit period and no grace period built into the term, unlike net 30 or net 15, which give the buyer a defined number of days. In practice most US businesses treat a due upon receipt invoice as payable within one to three business days, because the term sets an expectation rather than a precise deadline.

Last updated July 2026.

It is the bluntest payment term in common use, and the one most likely to be ignored. Sellers like it because it asks for money now. Buyers dislike it because it collides with approval workflows that were never designed to move in a day. This guide covers what the term actually obliges a customer to do, when to use it and when it backfires, how to word it on an invoice, and what happens when it is not paid.

What does due upon receipt mean on an invoice?

It means payment is expected as soon as the invoice arrives. The obligation starts the moment the customer receives the document, not 30 days later, and not when they get around to opening it. The seller is telling the buyer that no trade credit is being extended for this transaction.

The term appears on invoices as "Due upon receipt", "Due on receipt", "Payable upon receipt", or occasionally just "Immediate". They all mean the same thing. It is functionally the opposite of net 30 payment terms, where the buyer has a defined 30 calendar days from the invoice date before the balance becomes overdue.

How many days do you actually have to pay a due upon receipt invoice?

Legally, on the day you receive it. Practically, most vendors do not treat an invoice as late until a few business days have passed, because they know an ACH transfer takes time to initiate and an approval takes time to obtain. Two to three business days is the working convention in US B2B trade.

The ambiguity is the problem. Nowhere in the term is a number, so there is no shared definition of "late". A vendor might follow up on day two; a buyer might reasonably believe they have a week. If the timing matters to you as a seller, put a date on the invoice. "Due upon receipt. Payment expected by January 12, 2026" removes the argument entirely and is far easier to enforce.

Due upon receipt vs net 30: which should you use?

The honest trade-off: due upon receipt maximizes the speed of a single payment and minimizes your leverage in a relationship. A customer who processes hundreds of invoices a month will drop yours into the same weekly payment run as everything else regardless of what you printed on it. A homeowner paying a plumber will pay it on the spot. Match the term to who is actually paying.

When should you use due upon receipt?

The term works when the buyer can pay without a process. That usually means one of these situations:

• One-off service calls and repairs. The technician is standing in front of the customer. Payment now is the natural moment.
• Small amounts. An invoice below a few hundred dollars is often below the buyer's approval threshold, so a single person can pay it without routing it anywhere.
• New customers with no credit history. Extending net 30 to an account you have never worked with is a lending decision. Due upon receipt for the first few jobs is a reasonable way to build a payment record first.
• Customers with a history of paying late. Moving an account from net 30 to due upon receipt is a legitimate response to repeated late payment, provided the contract allows it.
• Final invoices before delivery of something withheld. Final artwork, final drawings, or release of a completed build.

When does due upon receipt backfire?

Against a business with a real accounts payable function, it usually does nothing at all. The invoice arrives, it gets captured, coded, matched, approved, and scheduled into the next payment run. That cycle takes days at best and weeks at worst, and no printed phrase shortens it. You have not been paid faster; you have simply written an invoice that is overdue the moment it is entered.

That creates a second, subtler problem. Every invoice with an impossible term shows up as delinquent in the buyer's aging report, which teaches their AP team to stop treating your invoices as urgent at all. Terms only work when they are credible. Asking for the impossible is a fast way to be ignored on the day it actually matters.

It also removes a negotiating card. Net 15 asks for something a mid-sized buyer can genuinely deliver and gives you a specific date to enforce. Due upon receipt asks for something they cannot deliver and gives you no date at all.

How do you write due upon receipt on an invoice?

Put it in the payment terms field, and then remove the ambiguity around it. A workable terms block looks like this:

Payment terms: Due upon receipt. Payment is expected within 2 business days of the invoice date, January 10, 2026. We accept ACH and check. A late fee of 1.5% per month applies to balances unpaid after 30 days, as set out in section 6 of the signed agreement.

Four things are doing work there. The term itself, an actual date so nobody counts days, the payment methods so nobody has an excuse, and a late fee that references a contract the customer already agreed to. A late fee that first appears on the invoice, with no prior agreement, is easy to challenge and usually written off. Interest rates chargeable on overdue commercial balances are capped by state law in the US and the caps differ, so set the rate against your own state rather than copying a figure from a template. The full set of clauses that belong in a terms block is covered on our invoice payment terms page.

What if a due upon receipt invoice is not paid?

Follow up quickly, because the whole point of the term is speed and a silent week destroys it. A workable sequence for a US small business:

1. Day 3. A short, neutral email confirming the invoice was received and asking when payment will be issued. Most non-payments at this stage are administrative, not disputes.
2. Day 7. Call whoever actually approves payments, not the person who requested the work. They are frequently different people and only one of them can release money.
3. Day 14. A written reminder referencing the contract clause on late payment, with the balance and any accrued interest stated.
4. Day 30. Consider pausing further work, and confirm in writing that you are doing so and why.

If you find yourself running this sequence often, the term is not the problem. Businesses that spend real hours chasing money that is already owed to them almost always have a collections process problem rather than a payment terms problem, and switching everyone to net 15 with a firm due date collects faster than due upon receipt plus hope.

Does due upon receipt mean the same as COD?

No. Cash on delivery (COD) means payment happens when the goods physically arrive, and the goods are typically not handed over until it does. Due upon receipt refers to receipt of the invoice, not receipt of the goods, and nothing is withheld. COD is a delivery condition enforced by the carrier or the driver. Due upon receipt is a payment expectation printed on a document.

They also differ in what they protect against. COD protects the seller from ever parting with goods unpaid. Due upon receipt protects nothing; it simply asks. Cash in advance (CIA) and payment in advance (PIA) go further still, requiring the money before anything ships at all.

How due upon receipt invoices are handled in accounts payable

From the buyer's side, a due upon receipt invoice needs the same treatment as any other, only faster. It has to be captured, coded to the right general ledger account, matched if a purchase order exists, and approved. What changes is that it should skip the queue rather than wait for the weekly batch.

That only works if the term is visible as data rather than as text buried in a PDF. If the payment term and the due date have to be read off the document by a person and typed into the ledger, an invoice that is due today looks identical to one due in six weeks until somebody opens it. Teams that pull the term, the invoice date, and the due date off the document automatically can sort the queue by urgency on day one, which is the practical fix. That is exactly what invoice data capture software does: upload the PDF, scan, or photo and the payment terms, dates, vendor, tax, totals, and every line item come back as structured data ready for the ledger.

The rest of the AP cycle then behaves properly. The aging report buckets the invoice correctly instead of parking it in "current" for a month, and the invoice reaches the approver while the term still means something.

Common questions

Is due upon receipt legally enforceable? The obligation to pay is enforceable because a valid invoice for delivered goods or services creates a debt. The specific timing is weaker: "upon receipt" is not a date, so proving exactly when a payment became late is harder than under net 30. Stating a date alongside the term solves this.

Can I charge interest from day one? Only if the customer agreed to that in advance and the rate is lawful in your state. Most contracts start interest after a defined period, commonly 30 days, precisely because "immediately" is difficult to defend.

Does due upon receipt speed up payment? For consumers and micro-businesses, yes, noticeably. For companies with an AP department, the evidence in your own aging report will tell you: compare the average days to pay on your due upon receipt invoices against your net 30 invoices for the same customers. Many sellers find there is no difference at all.

What should I use instead? Net 15 with a printed due date is the most common upgrade. It is short enough to protect cash flow, long enough for a buyer's approval cycle to complete, and specific enough to enforce. Pair it with an early payment discount if you want to genuinely accelerate cash rather than just ask harder.

The short version

Due upon receipt tells the customer that no credit is being extended and payment is expected now. It is the right term for one-off work, small amounts, unproven accounts, and anyone who can pay without an approval chain. It is the wrong term for a mid-sized business with an AP department, where it produces an invoice that is overdue on arrival and treated accordingly. If speed is what you need, name a date, state the payment method, and reference a late fee the customer already agreed to. Every other term you might use instead is defined, with worked due dates, on our invoice payment terms page, and the broader vocabulary is in the accounts payable glossary.