Email is not a workflow: getting billing and contracts out of shared inboxes

David Mensah, Developer Advocate at Auralis AI

David Mensah

November 18, 2026 · 3 min read

A laptop beside a clipboard with a to-do list
On this page
  1. What a shared inbox can’t tell you
  2. The part e-automate already handles well
  3. Getting them out
  4. Sources

In 2016 the Federal Reserve Bank of Minneapolis looked at how American businesses exchange invoices. About 24 percent went electronically in 2014, and the paper expected that to reach only 38 percent by 2024. The same paper described how smaller businesses tend to cope: they log in to a portal a bigger trading partner set up, or they accept invoices as PDF attachments by email. Plenty of office technology dealers will recognize the second one.

What a shared inbox can’t tell you

Email is good at getting a message from one person to another, and bad at tracking something that takes more than one step, like a contract renewal, a disputed invoice, or a billing question that needs someone in accounting to weigh in. Most shared inboxes have no status on a message. A question someone is working on can look just like one nobody has opened, and often the way to tell them apart is to read the thread and hope the last person left a note.

Dealers we talk to describe the result plainly: invoices and remarks go out by email, and the backlog builds. When they list the work they’d most like off the desk, meter reads and dispatch come first and contract and billing email comes last. Our read on that ranking is that it’s about what hurts most every day, so billing email isn’t small because it’s last. We suspect it waits longest because nothing about it looks urgent until the customer calls.

Dealers also tell us that work handled in tools outside e-automate creates double entry every day, and an email thread is one of those tools: whatever gets agreed there still has to be keyed into the ERP.

The part e-automate already handles well

Once a contract is ready to bill, e-automate has a proper process for it. The Contract Billing window is a live list of every contract that needs billing, built mostly from the dates on the contracts themselves. Open it and today’s date goes into the billing cutoff field, and with auto populate on, every contract with a base or overage bill date on or before that date loads in. Adding contracts to the billing queue locks them from edits until they’re fully billed, and each one moves from the Contracts tab to the Billing queue, to Ready to invoice/propose, and finally to Invoices/Proposals.

During billing, each contract sits on a defined tab that shows where it is in the process. In our experience, the renewal questions and invoice disputes that come before billing don’t get that treatment and stay in the inbox.

Getting them out

Customers should keep emailing about their bill however they like. The work is in what happens after the message lands: reading it, working out which account and contract it’s about, and getting the answer into e-automate instead of leaving it in a thread. We want Auralis to take that part off the desk for billing and contract questions, the same way it handles meter reads, toner and service calls around the clock and writes them straight into e-automate.

To see which e-automate records Auralis reads and writes, invoices and contracts included, download How do we connect to your E-Automate?.

Sources

Share this

For e-automate dealers

See Auralis on your own service desk

A 30-minute walkthrough on your workflow — meter reads, dispatch, supplies and escalation.

Book a demo
David Mensah, Developer Advocate at Auralis AI

David Mensah

Developer Advocate

David is Auralis's developer advocate, bridging engineering and the outside world with the tutorials, integration guides, and technical content that help teams build with Auralis. If you've ever connected Auralis to your stack in under an hour, you've read his work. His documentation philosophy is that the fastest support ticket is the one that never gets filed: clear guides, honest examples, and answers where developers actually look. He works directly with customer engineering teams to turn their feedback into better docs and a better product.

We use cookies to run this site and, with your consent, to analyze usage and improve our marketing. You can accept all, reject non-essential, or choose. See our Cookie Policy.