Why Customers Pay Late: On-Time Invoices, Logged Disputes

Why Customers Pay Late: On-Time Invoices, Logged Disputes

Customers often pay late because the invoice itself was late or got stuck, not because they do not want to pay. In practice, the payment term does not start running until a correct invoice reaches the person at the customer who is authorized to approve it. The fix has three steps. Issue the invoice on the day delivery is confirmed or on a fixed monthly date; the latest date under the VAT Implementing Regulations is the 15th of the month after the supply. Correct any error after issue with a credit or debit note that references the original invoice, by the 15th of the month after the event, never by deleting it. And log every objection with an owner, a reason and a date, so the undisputed part stays collectible.

From a confirmed delivery to an invoice that gets paid

In part four the invoice got a single source, the confirmed delivery, with the signed note attached to it. But a correct invoice can still sit unpaid for reasons that have nothing to do with its numbers. This part is about the distance between issuing the invoice and receiving the money, and three causes recur there, in good faith on both sides:

• The invoice goes out late. The goods were delivered or the service finished early in the month, and the invoice waited for month-end to go out with the others. If your terms count the payment period from the invoice date, every day the invoice waits is a day added to your wait, without the customer being one day late.
• The invoice reaches someone who cannot approve it. It goes to the contact your team deals with, or to a general mailbox nobody watches, or it arrives without the purchase order number the customer's accounts team requires. In part three the customer record started carrying the name of the person who receives and approves invoices; here that name becomes the only address the invoice is sent to.
• A dispute with no owner. The customer objects to one line in a call with the sales rep, the rep promises to look into it, and finance never hears about it. The whole invoice stays on hold at the customer, and collections calls asking for an amount the customer knows is in dispute.

Remember that your customer's accounts team checks your invoice before recording it, as we described from the buyer's side in Supplier Invoices: What to Check Before Claiming Input VAT. An invoice missing a required detail, or carrying their company name abbreviated rather than as it appears in their commercial register, stops there because their system works as it should, not because they are avoiding payment.

When must the tax invoice be issued? What the Regulations say

The Implementing Regulations of the VAT Law set clear limits on invoice timing for sales between businesses. These are the ones that matter most if you sell on credit:

• A tax invoice between businesses must be issued no later than the 15th day of the month following the month in which the supply took place (Article 53, paragraph 1(b)). A supply made on 3 October therefore has a latest invoice date of 15 November.
• A simplified invoice between businesses is an exception allowed only for supplies under 1,000 riyals (Article 53, paragraph 1(c)), so it cannot replace the tax invoice on your regular supplies to trade customers.
• The monthly summary invoice: you may issue one summary tax invoice to a single customer covering several separate supplies within a period of no more than one calendar month, provided it carries the details required by paragraph 5 of the same article, issued no later than the 15th of the following month (Article 53, paragraph 4). It suits a distributor delivering to the same customer several times a week, or a maintenance company visiting the same building more than once a month. It is best to keep each delivery note or completion sign-off linked to its own line on the summary, so the proof does not get lost inside the month's invoice.
• Service contracts with payments on set dates: where services are supplied on a continuing basis and the contract sets payments on specific dates, VAT is due on the earliest of the payment due date, the actual payment date or the invoice date, and at least once in every 12 consecutive months (Article 20, paragraph 1). Other continuous supplies are due at the earlier of the invoice or the payment, to the extent of that amount (Article 20, paragraph 2). This matters for a monthly maintenance contract or a corporate account at a hotel billed in instalments. For contracting, the Regulations do not name work billed through progress claims, so ask your tax adviser which paragraph applies to your contract.

But the latest date in the Regulations is a compliance limit, not an operating target. An invoice issued on the 15th of the following month is compliant, but if your payment term runs from its date, it has delayed your money by weeks. The simplest operating rule is one of two, chosen by the owner for each customer: an invoice issued the day delivery is confirmed, or a summary invoice on a fixed day each month, agreed with the customer and known to their accounts team. Either way, the system tracks every confirmed delivery not yet invoiced and shows its age, as we started in part four.

No deleting after issue: the credit note and the debit note

When a customer objects to an issued invoice, the quickest fix seems to be cancelling it and issuing a correct one in its place. Electronic invoices do not work that way. The Zakat, Tax and Customs Authority's detailed e-invoicing guideline lists editing or deleting an invoice after issue among the prohibited functions of an e-invoicing solution, and states that anyone who wants to cancel an invoice may do so only through a credit note linked to it, followed by a new invoice (sections 5.6 and 6.5). In the integration phase, the guideline says every tax invoice between businesses is cleared and stamped by the Authority before you share it with your customer, and that clearance covers the related credit and debit notes (section 6.4). What that phase means for the seller we covered in E-Invoicing in the Factory and Warehouse.

Article 54 of the Regulations sets out when each note is issued:

• A credit note when, after the invoice, one of the cases in Article 40, paragraph 1 occurs and the VAT shown on the invoice is more than the VAT due (Article 54, paragraph 1). The Article 40 cases are: cancellation or suspension of the supply in whole or in part, a material change in its nature that changes the tax, a change to its agreed value for any reason including an additional discount after the sale, or a return that the seller accepts.
• A debit note in the same cases when the VAT shown is less than the VAT due (Article 54, paragraph 2).
• Correcting data: if you find an error in your own details or the customer's details on the invoice, such as their company name or address, it is corrected with a debit or credit note as the case requires, and both of you keep the invoice and the note together (Article 54, paragraph 3).
• Referencing the original: the note carries the details required by Article 53 and clearly references the invoice or invoices it relates to (Article 54, paragraph 4). The guideline allows one note to reference several invoices by a range of their serial numbers (section 4.3).

Then the deadline, a paragraph that articles written before it was added do not mention: a sixth paragraph was added to Article 54 by a decision of the Authority's board on 19 November 2024, requiring the note to be issued no later than the 15th day of the month following the event that requires it. If the sales manager agrees a discount with the customer on 20 October to close a dispute, the credit note is due no later than 15 November. That deadline is missed when the agreement stays in a phone call that finance never heard about. Which tax period the note affects we covered in a return is not a cancelled sale, it is a credit note, and questions about your specific case belong with your tax adviser.

The dispute log: every objection gets an owner, a reason and a date

A dispute is not a failed sale; it is a normal part of selling on credit. The problem is when it lives in a call or a WhatsApp chat with the sales rep, where neither the person who issues notes nor the person who follows up collections can see it. The phone and WhatsApp are good tools for receiving an objection, but they are not a record of it. The fix is one log that every objection enters the moment it arrives, whatever channel it came through, with each entry carrying:

• The invoice, the line and the disputed amount, not the whole invoice.
• The reason, from a fixed list: price, quantity, quality, missing document, or wrong recipient. A fixed list is what makes the log countable two months later: how many disputes were about price, and how many were a missing document?
• The owner, by reason: a price dispute goes to whoever approved the discount in part two, quantity to operations, who hold the delivery note, quality to whoever decides on a replacement or a discount, and a missing document or wrong recipient to finance, who also correct the customer record so the error does not repeat.
• A target date for resolution, set by the company for each reason; a dispute that passes it becomes visible to the owner's manager.
• The outcome: an objection answered with evidence such as the signed delivery note, a credit or debit note issued on time, or a missing document completed and resent to the right person.

Everyone sees the log: the sales rep knows their customer's objection reached the person who will resolve it, finance knows which note is waiting to be issued, and collections knows which amount not to chase right now because it is being resolved. Nobody calls a customer to demand an amount they disputed a week ago and are still waiting for us to answer.

The undisputed part stays collectible

When a dispute is logged at the invoice level, the whole invoice stops because of one line. An invoice of 12 lines where the customer objected to one because an item arrived damaged waits in full until that line is settled. When the dispute is logged at the line level, you can ask the customer to approve the other eleven lines and pay them on time, while only the disputed line stays in the log until it is resolved. These numbers are an example, but the principle holds: the undisputed amount is treated like any normal receivable, and the disputed amount has an owner and a date.

Will the customer accept paying part of an invoice? That depends on how their accounts team works, and some teams only pay a complete invoice. Even then, a dispute with a defined amount, reason and owner is resolved faster, because both sides are talking about a specific line rather than a whole invoice. When the dispute ends in a discount or a return, the credit note is issued linked to the original invoice, the invoice closes at its correct amount, and your statement matches your customer's.

The Origami view

When we build the invoicing and disputes workflow for a company, we start from its late invoices: how long passed between delivery and issue, who they were sent to, where the objection was recorded if it was recorded at all, who decided on the discount, and when the note was issued. Those answers map the current workflow as it really is, before we draw a single screen.

Then we turn them into one connected workflow: an invoice built from the confirmed delivery and issued on the schedule the owner sets for each customer, sent to the authorized approver from the customer record; a line-level dispute log with an owner and a date; and a credit or debit note generated from the dispute's outcome with its deadline tracked, all connected to your accounting system and e-invoicing. This is part of the custom systems we build through our services.

An exercise for this week: why were your last twenty invoices paid late?

Before any system, you need to know why your customers actually pay late. This is an exercise for the finance manager and the sales manager in a single session:

• Pick the last twenty invoices that passed their due date.
• Record three dates for each: confirmed delivery, invoice issue, and arrival with the authorized person at the customer, if you know it.
• Ask whether it reached the right person with what their accounts team requires, such as the purchase order number and the delivery note.
• If there was an objection, classify it under one of the five reasons: price, quantity, quality, missing document, or wrong recipient. Record who is following it up now, if anyone is.
• If a dispute ended in a discount or a return, check whether the note was issued, and when, against the 15th of the month after the date of the agreement.

The number of late invoices whose delay started on our side rather than the customer's, and the number of disputes nobody knows who is following, are the baseline for this part.

In the next part

The invoice now goes out on time and reaches the person who approves it, and every dispute has an owner and a date. The next part is about the follow-up after that: receivables aging by due date in buckets the owner chooses, a collection calendar for every invoice with a reminder before the due date, on it and after it, a known escalation path, a monthly statement sent to the customer to confirm the balance, and then what the law says when a customer still does not pay.

Sources

• Zakat, Tax and Customs Authority: Implementing Regulations of the VAT Law (official Arabic text) — Article 20, paragraphs 1 and 2 (when VAT is due on continuing and continuous supplies), Article 40, paragraph 1 (cases that change the value of a supply), Article 53, paragraph 1(b) and (c) (latest date for a tax invoice between businesses, and the simplified invoice under 1,000 riyals) and paragraph 4 (the summary tax invoice), Article 54, paragraphs 1 to 4 (credit and debit notes, correcting data, and referencing the original invoice) and paragraph 6 (deadline for issuing the note, added by the Authority's board on 19 November 2024).
• Zakat, Tax and Customs Authority: Detailed E-Invoicing Guideline (Arabic) — section 4.3 (credit and debit notes and referencing the original invoices), sections 5.6 and 6.5 (prohibited functions, including editing or deleting an invoice after issue), and section 6.4 (clearance of invoices and notes before they are shared with the buyer).