Receivables: what actually separates one file from another

When a payment goes past due, the first question is usually “how do we collect it?”. The more useful question comes before that one: what does the file actually prove? Because the strength of the documentation is what widens or narrows every option that follows.

And to say it plainly at the outset: no one can promise you a result. Anyone who does is promising something they do not control. What can be committed to is method — and in practice, method is the largest single difference between a file that moves and a file that sits.

One: the file is built before the delay

The strongest files are the ones whose documents were gathered in the ordinary course of dealing, not after the relationship soured. The weakest rest on a personal trust that was never committed to paper. What makes the difference:

• A contract or purchase order setting out scope, price and due date.
• Invoices that are numbered, sequential and consistent with the contract.
• Proof of delivery — a signed receipt, or an acknowledgement in writing.
• Correspondence showing the amount acknowledged or a promise to pay, even in a short message.
• A record of what was paid and when: a part payment is an acknowledgement of the principal.

A gap in one of these does not make a file hopeless. It does mean the road is longer and the options fewer. This is why we read the documents before saying anything about time or cost.

Two: contact in the debtor’s own language

In a market as international as Qatar’s, a great deal of delay is misunderstanding rather than bad faith. A demand sent in a language the recipient does not read hands them a genuine excuse — and makes it hard, later, to argue they were on notice.

Writing in their language closes that gap. It moves the file from “nothing arrived that I could read” to “it arrived and I am expected to answer”. That alone shifts a great many files.

Three: documented follow-up

Every contact is recorded: date, channel, content, and the response. Not for the sake of formality, but for two practical reasons:

• The file does not restart from zero every time somebody changes on either side.
• There is an orderly record if the matter later needs escalating.

Files run on memory and unlogged phone calls are the ones that stall most often — not because the claim is weak, but because nobody can establish what happened.

Four: escalation is a decision, not a reflex

When amicable follow-up is exhausted, escalation is not automatic. The options available under the applicable regulations are set out, together with what each involves in time, cost and likelihood — and the decision stays with the client. Sometimes a settlement below the full amount is the better outcome when the alternative is a year of procedure. Sometimes it is not.

That judgement belongs to the person whose money it is. Our job is to put an honest picture in front of them to decide on.

Five: the time factor

Every month that passes weakens a file from three directions at once: the debtor’s capacity changes, documents scatter, and the people who knew the detail move on. A receivable followed up a month after it fell due is not the same receivable two years later, even though the figure is identical.

Which is why the most useful step is usually the earliest one: a clear written demand, in a language the recipient reads, shortly after the due date.

What we commit to, and what we do not

We manage and follow up collection files methodically, assessing each case on its own circumstances, its documents and the options available under the applicable regulations. No outcome is guaranteed — recovery depends on the strength of the documentation, the debtor’s capacity and the time that has passed. What we do commit to is the manner of the work: assessment before any promise, documented contact throughout, and telling a client what we see rather than what they would prefer to hear.