Skip to content
E-mail validated e-Invoices to buyers automatically

How do I e-mail the e-Invoice to my customer automatically? Switch on Send Email To Buyer

“How do I e-mail the e-Invoice to my customer automatically?” Switch on Send Email To Buyer for the company that issues the invoices, and have BigLedger support confirm the e-mail set-up behind it. From then on, when LHDN validates a document, BigLedger e-mails the validated e-Invoice PDF to the buyer’s e-mail address on that e-Invoice — nobody has to send it by hand.

This page is for whoever looks after e-Invoicing in your accounts team. Allow about fifteen minutes, most of it waiting for one test document to validate. It applies whether your day-to-day accounting runs in BigLedger or in an older system, because the e-Invoice itself is produced in BigLedger.

Meet GadgetSphere

GadgetSphere Sdn Bhd (GS) and GadgetSphere Distribution Sdn Bhd (GSD) both issue invoices to business customers. The corporate buyers of GSD keep asking for “the LHDN copy” by e-mail, and someone in accounts has been downloading and forwarding PDFs one at a time. You want that to stop.

Before you start

  • E-Invoice is already working for the company. Its documents reach Valid. If they do not, start with MyInvois setup.
  • The buyer’s e-mail address is captured before Finalise. The e-mail goes to the buyer e-mail on the e-Invoice record (unless support has set your subscription to e-mail the customer branch instead — then it goes to the address the customer branch carries when it is sent), which is copied from the document’s e-Invoice buyer details (or the customer record) when the e-Invoice is built. Correcting the customer record afterwards does not change an e-Invoice that already exists.
  • You can open the Organisation applet and edit the company.
  • Know what is already queued. Before you switch on a company that has been issuing e-Invoices for a while: every validated e-Invoice is queued for e-mail whether the switch is on or not, and the queue keeps what it holds. Switching on sends that backlog too, oldest first, so buyers can receive e-mails for e-Invoices validated months ago. Ask support to look at what is queued for the company first if that would surprise your customers.

Step 1: Switch on Send Email To Buyer for each issuing company

Organisation → the company → E-Invoice tab → Send Email To Buyer

Turn Send Email To Buyer on and save. The switch belongs to the company, and BigLedger reads it for the company on the source document. So if two of your companies issue invoices — GS and GSD in the example — switch it on for both. A company left off simply sends nothing.

Step 2: Ask BigLedger support to confirm the e-mail set-up

The e-mail needs an e-mail subscription for the company — the sender address, subject, body and file name — which BigLedger support sets up for you. Without a sender address, nothing is sent and no error is shown. Ask BigLedger support to confirm, for each company you switched on, that:

  1. the e-mail subscription exists and has a sender address, and
  2. the scheduled background run that sends these e-mails is running for your tenant.

Step 3: Test with one document sent to a mailbox you control

Raise one real document for a customer whose e-Invoice buyer e-mail is a mailbox you can read (your own, for the test), and finalise it. The e-mail does not go at Finalise or at submission: it goes when LHDN validates the document. Once the e-Invoice shows Valid, check the mailbox.

By default the attachment is named in the pattern E-INVOICE-<supplier name>-<document type>-<date>-<document number>.pdf; your subscription can change that.

Step 4: Know where to look when a buyer says nothing arrived

MY E-Invoice Admin → Internal Submission → Email Dashboard

The Email Dashboard lists the validated-PDF e-mails BigLedger has queued, with their process status, e-mail status, any error message, the receiver e-mail and the retry count. Find the buyer’s document there and read the receiver address and status before you resend anything.

A row that stays IN_QUEUE at retry 0 with no error has not been tried. The usual causes are a company with no sender address (Step 2), or, on a tenant where some companies have the switch off, a run whose every slot is taken by those companies’ held e-mails, so yours wait behind them. Neither shows an error; both are for BigLedger support, so send them the document number and what the dashboard shows.

What success looks like

Your test e-mail arrived with the validated PDF attached after the document turned Valid. On the Email Dashboard, the entry for that document shows the receiver address you expected and no error. Do the same check once for each company you switched on.

Common mistakes

  • Switching on one company when another issues the invoices. The switch is per company. Check every company that raises e-Invoices.
  • Expecting consolidated e-Invoices to be e-mailed. A month’s consolidated e-Invoice is not sent automatically. To send one, open it under Internal Submission → To IRB E-Invoice, go to Notification → Resend Email, add the address under Additional Recipient Email, and press Submit.
  • Pressing Refresh and expecting an e-mail. Refresh sends no e-mail. Resend Email — a tab under Notification, shown only on a Valid e-Invoice — is the only thing that sends on demand, and it sends whether or not the switch is on.
  • A blank or wrong buyer e-mail on the e-Invoice record. The e-mail goes to the address on the e-Invoice record, not to whatever the customer record says today — except where your subscription is set to e-mail the customer branch, which then wins over the record and over an Additional Recipient Email alike. Ask support which way yours is set before you rely on either. Use Resend Email with an Additional Recipient Email to send this one, and fix the address at source for the next document.

If it still does not work

Contact BigLedger support with the company, the document’s e-Invoice status, the buyer e-mail shown on the e-Invoice record, the time it turned Valid, and what the Email Dashboard shows for it (status and error message).

Related documentation

Last updated on