Finance managers consistently underestimate the time cost of manual accounts receivable reconciliation. The common estimate is something like "a couple of hours a week," which understates the actual time and misses the indirect costs that make manual reconciliation significantly more expensive than it looks.
We spent time during our early-access pilot asking finance teams to track their actual AR time, not their estimated time. The numbers were consistently higher than their initial estimate, sometimes by a factor of two. That gap between estimate and reality is not because finance teams are inefficient. It is because reconciliation time is fragmented and diffuse: distributed across email threads, bank statement reviews, follow-up calls, and spreadsheet updates in a way that never shows up as a single uninterrupted block that can be accurately timed.
Where the Hours Actually Go
Manual AR reconciliation for a team handling 50 to 150 active client accounts in Saudi Arabia typically involves the following distinct activities, all of which cost real staff time:
Bank statement review and matching. Incoming IBAN transfers arrive with varying degrees of payment reference quality. Some clients include your invoice number. Some include their own reference. Some include nothing identifiable. For a team with 80 active accounts, a typical week might have 15 to 25 payments arrive. Matching each payment to an open invoice requires someone to review the transfer details, look up the corresponding client account, verify the amount, and close the invoice. When the reference is unambiguous, this takes 2 to 3 minutes per payment. When it is not, the investigation can run considerably longer.
Discrepancy investigation. A client who paid SAR 12,400 against an invoice for SAR 12,750 has a SAR 350 discrepancy that needs resolution. Was it a bank fee deducted from their end? A discount they believed they were entitled to? An error in the invoice amount? Resolving a single discrepancy typically requires an email or phone exchange and a check against the client record. At 5 to 8 discrepancies per month, this is several hours of back-and-forth cumulatively.
Aging report production and review. Producing a manual aging report means someone extracting data from a spreadsheet or an accounting system, categorising open invoices by overdue duration, and reviewing the output to decide on collection priorities. For a team doing this weekly, the production step alone takes 30 to 90 minutes depending on the state of the underlying data.
Status updates for other stakeholders. Finance teams in growing organisations regularly field requests from sales, account management, and leadership for the current payment status of specific clients. Each inquiry requires a lookup, and the cumulative time spent on ad hoc status updates is rarely counted in time estimates but adds up meaningfully.
A Realistic Time Estimate for a 2-to-10 Person Finance Team
For a finance team of two to three people handling 80 to 120 active accounts with a mix of project-based invoicing and recurring subscriptions, a realistic estimate of direct AR reconciliation time is in the range of 6 to 12 staff hours per week. That is not an extreme case. It is the baseline for a moderately active invoicing volume without unusual complexity.
At a fully-loaded labour cost of SAR 35 to 50 per hour for a finance coordinator-level role in Riyadh (including benefits and overhead), that translates to SAR 210 to 600 per week in direct labour cost for the reconciliation activity alone. Over a full year, that range is SAR 11,000 to 31,000 in labour cost for a single process that is, in principle, fully systematisable.
This is a lower-bound estimate. It does not include the error rate. Manual processes produce errors, and errors in AR reconciliation are not free. An invoice marked paid that is not paid is a receivable that ages without anyone chasing it. An invoice marked outstanding that has already been settled generates unnecessary reminder messages, which damage client relationships and create additional back-and-forth to resolve. The indirect cost of these errors, in staff time to investigate and in client-relationship friction, is real even if it is difficult to quantify precisely.
The Spreadsheet Trap
The most common reconciliation tool for teams in this size range is still a spreadsheet, often combined with an accounting system that lacks bank-transaction matching. The spreadsheet works as an AR tracking layer: open invoices, expected payment dates, payment status, and notes. The problem is that the spreadsheet is always a snapshot of the moment it was last updated, and the update burden falls on the human who owns it.
In practice, this means the spreadsheet is frequently out of date. A payment that arrived two days ago has not been matched yet. A client who called to discuss their overdue invoice left a note in an email thread, not in the spreadsheet. A partial payment was entered in a way that does not make the outstanding balance immediately visible.
The person who can read the spreadsheet accurately is the one who also carries the context that supplements it. When that person is unavailable, the spreadsheet is misleading. Teams learn this over time and develop informal habits to compensate: calling the person to ask, adding narrative notes, or simply re-verifying the status before relying on it. Each compensating behaviour adds time and does not fix the underlying problem.
What ZATCA's E-Invoicing Mandate Changes
For VAT-registered businesses in Saudi Arabia, the ZATCA Fatoora e-invoicing mandate creates a data trail that should, in principle, simplify reconciliation. An invoice with a UUID and a QR code is a uniquely identifiable document. If the payment reference in an incoming transfer matches the invoice UUID or invoice number, the match is unambiguous.
The catch is that payment reference discipline on the client side is still largely manual. Saudi B2B bank transfers do not automatically populate a reference from the invoice. The client's accounts payable team has to manually enter a reference when initiating the transfer, and many do not. Until SADAD integration becomes standard across a company's client base, a significant portion of incoming transfers will still arrive with insufficient reference information to match automatically.
SADAD biller codes change this for clients who use corporate internet banking with a SADAD-registered biller. When a client pays through SADAD, the biller code and a customer reference are both captured, giving the receiving company a structured match path. For a business with a substantial portion of clients paying through SADAD, the reconciliation workload drops considerably.
The Decision to Automate Reconciliation
The decision to move from manual to automated reconciliation is not primarily a cost decision in the short term. An automated system requires setup time, integration work, and a period of parallel running while the team builds confidence in the matching logic. For a very small team with a stable and small client base, the payback period might be long.
The trigger for most finance teams is not reaching a specific account-count threshold. It is reaching the point where the manual process is causing visible problems: reminders going out incorrectly because payment status is stale, aging reports that management does not trust because of known gaps, or a recent quarter where a significant receivable was identified late. At that point, the question is not "is automation worth it" but "what is the fastest path to a reliable process."
The design principle we work from is that reconciliation should be the least interesting part of a finance team's week. It is a matching problem, not a judgment problem. Judgment belongs in decisions about payment terms, escalation thresholds, and client-relationship management. The matching work is the overhead that automation is good at absorbing.