Receipt Capture-Channel Control Checklist

The receipt inbox is becoming a set of channels

A document can now arrive through a phone share sheet, an email inbox, a text message, a card transaction, or a lost-receipt attestation. That convenience can shorten the distance between purchase and recordkeeping, but it creates a new finance question: can the team explain where each document came from, how it was matched, and what changed before approval?

Microsoft lists July 1, 2026 as the public-preview date for a planned Business Central Expense Agent mobile feature . The release-plan page says users can share a new photo or an existing image or document from a phone, after which the agent extracts information and creates an expense entry for the user to review. Microsoft warns that planned functionality can change or may not ship as projected.

A separate PEX update published July 21 describes an Outlook-connected matching beta, submissions from previously unregistered email addresses or phone numbers, and a lost-receipt affidavit. These are vendor descriptions, not independent proof that every implementation is accurate or secure. Together, though, they are a dated signal that finance teams need controls for several intake paths rather than one.

For a broader systems view, review the ServingIntel integrated operations platform.

What a controlled receipt record should answer

A review-ready record should let a reviewer identify the channel that delivered the document, the person or system allowed to use that channel, the transaction that was matched, the source of every important field, and the exceptions or approvals that followed.

The image is one part of that record. Channel provenance, transaction context, changes, and decisions are the rest.

For neutral background and operating context, see IRS Publication 463.

An eight-control capture-channel checklist

1. Name every accepted channel

Inventory the ways receipt evidence can enter the process: mobile camera, phone share, forwarded email, monitored mailbox, text message, web upload, card feed, accounting integration, manager attachment, and missing-receipt declaration.

Give each channel an owner and a purpose. A shared card may need a different intake path from a named employee card. An automated inbox may be appropriate for emailed hotel folios but not for sensitive internal correspondence. If a channel cannot be owned, monitored, and retired, it should not quietly become part of the official workflow.

2. Authenticate the submitter without confusing identity with proof

Record the employee, account, device session, mailbox, or integration that submitted the evidence. Use an authentication step when a receipt may arrive from an address or phone number that is not already registered. Expiring codes, transaction details, and confidence thresholds can reduce accidental or unauthorized matches.

Related infrastructure planning is available in ServingIntel POS hardware guidance.

Authentication establishes who used a channel. It does not prove that the purchase had a business purpose or that the document is genuine. Keep those decisions separate so a trusted login does not become an automatic approval.

3. Preserve provenance before transforming the file

Keep the original file or message, the received time, the channel, the sender identifier available to the business, and a stable file hash. Record whether the channel compressed the image, removed metadata, converted a document, or extracted an attachment from a message.

Store the normalized copy separately from the original. A cropped, deskewed, or enhanced image may improve extraction, but it should not replace the evidence that arrived. Reviewers need to know whether they are looking at an original, a derived copy, or a later replacement.

A complementary portfolio perspective is available in the ServingIQ AI decision-log guide.

4. Match against an independent transaction

Use a card feed, bank record, approved purchase order, booking, delivery record, or other system-generated event to corroborate the expense. Compare the merchant, amount, date, currency, card or account, and location when available.

Do not let the same uploaded image create the transaction and prove it without another check. For employee-funded or cash purchases, require supporting context such as a business-purpose statement, event information, delivery confirmation, or manager acknowledgment.

5. Separate extracted facts from user edits

Mark which fields came directly from the document, which came from a transaction feed, which were inferred by software, and which a person changed. Store the before-and-after values and the editor.

Use the following resource when assigning escalation and recovery ownership: ServingIntel support resources.

Extraction is only the start of the data path. Continia's July 1, 2026 release notes describe a fix for a workflow in which receipt VAT data from an AI scanner was not copied to allocation lines. One vendor's bug does not define the whole market, but it is a useful reminder: test field mapping, allocations, tax treatment, and synchronization in addition to image recognition.

6. Give missing receipts a documented exception path

A missing receipt should not force an employee to invent a substitute or leave finance with an undocumented verbal explanation. Define when an attestation is allowed, what transaction evidence must exist, who approves it, and which thresholds require additional review.

Keep the declaration, business purpose, approver, timestamp, and supporting evidence together. If the original receipt appears later, preserve the history and mark the original as replacement evidence instead of silently deleting the exception.

For additional independent reference material, review Federal Trade Commission business guidance.

7. Detect duplicates across channels

The same receipt may arrive through email and mobile share, or be forwarded by two people. Check exact file hashes, transaction identifiers, amount and date combinations, and near-duplicate images. Prevent the second arrival from creating a second reimbursable expense.

Route ambiguous matches to review. A duplicate image can reflect a mistake, a shared purchase, a reassigned expense, or misconduct. The system should surface the collision and preserve the resolution rather than making an unexplained adverse decision.

8. Monitor the channel, not only the claim

Track unmatched receipts, auto-match rates, manual reassignments, duplicate collisions, extraction corrections, exception use, and time from purchase to complete record. Break the measures down by channel, location, and payment method.

For another practical workflow in the portfolio, read the SI Assist incident-response playbook.

These measures reveal whether convenience is improving the record or only moving work downstream. A mailbox with a high match rate but frequent wrong assignments is not performing well. A mobile path that reduces late submissions while preserving edit history may be worth expanding.

Build a channel-by-channel control matrix

For each intake path, document:

allowed users and the authentication method;
data and attachments collected;
original-evidence retention rules;
transaction-matching inputs;
fields extracted or inferred;
allowed edits and required history;
duplicate-detection logic;
the exception route and retention owner; and
metrics that trigger review.

Start with the highest-volume channel and run sample transactions end to end. Include an unreadable image, a forwarded receipt, an unregistered sender, a shared card, a duplicate attachment, a corrected amount, and a genuinely missing receipt.

For additional restaurant and senior-living technology context, consult ServingIntel News & Insights.

Keep the record useful for finance and tax review

For U.S. travel, gift, and transportation expenses, IRS Publication 463 says adequate records generally combine documentary evidence with a timely record of the amount, time, place or description, and business purpose. It also notes that computerized records can be adequate and that a receipt and surrounding record can complement each other.

That guidance is not a universal retention schedule, and rules vary by expense and jurisdiction. Finance teams should confirm requirements with their tax and legal advisers. Operationally, the lesson is straightforward: choosing a convenient intake channel does not remove the need for a complete, orderly record.

Questions to ask a provider

Can administrators limit the channel by user, group, card, or location?
How are external email addresses and phone numbers authenticated?
Is the original message or file retained before processing?
Can reviewers see the channel, sender, match reason, and confidence?
Which fields are extracted, inferred, or imported from another system?
Are every edit, rematch, approval, and replacement timestamped?
How are exact and near-duplicate submissions handled across channels?
Can a missing-receipt declaration be limited by amount or category?
What happens when a message contains unrelated or sensitive content?
Which reports show false matches, correction rates, and unresolved items?

When mapping receipt evidence into broader transaction systems, ServingIntel's guide to POS software can help teams ask where records originate and which system owns each field. Teams reviewing capture devices and store workflows can use the same control questions while exploring POS hardware .

For a final neutral reference point, consult NIST AI Risk Management Framework.

Make convenience explainable

The goal is not to force every receipt through one rigid route. It is to make every approved route explainable.

A well-designed intake process preserves the original evidence, authenticates the channel, corroborates the transaction, separates extraction from editing, records exceptions, and monitors where failures occur. When receipts arrive everywhere, finance does not need less control. It needs controls that travel with the document.