Retail and Wholesale in Oman: Managing Credit Customers Without Losing Cash Flow

Revenue is not cash

A mixed retail and wholesale business can look healthy while becoming short of cash. Retail customers pay at the till. Wholesale customers may order in volume, receive delivery, obtain an invoice and pay thirty, sixty or more days later. The supplier has already funded inventory, freight, VAT, staff and operating cost.

The risk is not credit selling itself. Trade credit can increase volume and deepen customer relationships. The risk is treating every order as revenue before confirming how much exposure the business is willing and able to finance.

A sound process connects six decisions:

customer approval → credit limit → order exposure → delivery evidence → invoice and collection → cash forecast

If these live in separate spreadsheets, the salesperson can promise stock without seeing overdue balances, finance can chase an invoice the customer disputes, and management can forecast cash that will not arrive.

This article describes operating controls, not legal, tax or debt-recovery advice. Confirm contract enforceability, VAT treatment, provisioning and collection remedies with qualified Omani advisers.

Separate cash and credit customer journeys

Do not turn every point-of-sale customer into a receivables account. Use distinct customer types:

• cash retail customer;
• named cash or loyalty customer;
• prepaid business customer;
• wholesale credit customer;
• government or large-account customer with contractual terms;
• related party;
• temporarily suspended or collection-only account.

Only an approved credit customer should place an order that creates receivable exposure. The customer master should contain legal name, commercial and tax identifiers, addresses, authorised buyers, delivery locations, contacts, agreed terms, currency, credit owner, limit, security or guarantee details, tax-invoice needs and effective dates.

Keep trading name and legal debtor separate. A store name may belong to a company that owns several outlets. The invoice, statement and collection action must identify the party contractually liable.

Onboard credit with evidence

A signed application is a request, not a credit decision. Gather information proportionate to the limit:

• commercial registration and authorised signatory evidence;
• VAT identification where applicable;
• billing and delivery addresses;
• ownership or group relationship;
• bank and trade references where appropriate;
• expected monthly purchases and peak season;
• requested terms and reason for credit;
• existing exposure across branches or related customer accounts;
• financial information for material limits;
• purchase-order and invoice-submission requirements;
• dispute and returns process;
• guarantees, deposits or other risk mitigants.

Verify information independently. A sales representative should sponsor the commercial relationship but should not approve the limit alone. Credit approval needs separation from sales incentives.

Document the rationale, approving authority, effective period and review trigger. “Important customer” is not a rationale. A temporary launch limit can increase after observed payment behaviour.

A credit limit should cover total committed exposure

Accounts receivable alone understates risk. At order acceptance, exposure can include:

• posted unpaid invoices;
• delivered but unbilled goods;
• picked or dispatched orders;
• confirmed open orders;
• approved returns or credit notes not yet posted;
• dishonoured or unidentified payments;
• guarantees, deposits or collateral recognised under policy;
• exposure in other branches, channels or related accounts.

Define the formula centrally. A practical representation is:

gross receivables + committed orders + unbilled deliveries − eligible unapplied cash − approved credit relief

Not every unapplied receipt should reduce exposure. A payment with an unknown payer or disputed ownership is not reliable relief. Likewise, a proposed return should not release credit before authorised receipt or acceptance.

Reserve exposure when the business commits to the order, not only at invoice. Otherwise several salespeople can each consume the same remaining limit before dispatch.

Terms and limits are different controls

A limit caps total exposure. Payment terms establish when each invoice falls due. A customer can remain below limit yet consistently pay late; another can reach limit while every invoice is current.

Store terms as controlled policies—advance, cash on delivery, seven days, thirty days from invoice, or contract-specific milestone terms. Avoid free-text “30/60” descriptions.

Calculate due dates from the contractual trigger. If a customer pays thirty days after accepted delivery, an invoice-date calculation may produce disputes. Record delivery acceptance and any invoice-portal acceptance required by the contract.

Changes need approval and effective dates. Extending terms on one sales order is a credit decision because it increases financing cost and uncertainty even if the nominal limit remains unchanged.

Use a pre-dispatch credit gate

Credit should be checked at order entry, allocation and dispatch. Exposure can change between those points as other invoices become overdue or payments arrive.

The gate should consider:

• available limit after this shipment;
• oldest overdue invoice and ageing bucket;
• broken payment promises;
• unresolved disputes;
• expired credit review or documents;
• returned or dishonoured payment;
• unusual order size or product resale risk;
• customer or group exposure;
• contractual purchase-order and delivery requirements.

Do not use one yes/no rule for every customer. A small technical exceedance on a current account may route for approval. A customer with a serious overdue balance may be blocked even below limit. Define hard stops and approval bands.

Every override should capture amount, reason, approver, expiry and conditions—for example partial prepayment or collection of a named overdue invoice. Report override performance: how much was approved, how much became overdue and which approvers repeatedly extend weak accounts.

Delivery evidence protects collection

Many “late payments” begin as documentation failures. The customer cannot process an invoice because the purchase-order number is absent, delivery acknowledgement is unreadable, quantity differs or the invoice went to the wrong portal.

Connect the order, pick, delivery and invoice. Capture:

• customer purchase order and authorised buyer;
• delivery location and time;
• item, quantity, batch or serial where relevant;
• recipient name and acknowledgement;
• shortage, damage or rejection at delivery;
• proof-of-delivery document;
• installation or service acceptance where applicable;
• invoice-submission channel and confirmation.

Resolve delivery exceptions before billing where possible. If an invoice proceeds with an exception, flag it for proactive contact rather than waiting until due date.

Oman VAT invoicing belongs inside the order-to-cash flow

Oman Tax Authority guidance states that a taxable supplier must issue a tax invoice for taxable supplies and specifies information required under the VAT framework. OTA material also describes full, simplified and, in applicable circumstances, summary invoice approaches. Requirements depend on the transaction and current rules.

The ERP should determine invoice type and tax treatment from customer, supply and value—not from whether the customer has credit terms. Credit affects collection; it does not postpone VAT obligations automatically.

Maintain supplier and customer details, tax identification, sequential number, invoice and supply dates, descriptions, quantity, taxable value, rate, tax amount, discounts and currency conversion evidence where relevant. Link credit and debit notes to the original invoice.

The OTA VAT taxpayer guide notes a general fifteen-day timing point for issuing tax invoices after the relevant event. Configure and monitor the applicable deadline rather than allowing wholesale invoices to wait for the monthly collection run.

If invoicing in foreign currency, preserve transaction currency, OMR tax amount and the approved exchange-rate source and date as required. Exchange differences on later settlement belong to accounting; they should not rewrite the original tax evidence.

Prepare the ERP for Fawtara

The Oman Tax Authority's Fawtara page describes a phased electronic invoicing model involving standardised exchange through service providers, validation and transmission to OTA. Rollout groups and technical obligations should be confirmed from current official announcements.

Preparation is not merely adding an invoice PDF. Clean:

• customer legal and tax identities;
• item and service descriptions;
• units of measure;
• tax categories and exemption evidence;
• invoice and credit-note references;
• sequential numbering;
• currency and rounding;
• delivery and supply dates;
• branch and registration data.

Store submission, validation, rejection and customer-delivery status separately from accounting-posted status. An invoice can be posted internally but rejected externally. That exception needs correction without uncontrolled deletion or duplicate numbering.

Apply receipts quickly and accurately

Cash in the bank does not reduce collection work until it is identified and applied. Integrate bank statements or import them daily. Match by customer, amount, reference, invoice, date and approved tolerance.

Use receipt states:

1. received in bank;
2. payer identified;
3. customer account confirmed;
4. invoice allocation proposed;
5. allocation approved or automatically matched;
6. exception resolved.

Do not post unidentified receipts to whichever customer needs credit headroom. Hold them in a controlled account and investigate. Record deductions separately: withholding, bank charge, short payment, discount, return or dispute. A net receipt should not silently close the gross invoice.

Send customers allocation confirmation or an updated statement where useful. This prevents finance teams from chasing invoices the customer believes it has paid.

Separate disputes from credit risk without hiding either

An invoice can be unpaid because the customer cannot pay, will not pay or has a valid operational dispute. One ageing report cannot distinguish them.

Create dispute cases linked to invoice lines with reason, amount, owner, evidence, next action and target date. Common reasons include price, quantity, delivery, damage, return, missing purchase order, VAT information and duplicate billing.

The undisputed amount should remain collectible. A customer disputing OMR 100 on a OMR 5,000 invoice should not automatically delay the whole balance.

Track dispute ageing separately and show its impact on available credit. Whether a disputed amount consumes the limit should follow policy and risk. Automatically excluding all disputes rewards customers for raising them; treating every valid dispute as delinquency conceals internal service failures.

Analyse root causes by salesperson, warehouse, item, customer and reason. Credit control improves cash flow partly by preventing invoices from becoming disputes.

Set service-level targets for each dispute category. Pricing and missing-document cases should move faster than technical quality investigations. Escalate cases with no customer response as well as cases waiting internally. When a correction is agreed, control whether the resolution requires a replacement document, credit note, return, additional delivery or commercial write-off. The collector should see the resolution and revised collectible amount immediately; the customer should receive consistent communication from sales, operations and finance.

Close a dispute only when the operational correction and accounting treatment are complete. A verbal agreement does not clear the invoice, restore the credit limit or create valid tax evidence. Retain the original claim, supporting documents, approval and final outcome so repeated causes can be prevented.

Build a collection cadence before invoices become overdue

Collection starts with correct onboarding and delivery, not the first angry call after sixty days.

A practical cadence:

• send invoice and submission confirmation immediately;
• confirm acceptance for high-value or exception-prone customers;
• issue statement before due date;
• obtain a promised date for material balances;
• remind on due date;
• escalate according to amount, age and behaviour;
• suspend or condition new orders under policy;
• route legal or specialist recovery only with authorised evidence.

Record promises to pay with amount, date, contact and notes. Measure kept promises. Repeatedly moved promise dates are a stronger forecast warning than nominal terms.

Provide collectors a work queue prioritised by exposure, ageing, broken promises and customer risk. A list sorted only by customer name wastes effort.

Forecast cash from behaviour

An invoice due next Thursday is not necessarily cash next Thursday. Build expected receipt dates from:

• contractual due date;
• customer's observed payment lag;
• accepted promise to pay;
• dispute status;
• invoice-submission acceptance;
• seasonality and known closure days;
• expected credit note or deduction;
• current block and escalation status.

Maintain base, optimistic and downside views for material accounts. Reforecast when a promise breaks or dispute emerges. Reconcile forecast to actual receipts and improve assumptions by customer segment.

Combine receivables with committed purchases, payroll, rent, VAT and other obligations. Sales growth that consumes inventory and increases receivables can reduce cash even while profit rises.

Review credit by customer group

Related stores or companies may buy through separate accounts while risk belongs to one economic group. Maintain parent-child relationships and both account and group limits. Prevent duplicate customer creation from bypassing a block.

Group exposure must not erase the legal debtor. Statements, invoices and collection actions remain tied to the correct entity. The group view supports risk decisions and escalation.

Watch concentration. A portfolio can show low average days outstanding while one customer represents a large share of cash due. Report top exposures, overdue concentration and dependency on promised receipts.

Provisioning and write-off need governance

Accounting provisions should follow the organisation's applicable financial reporting policy and professional advice. The ERP must provide reliable ageing, payment history, disputes, security, customer status and collection evidence.

Write-off does not mean deleting the invoice. Use authorised entries that preserve customer history, tax treatment, recovery status and approvals. If a later recovery occurs, link it to the written-off balance.

Keep commercial waiver, credit note, bad-debt write-off and cash discount distinct. They have different causes, approvals and potential tax consequences.

A weekly credit-control dashboard

Show decisions, not decorative totals:

• total exposure and available headroom;
• current, overdue and severely overdue balances;
• ageing migration since last week;
• orders blocked or overridden;
• largest customers and concentration;
• promises due, kept and broken;
• disputes by reason, owner and age;
• unapplied and unidentified cash;
• invoices awaiting submission or rejected;
• expected receipts for the next four to thirteen weeks;
• customers due for limit review;
• credit notes and returns awaiting completion.

Drill from every number to customer, invoice, order, delivery and action. Assign owners and decisions in the same workflow.

FAQ

Should every wholesale customer receive credit? No. Start with prepayment or cash on delivery where evidence is insufficient. Credit is a priced and controlled commercial decision.

When should an order consume the credit limit? When the company makes a meaningful commitment—typically order confirmation or stock allocation under policy—not only after invoice posting.

Should disputed invoices be removed from ageing? No. Show them separately while retaining the receivable and exposure according to approved policy. Collect undisputed amounts.

Does a credit customer need a different VAT invoice? Payment terms do not by themselves determine invoice type or VAT treatment. Apply Oman VAT invoicing rules to the supply and customer facts.

Can sales managers override a blocked account? Only within defined authority, with reason, conditions, amount and expiry. Material or repeated exceptions should go to independent credit approval.

Where a system helps

An integrated SMB ERP can reserve exposure at order, block risky dispatches, connect proof of delivery to compliant invoices, match bank receipts, manage disputes and feed behavioural cash forecasts. Sales and finance work from one customer position instead of arguing over several spreadsheets.

Explore RetailOS for SMB ERP.

Related reading: UAE Trade Licence Activities and Your ERP Chart of Accounts (KB-461) and Omnichannel Stock Accuracy (KB-464).

Sources

• Oman Tax Authority, VAT Information Sheet
• Oman Tax Authority, VAT Taxpayer Guide
• Oman Tax Authority, Fawtara E-invoicing