SAP Concur, expense fraud, and the deeply annoying fact that the most boring document in your life became a trust problem
Greetings dear readers!
I write to you from the glamorous intersection of expense reports, AI fraud, missing receipts, and the quiet administrative dread that arrives every time someone says, “Can you upload the itemized version?”
This week I have been thinking about receipts.
I know.
Try to contain yourself.
Receipts are not supposed to be interesting. Receipts are supposed to be the little paper thing you throw away after buying toothpaste, or the email you ignore after renewing some software subscription you fully intended to cancel three months ago.
They are not supposed to become a viral AI fraud issue.
And yet here we are.
Because apparently the future did not arrive in a silver jumpsuit. It arrived as an AI-generated fake steakhouse receipt submitted through an expense report.
Which, honestly, feels about right.
The boring document is no longer boring
For most of modern financial life, receipts had one job: prove that something happened.
You bought lunch.
You took a taxi.
You stayed at a hotel.
You paid for software.
You ordered supplies.
You went to a client dinner that may or may not have included one emotionally ambitious appetizer.
The receipt was the proof.
Not exciting proof. Not glamorous proof. But proof.
And that worked because receipts were annoying enough to fake that most people didn’t bother unless they were already committed to being a problem.
You had to edit something. Photoshop something. Reuse something. Find a template. Create a fake merchant. Make it look plausible. Maybe mess with a PDF. Maybe print and scan it again like a tiny office criminal in a low-budget corporate thriller.
There was friction.
AI removed the friction.
That is the part that matters.
The issue is not that artificial intelligence invented expense fraud. People have been lying about business expenses since the first person realized “client dinner” sounds more legitimate than “I was hungry and the company card was available.”
The issue is that AI makes the lie cheaper, faster, and prettier.
SAP Concur has already said its Verify AI receipt detection flagged about 1% of reviewed receipts as potentially AI-generated, including receipts created with tools such as ChatGPT, Gemini, and Stable Diffusion. The company also framed the issue clearly: AI is not necessarily increasing the frequency of fraud, but it is changing how fraud happens.
That sentence should make every finance team sit up slightly straighter.
Because 1% sounds small until you remember how many receipts pass through corporate expense systems.
One percent of your personal receipts is annoying.
One percent of a global company’s expense receipts is a compliance headache wearing comfortable shoes.
This is not really about fake receipts
The headline is fake receipts.
The real issue is trust.
That is why this is interesting. Not because someone can now generate a fake burrito receipt with suspiciously realistic tax lines. That is silly, yes, but silliness is rarely the whole story.
The deeper issue is that we used to trust documents because they looked like documents.
That world is ending.
A receipt that looks real may not be real.
A PDF that looks official may not be official.
An invoice that looks boring may be synthetic.
A reimbursement claim that looks normal may be fiction with formatting.
This is where everything gets a little uncomfortable.
Because most human review depends on visual trust. You look at the receipt. It has a logo. It has a date. It has a merchant name. It has tax. It has a total. It has the tired little layout of something produced by a payment terminal that has never known joy.
Fine. Approved.
But AI is very good at making things look boring.
And boring is dangerous because boring gets waved through.
Nobody wants to spend fifteen minutes investigating a $42 lunch receipt unless the universe has been very cruel to them professionally.
So the fake receipt does not need to be perfect.
It just needs to be dull.
That is the nightmare.
“Do not trust your eyes” is now finance advice
There was a line in the Financial Times coverage of this issue that stuck with me: SAP Concur’s Chris Juneau said companies are being told not to trust their eyes when it comes to AI-generated receipts. The same reporting noted that AppZen saw AI-generated receipts account for about 14% of fraudulent documents submitted in September 2025, up from none the previous year.
“Do not trust your eyes” is such a bleakly perfect sentence for 2026.
It sounds like something from a spy movie, except the spy movie is about reimbursement policy.
But it captures the shift.
Manual review used to be the defense. Now manual review is becoming the weak point.
Not because finance teams are incompetent. They are not.
Because the object changed.
The receipt used to be a record. Now it can be a generated artifact.
That means the system cannot stop at “does this look right?”
It has to ask better questions.
Does this match the transaction?
Does the merchant make sense?
Does the timing make sense?
Does the metadata make sense?
Does the amount fit the pattern?
Is this duplicated?
Is this policy-compliant?
Was this receipt captured from the source, or uploaded later as an orphaned image with a charming backstory?
Yes, I am aware that “orphaned image with a charming backstory” sounds dramatic.
But finance systems are full of them.
SAP Concur is not randomly relevant here. SAP Concur is the signal.
This is where SAP Concur matters.
Not as a random SEO keyword. Not as a “let’s shove enterprise software into the article and hope Google claps” situation.
SAP Concur matters because it shows where the grown-up version of this problem is going.
In March 2026, SAP Concur announced new AI capabilities including an Expense Automation Agent that can automatically create and populate expense reports, and an Expense Pre-Submit Audit Agent that validates receipts and flags discrepancies before submission. These tools are meant to reduce manual effort, catch issues earlier, and prevent reimbursement delays.
That is the interesting part.
The enterprise world is not saying, “Everyone should try harder to manage receipts.”
It is saying, “This workflow is too manual, and the manual parts are breaking.”
Exactly.
Expense reporting has always been a little ridiculous.
You travel for work. You pay for things. You attend meetings. You buy meals. You take cars. You maybe buy emergency chargers because your phone is dying and apparently modern life is just a series of battery negotiations.
Then later, when all context has evaporated, you sit down and try to reconstruct your spending like a forensic accountant with jet lag.
What was this meal?
Who was there?
Was this business-related?
Was this within policy?
Where is the itemized receipt?
Why does the credit card charge not match the total?
Did you tip?
Was alcohol included?
Why did you wait 38 days?
Why are you like this?
The answer is usually: because the system made the correct behavior too annoying.
That is not a morality issue.
That is a design issue.
The old expense workflow is basically a tiny obstacle course
Let’s be honest about how expense tracking usually works.
Spend money.
Get receipt.
Lose receipt emotionally, spiritually, or physically.
Promise to deal with it later.
Do not deal with it later.
Receive reminder.
Open expense tool.
Forget business purpose.
Search inbox.
Download PDF.
Upload PDF.
Pick category.
Pick wrong category.
Submit.
Get rejected.
Say something unprintable.
This is not a workflow.
This is a trap with dropdown menus.
And companies know it. That is why systems like SAP Concur are moving toward more automation, earlier validation, and fewer manual steps.
The goal is not to make employees better at receipt paperwork.
The goal is to make receipt paperwork less dependent on employee memory in the first place.
That distinction matters.
Because memory is a terrible financial system.
The real problem starts before the expense report
Most people think the expense report is where the problem happens.
It is not.
The problem happens at capture.
That is the moment the whole system either works or breaks.
A receipt appears. What happens next?
If the receipt is captured immediately, you have evidence.
If it is routed properly, you have a record.
If it is connected to context, you have meaning.
If it is reviewed later, calmly, you have control.
But if the receipt floats away into inbox sludge, wallet lint, camera roll chaos, or a vendor portal you will never log into again, then the whole system begins to degrade.
This is true for corporate expense reports.
It is also true for freelancers, consultants, small business owners, creators, and anyone who has ever said, “I’ll organize my receipts before tax season,” with the misplaced confidence of someone who has learned nothing from being alive.
The issue is not whether receipts exist.
They usually exist.
Somewhere.
The issue is whether they are usable.
A receipt you cannot find is not a receipt. It is a rumor.
Everyone has an expense management problem now
Large companies have SAP Concur.
Everyone else has Gmail.
That is the class divide of financial operations.
Enterprises have approval flows, corporate cards, travel policies, audit rules, finance teams, fraud detection, reimbursement systems, and increasingly AI agents trying to prevent humans from turning expense reports into group suffering.
Individuals have inboxes.
And honestly, the inbox is not a bad place to start. It is already where most modern receipts go.
Amazon. Uber. Delta. Apple. Google. Adobe. Shopify. Stripe. Square. SaaS tools. Parking apps. Delivery platforms. Hotels. Airlines. Restaurants. Subscription software. Random online purchases made at 11:43 p.m. by a person who believed, briefly, in optimization.
The data is already arriving.
The failure is routing.
This is the part I keep coming back to.
Most people do not have a receipt problem.
They have an intake problem.
The receipt exists, but it never enters a system.
So when tax season arrives, or a reimbursement is due, or a business expense needs to be reviewed, everyone acts surprised that the financial evidence has scattered itself across twelve platforms like it was raised by wolves.
AI fake receipts make clean records more valuable, not less
There is a very wrong conclusion people could draw from this whole AI fake receipt situation.
They could say: “Well, if receipts can be faked, then receipts are meaningless.”
No.
Receipts are more important now.
But the standard is higher.
The old standard was: keep the receipt.
The new standard is: maintain a trustworthy record.
That means the receipt should not just sit somewhere as an image. It should be connected to transaction data, merchant information, date, amount, category, payment method, business purpose, and retrieval.
In other words, the receipt is no longer just proof.
It is one piece of a financial evidence system.
This is why I think the SAP Concur developments are useful beyond enterprise expense management. They point to a broader reality: the future of receipts is not storage. It is validation.
Not “where did I put this?”
But “does this record make sense?”
Not “did I keep the PDF?”
But “can I trust the transaction trail?”
Not “can I upload something?”
But “can the system catch the issue before it becomes someone else’s problem?”
That is the shift.
Freelancers should care about this too
I know this sounds corporate.
It is not only corporate.
If you are a freelancer, self-employed person, small business owner, consultant, creator, or anyone who files business expenses, this is very much your problem too.
Not because you are submitting fake receipts.
Please do not do that. Boring crimes are still crimes.
You should care because the value of clean documentation is rising.
Income is often automatically reported. Platforms, payment processors, invoices, 1099s, bank deposits — there is usually a record of money coming in.
Expenses are different.
Expenses depend on you.
If your expenses are under-documented, your business may look more profitable than it actually was. If your business looks more profitable than it actually was, you may pay taxes on money you did not really keep.
This is the deeply irritating part of small business finance.
The money you earn gets tracked.
The money you spend to earn it has to be defended.
So yes, receipts matter.
Not because receipts are glamorous.
Receipts are the opposite of glamorous. Receipts are what glamour leaves behind when the lighting is turned off.
But they matter because they are evidence.
And evidence is what keeps your financial life from turning into vibes.
The correct system is not more complicated
This is where people overcorrect.
They see a problem and immediately try to build a cathedral.
A spreadsheet.
A dashboard.
A folder structure.
A tagging system.
A naming convention.
A monthly reconciliation ritual.
A beautiful Notion template that becomes decorative shame by week three.
Please do not become a Victorian archivist of your own receipts.
The goal is not to make the system impressive.
The goal is to make it survive.
That is the problem with a lot of receipt management advice. It assumes the answer is more effort. More discipline. More categories. More precision. More admin. More tiny acts of responsible suffering.
No.
The correct system is usually simpler.
Capture first.
Organize automatically.
Review calmly.
That’s it.
That is the whole thing.
The first move is not categorization. Categorization comes later.
The first move is capture.
Because if the receipt is not captured, nothing else matters.
This is where Forward Receipts fits
Forward Receipts is built around one behavior that actually survives contact with real life:
Forward the receipt.
Not because forwarding a receipt is spiritually profound.
It is not.
It is a small, boring action. That is why it works.
The receipt arrives while the context is still fresh. You forward it. The system captures it. The evidence stops floating around your inbox pretending it is “technically available” when we all know that means absolutely nothing under pressure.
Forward Receipts is not trying to be SAP Concur for giant companies with global travel programs, approval chains, corporate card policies, and finance teams named Brenda who can sense policy violations through walls.
That is not the point.
The point is that the underlying principle is the same.
Money needs systems.
Receipts need routing.
Evidence needs structure.
And the correct action has to be easy enough that people actually do it.
That is the part most financial tools still get wrong. They are designed as if the user is sitting peacefully at a desk, hydrated, organized, and emotionally available to categorize expenses.
That person does not exist.
The real user is busy, distracted, under-caffeinated, in motion, switching between tasks, answering emails, maybe trying to remember whether the thing they bought was for work or life or some doomed overlap of the two.
A good system respects that.
The receipt is the first domino
This whole AI fake receipt issue feels futuristic, but the operational lesson is actually very old.
Bad inputs create bad systems.
If the receipt is fake, the report is compromised.
If the receipt is missing, the deduction is weaker.
If the receipt is uncategorized, the data is messy.
If the receipt is delayed, the context decays.
If the receipt is scattered, the record is incomplete.
If the receipt cannot be retrieved, the system is broken.
Everything starts at the receipt.
That is why SAP Concur is pushing receipt validation earlier in the process. The Expense Pre-Submit Audit Agent is designed to check receipts and flag discrepancies before submission, not after the whole thing has already become a rejection loop with feelings.
This is good system design.
Catch problems early.
Reduce rework.
Prevent garbage from moving downstream.
The same logic applies to personal and small business finance.
Do not wait until tax season to find out your receipt system is imaginary.
Do not wait until reimbursement is rejected to care about itemized records.
Do not wait until your accountant asks for proof to begin your archaeological dig through Gmail.
Build the intake layer first.
Fraud is the scary version. Leakage is the everyday version.
Expense fraud gets attention because it sounds dramatic.
AI fake receipts. Synthetic documents. Corporate reimbursement schemes. Finance teams fighting robots with robots.
Very cinematic.
But most people are not losing money because of dramatic fraud.
They are losing money through leakage.
A reimbursable expense never submitted.
A tax-deductible receipt never captured.
A subscription that renews for six months too long.
A business purchase with no record.
A return window missed.
A duplicate charge ignored.
A software tool bought for a project that no longer exists.
A “temporary” expense that quietly became permanent.
This is less exciting than fraud.
It is also much more common.
Financial leakage is what happens when money leaves without creating a usable record.
That is the real enemy for most people.
Not villainy.
Blur.
The finance leaders are nervous for a reason
SAP Concur’s 2026 fraud discussion points to a larger confidence gap in finance operations. According to its summary of the IFOL Finance Leaders’ Fraud Report 2026, only 22% of finance leaders said they feel very well protected against fraud, down from 32% the previous year. The same article said 19% of organizations experience fraud frequently, while another 33% experience it occasionally.
That is not a small vibe shift.
That is a sign that fraud is becoming harder to see.
And if fraud is harder to see at the enterprise level, with all the software and policies and controls and compliance teams, then individuals should not assume their personal receipt chaos is somehow fine because “it’s probably in my inbox.”
Probably is not a system.
Probably is a future problem wearing a hoodie.
What changes now
The receipt era is changing.
I realize that is a deeply strange sentence.
Nobody wants to live through a “receipt era.” Nobody asked for this. We were promised flying cars and instead got AI-generated Chili’s receipts.
But here we are.
The old receipt era was about keeping proof.
The new receipt era is about building trust.
That means:
Capture receipts early.
Keep them centralized.
Make them searchable.
Connect them to transactions.
Attach business purpose while the context still exists.
Use automation where possible.
Do not rely on visual review alone.
Do not treat receipts as clutter.
Do not treat tax season as a personality test.
This does not mean you need to become obsessive.
Actually, please don’t.
The point is not to spend your life lovingly maintaining financial documentation like a tiny museum curator of your own spending.
The point is to design a system so you do not have to think about it so much.
Final thought: the receipt is where the money tells the truth
Money is abstract until it leaves.
Then it becomes a transaction.
And a transaction without a record is just a little disappearance.
That is why receipts matter. Not because they are interesting. They are not. Most receipts look like they were designed by a printer having a personal crisis.
They matter because they are the first layer of financial truth.
SAP Concur is solving this at enterprise scale with AI-powered expense automation, receipt validation, and fraud detection.
Forward Receipts is built from the same basic insight at a smaller, more human scale:
Capture the receipt before it disappears.
Do not wait until later.
Later is where receipts go to become lies, mysteries, or tax-season punishments.
Forward the receipt when it arrives.
Let the system hold the evidence.
Then get on with your life.
That is the whole point.
Not more discipline.
Less chaos.
Not more admin.
Better routing.
Not a heroic financial personality transplant.
Just one small default that makes the rest of the system work.
Forward the receipt.
Start there.
