Cash does not always get blocked inside one function.
It often gets blocked between two functions.
This sentence is essential to understand many payment delays. In a company, each department may feel that it has done its part of the work correctly. Sales sold. Sales Administration created the order. Operations delivered. Billing issued the invoice. Collections chased. Accounting processed payments received. Legal will intervene if necessary.
And yet, cash does not come in.
Why?
Because information did not circulate. Because the commercial exception was not transmitted. Because the dispute was known by Operations but not by Finance. Because a credit note was being discussed on the Sales side without being visible to Collections. Because a correction was made, but nobody informed Billing.
Because customer data exists in a local file, but not in the master system. Because Legal discovers too late a clause that should have been secured before signature.
Cash is then lost in the gaps of the organization.
Silos do not always create immediately visible errors. They create breaks in continuity.
And in the Quote-to-Cash cycle, any break in continuity can become a collection delay.
The Silo: Local Performance Is Not Enough
A silo is not necessarily a department that works badly.
It is sometimes a department that works correctly within its own scope, but without enough connection with the others.
Sales optimizes signature.
Sales Administration optimizes order entry.
Operations optimizes delivery.
Billing optimizes issuance.
Collections optimizes chasing.
Accounting optimizes entry processing.
Legal optimizes contractual security.
Each function can therefore meet its local objectives.
But cash depends on the handover between these objectives.
A well-signed sale but poorly transmitted becomes a fragile order.
An order created without complete information becomes a disputable invoice.
A delivery performed without evidence becomes a receivable that is difficult to defend.
An invoice issued without the compliant customer channel becomes a rejected invoice.
A reminder sent without knowledge of the dispute becomes ineffective.
A correction made without shared information becomes invisible.
Cash requires chain performance, not only department performance.
Cash Gets Blocked Between Functions
In many files, it is difficult to say that one single function is responsible.
The blockage is at the interface.
Between Sales and Sales Administration: a negotiated discount was not integrated.
Between Sales Administration and Billing: a specific condition was not transmitted.
Between Operations and Collections: a customer reservation is known but not shared.
Between Billing and Accounts Receivable Accounting: a credit note is issued but incorrectly applied.
Between Collections and Sales: the customer has promised payment, but is negotiating a concession in parallel.
Between Legal and Sales: a vague acceptance clause is discovered after the dispute.
Between Credit Management and commercial teams: a limit is exceeded, but orders continue to be pushed without a securing scenario.
Cash does not always get blocked because someone did nothing.
It gets blocked because the action of one department was not connected to the action of the next one.
The problem is often less in the task than in the transmission.
Poor Transmission Between Sales and Sales Administration
The transmission between Sales and Sales Administration is one of the most sensitive areas.
Sales negotiates with the customer. It knows the context, promises, concessions, special conditions, deadlines, discounts, expected documents and sensitive points.
But if these elements are not clearly transmitted to Sales Administration, the order will be created on an incomplete basis.
A special discount may be forgotten.
An exceptional payment term may not be set.
A mandatory purchase order may not be requested.
Milestone billing may be replaced by standard billing.
An address or entity may be approximate.
An oral commitment may remain invisible.
The customer remembers what was negotiated.
When the invoice arrives, it compares it with its agreement.
If it does not match, it blocks.
This is not a simple administrative problem. It is a break between the commercial promise and administrative execution.
The sale was signed, but it was not sufficiently transformed into an executable and billable order.
The Commercial Exception Not Shared
Commercial exceptions are particularly dangerous when they remain inside the Sales silo.
An exception can be legitimate.
A strategic customer obtains a discount.
An urgent delivery is accepted before PO regularization.
A specific term is granted.
Deferred billing is negotiated.
A commercial credit note is promised.
A penalty is accepted.
But if the exception is not documented, approved and transmitted, it becomes a future dispute.
Billing issues according to standard rules.
Collections chases according to the invoice issued.
The customer replies that this was not the agreement.
Sales confirms afterwards that an arrangement existed.
Cash is delayed.
In this case, the problem is not only the exception.
The problem is the invisible exception.
A silo turns a commercial decision into a financial dispute.
Dispute Known but Not Shared
Another very frequent case concerns disputes.
The customer reports a problem to a salesperson, a project manager, a technician or someone in Operations.
The topic is known locally.
But it is not visible in the customer account.
Collections sees an overdue invoice and chases.
The customer replies: “We already reported the problem to you.”
Collections discovers the dispute late.
The invoice has aged.
The relationship has become tense.
The forecast was wrong.
Credit Management may have made a decision based on incomplete information.
The dispute was not absent. It was locked inside a silo.
A dispute that is not shared is particularly costly, because it gives the company the illusion of a simple receivable while a blockage already exists.
The rule should be clear: any customer dispute likely to block payment must be visible to Collections, Finance and Credit Management.
Not to blame.
To act.
Operations Corrects Without Informing Finance
Sometimes, Operations treats a problem, but does not transmit the information to financial functions.
A product is replaced.
An additional service is performed.
A reservation is lifted.
A report is sent to the customer.
A milestone is finally validated.
A defect is corrected.
But Collections does not know it.
Billing does not know whether it can reissue.
Finance does not know whether the credit note is still necessary.
Credit Management does not know whether the dispute is resolved.
The invoice remains open with an old status.
The customer may even be chased although the problem has been treated, or conversely may not be chased although the issue is closed.
The operational correction must be connected to financial treatment.
Solving a problem technically is not enough.
Its cash impact must also be closed.
Otherwise, the file remains blocked in systems, even if operational reality has moved forward.
Collections Without Resolution Power
Isolated Collections is often ineffective.
The collector can call, send emails, request dates, chase several times. But if the delay comes from a quality dispute, a credit note to approve, a PO to correct, proof of delivery to provide or a billing error, they cannot solve it alone.
They depend on other functions.
If these functions do not answer or do not understand the cash stake, Collections becomes a powerless messenger.
It transmits the customer’s request.
It chases internal teams.
It waits.
It chases again.
Meanwhile, the invoice ages.
Mature Collections must have coordination power, or at least clear access to resolution owners.
It must be able to request an action, set a target date, escalate if necessary and make the blocked amount visible.
Otherwise, the organization asks Collections to bring cash in without giving it the means to remove blockages.
This is a frequent contradiction.
Legal Involved Too Late
Legal sometimes intervenes too late in the cycle.
It is called when the dispute is already established, when the customer refuses to pay, when the penalty has been applied, when the clause is contested or when litigation becomes possible.
Its intervention is then necessary, but sometimes late.
Some difficulties could have been avoided through earlier securing.
Imprecise payment clauses.
Poorly defined milestones.
Vague acceptance terms.
Poorly framed penalties.
Insufficient guarantees.
Suspension conditions not provided for.
Ambiguous service scope.
Expected documents not listed.
When these topics are discovered after the fact, cash is already exposed.
Legal must not be seen only as a crisis function.
It can contribute to preventing blocked cash upstream.
The challenge is not to legalize every sale, but to identify the contracts or files where clauses strongly influence the ability to invoice and collect.
Scattered Customer Data
Customer data is another source of silos.
One piece of information is in the CRM.
Another in the ERP.
Another in a commercial file.
Another in a customer portal.
Another in the emails of an account manager.
Another in the collection tool.
Another in Accounting.
Nobody has a complete view.
The result: wrong entity, wrong address, old contact, wrong billing channel, incorrect payment terms, duplicate customers, poorly consolidated limit, incomplete group exposure, payment applied to the wrong account.
Scattered data creates discreet delays.
The customer may receive an invoice in the wrong place.
Collections may contact someone who is no longer in the role.
The limit may be calculated on only part of the exposure.
A payment may be allocated to the wrong account.
Cash needs reliable, shared and maintained data.
Master data is not an isolated technical topic.
It is a cash infrastructure.
The Case of Customer Portals
Customer portals often create additional silos.
Sales teams know that the customer uses a portal.
Sales Administration may know the required references.
Billing uploads the invoice.
Collections discovers later that it has been rejected.
Operations must validate receipt.
Accounts Receivable Accounting waits for payment.
But nobody follows the status end to end.
An invoice may be uploaded but rejected.
Accepted but waiting for approval.
Waiting for receipt.
Waiting for attachment.
Waiting for correction.
If portal status is not shared, each function believes the file is moving forward.
In reality, it is blocked.
The portal is not only a billing tool. It is an interface space between the customer and the supplier.
It must have a clear owner and accessible information.
Otherwise, it becomes an external silo that slows down cash.
When Objectives Create Silos
Silos do not only come from the organization. They also come from objectives.
If Sales is measured only on signed revenue, it may underestimate the quality of terms.
If Sales Administration is measured only on order entry speed, it may accept incomplete orders.
If Operations is measured only on delivery, it may neglect evidence.
If Billing is measured only on the number of invoices issued, it may quickly issue invoices that will be rejected.
If Collections is measured only on reminders sent, it may push without resolving.
If Finance is measured only on risk reduction, it may block without looking for the conditions of yes.
Local indicators can therefore create behaviors that slow down global cash.
Objectives must be aligned with the chain.
The right indicator is not only: has my department done its task?
It is also: has my task allowed the next step to move forward?
Silos Create Double Messages to the Customer
Another dangerous effect of silos is double messaging.
The salesperson promises the customer that a credit note will be issued.
Collections continues to claim the full amount.
Operations tells the customer that a dispute is being handled.
Finance does not see it and blocks orders.
Legal prepares a formal letter.
The salesperson negotiates a new order in parallel.
The customer receives contradictory messages.
This damages the company’s credibility.
A customer may exploit these contradictions. But it may also simply lose trust.
A siloed organization gives the impression that it does not talk to itself.
Yet in Collections, message consistency is a source of strength.
Before escalating, blocking, negotiating or threatening, the company must align its functions.
Cash needs one clear position.
Silos Slow Down Decisions
A payment delay is often resolved by a decision.
Should a credit note be issued?
Should the invoice be maintained?
Should a penalty be accepted?
Should the company deliver despite overdue invoices?
Should a down payment be requested?
Should a limit be reduced?
Should the case move to litigation?
In a siloed organization, the decision circulates.
Sales waits for Finance.
Finance waits for Operations.
Operations waits for the customer.
Legal waits for the contract.
Sales Administration waits for approval.
Collections waits for everyone.
Meanwhile, nothing is decided.
The invoice ages.
Cash does not come in.
The problem is not always lack of information.
It is sometimes lack of a decision circuit.
A cash topic must have governance: who decides what, from which threshold, within which timeframe, with which information?
Without this, delay becomes structural.
Silos Make Causes Invisible
When information remains scattered, the company does not see root causes.
It sees late invoices.
But it does not know that many come from missing POs.
Or portal invoice rejections.
Or receipts not validated.
Or commercial credit notes not transmitted.
Or repetitive quality disputes.
Or incorrect customer data.
Each department sees part of the problem. Nobody sees the global trend.
Collections treats invoice by invoice.
Management looks at DSO.
But causes are not consolidated.
Silos prevent learning.
A company can repeat the same problem for months without seeing it clearly.
Customer cash management must therefore consolidate causes, not only amounts.
This is how the organization learns.
The Sales–Sales Administration Interface
The interface between Sales and Sales Administration deserves specific attention.
It must make it possible to transmit everything that makes the order executable and billable.
Payment terms.
Prices and discounts.
Exceptions.
Legal entity.
Purchase order.
Billing address.
Billing channel.
Customer references.
Milestones.
Required documents.
Specific commitments.
Identified risks.
A simple email or informal conversation is not always enough.
Structured fields, approvals, controls and clear responsibility are needed.
The quality of this interface determines what follows.
A clean order often starts with a clean handover between Sales and Sales Administration.
If this interface is weak, problems will appear later, when the company has already delivered and the customer refuses to pay.
The Sales Administration–Billing Interface
Sales Administration may have the information, but it must still be transmitted correctly to Billing.
Billing must know what to invoice, when, to whom, according to which terms, with which references and which supporting documents.
A poor Sales Administration–Billing interface can create price, quantity, due date, milestone or entity errors.
The customer does not see the upstream effort.
It only sees an incorrect invoice.
The company must therefore secure this handover.
Data must be in the system, not only in notes.
Exceptions must be approved.
Documents must be available.
Terms must be consistent.
Billing cannot produce a payable invoice if upstream information is incomplete.
The invoice is the mirror of the quality of previous interfaces.
The Operations–Finance Interface
The Operations–Finance interface is often critical in services, projects, maintenance, installation, logistics or industry activities.
Operations knows whether the work has been done.
Finance must know whether the invoice can be issued, defended and collected.
Evidence, milestones, receipts, reservations, delays, non-conformities and validations must therefore be shared.
If Operations delivers without documenting, Finance invoices with a weak file.
If Operations corrects without informing, Finance continues to consider the dispute open.
If Operations knows about a reservation but does not report it, Collections discovers the blockage too late.
Cash depends strongly on this interface.
It must be organized, not improvised case by case.
Operations must not see evidence as an administrative request.
Evidence is what turns execution into a defendable receivable.
The Collections–Credit Management Interface
Collections and Credit Management must work together.
Collections sees the customer’s real behavior: answers, promises, delays, disputes, excuses, partial payments, quality of exchanges.
Credit Management uses this information to decide: limit, block, terms, down payment, guarantee, monitoring, escalation.
If information does not circulate, credit decisions are weaker.
A customer may keep a high limit while it no longer respects its promises.
Another may be blocked although its delays come from our internal errors.
Collections must therefore feed Credit Management with qualified information, not only overdue amounts.
Credit Management must, in return, give Collections an action framework: thresholds, priorities, conditions, risky customers, treatment strategy.
This interface connects day-to-day payment reality with risk arbitration.
The Cash Application–Collections Interface
Cash application and Collections must also be connected.
Collections must not chase an invoice already paid.
Cash application must be able to identify payments thanks to information obtained from the customer.
Unreferenced payments, grouped payments, deductions and offsets often require collaboration.
If this interface is weak, the company creates false delays.
The customer is chased wrongly.
Orders may be blocked wrongly.
DSO may be distorted.
Teams waste time.
A good interface makes it possible to quickly turn payments received into clean customer accounts.
Cash received then becomes reliable information.
Without reliable matching, the aged balance loses part of its value.
The Finance–Legal Interface
When files become sensitive, the Finance–Legal interface is important.
Finance knows amounts, age, promises, disputes, cash impacts, provisions, limits and exposure.
Legal knows rights, obligations, clauses, remedies, litigation risks, guarantees and suspension conditions.
If Legal intervenes too late or with an incomplete file, action is less effective.
If Finance acts formally without legal securing when the stakes are high, it can weaken the company’s position.
The interface must therefore be proportionate.
Not all delays require Legal.
But significant, contractually sensitive or pre-litigation files must be prepared together.
Cash is also protected through the legal solidity of actions.
Reducing Silos Through Rituals
Silos are reduced through cross-functional work habits.
It is not enough to ask teams to communicate better.
Rituals must be created.
Weekly review of significant disputes.
Review of rejected invoices.
Large account review.
Blocked order review.
Risk exposure review.
Expected credit note review.
Unmatched payment review.
These rituals must be short, factual and action-oriented.
For each file: amount, cause, owner, action, target date, escalation if necessary.
The goal is not to comment on the aged balance.
The goal is to decide what must happen next.
Cross-functional rituals create a space where cash leaves the silos.
Reducing Silos Through Shared Data
Rituals are not enough if data remains scattered.
Shared information is needed.
A visible invoice status.
A coded cause of delay.
A dispute owner.
A promise date.
A target resolution date.
A payment status.
A portal status.
A consolidated limit and outstanding balance.
Usable collection comments.
The ideal is not always to have one perfect system. Many companies work with several tools.
But critical information must at least be accessible to the functions concerned.
Shared data avoids double messages and blind decisions.
Cash is managed better when everyone sees the same reality.
Reducing Silos Through Handover Rules
Each critical interface should have handover rules.
A sale becomes an order only if key terms are entered.
An order moves to execution only if the mandatory PO is available.
An invoice is issued only if the required supporting documents exist.
A dispute is opened only if it has a cause, an amount, an owner and a target date.
A credit note is promised only if it follows an approval process.
A blocked order is released only if the conditions are documented.
These rules must not be bureaucratic.
They must prevent predictable problems.
A good handover between functions reduces future delays.
Cash is often won or lost when a file changes hands.
Reducing Silos Through Clear Escalation
Some files cannot be resolved at operational level.
They must be escalated.
But escalation must be clear.
When should escalation happen?
To whom?
With what information?
For which decision?
Within what timeframe?
Without escalation rules, teams hesitate. They wait too long. They chase without being able to decide. Disputes age.
Clear escalation prevents stagnation.
It makes it possible to bring topics to the right level before they become critical.
Escalation should not be seen as a failure.
It is a normal governance tool when cash is blocked between several functions.
Example: Delay Created Between Sales and Sales Administration
A salesperson negotiates a special 12% discount to win an order.
The agreement is confirmed by email to the customer, but the discount is not integrated into the order tool.
Sales Administration enters the order at the standard price. The invoice is issued for the wrong amount.
The customer blocks payment.
Collections discovers the issue after due date.
The sale was real. The customer was not in difficulty. Delivery had taken place.
Cash was blocked between Sales and Sales Administration.
The solution is not only to correct the invoice.
The interface must be secured: any exceptional discount must be approved, integrated into the order and visible to Billing.
Example: Dispute Known by Operations but Invisible to Finance
A customer reports a quality reservation to the operational manager.
Operations plans a corrective intervention.
But the information is not transmitted to Collections.
The invoice reaches due date. Collections chases. The customer replies that it is waiting for the promised correction.
Collections loses credibility.
The invoice has aged unnecessarily.
The problem was not the existence of the dispute.
The problem was its invisibility.
The solution is to make every dispute likely to block payment visible in the tool or in the cash review, with an owner and a target date.
Example: Correction Made but Cash Not Released
A technical service corrects a defect at the customer’s site.
The customer is satisfied and accepts to pay after receiving the intervention report.
The report is sent by the technician to the customer’s operational contact, but not to Billing or Collections.
Collections continues to see the dispute as open.
The invoice is not chased correctly.
Payment is delayed.
The correction took place, but its cash effect was not managed.
Technical resolution must always be connected to financial resolution.
A dispute is not closed when the problem is corrected. It is closed when the customer account is clarified.
Example: Scattered Customer Data
A customer changes its billing address and imposes a new portal.
The salesperson receives the information.
Sales Administration updates a local file.
Billing continues to send invoices by email.
Collections chases the old contact.
Accounts Receivable Accounting receives no payment.
After several weeks, the company discovers that the invoices were never integrated by the customer.
Cash was blocked by data that was not shared.
The solution is to maintain reliable master data and define a clear update process.
Critical customer data must not live only in an email inbox or a local file.
Example: Legal Called Too Late
A project contract provides for billing at the final milestone, but the validation criteria are vague.
The customer refuses to sign final acceptance by invoking elements that were not explicitly defined.
The balance invoice remains blocked.
Legal is called after several months of discussion.
It sees that the clause is ambiguous and that the company’s position will be difficult to defend.
The problem could have been reduced upstream through a more precise definition of acceptance criteria and validation methods.
Cash was blocked between commercial negotiation, operational execution and legal securing.
Legal called too late cannot always repair an ambiguity already signed.
Silos as a Hidden Cost
Silos have a cost.
They increase DSO.
They create disputes.
They delay invoices.
They multiply credit notes.
They generate unnecessary reminders.
They degrade the forecast.
They consume internal time.
They irritate customers.
They weaken credit decisions.
They can lead to losses.
This cost is rarely measured as such.
It appears as delays, old invoices, disputes, unmatched payments, overdue invoices, provisions or write-offs.
But behind these figures, there is often the same cause: the organization does not transmit the right information at the right time.
The cost of silos is therefore not only organizational.
It is financial.
Key Takeaways
Silos slow down cash because they break the continuity of the Quote-to-Cash cycle.
Cash does not always get blocked inside one function. It often gets blocked between two functions.
Between Sales and Sales Administration, a discount or exception can be poorly transmitted.
Between Operations and Finance, a dispute can be known but not shared.
Between Operations and Collections, a correction can be made without payment being released.
Between Collections and Credit Management, customer behavior may not be integrated into limit or blocking decisions.
Between cash application and Collections, a payment received can remain invisible.
Between Legal and Sales, a vague clause can be discovered too late.
Silos create delays, disputes, non-payable invoices, unnecessary reminders, unjustified blocks and poorly informed decisions.
Reducing silos requires clear interfaces, shared data, handover rules, identified responsibilities, cross-functional rituals and effective escalations.
A mature organization does not only ask each function to do its work well.
It ensures that each function transmits to the next one what it needs to turn the sale into cash.