What should an accounts receivable process achieve?
An accounts receivable process should establish what customers genuinely owe, when payment is due and what action is needed to collect it. It combines accurate invoicing, receipt allocation, ageing, dispute resolution and assessment of recoverability. A list of unpaid invoices becomes useful only when the balances are reliable and somebody owns the next action.
For a Cyprus business, collection, accounting and tax are related but separate decisions. An overdue invoice is not automatically an irrecoverable debt, an accounting impairment does not itself establish a tax deduction, and a credit note should not be issued merely to make an unpaid balance disappear. Keep the evidence for each decision distinct.
This guide focuses on customer-ledger controls and collection workflow. It does not prescribe court procedures or a universal sequence of legal demands. Contract terms, the customer's circumstances and the nature of the transaction affect escalation. The cash forecast guide explains how confirmed collection assumptions feed into future liquidity.
Prevent avoidable delays before extending credit
Confirm the customer's legal name, billing details, authorised contact and required purchase-order reference before starting work. Agree the scope, price, payment terms and evidence of completion. A trading name alone may not identify the party responsible for payment, particularly where several group companies use similar branding.
Set an internal approval process for credit terms and limits. Consider the size of the exposure, previous payment behaviour and concentration in a single customer. The same credit limit may be inappropriate for a long-standing customer with reliable payments and a new customer placing an unusually large order. Document exceptions and who approved them.
For projects, agree milestones and invoicing requirements early. If payment depends on acceptance, identify who can accept the work and what evidence is required. A finance team cannot solve every collection delay by sending more reminders if operational staff never obtained the document the customer needs to approve the invoice.
Issue accurate invoices and prove delivery
Invoice the correct entity promptly once the relevant billing conditions are met. Check references, descriptions, amounts, tax treatment, bank details and due dates. The VAT invoice requirements guide covers invoice content; the collection control here is to ensure the customer receives a usable invoice through the agreed channel.
Retain evidence of delivery to the billing contact or portal, including any rejection message. Uploading an invoice to the wrong portal account can leave it outside the customer's approval process. If the customer requests a correction, identify whether the problem concerns a reference, the underlying price, the supply or the legal recipient before changing the document.
Control changes to payment details. Verify any proposed bank-detail change through a trusted channel rather than relying solely on a new email. Keep a record of the approved details on outgoing invoices. A payment diverted by fraud or made to an unrelated account creates a different problem from an ordinary late payment.
Reconcile the customer ledger before chasing
Export open invoices at a stated reporting date and reconcile the total to the receivables control account. Include invoice numbers, dates, contractual due dates, original values, credits, allocated receipts and remaining balances. Use the same cut-off for the ledger and the bank information, so that recent receipts are not counted inconsistently.
Investigate unallocated receipts before sending collection messages. Customers may pay several invoices together, use a different reference or deduct an agreed credit. Match the payment using reliable evidence rather than allocating it to whichever old invoice makes the report look better. Record any difference requiring clarification.
Review customer credit balances separately. They may represent advances, overpayments, unmatched credit notes or allocation errors. Do not offset one customer's debt against another customer's credit simply to reduce the headline receivables total. The bank reconciliation guide helps establish that the receipt itself is correctly recorded before its customer allocation is resolved.
Age overdue invoices from the contractual due date
An overdue ageing report measures lateness from the due date. A report based on invoice date measures how long the invoice has existed, which is a different question. Mixing the two can misclassify a customer with agreed sixty-day terms as late when payment is not yet due. Label the method and reporting date clearly.
Use non-overlapping buckets, such as not due, 1–30 days overdue, 31–60, 61–90 and over 90. Confirm how the software treats an invoice due on the reporting date; it should not be described as overdue before its payment deadline has passed. Keep disputed amounts identifiable within their actual ageing category rather than moving them back into the current column.
| Bucket | Illustrative outstanding amount | Operational interpretation |
|---|---|---|
| Not overdue | €5,000 | Confirm invoice acceptance and expected payment |
| 1–30 days overdue | €4,000 | Identify administrative delays and missed commitments |
| 31–60 days overdue | €3,000 | Review disputes and collection plan |
| 61–90 days overdue | €1,000 | Escalate material unresolved issues internally |
| Over 90 days overdue | €1,000 | Assess evidence of recoverability and next steps |
| Total | €14,000 | Agree to the corrected customer schedule |
These buckets are reporting choices, not statutory deadlines or automatic write-off triggers. A large current invoice can pose more collection risk than a small old invoice. Review concentration, disputes and customer circumstances alongside age.
Worked example: correct the list before collecting
Assume an uncorrected open-invoice schedule totals €18,000. It omits the effect of a €3,000 receipt awaiting allocation and a valid €1,000 credit note awaiting matching. After identifying the correct invoices, the remaining open amount is €18,000 − €3,000 − €1,000 = €14,000. This is an illustrative customer-schedule reconciliation, not a tax calculation.
Whether a general-ledger journal is needed depends on what has already been posted. If both items are already in the control account, matching them corrects the open-item schedule without recording the cash or credit again. If an item is genuinely absent from the ledger, the accountant must record it appropriately. Do not duplicate an entry merely because the collection report was incomplete.
Suppose €4,000 of the corrected €14,000 is disputed. Present €10,000 of other open debt and the €4,000 dispute separately. The dispute remains part of the gross receivable until an appropriate accounting adjustment is made; categorising it does not cancel the debt. Record the issue, supporting documents and person responsible for resolution.
If the €3,000 receipt has already reached the bank, it is not a future collection in the cash forecast. Correct the customer schedule and the forecast assumptions together. Otherwise, an apparently improved collection position may still leave management planning around cash it has already received.
Create a collection queue with named actions
Add an owner, last contact date, reason for non-payment, promised payment date and next action to each material overdue balance. Prioritise by amount, age, customer concentration, broken promises and signs of financial difficulty. A colour-coded ageing report can flag a problem, but it cannot resolve it without a responsible person.
A practical internal sequence is to confirm invoice receipt before the due date, follow up after a missed date and escalate persistent or material delays to management. These are operating suggestions, not legal notice periods. Adapt the frequency to the relationship and evidence, and avoid sending contradictory messages from sales, finance and an external adviser.
Keep reminders factual: identify the invoice, outstanding amount and agreed due date, ask whether anything prevents payment, and request a specific response. Record the response accurately. “Customer contacted” is not equivalent to “customer agreed to pay on Friday”; that difference matters when the forecast relies on the expected receipt.
Separate disputes from administrative delays
Classify the underlying issue. A missing purchase order belongs with the person who can obtain it; disagreement over delivery requires operational evidence; an incorrect price needs commercial review; financial difficulty may require a different collection strategy. Repeated generic reminders can waste time when the actual obstacle has not been assigned to somebody able to resolve it.
Maintain a dispute register with the disputed amount, undisputed portion, reason, evidence, owner and target resolution date. Do not assume that the entire invoice is disputed if only one line is challenged. Equally, do not describe a genuinely disputed amount as an agreed overdue payment without considering the facts.
A valid price reduction or correction may require a credit note under the relevant rules. The credit note guide addresses that process. Non-payment alone does not justify inventing a return, cancellation or discount. Preserve the original invoice and a clear audit trail for any authorised adjustment.
Document payment plans and assess escalation carefully
For an agreed instalment plan, record the covered invoices, amounts, dates and how payments will be allocated. Identify who approved the arrangement and what happens operationally if a payment is missed. Update the forecast using the agreed schedule, while keeping the original debt and correspondence traceable.
Before adding interest, compensation or collection charges, check the applicable law and contract. The European Union's Your Europe late-payment guidance distinguishes commercial transactions from consumer situations and sets out conditions. It should not be treated as authority to impose the same charge on every customer. Rates and circumstances need checking for the relevant period.
Review any proposed suspension of supply, formal demand or legal escalation with the appropriate adviser where necessary. This guide does not establish the enforceability of a particular claim. Keep communications proportionate and accurate, and share the file only with people who need it for the collection or advisory task.
Distinguish collection, impairment and write-off
Collection seeks payment. An impairment allowance reflects the accounting assessment of expected losses. A write-off changes the recorded asset when the relevant accounting criteria are met. These are not interchangeable actions. A collection team should not automatically delete every balance over ninety days, and an accounting allowance does not necessarily end collection efforts.
IFRS 9 includes expected credit loss requirements. Where applicable, the accountant should assess the relevant model and evidence, including customer-specific information and appropriate forward-looking factors. Do not assume that every current invoice has zero risk or that the same unsupported percentage fits every customer group.
Retain the calculation, evidence considered, approval and changes from the previous assessment. If using historical collection experience, consider whether current conditions make it representative. Information received after the reporting date may also need assessment under the applicable reporting requirements. Keep the gross debt, allowance and resulting carrying amount understandable to management.
Assess tax and VAT separately from the ledger adjustment
An accounting impairment or write-off does not automatically determine the income-tax treatment. Retain the original transaction evidence, collection history, correspondence, assessment of recoverability and approval. Ask the accountant to evaluate the applicable tax rules and record any difference between accounting expense and the tax computation.
Cyprus VAT bad-debt relief has specific conditions. Article 27 of the VAT Law addresses matters including VAT accounted for and paid, a book write-off, collection steps and an elapsed twelve-month period beginning with the transaction date, subject to the remaining provisions and regulations. An overdue flag by itself is not a refund claim.
Before making a claim, check the complete requirements, supporting records, partial payments and treatment of any later recovery. Keep the VAT review separate from issuing a genuine commercial credit note. These routes answer different questions and should not be used interchangeably to clear an uncomfortable customer balance.
Review progress and hand over a usable file
At the monthly close, reconcile the final customer schedule, review old credits and unallocated receipts, update disputes and reconsider recoverability. Between closes, maintain the collection queue often enough to react to missed promises. Preserve earlier reports so improvements can be distinguished from reclassification or write-offs.
Report total receivables, overdue amounts, major concentrations, disputed balances and actions due in the management accounts. If using days-sales-outstanding, define the sales period, average balance and VAT basis; seasonality or a few large invoices can distort the ratio. Do not let a single average hide the customers driving the risk.
Give the accountant the reconciled schedule, source-document references, recent receipts, dispute log and proposed adjustments. Restrict customer information to authorised users and retain it according to applicable requirements. The aim is a reliable record of what is owed, a credible collection plan and a separate, documented accounting and tax assessment where needed.