Cash Application and a 90-Day Plan to Digitize Sales

Cash application means matching every transfer that reaches your account to the invoice or invoices it pays on the day it arrives, not at month-end. Collections then knows who has actually paid and stops chasing them, any amount that arrives without a reference sits in a queue with an owner, and the owner knows how much cash is coming in over the next few weeks before committing to a large purchase. In part six every invoice got a collection calendar and a log of payment promises. This seventh and final part completes the road: three cases that confuse matching and four tools that solve them, then a week-by-week view of cash flow, then a 90-day plan for digitizing sales in an order that never stops selling for a single day.

Three cases that leave incoming money without an address

In many companies, matching receipts lives with one accountant who opens the bank statement, reads the sender's name, and remembers which customer pays in which way. The statement and the spreadsheet are good tools, and an accountant who knows that a particular customer's transfers come in under its parent company's name is real value to the business. But matching stumbles in three cases that keep recurring:

• A transfer with no reference. An amount arrives under an abbreviated name, or the name of a sister company of the customer, with no invoice number. The money sits in the account, the customer stays overdue in the aging report, and collections may call them tomorrow to chase an amount they have already paid.
• One transfer paying several invoices. The customer's accounts team bundles the month's invoices into one payment. If nobody knows exactly which invoices the amount covers, it is spread over the oldest ones by guesswork, so an invoice the customer did not mean to pay is closed while another they did pay stays open.
• A payment short of the invoice. The customer pays the invoice minus the value of a line they dispute: an item that arrived damaged, a maintenance visit they say never happened, or a quantity in a progress claim they have not approved. If the amount is recorded on its own with no reason, the difference becomes a small balance whose story nobody knows two months later.

None of this means the customer is hiding anything. Their accounts team works its own way and pays the way it always has. The answer is to give them a route that lets every transfer find its invoice, and to handle whatever is left without an address in one visible place.

Four tools that let every transfer find its invoice

• A dedicated account number per customer, if your bank offers it. If your bank provides virtual account numbers linked to your main account, give each customer its own number, printed on its invoices and statement. The transfer then identifies its sender by the number it arrived at, even if the payer wrote no reference at all. Ask your bank about the service and its terms before you build on it.
• A remittance note from the customer. Ask the customer's accounts team to send, with every transfer, a note of the invoices it pays and the amount of each, to one email address dedicated to receipts rather than to the sales rep's inbox. Print that request, and the invoice number to quote in the transfer reference, on the invoice itself and on the monthly statement, so the request travels with every document.
• A daily bank-statement import. Instead of opening the statement at month-end, each day's transactions enter the system on the day: a file downloaded from the bank's corporate portal, or a direct connection where one is available. The Open Banking Framework issued by the Saudi Central Bank focused its first version on the Account Information Service, which lets a bank's customers share their financial data securely with a third-party provider, as we explained in Open Banking in Saudi Arabia. The system then proposes a match from the invoice number in the reference, from the customer's dedicated account, or from an amount that matches a single open invoice for that customer, and the accountant approves it.
• Unapplied cash as a visible queue with an owner. Every amount whose invoice is unknown goes into one queue, not a suspense account that grows in silence. Each line has an owner who follows it and a date, and if the customer is known but the invoices are not, the customer shows in the aging report with a flag: payment received, awaiting allocation. The collection calendar stops chasing them until it is cleared, and the owner decides whether the delivery hold from part three lifts before allocation or after.

A payment short of the invoice: apply what arrived, log the difference

When a customer pays less than the invoice, do not close it and do not chase the difference before you know why. Apply the amount received to the undisputed lines, and enter the difference in the dispute log from part five with its reason, owner and date. If the dispute ends in your favour, the difference goes back into the collection calendar with its evidence, such as the signed delivery note. If it ends in a discount or a return, that is one of the cases that change the value of a supply under paragraph 1 of Article 40 of the VAT Implementing Regulations, which include a reduction agreed after the sale, so a credit note is issued that clearly references the original invoice (Article 54, paragraphs 1 and 4) no later than the 15th day of the month following the event (Article 54, paragraph 6).

The reverse also happens: a transfer larger than the open invoices, or an advance payment before delivery such as some contracting agreements provide for. The difference is recorded as a credit balance in the customer's name, shows on their statement, and is applied to their next invoice or refunded by an approved decision; it does not dissolve into the general account. Any tax treatment of an advance payment or of a balance refunded to the customer is a question for your tax adviser.

Cash flow week by week: the number before any big commitment

Once receipts are matched every day, the company holds the most accurate knowledge it has about the money coming in. A cash view gathers it into one table, week by week, over a horizon the owner chooses, a quarter for example, from three sources of inflow:

• Invoices not yet due, each in the week of its due date, calculated from the payment terms the owner set for each customer in part three.
• Recorded payment promises on overdue invoices from part six, in the week they fall due, on a separate line because they are a promise, not an entitlement.
• Disputed amounts and retentions, kept out of the forecast until the dispute is resolved or the release condition is met, on a line for information only.

Against them sits the outflow: the scheduled supplier payment run we built in the purchasing series in Paying Suppliers on Schedule and Reconciling Statements, with the supplier invoices due each week, plus fixed commitments such as payroll and rent. The gap between expected inflow and scheduled outflow in each week is the number the owner needs before signing a large purchase order or accepting a project that needs funding up front. A week that shows a shortfall a month before it happens leaves time to speed up a collection or reschedule a payment; a shortfall discovered on the day leaves nothing but a bank facility and its cost.

To keep the number honest, compare each week what you expected with what actually arrived, customer by customer. A recurring gap with one particular customer tells you how far to rely on their promises when you plan, and it is a conversation for the account manager to have with them, not a verdict on the customer.

Where AI comes in

Once the chain is in order, AI has real work to do in receipts: reading remittance notes that arrive in emails or their attachments and pulling out the invoice numbers, proposing a match for a transfer with no reference from its amount, date and how the customer has paid before, and drafting reminders in your team's voice for them to review before anything is sent.

But that value comes after the chain, not before it. Proposing a match needs a customer with one record, not three names, invoices issued from a confirmed delivery, and disputes logged with their reasons. On messy data, AI proposes wrong matches with complete confidence. And a proposal stays a proposal: the accountant approves it, and the decision stays with a person.

The Origami view

When we build the sales cycle for a company, we build matching and the cash view at the end, not the beginning. The reason is that the dashboard reads what the stations before it produce, and a dashboard built on a duplicated customer list and invoices with no link to a delivery gives elegant numbers nobody trusts, so the owner goes back to asking the accountant.

So we start with the customer record and the price list and build each station on the one before it, around how the company actually sells: who approves discounts, who signs for delivery on site, and how transfers and bank statements arrive. The cycle connects to your accounting system and e-invoicing rather than replacing them. This is part of the custom systems we build through our services.

A 90-day plan in an order that never stops selling

The temptation is to switch on the whole cycle in a single day. The order that protects day-to-day selling is the one we described in What Moves First? A Migration Order That Keeps You Trading: fixed data first, then transactions. Each stage can start with one branch or one group of customers before it is rolled out to the whole company.

• Month one: the customer record, the price list, quote approval and credit limits. The customer record is unified and duplicates are merged, and each customer gets its VAT number and commercial registration after the two free official checks from part three, its payment terms, and the person authorized to receive invoices. One price list and the discount authority from part two are approved, the owner sets each customer's credit limit, and quotes are then issued and approved in the system. Delivery, invoicing and collections carry on as before this month, so nothing stops.
• Month two: proof of delivery, the invoice from the delivery, and the dispute log. The customer signs for the delivery or the completed work on a phone, the draft invoice is generated from the confirmed delivery, and every objection gets a line with its reason and owner. The most important step this month is entering the open invoices issued before the system as opening balances for each customer with their due dates; otherwise the aging report starts incomplete from day one.
• Month three: the collection calendar, customer statements, cash application, then the cash-flow dashboard. The collection calendar starts for every invoice, the first monthly statement goes out, the bank statement is imported daily, and the unapplied-cash queue opens. At the end of the month, once every station is producing its data, the cash-flow dashboard opens.

Each stage has an announced date, set by the owner, when the old way stops: from a given date no discount goes out except through the system, and from another no invoice is issued except from a confirmed delivery. Without an announced date both ways carry on side by side, and the easier one wins. At the end of each month, review three indicators you read from the system itself: how many invoices were issued from a confirmed delivery, how many transfers were matched on the day they arrived, and how many disputes passed their date. The direction of these numbers from month to month is more honest than any target you set at the start.

Whatever existed before the system in files, email and paper is not deleted after the move. Paragraph 1 of Article 66 of the VAT Implementing Regulations requires invoices, records and accounting documents to be kept for at least 6 years from the end of the tax period they relate to. The old archive stays kept and reachable, and anything specific to your company's situation is a question for your accountant or tax adviser.

Closing the series

Over seven parts we walked the sales cycle station by station: we mapped its seven stations and where money stalls at each one, then the quote and discount authority, then credit limits and guarantees before selling on terms, then proof of delivery and the invoice that starts from it, then the on-time invoice and the dispute log, then receivables aging and the collection calendar, and finally cash application, the cash view and the plan to put it all in place.

The takeaway worth keeping: digitizing sales is not a lack of trust in customers or in the sales team. It means every riyal you are waiting for has a written route from the quote to the bank account, where everyone knows their role and the owner sees the money coming before committing, not after needing it. The start is a small step you can take this week: take last month's customer transfers, and count how many were matched to their invoice on the day they arrived, and how many are still waiting.

Sources

• Saudi Central Bank: SAMA Issues the Open Banking Framework — the first version of open banking services focused on the Account Information Service and the second on the Payment Initiation Service, with the aim of letting customers of financial institutions share their financial data securely with a third-party provider.
• Zakat, Tax and Customs Authority: Implementing Regulations of the VAT Law (official Arabic text) — Article 40, paragraph 1 (cases that change the value of a supply, including a reduction after the sale and an accepted return), Article 54, paragraphs 1, 4 and 6 (the credit note, the reference to the original invoice, and issuing it no later than the 15th day of the following month), and Article 66, paragraph 1 (keeping invoices and records for at least 6 years).