From Spend to Books: Closing the Loop Between Expenses and Accounting | Wafeq × Pemo Webinar



Every finance team knows the feeling: expenses happen in real time, but the books only catch up at the end of the month — after hours of chasing receipts, manually reconciling statements, and fixing categorization errors that could have been avoided from the start. The gap between spending and accounting is not just an inconvenience; it is a structural inefficiency that slows finance teams down, creates compliance risks, and introduces friction between departments.

In a recent webinar, Nadim Alameddine, Founder and CEO of Wafeq, and Ayham Gorani, Co-founder of Pemo, sat down to discuss exactly where this gap comes from, what it costs businesses in practice, and what a truly connected spend-to-accounting workflow looks like. Here is everything covered in that conversation.

The Problem: Spending and Accounting Have Always Been Disconnected

For most businesses, the way expenses are managed has not changed much in decades. An employee needs to pay for something — a SaaS subscription, a supplier invoice, a travel expense — and they either use the business owner's card, their own personal card, or a shared company card. At the end of the month, the finance team receives a bank statement, tries to match every transaction to a receipt, figures out who paid for what, and manually enters everything into the accounting system.

Ayham described this from personal experience. When he was running his first company in the UAE, his team of 70 employees shared a single prepaid credit card. Every time someone needed to pay for AWS, Google, or any online tool, they had to request a one-time password from him directly — during weekends, evenings, and family time. But the bigger problem was not the OTP. It was what happened at the end of the month.

"I would get the statement of my credit card, and I would have to track for every invoice, for every payment, who paid it — trying to figure out who was really paying for Facebook, who was paying for AWS, who was paying for the supermarket, and try to chase all the invoices. That process would usually take one or two days per month, and it was never accurate."

This is the reality for a significant portion of SMEs across the region. Two days of manual reconciliation per month, multiplied across a year, is a material cost — and that is before accounting for the errors, the missing receipts, and the compliance gaps that accumulate along the way.

Watch the full webinar to see the Pemo-Wafeq integration in action

Why the Gap Exists: The Structural Breakdown Between Transactions and Books

The disconnect between expenses and accounting is not caused by a lack of effort. It is caused by the way the two workflows are structured. Spending happens instantly — the moment a card is swiped or a payment is made, money moves. But accounting happens retrospectively: the finance team receives information about that transaction later, through a bank statement, an email, or a spreadsheet that someone remembered to update.

By the time the accountant sees the transaction, the context around it — what it was for, which project it should be attributed to, whether it was VAT-claimable, who approved it — has already faded. Reconstructing that context manually for hundreds of transactions every month is exactly the kind of low-value, high-effort work that modern finance teams should not be doing.

Nadim pointed out that this challenge is especially pronounced in the UAE, where open banking infrastructure is still limited. Most banks do not provide real-time transaction feeds, which means accountants have to wait for end-of-month statements rather than seeing expenses as they happen. The result is a finance function that is always operating in the past rather than the present.

Who Is Most Affected?

While the spend-accounting gap affects businesses of all sizes, it is most acute in companies that have high transaction volumes relative to their team size. Ayham noted that the correlation is not necessarily with company size — it is with industry and operating model.

Healthcare businesses, construction companies, and technology startups tend to have the highest expense volumes. A tech startup with even a small team might have 50 to 100 active software vendors: GitHub, AWS, Google Cloud, TikTok Ads, Meta Ads, LinkedIn Ads, and dozens of other SaaS tools. Each of those vendors represents a recurring transaction that needs to be captured, categorized, and reconciled every month. Managing that manually is not just slow — it is genuinely unsustainable as the company grows.

The traditional answer to this problem was to give employees access to a company credit card. But as Nadim described, that creates its own risks. What happens if the employee leaves the company and their card is still linked to an AWS account? What happens if there is not enough balance on their personal card when a subscription renews? What happens if an employee uses a company card for a personal purchase? These are not edge cases — they are daily operational realities for finance teams across the region.

The Pemo Approach: Real-Time Corporate Cards With Built-In Controls

Pemo was built to solve exactly this problem. Rather than giving employees access to a single shared card or asking them to use their own personal cards, Pemo allows businesses to issue individual corporate cards to any employee — virtual or physical — with dynamically configurable spending limits, merchant restrictions, and approval workflows.

The key distinction from a traditional bank card is programmability. A finance team can set a specific monthly limit for a specific employee, restrict the card to specific merchant categories, and change those parameters instantly without going to a bank branch or filling out paperwork. For high-risk scenarios — like a fleet manager who needs to fuel vehicles — Pemo offers prefunded cards that require approval before funds are loaded, ensuring that spending can only happen against a pre-approved budget.

This fundamentally changes the risk profile of corporate card programs. Instead of unlimited exposure on a shared card, every card in the organization has a defined ceiling. If a card is compromised — which Ayham noted is a growing risk given the rise of AI-enabled cybercrime — the maximum exposure is whatever limit was set on that specific card, not the entire company account.

The Accountant's New Role: From Reconciliation to Review

One of the most important shifts that Pemo enables is a change in what accountants actually spend their time doing. Instead of chasing receipts, manually entering transactions, and doing end-of-month reconciliation, accountants using Pemo operate in a fundamentally different mode.

Every transaction made on a Pemo card appears in real time in the Pemo platform. Employees receive an instant push notification prompting them to upload their receipt or tax invoice. Pemo's AI engine then reads the uploaded document using OCR, extracts key fields — invoice number, VAT amount, line items, quantities, supplier TRN — and automatically matches the document to the corresponding card transaction.

The AI-powered categorization engine, which Pemo calls Copilot, then automatically assigns the correct expense account, VAT code, vendor, and project based on the transaction and receipt data. By the time the accountant opens their accounting export page, the majority of the work is already done. Their job is to review, validate, and mark transactions as ready — not to build the entry from scratch.

Annas, the engineer behind the Pemo-Wafeq integration, demonstrated this in the webinar using a real transaction on the Apple App Store. The Copilot had automatically categorized the expense as an information technology expense, set the vendor as Apple, applied the correct VAT code, and generated a memo describing the transaction. The accountant's role was simply to confirm that the fields were correct and mark the expense as ready to be pushed to the books.

The Pemo-Wafeq Integration: Closing the Loop Completely

The most technically significant part of the webinar was the live demonstration of the Pemo-Wafeq integration — the moment where all of the captured, categorized expense data flows automatically into the accounting system.

When an accountant marks expenses as ready in Pemo and clicks export, the integration does several things simultaneously. It creates any new vendors in Wafeq that do not yet exist, using the merchant name and TRN extracted from the uploaded tax invoice. It pushes each expense transaction into Wafeq's cash expenses section, complete with the correct account, payment method, supplier, VAT amount, project attribution, and a copy of the attached receipt. It also pushes any associated fees — such as Pemo's international transaction fees — as separate line items under the correct account, with Pemo itself listed as the supplier.

The result is a Wafeq account that reflects actual company spending in near real time, with virtually no manual data entry. The bank reconciliation step — matching the Pemo wallet statement to the transactions already in Wafeq — is then handled automatically using Wafeq's reconciliation rules engine, which can be configured to match on reference numbers, amounts, or custom criteria.

Nadim highlighted one particularly elegant aspect of this workflow: for businesses that use automated payment tools like Stripe, expense receipts from SaaS vendors can be forwarded directly to a dedicated Pemo email inbox. Pemo reads the receipt, matches it to the transaction, categorizes it, and marks it ready for export — with zero manual intervention from either the employee or the accountant.

AI-Powered Compliance Checks: Beyond Basic OCR

One of the more sophisticated capabilities discussed in the webinar was Pemo's approach to VAT compliance and receipt authenticity. Simply capturing a receipt is not enough — the receipt needs to be a valid tax invoice, the VAT needs to be correctly calculated and claimable, and the document needs to be authentic.

Pemo's AI engine performs several layers of validation on every uploaded document. It checks whether the document qualifies as a valid tax invoice by looking for the supplier's TRN number and the correct invoice labeling. It matches the transaction date from the bank against the invoice date to detect discrepancies. It checks for duplicate invoice numbers from the same merchant to flag potential fraud. It even detects AI-generated or AI-tampered receipts — an increasingly relevant check as generative AI makes it easier for bad actors to create convincing fake receipts.

On the VAT side, the system reads the applicable VAT rate from the receipt and pre-populates the correct rate on the accounting export page. For transactions where the employee has uploaded a photo of the product rather than the actual tax invoice, the system flags this and notifies both the employee and the accountant, because a product photo is not a valid document for VAT reclaim purposes. In one example shared during the webinar, the system identified that an employee could save a specific amount in reclaimable VAT simply by uploading the proper tax invoice instead of a product image.

The AI Receipt Chaser: Removing the Biggest Operational Headache

Perhaps the most practically impactful feature discussed in the webinar was Pemo's AI-powered receipt chasing agent. Chasing employees for missing receipts is one of the most time-consuming and morale-draining tasks that accountants face. It is repetitive, it creates friction between teams, and it always seems to peak at the worst possible moment — the end of the month, when everyone is already under pressure.

Pemo has automated this entire process. When a transaction occurs, the employee receives an immediate push notification. If they do not upload a receipt within a few days, the AI agent follows up automatically. As the end of the month approaches, the frequency of follow-ups increases. For employees who continue to ignore the prompts, the system can automatically block the card — making the card itself the incentive for compliance rather than relying on the accountant to manually chase each person.

The agent also sends weekly summary emails to accountants listing which employees are not meeting their receipt submission policy requirements, allowing the accountant to take targeted action rather than sending a blanket reminder to the entire company. And crucially, when employees do eventually upload their receipts, the matching to the correct transaction is done automatically — so there is no secondary burden on the accountant to figure out which receipt belongs to which expense.

Cash Flow Forecasting: AI Beyond the Transaction Level

The conversation also touched on how AI is beginning to reshape finance management at a higher level than individual transactions. Pemo has built a cash flow forecasting feature that uses AI to predict how much money a business will need in its prepaid wallet over the next seven days, based on historical spending patterns and known upcoming payments.

Rather than requiring finance teams to manually plan their wallet top-ups — a task that Ayham acknowledged was creating unnecessary friction for customers — the system now proactively alerts businesses when they are at risk of running short, and recommends exactly how much to top up. This removes an entire category of cognitive load from the finance function and ensures that subscription renewals and recurring payments are never missed due to a depleted wallet.

Looking ahead, the Pemo team is also working on natural language reporting — the ability for accountants and finance managers to ask questions about spending data in plain language and receive structured reports in response. Rather than being limited to a fixed set of dashboards, finance teams would be able to query their own expense data the way they would query a knowledgeable analyst, getting answers tailored to the specific lens that matters to their business.

The Bigger Picture: What a Connected Finance Workflow Actually Looks Like

The core message of the webinar was not about any single feature. It was about what becomes possible when the gap between spending and accounting is closed structurally rather than patched manually.

When every card transaction is captured in real time, every receipt is collected automatically, AI categorizes every expense, and every journal entry is pushed to the accounting system without manual data entry, the finance function changes fundamentally. Accountants stop being data entry operators and start being analysts. Month-end closes stop being chaotic sprints and start being orderly confirmations of work that has already been done continuously throughout the month. VAT reclaims become reliable rather than approximate. Compliance becomes the default state rather than an end-of-period scramble.

As Nadim noted, the biggest competitor for both Wafeq and Pemo in the market today is still the Excel spreadsheet. A significant portion of SMEs in the UAE and the broader region are still managing expenses and accounting using manual processes that were designed for a different era. The tools to replace those processes now exist, they are accessible, and they are increasingly powered by AI, which makes them smarter with every transaction that flows through them.

Conclusion

The spend-to-books gap is not inevitable. It is a product of disconnected systems, manual workflows, and tools that were not designed to talk to each other. When a corporate card platform like Pemo integrates deeply with an accounting system like Wafeq, that gap closes, and finance teams get back the time, accuracy, and visibility they need to do work that actually matters.

Businesses across the UAE that have made this shift are no longer chasing receipts at the end of the month. They are reviewing clean, AI-categorized data that is already in their books, already reconciled, and already ready for reporting. See how Wafeq can connect your accounting workflow.