Evention Stops Growing Its Microsoft Exchange Rule Pile with Files.com Inboxes

Evention automates the back-office accounting that hospitality and retail operators still mostly do by hand: cash reconciliation, credit card reconciliation, tips and gratuities. Its software reconciles payments daily across more than 42,000 terminals, devices, and locations for major hotel brands, casinos, grocers, and convenience chains, and it pairs that software with cash-recycling machines to take manual cash counting out of the back office entirely.

None of that works without other companies' data. Evention's products run on files produced by systems its clients already operate: point-of-sale systems, property management systems, and the cash machines themselves. Those systems ship reports on a schedule, and Evention reconciles what they say against each other. Most of that data arrives over FTP and SFTP into Files.com, where roughly 600 retail and hospitality properties deliver cash-machine files into a folder structure that gives every client its own credentialed drop point, at a rate of roughly 4,000 client files a day.

But a client system can only deliver what it knows how to send. For a meaningful share of the systems Evention connects to, the only export mechanism on offer is scheduling a report to an email address. Evention does not get to choose the channel. The sender does.

Evention moved that intake to Files.com inboxes, making emailed reports part of the same automated, monitored pipeline as SFTP deliveries. It started with new clients, so hundreds of live senders did not have to be reconfigured and the Exchange rule pile stopped growing.

Fifteen Years Inside the Mail Server

For 15 years, Evention collected those emailed reports with Microsoft Exchange Online: a set of mailboxes and an ever-growing pile of routing rules directing each client's attachments into the right processing path. It worked, in the sense that files arrived. But it meant a second file-ingestion system had quietly grown up inside the mail server, carrying production data for hundreds of live clients, entirely outside the platform where the rest of Evention's client data was collected, automated, and monitored.

The cost showed up in two places. The first was maintenance. Brian Roth, Evention's Co-Founder and Chief Technology Officer, put it plainly:

“It's kind of a house-of-cards system that eventually is just going to stop working.”

The second was blindness. A routing rule can direct an email that arrives. It can say nothing about an email that does not. Evention's products depend on client systems shipping data on a fixed cadence, and when one of those systems silently stopped sending, the mailbox had no way to flag the absence.

The system survived this long because the senders were not Evention's to change. Every one of those email addresses was configured into a client's POS or event-management system, so replacing the collection point meant either forwarding the old addresses indefinitely or asking hundreds of clients to reconfigure where their systems send. So the mailboxes stayed, and every new email-delivering client added another rule to the pile. The problem was real enough that Evention had started designing its own replacement service before finding the capability already built into the platform that handled the rest of its intake.

What the Replacement Had to Do

As Evention's client base grew, so did the email channel, and each new client made a configuration with a hard ceiling harder to maintain. A real fix had to do four things: accept a file from a system whose only interface is a scheduled email, admit only the file types Evention's platform actually processes, land the file in the same per-client folder structure that FTP deliveries use, and roll out one client at a time without touching a single live sender.

Files.com email inboxes met all four, and Evention made them its collection point for emailed client data.

An Email Address That Lands in the Same Folder as SFTP

A Files.com inbox gives a folder its own email address. Evention provisions one for a client, and the client's system schedules its report to that address exactly as it once did to an Exchange mailbox. Nothing changes on the sender's side except the address.

When the message arrives, extension filtering keeps everything but real data files out. Evention's first test showed exactly why that filter matters: a single emailed CSV can arrive accompanied by every image file in the sender's email signature. With filtering in place, only the file types Evention's platform processes ever land in the folder.

From there, an emailed file is indistinguishable from one delivered over SFTP. It sits in that client's folder in the same structure, where the same Files.com Automations and webhooks that handle FTP-delivered files pick it up and hand it to Evention's ingestion code and onward into its data platform.

The rollout was deliberately incremental. Evention tested the inboxes with a couple of new clients in May 2025, then made them the standard path for every new client that delivers by email. No live sender was asked to change anything.

The Rule Pile Stopped Growing

With Files.com inboxes as the standard path, a client that can only email a report is now onboarded the same way as a client that speaks SFTP: it gets a folder and an address, not another routing rule. Three things changed.

• Emailed client data runs through the same pipeline as everything else. Same folders, same automations, same webhooks feeding Evention's downstream systems, with no separate handling for the email channel.
• Absence is detectable. Because emailed files land on the platform, the same monitoring that watches for missing FTP deliveries can watch emailed feeds too. A report that never arrives is a detectable event instead of a silent gap in a mailbox.
• Onboarding stopped compounding the risk. Every new email client used to make the Exchange configuration harder to maintain. Now each one lands on Files.com, and the failure mode Roth described no longer grows with the business.

Roth's framing of the monitoring question captures the shift:

“If you want to know when we didn't get an email from someone, you have to hook it into the Files.com ecosystem, not our janky Exchange server solution.”

One Collection Layer, However the Client Sends

Emailed data files, it turns out, belong in the file transfer layer, not the mail server. And moving them there did not require touching hundreds of live client configurations. Evention started with the next client instead of the last one, and every email-delivering client since has landed on the platform.