Phone: 0 (552) 380 25 25  |  Weekdays 10:00–18:00 · Technical support 24/7

🇹🇷 TR

Digital Bridge Blog

Business Email & Documents

Accounts Payable Inbox: How to Run a Shared Invoice Mailbox Without Losing a Single Invoice

An accounts payable inbox needs one address, a named owner and a visible status for every invoice. This operating model stops invoices going astray.

9 min read  · Digital Bridge Engineering Team
Accounts Payable Inbox: How to Run a Shared Invoice Mailbox Without Losing a Single Invoice

An accounts payable inbox is a single shared mailbox where every supplier invoice arrives, and where each email is given a named owner and a visible status: received, under review, awaiting approval, posted, paid. Run properly, it sharply reduces the risk of an invoice being forgotten in someone's personal inbox, booked twice or paid after its due date.

Why invoices go missing

In most companies invoices do not arrive through one door. One supplier emails the PDF to the buyer who placed the order; another sends it to the finance manager's personal address; subscription invoices keep landing in the mailbox of someone who left two years ago. Even where an invoices@ or accounts@ address exists, the password is usually shared and nobody can say who is looking at what.

The symptoms are familiar. "Who picked up this invoice?" gets asked several times a week. A message marked as read tells everyone that somebody is dealing with it, when often nobody is. When the supplier chases payment, the team hunts for the original, asks for a copy if they cannot find it, and now risks booking the same invoice twice.

This article is about the invoice workflow inside a shared mailbox. For the general case against password sharing and how to structure access, see our guide to shared mailbox management; for per-person rights in detail, read mailbox permissions and delegation.

What an unmanaged AP inbox really costs

Invoicing in Türkiye has gone electronic at speed, yet that has not emptied the finance team's inbox. According to the Turkish Revenue Administration (GİB) 2025 Annual Report, the number of e-Invoices issued each year rose from 534,971,392 in 2021 to 1,188,605,103 in 2025, and 11,523,831,577 e-Archive invoices were issued in 2025 alone. e-Archive invoices go to buyers who are not registered for e-Invoice, and they are usually delivered by email. Foreign supplier invoices, subscription invoices and statement reconciliation requests land in the same inbox.

The channel is fragmented too. The same report shows that 1,848,492 e-Invoice users work through private integrators (licensed third-party service providers), while only 1,988 connect their own systems directly to GİB. So even when the legal invoice sits on an integrator's portal, the "your invoice has been issued" notification and a PDF copy usually still arrive by email. In practice, the mailbox is the front door for invoice traffic.

The real cost of an uncontrolled inbox, though, is payment security:

The FBI's Internet Crime Complaint Center (IC3) recorded 24,768 business email compromise (BEC) complaints in the US in 2025, with reported losses of $3.05 billion. (FBI IC3 2025 Internet Crime Report)

A fake invoice, or a genuine one with altered bank details, is one of the most common tools in these attacks. If nobody records who looked at an invoice, what they checked and who approved it, a fraudulent one simply blends into the normal flow. We cover the attack itself in fake invoice email scams and bank detail change fraud; the aim here is an operating model that applies those checks as a matter of routine.

Then there are the quieter costs: missed early-payment discounts, late-payment interest claims, hours spent on the phone with suppliers asking whether their invoice has been approved yet, and a month-end close that will not close.

A seven-step operating model for your accounts payable inbox

  1. Publish a single intake address. Tell every supplier in writing that invoices go only to invoices@, and print that address on purchase orders and supplier records. Anything sent to a personal address is forwarded there, with a polite redirect note back to the sender.
  2. Give people their own access, not a shared password. Everyone signs in as themselves. Viewing, replying and deleting are separate rights, so a trainee can sort the inbox without being able to delete an invoice.
  3. Tag every email by type. Invoice, credit note, payment reminder, statement request, supplier query, other. The tag decides who picks the email up; AI-assisted email classification and triage speeds up this first sort.
  4. Assign every invoice an owner. Keep the rule simple: by supplier group, by department or by value band. "Read" is not the same as "assigned".
  5. Keep the status on the email itself. Received → under review → awaiting approval → posted to ERP → paid. When the status and notes live on the message, the answer to a supplier's chase is one glance away.
  6. Catch duplicates and risky invoices at the door. A second email carrying the same invoice number and supplier tax ID is flagged; any message mentioning a change of bank details goes to a separate approval step.
  7. Spend ten minutes a day on ageing. List everything that has been unowned or stuck in the same status for more than two working days, and move anything close to its due date to the top.

Personal inboxes, shared password, managed shared inbox: a comparison

Control pointScattered across personal inboxesaccounts@ with a shared passwordShared inbox with individual access
Where invoices arriveUnclear, depends on the personOne placeOne place
Who is handling itOnly that person knowsUnclearVisible through assignment
Status trackingMemory or a spreadsheetThe "read" flagTags and notes on the email
Deletion and audit trailNobody knowsUnknown who deleted whatDeletion is a separate right, action log kept
When someone leavesInvoices vanish with the mailboxPassword must be changedAccess removed, history kept
Evidence for auditorsTakes days to gatherIncompleteRecorded on the email

What happens to invoices when a colleague leaves is a risk in its own right; we walk through it step by step in offboarding email access.

From inbox to ERP: stop retyping the data

Tracking the email is only half the job; the other half is not keying the PDF into your ERP by hand. Amounts, due date, tax ID and invoice number can be captured automatically through OCR invoice processing or read from the e-Invoice XML. For invoices that arrive through Türkiye's e-Invoice system, proper e-Invoice integration can take email out of the loop entirely.

The attachment should not stay in the mailbox either. Once an approved invoice PDF is filed in a document area organised by supplier and period, auditors get what they ask for in minutes; we describe that flow in saving email attachments to document storage. After payment, matching the bank transaction back to the invoice can be automated as well, as covered in bank reconciliation automation.

To understand which invoices will keep coming by email, it helps to know the difference between e-Archive and e-Invoice; our short explainer on the e-Archive invoice in Türkiye covers it.

How we approach this at Digital Bridge

We do not install a boxed product and walk away. We start by mapping how an invoice actually travels through your business today.

  • Discovery and requirements. With your finance and purchasing teams, we map which addresses invoices have arrived at over recent months, how many hands each one passes through and where it waits longest. The tag list, assignment rules and approval steps are written from that map.
  • Pilot. We start with one supplier group or one legal entity. The shared inbox, tags and assignment rules go live; after a few weeks we review with your team how many emails were left unowned and how long each invoice took.
  • Data capture and integration. For PDF and scanned invoices we set up document OCR and feed the extracted data into your ERP system. We work with Logo, Mikro, Netsis, SAP and bespoke ERPs, and build the connection as part of our system integrations work.
  • Automating the repetitive steps. For jobs such as downloading invoices from an integrator portal or preparing the payment run, we assess RPA process automation, but we use an API first wherever one exists.

How the invoice inbox works in Smart360

Our own Smart360 product family brings business email, document management, an AI website agent, card access control, project management and e-commerce together under a single identity (SmartID) and one admin panel. In the invoice inbox the work runs through two of them: SmartMail shared mailbox management on the email side and SmartFiles document management on the document side. Much of the model above comes ready to use, with no server to install.

Here is a concrete scenario. A supplier invoice lands in invoices@. SmartMail automatically classifies it as invoice/payment and summarises it.

Attachment analysis shows the parties, issue and due dates, subtotal, VAT, grand total, invoice number and tax ID from the PDF without anyone downloading the file. The email is assigned to an AP specialist on the assignment board, who leaves a note ("posted to ERP, awaiting approval") and can flag it for a colleague if needed.

Each mailbox has nine separate permissions; deletion and quarantine management are switched off by default on new assignments, and every message carries a log of the actions taken on it. Every incoming email goes through identity, structure and content checks, including SPF/DKIM/DMARC, lookalike domains, Reply-To mismatches and signs of changed bank or payment details, and the verdict comes with a written explanation. Once approved, the invoice attachment is saved to the finance area in SmartFiles with one click; uploading a file with the same name creates a new version rather than overwriting the old one.

Mailbox access follows department membership, so anyone who leaves the department loses access automatically. Several companies' invoices can be handled from one account without any of them seeing another's data. That set-up suits sectors that handle high volumes of supplier invoices, such as accountancy practices, logistics and import-export firms, and manufacturing and supply businesses. For the wider selection criteria, see our guide on how to choose business email.

Your next step

Start by logging, for one week, which addresses invoices arrive at and whose hands they pass through; seeing that list usually makes the case for a single intake address on its own. Then get in touch. We will map your invoice flow with you and show SmartMail running on your own invoices@ address. For more on this topic, browse our Business Email & Documents guides.

Let us look at your case

Tell us about your process; after a needs analysis we send a written proposal with scope, phases and cost.

Request a Quote +90 552 380 25 25
Questions we hear most often

Frequently Asked Questions

Do we really need a separate address for invoices?

It is not mandatory, but it is strongly recommended. A general address such as accounts@ mixes invoices with bank correspondence and staff queries. A dedicated invoice address lets you give suppliers one clear instruction, treat every incoming email as an invoice candidate and measure the workload. You can keep the old address and move over gradually with a forwarding rule.

Why is the read flag not enough to track invoices?

The read flag only shows that someone opened the email. It does not say who, what they did or whether the job is finished. In a shared inbox it gives everyone the impression that somebody is dealing with it, so the invoice ends up with no owner. Tracking needs an assigned person and a status such as received, under review, awaiting approval, posted or paid.

If we already use e-Invoice in Türkiye, do we still need an invoice inbox?

In most cases, yes. Suppliers who are not registered for e-Invoice usually send e-Archive invoices by email. Foreign supplier invoices, subscription invoices, credit note correspondence, statement requests and payment reminders also arrive by email. e-Invoice integration removes part of the workload from the inbox, but it does not replace a well-run invoice mailbox.

Is a spreadsheet enough to track supplier invoices?

At low volumes it can get you started, but as long as the spreadsheet and the inbox live in separate places, one of them will fall out of date. Opening a row, updating the status and adding a note becomes a second job, and tracking stops when the person who maintains the sheet is on leave. Keeping the owner, status and notes on the email itself removes that double entry.

How do we catch a duplicate invoice before paying it?

The basic rule is to check the invoice number and the supplier's tax ID together. When the same invoice arrives a second time, or a supplier resends a copy, that pair should be searched before anything is posted to the ERP. Reading those fields from the PDF automatically makes the comparison faster, and a second check before the payment run goes to the bank adds a final safety net.

Does SmartMail work with our existing domain and ERP?

SmartMail runs on your existing domain; domain and DNS settings are managed from the Smart360 admin panel, and the account opens as soon as payment is confirmed. Passing invoice data into your ERP is a separate integration project. We scope it after a requirements analysis, based on the ERP you use, and set it out in a written proposal.

Have a different question? Ask Us

Talk to an Engineer

Tell us what you need to solve. We'll come back with a written proposal.