Automatic invoice collection from Gmail: a practical guide for online stores

Every month the same documents trickle into your inbox: the shipping carrier's invoice, the payment processor's statement, the hosting bill and the ad platform's receipt. Someone has to find each one, download it, check the amount and VAT and pass it to the accountant, and the one that gets missed is the one that turns up at year-end. Automatic invoice collection hands that job to software: it searches your Gmail for each vendor's invoices, reads them, files them under the right month and forwards them on schedule. This guide explains how it works in StoreChart, what the AI reads from each document, how duplicates are handled and how to set it up so it stays accurate.

Why manual invoice collection breaks down

The work itself is simple. The variety is what makes it fragile:

• Different formats: one vendor attaches a PDF, another sends a link to a billing portal.
• Double documents: a third sends an invoice and a separate receipt for the same charge.
• Confusing months: an accountant's invoice for March arrives on April 5.
• Other currencies: a payment processor bills in dollars while everything else is in shekels.

Say a store works with 15 regular vendors. That is at least 15 documents to chase every month, more when some bill weekly. Each one is a chance to mistype a total or file it under the wrong month.

The costs show up later:

• An expense missing from the books.
• VAT that was never claimed.
• A month that cannot be closed because one invoice is still somewhere in the inbox.

Read-only Gmail connection

You connect from the expenses module with Google's own sign-in screen. StoreChart asks for read-only access to Gmail and for your email address, nothing more.

• What it can do: search messages and download attachments.
• What it cannot do: send, delete or change anything.
• Access tokens: stored encrypted.
• Disconnecting: in StoreChart, or by revoking access from your Google account, whenever you like.

A business that receives invoices in more than one mailbox can connect several Gmail accounts. Each expense searches all of them by default, or only the ones you choose. Connecting a mailbox and changing collection settings require the expenses-integration permission, so you decide which team roles can touch them.

Choosing which vendor invoices to collect

Collection is organized around your recurring expenses, the monthly tracker of bills you expect to pay. For each regular vendor you create an expense with its category and expected amount, then switch on Gmail collection for it. Then you teach it what the invoice looks like:

1. Search your mailbox by the vendor's sender address or name, optionally with subject keywords.
2. Pick one real invoice from the results as a sample.
3. Confirm what the AI read. StoreChart parses the sample and saves a profile of the vendor: who sends it, what kind of document it is and the vendor's details.

From then on, each search is built from that expense's rules:

• Sender addresses for the vendor.
• Subject keywords in the email.
• Delivery mode: an attachment, a download link, or either.

Invoice OCR: what the AI reads

Each PDF or image goes to a multimodal AI model. It reads the page rather than fixed positions on a template, so a new layout from the same vendor is not a problem. It extracts:

• Document type: tax invoice, invoice-receipt, invoice, receipt or credit note.
• Amounts: the total, the amount before VAT and the VAT amount, with the currency.
• Issue date: read in the day-month order used on Israeli invoices.
• Vendor details: the invoice number, the vendor name and the vendor's tax ID.
• Billing period: the month the charge is for, when the document states one.

The decision whether a document is an invoice at all is made by rules, not by the model's opinion. The model reports what it sees, and StoreChart combines the signals:

• An invoice heading.
• A tax ID.
• A VAT line and a totals block.

Price quotes, order confirmations, marketing material and contracts are set aside rather than booked as expenses.

Duplicates and wrong documents

Duplicates are stopped before they reach your books. A document is not imported again when:

• The email and file were already collected.
• The invoice number matches one already filed under the same expense.
• The date, amount and file name all match an existing invoice.

In the scan results it appears as already collected, next to the invoice it matches.

When you run a scan yourself, the result is a proposal. You review the documents found, keep the right ones and untick the rest. For each one you choose a reason: wrong document type, wrong vendor, wrong month, duplicate or other.

StoreChart learns from that review. If you untick a vendor's separate receipt, for example, it stops downloading that kind of document for that expense next month. The learning never excludes the sender or document type your approved sample came from, because a wrong exclusion would silently stop the invoice from arriving.

Scheduled invoice collection

Once your expenses are set up, turn on automatic collection and choose how often it runs, at an hour in your timezone:

• Daily: one run every day.
• Weekly: on the days you pick.
• Monthly: on a set day of the month.

Scheduled runs work unattended with what each expense has learned. The monthly tracker then shows each expense as pending, collected or sent to the accountant, with the collected amount and VAT.

A vendor that bills in another currency is converted at the rate of its invoice date. The totals feed the expenses in your profit reports.

Automatic sending to your accountant

Enter your accountant's email address once. You then have two ways to send:

• By hand: invoices you select, with a short note and a copy to your own inbox.
• Automatically: on a set day of the month between the 1st and the 28th.

Each email carries the original files and an itemized list. A large batch is split across several emails instead of being dropped, and every invoice sent is marked as sent in the tracker.

Example: a month of automatic invoice collection

A store sets collection to run weekly on Sunday mornings and automatic sending on the 10th:

1. First week: the scheduled runs pick up the hosting bill, the payment processor's statement and the carrier's invoices. Each is filed under its own expense with the amount and VAT filled in.
2. By the 8th: the tracker shows 13 of 15 expected invoices collected.
3. The two still pending: one vendor switched to emailing a portal link, so the owner changes that expense's delivery mode. The other is a paper invoice, which gets uploaded by hand.
4. On the 10th: everything collected goes to the accountant in one email, and each invoice is marked as sent.

If a vendor bills twice a month, set how many invoices that expense should expect. The tracker marks it collected only once all of them have arrived.

The figures in this article's examples are illustrative only and do not reflect actual customer data.

Setup tips that keep it accurate

• Start with your largest vendors. A handful of regular bills usually covers most of the month's documents.
• Choose a clean sample. Pick the document you actually want collected, such as the tax invoice rather than the payment receipt.
• Run the first month by hand. Review the results before you switch on the schedule, because every correction teaches the expense something.
• Check the delivery mode for vendors that email links to a billing portal.
• Upload the stragglers. Paper invoices and one-off purchases can be uploaded by hand and are read by the same AI parser.

For how collected expenses fit into the full picture of what your store earns, see the guide to calculating real profitability. The number of invoices you can store depends on your plan; see pricing. For the feature itself, see automated invoice processing from email.