Table of contents

Manual · Page 19 · 16 min

Chapter 17 | Delivery, Service Performance and Proof of Execution

Chapter 17 | Delivery, Service Performance and Proof of Execution - online reading page from the From Sales to Cash handbook, dedicated to the Quote-to-Cash cycle and Credit Management.

A sale does not automatically become payable because it has been signed.

In many activities, the customer will only pay if the company can demonstrate that it has delivered, performed or achieved what was planned. Cash therefore also depends on Operations.

This point is essential. Invoicing, reminders and collections are often discussed as if payment depended only on Finance. In reality, payment also depends on the quality of operational execution and the ability to prove it.

A product delivered without proof of delivery can be disputed.

A service performed without validation can be blocked.

A project milestone reached but not documented may not be invoiceable.

An intervention carried out without a signed report may be difficult to defend.

An invoice may be correct in amount, but weak because it is not supported by sufficient evidence.

In the Quote-to-Cash cycle, proof of execution is therefore a central link. It connects what was sold, what was done and what can be invoiced.

Cash Depends on Execution

The customer pays because it recognizes an obligation.

This obligation may come from a delivered product, a service rendered, a validated milestone, an executed contract, an acceptance issued or an accepted document.

If execution is clear, recognized and documented, payment becomes easier to obtain.

If execution is uncertain, disputed or poorly evidenced, the invoice becomes fragile.

This means that Operations has a direct impact on cash. The teams that deliver, install, intervene, produce, perform or manage projects do not only contribute to customer satisfaction. They also contribute to the company’s ability to collect.

An operation that is well executed but poorly documented can create a financial problem.

Operational reality must therefore be turned into usable evidence.

Delivery Is Not Always Enough

In a sale of goods, it may be tempting to think that delivery is enough.

The product has left. The customer has received it. The company invoices. The customer pays.

In practice, things are sometimes less simple.

The customer may dispute the quantity received. It may say that delivery arrived late. It may report a missing, damaged or non-compliant product. It may request proof of receipt. It may refuse to pay because the delivery note was not signed or because delivery was made to another site.

In some environments, the customer’s Accounts Payable department does not pay on the basis of a simple invoice. It requires a match between order, receipt and invoice. This is often called a three-way match: purchase order, receipt, invoice.

If receipt is not recorded or proven, the invoice remains blocked.

The company may have physically delivered. But if it cannot prove delivery in the expected format, cash may remain tied up.

The Delivery Note: Simple but Decisive Evidence

The delivery note is one of the most important documents in product sales.

It confirms that the goods were handed over or received. It may mention references, quantities, date, location, carrier, identity of the receiver and sometimes reservations.

A signed delivery note answers a simple question: did the customer receive what was delivered?

Without this document, the company may find itself in difficulty if the customer disputes.

The delivery note must therefore be readable, complete, linked to the right order and quickly accessible. It must not remain in an isolated logistics file, impossible to find at collection stage.

In many companies, the problem is not the complete absence of evidence. The evidence exists somewhere, but it is difficult to retrieve. It may be with a carrier, in a warehouse, in an email, in a separate system or with a person who is absent.

To collect quickly, evidence must be available.

Evidence that cannot be found when a dispute arises is almost as weak as evidence that does not exist.

Customer Acceptance: The Moment the Customer Recognizes Delivery

Acceptance is the moment when the customer recognizes that it has received the good or service.

It may be informal in some activities: a signature on a document, an email confirmation, a validation in a portal. It may be very formal in others: acceptance report, receipt certificate, quality validation, technical acceptance, provisional or final acceptance.

Acceptance has a direct impact on cash when it triggers invoicing or payment.

If the contract provides for invoicing upon acceptance, the company will not be able to invoice solidly until that acceptance is obtained.

If the customer delays acceptance, cash is delayed.

That is why acceptance must be anticipated from the order and execution stages. The company must know who must validate, according to which criteria, within which timeframe, with which document and through which channel.

Unclear acceptance creates a risk of blockage.

Clear acceptance accelerates the transformation of execution into a payable invoice.

The Acceptance Report

In projects, installations, works or complex services, the acceptance report is often an essential document.

It formalizes the customer’s acceptance of what has been delivered or performed.

It may be provisional or final. It may include reservations. It may trigger an invoice, a warranty, a remaining balance to be paid or the transfer of certain responsibilities.

A well-drafted acceptance report secures the receivable.

It indicates that the customer recognizes execution, even if some reservations sometimes remain to be addressed.

Conversely, the absence of an acceptance report may weaken the invoice if the customer disputes progress or compliance.

The acceptance report must therefore be integrated into operational project management. It must not be discovered when Finance asks why the invoice cannot be issued.

In milestone-based activities, obtaining the acceptance report is sometimes as important as technically performing the work.

Without formal acceptance, the company may have produced value without being able to convert it into cash.

Service Performed

In many services, the customer pays after recognition of the service performed.

Service performed means that the customer recognizes that the service has been carried out in accordance with what was planned.

This validation may take several forms: signature of a report, validation of a deliverable, confirmation by a manager, approval in a tool, acceptance of a timesheet, receipt of an intervention report.

Service performed is very important in consulting, maintenance, technical interventions, recurring services, IT projects, advisory services, training or support.

If the service performed is not validated, the invoice may be blocked.

The customer may say: “The service may have been performed, but it has not yet been validated in our system.”

For the supplier, this sentence may be frustrating. But if the rule was known, it had to be planned.

Recognition of the service performed is therefore both an operational and financial step.

It must be followed with the same rigor as a physical delivery.

The Intervention Report

In maintenance, repair, installation or on-site service activities, the intervention report is often the main evidence.

It describes what was done, when, where, by whom, for which customer, on which equipment, with which parts, for how long and with what result.

When signed by the customer, it becomes very useful evidence to invoice and defend the receivable.

Without an intervention report, the customer may dispute the duration, the nature of the intervention, the technician’s presence, the parts used or the billable nature of the operation.

The report must therefore be produced quickly, correctly completed and linked to the order or contract.

An incomplete report can create discussions. A report sent late can delay validation. An unsigned report can be disputed.

Here again, the issue is not only operational. It is financial.

Each properly prepared intervention report reduces dispute risk and accelerates collection.

Project Milestones

In long projects, invoicing is often organized by milestones.

A milestone may correspond to a completed phase, a delivered item, an installation, a test performed, a golive, delivered training, customer validation or a level of progress.

The milestone avoids waiting for the full end of the project before invoicing. It structures cash over time.

But a milestone must be evidenced.

If the contract states “invoicing upon validation of milestone 2”, the company must know what proves this validation. Is it an email? An acceptance report? A signature? A report? The absence of reservations after a given period? Validation in a tool?

A milestone without clear evidence can become a point of tension.

The supplier considers that the milestone has been reached. The customer considers that it has not yet been reached. The invoice is blocked. The project continues, but cash does not follow.

Good milestone management therefore requires collaboration between Operations, the project manager, Sales Administration, Billing and Finance.

A milestone reached but not documented is unsecured potential cash.

Documentary Evidence

Proof of execution can take many forms.

Signed delivery note.

Acceptance report.

Intervention report.

Validated timesheet.

Confirmation email.

Certificate of conformity.

Photo of delivery or installation.

Acknowledgment of receipt.

Portal validation.

Test report.

Closed ticket.

Training report.

Consumption statement.

Usage data.

Quality document.

What matters is not only the type of evidence. It is its acceptability to the customer and its ability to support the invoice.

Useful evidence must be linked to the right order, the right customer, the right site, the right date, the right amount or the right milestone.

Generic or imprecise evidence may not be enough.

Documentary evidence must therefore be considered as part of the invoicing file.

It must make it possible to answer quickly if the customer asks: “Why should I pay this invoice?”

Without Evidence, the Invoice Becomes Weak

An invoice may be formally correct and yet operationally weak.

It may contain the right amount, the right VAT, the right address and the right terms. But if it is not supported by proof of execution, it remains vulnerable.

The customer may dispute delivery, progress, quality, quantity, date, compliance or validation.

In that case, Collections is in difficulty. It can chase, but the customer will respond that it is waiting for evidence, a document or internal validation.

The invoice then becomes a blocked receivable.

This blockage is not always non-payment in the strict sense. It is not necessarily a definitive refusal to pay. It is a temporary inability to obtain payment because the file is not strong enough.

Cash remains tied up until the evidence is provided or the dispute is resolved.

Proof of execution is therefore a condition of invoice strength.

Evidence Must Be Planned Before Execution

The company should not wait for a dispute to ask what evidence would have been necessary.

Evidence must be planned before execution.

From the order stage, the company must know what will be required to invoice and collect: signature of the delivery note, validation of the service performed, intervention report, acceptance report, certificate, receipt in the customer portal.

Operations must know these requirements.

If the technician knows that a signed report is mandatory to invoice, they will have it signed on site. If the project manager knows that an acceptance report is required for the milestone, they will organize it. If Logistics knows that the customer requires a named delivery note, it will prepare it.

Conversely, if evidence requirements are not communicated, teams may execute correctly but forget the document that will allow collection.

Evidence must not be an after-the-fact search.

It must be part of execution.

The Role of Operations in Cash

Operations directly contributes to cash quality.

It delivers, performs, installs, maintains, produces, supports, validates and documents.

It is often best placed to obtain evidence at the right time, because it is close to operational reality and to the customer.

A delivery driver can obtain a signature.

A technician can have their report validated.

A project manager can obtain an acceptance report.

A consultant can have a timesheet approved.

A service manager can confirm that a ticket is closed.

These actions sometimes seem administrative. In reality, they are financial.

Without them, the invoice may be issued but difficult to defend.

Cash is therefore not only Finance’s responsibility. It is a collective responsibility that begins with execution quality.

The Link Between Evidence and Dispute

Many disputes are in fact evidence disputes.

The customer does not always say: “You did nothing.”

It may say: “I do not have proof that it was done,” “it has not been validated,” “delivery is not recorded,” “the report is not signed,” “the milestone is not accepted,” “the service performed is not confirmed.”

In these situations, the discussion is less about the reality of execution than about its recognition.

Evidence reduces this grey area.

It turns a statement into a verifiable element.

Without evidence, the company depends on memories, scattered emails, commercial discussions or internal searches. With evidence, it can defend the invoice more quickly.

Good evidence does not remove all disputes. But it accelerates their resolution.

Reservations: Delivering with Partial Disagreement

Sometimes the customer accepts a delivery or service with reservations.

This means that it recognizes part of the execution, but points out items to correct or complete.

Reservations must be handled carefully.

They must be precise, dated, documented and monitored. The company must know whether they block the whole invoice, only part of it, or whether they do not prevent the main payment.

Acceptance with reservations may be preferable to no acceptance at all, because it recognizes at least part of the work performed. But if reservations are vague or not handled, they can block cash for a long time.

The contract or quote should ideally specify the effect of reservations on invoicing.

Not all reservations should prevent all payment. A minor reservation should not necessarily block 100% of a large invoice, unless the contract provides for it.

Managing reservations is therefore an operational, legal and financial topic.

Evidence and Invoicing Timing

The invoice must be issued at the right time.

If it is issued before the necessary evidence is available, it may be rejected.

If it is issued too late when the evidence already exists, the company unnecessarily delays its cash.

The right timing therefore depends on the link between execution, evidence and invoicing.

In a sale of goods, the invoice may be triggered upon shipment, delivery or acceptance, depending on the agreed rules.

In a service, it may be triggered upon performance, validation, milestone, period-end or delivery of a deliverable.

In a project, it may depend on an acceptance report or stage validation.

The challenge is not to leave an unnecessary gap between evidence and invoice.

As soon as execution is evidenced and invoicing conditions are met, the invoice must be issued quickly.

Every day between available evidence and invoice issuance is a day of lost cash.

Evidence Must Be Accessible to Finance

Evidence is useful only if the teams that need it can retrieve it.

In some companies, evidence exists but is scattered.

Delivery notes are with the carrier.

Intervention reports are in a business tool.

Acceptance reports are with project managers.

Validations are in emails.

Timesheets are in another system.

Quality documents are kept by Operations.

When the customer disputes, Collections must hunt for evidence. This takes time. The customer waits. The invoice ages.

To avoid this, access to evidence must be organized.

Key documents must be linked to the order, invoice, project or customer account. They must be available to Sales Administration, Billing, Collections and Credit Management when necessary.

The circulation of evidence is as important as its existence.

Inaccessible evidence does not effectively protect cash.

Example: Delivery Completed, Payment Blocked

Imagine a company delivering equipment for 75,000 euros.

Delivery has taken place. The customer is already using the equipment. The invoice is issued with payment in 60 days.

At due date, payment does not arrive. Collections contacts the customer. The customer replies that the invoice is blocked because Accounts Payable does not have a signed delivery note.

Logistics states that the carrier delivered. Sales confirms that the customer received the equipment. But no one immediately finds the signed document.

The invoice remains open for several weeks.

The problem is not that the customer never received the equipment. The problem is that the company cannot quickly produce the expected evidence.

This situation illustrates a simple point: a delivery without accessible evidence can become a fragile receivable.

Example: Service Performed but Not Validated

Take a consulting service for 40,000 euros.

Consultants worked for two months. Meetings took place. Deliverables were sent. The invoice is issued at the end of the assignment.

The customer does not pay. It explains that the service performed has not been validated by the internal manager. That manager requests adjustments to a deliverable before approving the invoice.

The company considers that the work has been performed. The customer considers that validation is not complete.

The invoice remains blocked.

If the quote and order had included a clear validation procedure, with criteria, response deadline and written reservations, the blockage would have been easier to resolve.

In services, proof of execution is not limited to “we worked.” It must be recognized in the format expected by the customer.

Example: Milestone Reached but Not Invoiceable

A company carries out an IT project invoiceable in three milestones.

Milestone 2 corresponds to making a test environment available. Technically, the environment is ready. The supplier’s project team considers the milestone reached.

But the contract requires written customer validation. This validation was not formally requested. The customer project manager is absent. Procurement refuses the invoice until the validation is uploaded to the portal.

The invoice for milestone 2 is delayed by several weeks.

The project moves forward, but cash does not follow.

The problem is not only technical. It is documentary and contractual.

A project milestone must be managed as a cash event. It is not enough to reach it. It must be recognized.

Evidence Also Protects When the Relationship Deteriorates

As long as the customer relationship is good, evidence may seem secondary.

The customer recognizes the service, contacts trust one another, payments arrive. But if the relationship deteriorates, if contacts change or if the customer faces financial difficulties, evidence becomes essential.

A customer under pressure may try to delay payments. It may dispute more. It may request supporting documents that it did not request before. It may use documentary weaknesses to postpone a due date.

At these moments, the company must be able to defend its receivables.

Proof of execution then becomes protection.

It reduces dependence on the customer’s goodwill.

A relationship of trust is valuable, but it does not replace solid documentation.

The Role of Sales Administration and Billing

Sales Administration and Billing must make sure that invoicing conditions are met.

Before issuing an invoice, it may be necessary to check that delivery has been completed, that the delivery note is available, that the milestone has been validated, that the service performed has been recognized or that the required document is attached.

If the invoice is issued without these elements, it may be rejected.

But if Sales Administration waits too long without chasing Operations for the evidence, cash is delayed.

The role of Sales Administration is therefore to coordinate: request evidence, check its consistency, trigger invoicing as soon as possible and alert if a document blocks the process.

Billing must not be isolated. It must be connected to operational execution.

A strong invoice rests on strong evidence.

The Role of Collections

When payment is late, Collections must quickly distinguish between several situations.

The customer does not pay despite an accepted invoice.

The customer has not received the invoice.

The customer is waiting for internal validation.

The customer disputes the price.

The customer disputes delivery or service.

The customer requests evidence.

This qualification is essential.

If the problem is missing evidence, stronger chasing is not enough. The expected document must be provided.

Collections must therefore have access to evidence or know quickly who can provide it.

It must also record the cause of delay. If several customers block invoices because of missing delivery notes, reports or validations, this reveals an upstream process issue.

Collections is not only used to obtain payment. It also helps the company understand why cash is blocked.

Evidence as a Collective Discipline

Proof of execution must not depend only on individual goodwill.

It must be integrated into processes.

Teams must know which evidence is required depending on the types of sales. Systems must allow this evidence to be recorded. Responsibilities must be clear. Documents must be accessible. Exceptions must be monitored.

This discipline may seem administrative, but it protects margin and cash.

A company that performs many services without clear evidence takes a risk. A company that delivers without collecting receipt documents weakens its receivables. A company that invoices milestones without structured validation exposes itself to delays.

Evidence is a hygiene practice in the Quote-to-Cash cycle.

It turns execution into a right to payment.

Key Takeaways

Cash also depends on Operations.

In many activities, the customer will only pay if delivery, acceptance, service performed or the contractual milestone is recognized. It is therefore not enough to have sold, or even to have executed. The company must be able to prove execution.

Evidence can take several forms: delivery note, acceptance report, service validation, intervention report, project milestone, timesheet, certificate, documentary evidence or portal validation.

Without evidence, an invoice may be legally or operationally weak. It may be disputed, blocked or paid late.

Evidence must be planned before execution, obtained at the right time, linked to the order or invoice, and accessible to the teams that follow cash.

A well-negotiated and well-administered sale can still become a blocked receivable if execution is not recognized or if evidence is missing.

In the Quote-to-Cash cycle, delivery is not enough. The company must deliver, obtain recognition and document it.

This recognition makes the invoice stronger, and therefore allows cash to come in faster.