In the Quote-to-Cash cycle, many delays do not come from a lack of goodwill.
They come from a very simple question that has not been clarified: who does what?
Who opens the customer account?
Who validates payment terms?
Who accepts a commercial exception?
Who releases an order?
Who corrects an invoice?
Who handles a dispute?
Who contacts the customer?
Who escalates?
Who decides on a credit note?
Who follows payment promises?
When these responsibilities are unclear, files slow down.
Each function thinks the topic belongs to another. Information circulates poorly. Decisions remain pending.
Invoices age. Customers receive contradictory messages. Collections chases without being able to resolve.
Sales requests an order release without knowing who can approve it. Finance waits for operational elements.
Operations corrects a problem without informing Accounting. Credit notes remain under approval.
Cash then gets blocked in grey areas.
Clarifying roles is therefore a very practical governance approach.
It is not about creating bureaucracy. It is about making the cycle smoother, faster and more accountable.
A mature organization knows how to distinguish three responsibilities: detecting, deciding and resolving.
Detecting, Deciding, Resolving
Every cash topic should be analyzed through three questions.
Who detects the problem?
Who decides the position to take?
Who concretely resolves the blockage?
These three roles can be carried by the same function, but this is not always the case.
Collections can detect that an invoice is blocked because of a quality dispute, but Operations must resolve the technical problem, and Sales management or Finance may have to decide on a commercial gesture.
Credit Management can detect a limit overrun, but the release decision may depend on an authorization level, and resolution may require partial payment obtained by Sales or Collections.
Accounting can detect an unmatched payment, but the customer must provide a remittance advice, and Collections may be best placed to obtain it.
Confusing these roles creates frustration.
The person who detects does not always have the power to decide.
The person who decides does not always perform the action.
The person who resolves does not always see the cash impact.
Governance is used to connect these roles.
Why Grey Areas Are Expensive
A grey area is a situation where nobody clearly knows who is responsible for the next action or decision.
It may seem harmless.
A credit note is waiting for approval.
A dispute is waiting for operational feedback.
An order is waiting for release.
An invoice is waiting for correction.
A payment promise is waiting for follow-up.
Customer data is waiting for an update.
But each wait consumes cash.
Time passes. The invoice ages. The customer reorganizes around the delay. The forecast becomes less reliable. Collections repeats the same messages. The relationship becomes tense.
Grey areas also create dilution of responsibility.
Everyone can say: “it is not me.”
Sales waits for Finance.
Finance waits for Operations.
Operations waits for the customer.
Collections waits for everyone.
Meanwhile, the money remains outside.
Clarifying roles makes it possible to turn a vague wait into a concrete action.
Who Opens the Customer Account?
Customer account opening is often the first act of governance.
It determines with whom the company contracts, to which entity it sells, which terms are applied, which billing address is used, which contacts must be entered, which invoicing channel will be used and which credit limit may be granted.
Responsibility must be clear.
Who requests the opening?
Often, Sales or Sales Administration.
Who collects the information?
Depending on the organization, Sales, Sales Administration, the customer itself or a master data team.
Who checks the data?
Sales Administration, Finance, Credit Management, Accounting or a dedicated team.
Who validates the risk?
Credit Management, sometimes with Finance or management depending on the amounts.
Who actually creates the account in the system?
The master data team, Sales Administration or Accounting depending on the organization.
The objective is to avoid creating a customer quickly but poorly.
An incomplete account opening can produce many difficulties: wrong entity, duplicate, wrong address, incorrect terms, missing limit, obsolete contact, invoicing channel not entered.
The customer account is a cash infrastructure.
It must have an owner for creation and an owner for maintenance.
Who Validates Payment Terms?
Payment terms are not a simple commercial detail.
They determine how long the company finances its customer.
They influence WCR, DSO, risk, real margin and Treasury.
The company must therefore know who can validate them.
Sales can negotiate.
But can Sales alone grant 60, 90 or 120 days?
From which threshold is Finance approval required?
Must exceptional terms go through Credit Management?
Must terms different from the standard be documented?
Who checks that they are correctly set in the system?
Clear governance can provide simple rules.
Standard terms are applied automatically.
Terms beyond a certain duration require approval from Credit Management or financial management.
Highly exceptional terms require commercial and financial arbitration.
Every exception must be documented and visible to Sales Administration and Billing.
Without rules, payment terms can lengthen through accumulated exceptions.
And the company later discovers that its cash is tied up in terms it never truly arbitrated.
Who Accepts the Exception?
Exceptions are unavoidable in commercial life.
A specific payment term.
A special discount.
A delivery before receipt of the PO.
Deferred billing.
A temporary limit.
A commercial credit note.
A payment plan.
An accepted deduction.
The problem is not the existence of the exception.
The problem is the exception that is not approved, not documented or not followed.
The company must therefore define who can accept what.
A small discount may be approved by the salesperson within an authorized margin.
A larger discount may require a sales manager.
An exceptional payment term may require Credit Management.
A delivery despite a limit overrun may require Finance approval.
A significant credit note may require an approval workflow.
A contractual exception may require Legal.
The exception must have an owner, a justification, a duration, a scope and a trace.
Otherwise, it becomes a source of dispute.
The practical rule is simple: an accepted exception must be visible to those who will have to execute it, invoice it, chase it or arbitrate it.
Who Releases an Order?
Order blocking is a sensitive decision.
It can protect the company against worsening risk. But it can also create commercial tension or delay an important sale.
The company must therefore clarify who can block and who can release.
Blocking can be automatic: limit exceeded, overdue invoices beyond a threshold, suspended account, missing information, high risk.
But release must not be improvised.
Who analyzes the reason?
Often Credit Management or Sales Administration depending on the cause.
Who checks recent payments?
Accounts Receivable Accounting or cash application.
Who qualifies overdue invoices?
Collections.
Who brings the commercial context?
Sales.
Who decides the release?
Credit Management in ordinary cases, then Finance, Sales management or a committee for sensitive cases.
The release must be conditional if necessary: partial payment, proof of transfer, down payment, temporary limit, partial delivery, validation of a plan, resolution of a dispute.
An order must not be released simply because commercial pressure is strong.
It must be released because an assumed decision has been made.
Who Corrects an Invoice?
An incorrect invoice must be corrected quickly.
But here too, roles must be clear.
Who detects the error?
The customer, Collections, Billing, Sales Administration or Sales.
Who confirms that the error is real?
It depends on the cause: price, quantity, VAT, entity, PO, currency, payment terms, supporting document.
Who decides the correction?
Billing should not always correct alone if the correction has a commercial, tax, contractual or financial impact.
Who issues the credit note or the new invoice?
Billing or Accounting depending on the organization.
Who informs the customer?
Collections, Billing, Sales Administration or Sales depending on the relationship.
Who checks that the corrected invoice is accepted?
Collections or the team in charge of the portal.
An invoice error not corrected blocks cash.
But an uncontrolled correction can also create risk: unjustified credit note, margin loss, tax inconsistency, poor contractual trace.
The company must therefore correct quickly, but with a clear workflow.
Who Handles a Dispute?
A dispute must never remain in a vague category.
It must have a cause, an amount, an owner, an expected decision and a target date.
But who handles the dispute?
It depends on its nature.
A price dispute often concerns Sales, Sales Administration and Billing.
A quantity dispute concerns Sales Administration, Logistics or Operations.
A quality dispute concerns Operations, Quality or the technical service.
A delivery dispute concerns Logistics, Transport, Sales Administration or Operations.
A service dispute concerns the project manager or the operational team.
A contract dispute concerns Legal, with Sales and Finance.
A penalty dispute concerns Operations, Legal, Finance and sometimes Sales.
A credit note dispute concerns the function that must validate the correction.
Collections often detects the dispute, but it cannot always resolve it.
However, it must remain the driver of the blocked cash: follow the target date, chase the owner, request payment of the undisputed amount, update the status, escalate if the dispute ages.
The dispute owner resolves the cause.
Collections ensures that cash is not forgotten.
Who Contacts the Customer?
The customer relationship may involve several contacts.
The salesperson speaks with the buyer or decision-maker.
Sales Administration speaks with administrative teams.
Collections speaks with Accounts Payable.
Operations speaks with users or project managers.
Legal may write in formal cases.
The question is not to choose one single contact for everything.
The question is to avoid contradictory messages.
Who contacts the customer to request payment?
Generally Collections.
Who contacts the customer to resolve a technical dispute?
Often Operations or the project manager, with information shared with Collections.
Who negotiates a payment plan?
Collections or Credit Management, sometimes with Sales.
Who announces a block?
It may be Credit Management, Collections or Sales depending on the context, but the message must be aligned.
Who discusses a discount or a commercial credit note?
Sales, but with approval according to internal rules.
Good governance does not eliminate multiple contacts.
It coordinates them.
The customer must hear a coherent position.
Who Escalates?
Escalation occurs when a topic is not resolved at the normal level.
It can be internal or external.
Internal: to a sales manager, operations management, Finance, Legal, Credit Management, general management.
External: to a customer accounting manager, buyer, CFO, project sponsor, director.
Escalation criteria must be defined.
High amount.
Significant age.
Broken promise.
Dispute with no owner.
Blocked credit note.
Invoice rejected several times.
Strategic customer.
Limit exceeded.
High financial risk.
File close to litigation.
Escalation must also be prepared.
Who prepares the file?
Who carries the message?
What decision is requested?
What timeframe is expected?
Escalation must not be a vague alarm.
It must be a decision mechanism.
Good escalation saves time because it brings the file to the right level with the right information.
Who Decides on a Credit Note?
The credit note is a sensitive topic because it directly affects margin, revenue, the customer relationship, tax and sometimes the contract.
It must not be issued only to make a difficult invoice disappear.
A credit note can be justified: price error, return, quantity not delivered, approved discount, accepted penalty, partial cancellation, approved commercial gesture, tax correction.
But it must be decided.
Who requests the credit note?
The customer, Sales, Collections, Sales Administration, Operations or Billing.
Who validates the reason?
The function concerned by the cause.
Who validates the amount?
Depending on thresholds: Sales, Finance, manager, management.
Who checks the tax or contractual impact?
Billing, Accounting or Legal depending on the case.
Who issues the credit note?
Billing or Accounting.
Who applies it to the right account?
Accounts Receivable Accounting.
Who chases the remaining balance?
Collections.
An expected but undecided credit note blocks cash.
A decided but unissued credit note blocks cash.
An issued but unmatched credit note blocks account readability.
Credit note governance must therefore cover the whole chain, from request to application.
Who Follows Payment Promises?
A payment promise must be followed.
Otherwise, it has only limited value.
Who obtains the promise?
Most often Collections, sometimes Sales or Credit Management.
Who records it?
The person who obtains it, in a shared tool if possible.
What must the record contain?
Amount, invoices concerned, promised date, contact person, payment method, possible conditions, level of confidence.
Who checks that payment arrives?
Collections, with Accounts Receivable Accounting or cash application.
Who acts if the promise is not kept?
Collections, with escalation to Credit Management, Sales or Finance depending on amount and risk.
A broken promise must be visible.
It changes the customer’s behavioral profile.
It may justify a block, a limit reduction, a down payment request, a formalized plan or an escalation.
Following promises is not only about forecasting cash.
It is about measuring customer reliability.
Who Updates Customer Data?
Customer data lives over time.
Billing address.
Contacts.
Invoice receipt email.
Portal.
Legal entity.
VAT number.
Payment terms.
Customer group.
Bank details.
Payment channel.
Mandatory references.
The question is: who updates this information when something changes?
If everyone can request a change but nobody is responsible for it, data deteriorates.
A process must therefore be defined.
Who can request a change?
Who checks legitimacy?
Who validates sensitive data?
Who updates the master system?
Who informs the functions concerned?
Some data can be simple. Other data is sensitive, such as bank details, legal entities, payment terms or credit limits.
Customer data must have governance.
Poor data creates non-payable invoices, unnecessary reminders, wrongly allocated payments and false credit decisions.
Who Maintains the Credit Limit?
The credit limit is not a fixed figure.
It must evolve with volume, payment behavior, solvency, margin, disputes, guarantees, insurance and commercial strategy.
Who requests a limit?
Often Sales or Sales Administration during an order.
Who analyzes it?
Credit Management.
Who provides commercial information?
Sales.
Who provides payment history?
Collections and Accounts Receivable Accounting.
Who approves according to thresholds?
Credit Management, Finance, Sales management or committee depending on amount and risk.
Who reviews periodically?
Credit Management.
Who triggers an exceptional review?
Any important signal: delay, overrun, broken promise, major new order, financial change, significant dispute.
The limit commits capital.
Its governance must therefore be clear.
A limit that is too low blocks unnecessarily. A limit that is too high exposes excessively. A limit that is not maintained quickly becomes obsolete.
Who Arbitrates Between Sales and Cash?
Some situations naturally oppose several objectives.
Sales wants to deliver.
Finance wants to reduce exposure.
Operations wants to respect the schedule.
The customer asks for time.
Collections wants to obtain payment.
Credit Management proposes a condition.
Who arbitrates?
For ordinary cases, Credit Management can decide within a defined framework.
For sensitive cases, a higher level is necessary: financial management, sales management, general management, credit committee, cash committee.
Arbitration must be organized before the crisis.
Which thresholds require approval?
Which customers are strategic?
Who can accept uninsured risk?
Who can authorize delivery despite significant overdue invoices?
Who can accept a long payment plan?
Who can decide to end the relationship?
Without arbitration rules, conflicts are settled through pressure, influence or urgency.
With clear governance, they are settled through documented decisions.
Who Manages the Customer Cash Forecast?
The customer collection forecast involves several functions.
Treasury needs the forecast.
Collections knows the promises.
Credit Management knows the risk.
Sales knows customer discussions.
Operations knows milestones and validations.
Accounting knows payments received.
Who manages the whole process?
In many organizations, Treasury consolidates, but it depends on information from Collections and Credit Management.
The process must be clarified.
Who updates probable collection dates?
Who qualifies uncertain amounts?
Who flags disputes?
Who validates assumptions on large accounts?
Who measures the gap between forecast and actual?
A reliable forecast requires responsibility for consolidation and responsibility for information.
Treasury cannot guess customer blockages.
Collections cannot ignore Treasury needs.
Governance connects both.
Who Decides to Move to Litigation?
Moving to litigation or external action is an important decision.
It changes the nature of the relationship.
It can have a cost, a commercial impact, legal risk and an image consequence.
Responsibilities must therefore be defined.
Who proposes the move?
Often Collections or Credit Management.
Who checks that the file is solid?
Credit Management, Finance, Legal.
Who approves?
Depending on the amount: Finance, management, Legal, committee.
Who transfers the file?
Collections, Legal or the litigation department.
Who informs Sales?
Credit Management or Finance.
Who decides to suspend the relationship?
According to arbitration rules.
Litigation must not be triggered too late through inertia, nor too early through impatience.
It must be a structured decision.
Clarity of roles makes it possible to move from amicable delay to formal handling at the right time.
Who Decides to Write Off a Receivable?
The write-off of a receivable must also be governed.
It can be economically rational, but it must not be silent.
Who identifies probably uncollectible receivables?
Collections, Credit Management, Accounting, Legal.
Who analyzes the cause?
Credit Management with the functions concerned.
Who approves the write-off?
Finance, management, according to thresholds and accounting rules.
Who records it?
Accounting.
Who draws the lessons?
Credit Management, with Sales, Sales Administration, Operations or Billing depending on the cause.
A write-off must answer two questions.
Why are we not recovering?
What must we change to avoid this happening again?
Governance is not only used to approve the loss.
It is used to learn.
Using a RACI Logic
To clarify roles, many companies use a simple RACI-type logic.
The principle is to distinguish several levels of responsibility.
Who performs the action?
Who is ultimately accountable for the decision?
Who must be consulted?
Who must be informed?
Whatever name is given to this method, the idea is very useful.
Take a quality dispute.
Operations performs the technical analysis.
The Quality or Operations manager may be accountable for the technical decision.
Sales and Collections must be consulted.
Finance and Credit Management must be informed if the amount affects cash or the limit.
Take an order release.
Credit Management may be accountable for the decision.
Collections provides the status of overdue invoices and promises.
Cash application checks recent payments.
Sales brings the commercial context.
Sales Administration is informed to execute.
This logic avoids confusion.
It must not be theoretical. It must serve concrete cases.
Defining Thresholds
Not all decisions should go through the same level.
Thresholds must be defined.
Amount thresholds.
Aging thresholds.
Discount thresholds.
Credit note thresholds.
Limit overrun thresholds.
Uninsured risk thresholds.
Dispute thresholds.
Litigation transfer thresholds.
Thresholds make it possible to fluidify small files and secure large ones.
A 300-euro invoice should not mobilize a management committee.
An exposure of 2 million euros should not be arbitrated informally by email.
Thresholds provide proportion.
They avoid both unnecessary heaviness and uncontrolled risk.
Practical governance must always be proportionate.
Documenting Decisions
An undocumented decision can become a future problem.
Releasing an order.
Granting a temporary limit.
Accepting a deduction.
Promising a credit note.
Changing a payment term.
Authorizing delivery despite overdue invoices.
Approving a payment plan.
Refusing an order release.
All these decisions must leave a trace.
Why was the decision made?
By whom?
For what amount?
For what duration?
Under which conditions?
What next review?
A trace is not only used for control.
It is used to understand, follow, explain and learn.
In customer cash, many internal conflicts come from forgotten informal decisions.
Documentation protects coherence.
Putting a Target Date on Each Action
An action without a target date is a disguised wait.
“The salesperson must check with the customer.”
“Operations must verify.”
“Billing must correct.”
“Legal must review.”
“Accounting must match.”
These sentences are not enough.
There must be a date.
When will the salesperson come back?
When will Operations give its conclusion?
When will the invoice be corrected?
When will the credit note be issued?
When is payment expected?
The target date turns a responsibility into a commitment.
It also makes it possible to escalate if nothing happens.
Without a date, files drift.
With a date, they become manageable.
Cash needs calendars, not only intentions.
Example: Order Blocked Without Clear Role
An important customer has 80,000 euros of overdue invoices and a new order of 120,000 euros.
The system blocks the order.
The salesperson requests urgent release.
Collections indicates that a payment may be “in progress.”
Accounting has not yet identified any transfer.
Credit Management is waiting for proof.
Nobody knows who can decide.
The order remains blocked for two days, then is released under pressure, without clear condition.
A few weeks later, the announced payment is still not received.
With clear governance, the process would have been different: Collections checks the promise, cash application checks payments, Sales provides context, Credit Management decides, possible release under written condition, review date set.
The problem was not only the customer delay.
It was the absence of a clear role in the release.
Example: Dispute with No Owner
An invoice of 90,000 euros is blocked because of a quality issue.
Collections notes “dispute.”
The salesperson says Operations must answer.
Operations thinks the customer must provide more details.
Finance waits for a credit note decision.
After two months, nothing has moved.
With clear governance, the dispute would have been qualified at opening: quality cause, disputed amount 20,000 euros, owner Operations, decision expected within ten days, payment of the undisputed amount requested by Collections, escalation if no answer.
The dispute could have been reduced, treated and followed.
Cash often gets blocked when the dispute belongs to nobody.
Example: Credit Note Promised but Not Approved
A salesperson promises the customer a credit note of 5,000 euros to preserve the relationship.
The total invoice is 70,000 euros.
The customer waits for the credit note and withholds the full payment.
Billing has not received an official request.
Finance has not approved the gesture.
Collections continues to claim 70,000 euros.
The customer replies that the credit note was promised.
The situation becomes confused.
With clear governance, a commercial credit note must be requested through a formal workflow, approved according to thresholds, issued by Billing, applied by Accounting, then Collections must request payment of the balance.
The commercial promise is not enough.
A cash decision must be executable.
Example: Payment Promise Not Followed
A customer promises to pay 40,000 euros on Friday.
The salesperson receives this information during a call and transmits it orally.
Collections does not record it.
Treasury does not integrate it.
Friday passes, no payment arrives.
Nobody reacts immediately.
The following week, the customer gives a new promise.
With clear governance, every promise must be recorded with amount, date, invoices, contact person and confidence level.
Collections checks on the expected date.
If it is not kept, the information becomes a risk signal and can trigger action.
An unfollowed promise is not a cash tool.
It is an illusion of visibility.
Creating a Culture of Responsibility Without Rigidity
Clarifying roles must not make the organization rigid.
It is not about preventing teams from cooperating or solving quickly.
On the contrary, clarity accelerates.
When everyone knows what they must do, files circulate better.
When a decision has an owner, it is made faster.
When an action has a date, it is followed better.
When an exception has a trace, it is executed better.
Governance must remain proportionate, pragmatic and cash-oriented.
The goal is not to request heavy approval for every detail.
The goal is to avoid grey areas on topics that truly block collection.
A good organization does not confuse control with heaviness.
It clarifies to make things flow.
Key Takeaways
Clarifying roles is an essential condition for cash governance.
In the Quote-to-Cash cycle, many delays do not come only from the customer, but from internal grey areas:
nobody knows who must detect, decide or resolve.
Responsibilities must be defined on key topics: account opening, validation of payment terms, acceptance of exceptions, order release, invoice correction, dispute handling, customer contact, escalation, credit note decision, promise follow-up, data update, limit maintenance, move to litigation and possible write-off of receivables.
Clear responsibility must answer several questions: who performs the action, who decides, who must be consulted, who must be informed, within what timeframe, with what trace?
The objective is not to create a heavy organization.
The objective is to avoid grey areas.
Because an invoice without an owner ages, an undocumented exception becomes a dispute, an unfollowed promise becomes an illusion, an undecided credit note blocks cash, and an order released without conditions can worsen risk.
Collective cash needs cooperation.
But it also needs clear responsibilities.