Cash flow & collections

Using Payment Data in Budgeting

Turn payment data into testable budget assumptions: distinguish transaction counts and averages, compare seasons and connect sales with collection timing.

What you will take away

Higher payment value does not establish higher average transaction value or individual spending.

Build scenarios from invoice count and average value using consistent tax and returns definitions.

Market statistics provide context, not the store's settlement statement or collection forecast.

“The market is growing, so increase our sales budget by the same percentage.” It sounds efficient and persuasive, but skips important questions. Does the measured activity resemble ours? Did transaction value rise because there were more transactions or because their average amount increased? Is the movement seasonal or persistent? An aggregate figure should start a discussion, not dictate a branch budget.

The Saudi Central Bank publishes weekly point-of-sale reports covering transaction counts, values and changes by activity and city. They provide external context, but are neither a merchant settlement statement nor its bank collections, and do not independently establish a particular business's market share. The following is a proposed analytical approach. Every numerical example is hypothetical, not a reported Saudi market result.

Unpack growth before turning it into a target

Suppose transaction value rises from SAR 1 million to SAR 1.1 million between comparable periods, while transaction count increases from 10,000 to 12,000. Value has grown 10% and count 20%, but average transaction value has fallen from SAR 100 to approximately SAR 91.67. Calling this “higher customer spending” would be imprecise: the average does not identify an individual's expenditure or the number of unique customers.

The movement could reflect product mix, promotions or more frequent smaller payments. To understand your business, examine invoices, units, prices and discounts internally. Do not automatically equate a payment transaction with an invoice: one invoice may be paid using several methods, while one payment may cover several orders.

Build two assumptions people can challenge

Instead of applying a broad percentage to total sales, specify volume and average invoice value. An illustrative store's base plan expects 1,200 invoices averaging SAR 150, producing SAR 180,000. A weaker scenario tests 1,080 invoices averaging SAR 145, producing SAR 156,600. The SAR 23,400 difference is not just a percentage. It follows from two assumptions whose rationale can be examined.

Define amounts consistently before comparing them. Do they include tax? Are they before or after returns? Use the same basis for both scenarios and actual performance. These examples assume a consistent basis; they are not a prescription for revenue recognition or tax calculation.

Next test whether operations can deliver the assumption. If reaching 1,200 invoices requires additional opening hours or stock that cannot arrive in time, the target is not ready for approval. Connect each assumption to an action: assortment, product availability, a specific campaign or a service improvement. Do not attribute the entire outcome to market growth.

Sales to cash is a bridge you cannot skip

Target sales can be achieved without the same amount reaching the bank during the month. Timing differs between immediate payment, credit sales and payment-provider settlements, while fees and refunds can reduce transfers. Build the collection forecast from the business's actual channel mix and terms, not national POS statistics.

For example, test the effect of a material settlement arriving early next month rather than at this month-end. That timing shift alone may leave the profit forecast unchanged, but it can make payroll or supplier payment dates more sensitive. Do not solve the gap by increasing late-month sales on paper. Show it and identify the funding source or payment timing that can genuinely be negotiated.

Keep fees distinct from sales as well. Treating the net bank deposit as sales and then deducting payment fees again reduces the result twice. Sound definitions matter before ambitious forecasts do.

Compare similar weeks, not just month names

Seasons, holidays and trading days do not occupy identical positions in every comparison period. Do not compare a major campaign week with an ordinary week and turn the difference into permanent growth. Record material events and separate new branches from branches operating in both periods, so additional selling space is not mistaken for improvement at established locations.

Budget monitoring should explain the variance: invoice count, average value, returns or collection timing. When assumptions change materially, update the forecast while preserving the approved budget for comparison, rather than overwriting it whenever a difference appears. Payment data is most valuable when it helps formulate a sharper question whose answer can then be tested against the business's own evidence.

Sources & further reading

Visit the original source to explore the concept and its wider context.

General educational content. Appropriate treatment depends on your business and accounting policies; consult your accounting professional when applying it to business records.