S52–4 days

Transactional SMTP Relay for Invoices and OTPs

Your ERP says the invoice was sent; the customer says it never arrived. We put invoices and OTPs on an isolated sending subdomain with DKIM and real bounce alerts, so a failed delivery is a message you receive, not a complaint three weeks later.

  • Isolated sending subdomain
  • DKIM signed, DMARC reported
  • Bounce alerts, not silence

If your invoices leave through the same shared hosting account as your website, two of these are already true.

  • Invoices land in Gmail spam while your website form emails arrive fine — same domain, different luck.
  • The host throttles at a few hundred an hour, so month-end statements take three days.
  • Nobody knows which invoices bounced last month because nothing reports it anywhere.
  • You want to move to a proper relay, but the sending code lives inside SQL Accounting or AutoCount.

What we set up

  • A dedicated sending subdomain, so relay reputation never mixes with the mailboxes your staff use.
  • DKIM signing and DMARC reporting on that subdomain, verified before the first real invoice leaves.
  • SMTP credentials wired into SQL Accounting, AutoCount or your own app; we test from your system, not from curl.
  • Bounce and complaint alerts delivered to a mailbox someone actually reads, with the failing address in the subject.
  • A monthly volume report and IP monitoring, so throttling or blocklisting is caught before month-end.
  • A one-page runbook: host, port, credentials owner, and what to change when the ERP is upgraded.

What we need: DNS access for the sending subdomain, one ERP account we may configure SMTP in, and a test customer address you can check in Gmail or Outlook.

Before and after the relay

Transaction mail is judged on whether it arrives and whether you find out when it does not.

ServiceThrough shared hostingThrough the relay
Sending sourcesame IP as every site on the hostdedicated subdomain, monitored
AuthenticationSPF at best, often nothingDKIM signed, DMARC reported
When a send failssilent, or a log nobody opensalert with the address
Monthly volumehost cap, often a few hundred an hourquota sized for month-end runs
Who fixes ita support ticket in another timezonethe person who set it up

Nett — No SST charged

Test what you have, then replace it

  1. Send a real invoice today

    We check where your current invoices actually land and read the authentication results, before proposing anything.

  2. Isolate and wire up

    The sending subdomain is published and signed, then SMTP credentials go into your ERP; mailboxes stay untouched.

  3. Watch one month-end

    Bounce alerts run through your first statement run; we tune limits and only then close the handover.

Check the headers of your own invoice

Send one invoice through the relay to a Gmail address you own, then open Show original. You should see dkim=pass on our subdomain, spf=pass and a Return-Path that is not a shared host. If any of those reads softfail, we have not finished.

Relay questions, before you trust it with invoices

Yes. The From address stays your invoice address on your domain; only the bounce address moves to a subdomain we sign and monitor, because that is what protects the reputation of the mail your staff send.

Both send through plain SMTP with a username and password, so yes. We configure it inside your system and send a real invoice out of it — a relay that only passes a command-line test has not been proven on your side.

Extra volume is queued and reported, never silently dropped, and we quote an additional block once two months show the real number. You should not pay for peak capacity you only touch at year-end.

No, and we will say so plainly. Marketing blasts on a transactional IP drag invoices into spam with them. Use a separate platform for newsletters; we will point you at one rather than sell you the wrong pipe.

Send one invoice, see where it lands

Send us one real invoice from your ERP and the Gmail address you will check. We report the authentication result and the fix, before you commit to anything.

Reply within one business day (Mon–Fri, 9am–6pm MYT).