A Restaurant Chain Automates Invoice Intake From Every Company-Owned Location Into NetSuite With Files.com

A US restaurant chain runs dozens of full-service restaurants and bars, with thousands of people working in them.

What makes the chain unusual at that size is that it has never franchised. Every location is company-owned and directly managed. There are no franchisees keeping their own books, which means the paperwork of every restaurant belongs to one corporate back office. Every invoice a location receives is corporate's to process.

An ERP in the Cloud, Invoices at the Stores

The company runs that back office on NetSuite, a single cloud ERP at corporate. The documents NetSuite processes start somewhere else entirely: at the restaurants, where invoices arrive and get scanned, at every location, continuously.

When the company deployed NetSuite, that gap was the problem. Between a scanner in a store and an ERP in the cloud, something has to carry the file, and the default something is a person. At the scale of dozens of restaurants generating paperwork every day, hand-carrying documents into an ERP is a standing labor cost. The company designed the deployment so files would pass into NetSuite automatically instead, eliminating the need for corporate staff to collect and feed them into the ERP.

Building that channel in-house is real infrastructure work. It means an always-on SFTP endpoint reachable from every location, identity and accounts for the people submitting, and a reliable machine handoff into the ERP at the far end. A restaurant company can stand all of that up itself and then operate it indefinitely. But the chain's IT team was delivering an ERP rollout, not building a file-transfer platform.

What the deployment needed was a managed cloud SFTP endpoint that every restaurant could reach and NetSuite could consume, with identity coming from the Microsoft directory the company already ran. The company selected Files.com to be that layer.

SFTP From Every Restaurant, Service Accounts Into NetSuite

The chain's IT team deployed one consistent submission path across the chain. Each restaurant sent its scanned documents over SFTP to the same Files.com endpoint, no matter which store they came from.

Microsoft Entra ID supplied identity through the corporate SSO the company already used, avoiding a separate list of file-transfer accounts for IT to maintain. On the ERP side, service accounts connected Files.com to NetSuite so documents could pass into the ERP for processing. The handoff was machine to machine.

From Store Scanner to ERP With Nobody in Between

With the pipeline in production, the store-to-corporate document flow runs the way it was designed to: automatically, end to end.

• Invoice intake runs without hands on it. A restaurant scans and submits, the document passes into NetSuite for processing, and nobody at corporate collects files or feeds them to the ERP by hand.
• The company runs no file-transfer infrastructure of its own. There is no SFTP server for IT to operate and patch, and no integration middleware to maintain. Files.com is the endpoint the stores reach and the handoff NetSuite consumes.
• Access stays aligned with the company directory. With Entra ID SSO, a corporate directory account is the file account, with no separate set of credentials for IT to maintain.
• The pattern scales with the chain. A new restaurant is another submission point on the same endpoint, and nothing changes downstream. NetSuite keeps consuming from the same place.

Every Location a Submission Point

Because the chain never franchised, corporate carries the administration of every restaurant the company opens. What changed with Files.com is what that carrying costs. Someone at a store scans an invoice and their part is done; the file crosses to NetSuite on its own. The processing happens inside the ERP rather than in a pile of incoming documents.

Any multi-location operator putting a cloud ERP at the center of its back office faces the same gap between where documents originate and where they are processed. The chain closed it without building or operating its own file-transfer infrastructure: each location became a submission point, and Files.com does the carrying.