How to set up billing@ without buying another mailbox

Quick answer for billing email alias

Create billing@ as a named alias to the bookkeeper’s Gmail or Outlook. Exclusive MX. Probe from another mailbox. Attach send-as only if invoices leave as billing@. That is a billing email alias without another mailbox.

A custom domain alias is not a ledger. Keep the books in the tool you already use.

Two dests only if counsel wants a copy. Name who replies to dunning.

Leftover MX hides invoices from the bookkeeper you mapped.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

custom domain alias: the real decision

Bought a seat named Billing.

Shared founder Gmail for invoices.

Catch-all plus hope.

Criteria: named billing@, one dest, exclusive MX, send-as only if needed.

Technical mail flow for billing email alias

Vendors write billing@. Hop two to the bookkeeper store. Header From stays the vendor.

Dunning replies as billing@ need hop five. One secret. Rotate on bookkeeper leave.

Unknown invoice@ sits in hold until you create it or print it.

Self-send from the bookkeeper Gmail to billing@ can hide the public path.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

email forwarding alias

Name the bookkeeper store. Then create the alias. Then print the string on invoices.

1. Create billing@ mapped to the bookkeeper.
2. Create invoices@ or ap@ only if you print them.
3. Exclusive MX. Delete leftovers.
4. Probe billing@ from another mailbox. Search spam.
5. If paper leaves as billing@, paid send-as. Dashboard pair. Gmail Send mail as.
6. Do not store SMTP in the accounting plugin chat thread.
7. When the bookkeeper leaves, remap dest and rotate.
8. Review hold for vendor-unique leftovers before you promote them.

Failure modes and proof

Seat named Billing.

Invoices in founder Primary with catch-all.

Free SMTP in the invoice tool.

Self-send.

Leftover MX.

MailerZ workflow and product boundary

Related: aliases and catch-all, use cases, send and reply, pricing.

Sales@ can fan-out. Billing@ usually should not.

Related pages: aliases and catch-all, use cases, send and reply, and pricing.

role address

One alias on Free if you still have a slot. A fourth money name is a plan conversation. Solo $40/year if invoices leave as the domain. A Workspace Billing user is the expensive wrong aisle. Confirm pricing.

Competitor blogs describe role aliases too. Cite nofollow. Do not invent their money-mail features.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Separate payments@ only if the processor prints it.

Do not merge legal@ and billing@.

PCI and card data do not belong in the alias. The alias is a route.

Quarterly leftover review.

Vendor leak: retire billing-old@, create billing@ new, update the footer.

Two-founders article is not this page.

The twenty-roles page is the sheet. This is the money row.

14-day Free store is not invoice archive. Keep the books elsewhere.

Deeper field notes for billing email alias

Money mail belongs to one search box

A billing email alias fails when invoices land in a founder catch-all, a vacant Workspace seat named Billing, or five people who each thought the other would pay. Map billing@ to the bookkeeper’s existing Gmail or Outlook. One dest. One human who opens that store daily. That is the whole product. MailerZ is the hop. The ledger stays in the accounting tool.

You do not buy another mailbox because the public string is not a person. It is a role address. A custom domain alias and an email forwarding alias are the same map in this product: named local-part, destination store, exclusive MX. Free can hold billing@ if you still have a slot among three. A fourth money name — invoices@, ap@, payments@ — is a ceiling conversation. Confirm /pricing.

Inbound vendors versus outbound paper

Most billing@ traffic is inbound: vendor invoices, processor notices, customer PO-to-invoice questions. Header From should stay that vendor. If you reply as billing@, that is hop five. Free cannot. Solo is forty dollars a year when the From must travel. Copy the dashboard pair. Do not paste a Gmail password into the invoice plugin. Unauthorized is 550 / 550 5.7.1.

If the invoice tool already sends as a processor domain, you may not need send-as on billing@ at all. Do not attach SMTP “for completeness.” Every secret is a rotation job when the bookkeeper leaves.

What not to merge

Do not merge legal@ and billing@. Do not merge sales@ and billing@ so “someone will see it.” Do not use catch-all as the accounts-payable hose. If you print ap@ or accounts@, create those names. Hold the rest. Vendor-unique leftovers (ap-acme@) get promoted when Acme used them, not when a scraper guessed them.

Card data does not belong in the alias. PCI is the processor’s job. The alias is a route for notices. Do not invent a compliance badge because the local-part says billing.

Leftover MX hides money

If Google still answers, the bookkeeper dest never sees the vendor. They will say forwarding is broken. Public lookup. Exclusive MailerZ MX. Delete leftovers. New unique subject from another mailbox. Search spam. Self-send from the bookkeeper Gmail to billing@ can look fine while vendors still hit the old host.

Leave and contractor pattern

Remap dest the day the bookkeeper’s last day is known. Rotate send-as the same hour. Do not keep their personal Gmail “until we find someone.” A contractor gets a dest you will delete, not the SMTP pair in email. Agencies: per-client billing@, per-client bookkeeper. Do not pour every client’s invoices into the agency inbox.

Evidence versus books

Delivery history shows hops this layer stored. It is not the invoice register. Keep QuickBooks, Xero, or the PDF folder. The 14-day Free window will not save a quarter of invoices. Paid 90 days is still hops. If you need a long money archive, that is the store or the accounting tool, not the hop.

Competitor blogs will show role aliases. Nofollow. Do not invent their billing features. RFC 5321 still describes the transport.

Footer and PDF hygiene

Create billing@ before you export a thousand PDFs. Changing the string later is a year of vendors. If you must retire a leaked billing@, create billing-ap@ or a dated name, update the site, and hold the old name until the last processor is moved — or disable it if abuse is the problem. Do not catch-all to “keep the old string alive forever.”

A complete worked story

The Billing user nobody logged into

They paid a Workspace seat called Billing so the accountant would “have an inbox.” The accountant lived in consumer Gmail and never opened the seat. Invoices sat unread. They created billing@ to the real Gmail, cut exclusive MailerZ MX, probed, and canceled the empty seat. Money mail started landing where the human already worked.

Operator brief

A longer operator brief for billing email alias

Teams that bookmark How to Set Up billing@ Without Buying Another Mailbox usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about billing email alias as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is Mail Box portal webmail, not IMAP, not POP, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening billing email alias. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for how to set up billing without buying another mailbox. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear billing email alias works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep billing email alias per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When How to Set Up billing@ Without Buying Another Mailbox is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how billing email alias stays a runbook instead of an incident.

A second worked pass for billing email alias: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a billing email alias mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

Processors, portals, and the string they already have

Stripe, PayPal, a bank, and an accountant’s portal will keep writing to whatever address you typed in 2022. A billing email alias you created yesterday does not update those portals. After exclusive MX and a successful probe, walk the processor list. Change the notification email to billing@yourdomain. If a portal still has founder@gmail.com, you have two money inboxes. The hop cannot merge them.

If a processor will only send to the login email, that is their rule. Either change the login, or accept that some notices bypass billing@. Do not enable catch-all to “catch processor surprises.” Create the surprise name if they print it.

Dunning without a second seat

If humans send payment reminders as billing@, that is paid send-as. If the accounting tool sends reminders from its own domain, leave MailerZ receive-only. Mixing both without an SPF story is how dunning lands in spam. Copy dashboard SPF, DKIM, and DMARC values only for the path you actually send. Confirm /pricing. Free will not finish dunning as the domain.

The bookkeeper’s vacation is a dated second dest or a remap, not a shared password with the founder. Money mail in a personal account you cannot revoke is the failure this page exists to prevent. When they return, remove the extra dest.

What finance thinks “another mailbox” means

They think billing@ needs a login, a phone, and a seat. Show them the map: public string, hop, existing store. Show exclusive MX. Show a probe Message-ID. Show that a Workspace Billing user would be a store they will not open. Quote live suite cards if they want the contrast. Do not invent savings percentages. Do not promise inbox placement for invoices. Vendors still classify.

If finance also wants Calendar on that seat, they wanted a human, not a role. Hire or assign a human store. Keep billing@ as the alias. Do not name the Workspace user Billing and walk away.

A money-mail drill you can run in thirty minutes

Write billing@ on a sticky note. Confirm the alias exists. Confirm the bookkeeper dest. Confirm exclusive MX on two public views. Send a unique subject from a mailbox that is not the bookkeeper. Find it in history. Find it in the dest including spam. Confirm Header From is still you, the tester, not a rewritten brand. If any step fails, stop printing the string on new PDFs. That drill is the difference between a billing email alias and a hope.

Add the processor walk the same afternoon. If three portals still notify founder@gmail.com, the hop is fine and the portals are not. MailerZ will not sync them. RFC 5321 does not update Stripe. Google Send mail as does not update a bank portal. Exclusive MX does not either. Humans change those forms.

PDFs, portals, and the string you cannot take back

Once billing@ is on a thousand invoices, you do not get to rename it because someone bought a Workspace seat. Keep the public string. Change the destination when the bookkeeper changes. That is the whole product: a stable local-part into a store people already open. MailerZ is not a finance suite. It will not sync Stripe, QuickBooks, or a bank portal. Humans update those forms.

Print leftover MX before you print a new PDF batch. Old Google MX still answering means some vendors never reach the bookkeeper. A uniquely titled probe from another mailbox is cheaper than a “where is our invoice” week. Free can prove inbound on ten aliases. Solo at $40 per year adds send-as if the bookkeeper must reply as billing@. Confirm MailerZ pricing.

Do not map billing@ to the founder and invoices@ to the bookkeeper without writing it down. Vendors will pick whichever string they still have. Two money names need two probes and two owners, or one name and one dest. Catch-all Forward is how a guessed payments@ fills the same inbox with phishing. Hold unknowns. If the bookkeeper also sends as billing@, attach paid SMTP in their client only. Do not share that secret with a WordPress form. Rotate it when they leave.

Old PDFs keep mailing billing@. That is why you do not rename the string after a seat purchase. Dest edits are cheap. Public renames are years of leftover vendor books.

FAQ

What is the safest way to handle billing email alias?

Create billing@ as a named alias into the bookkeeper’s existing Gmail or Outlook. Exclusive MX. Probe from another mailbox. Paid send-as only if invoices leave as billing@. Do not buy a seat to park the string. Hold unknowns.

Does this require a new mailbox?

No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Named billing@.
• One bookkeeper store.
• No extra seat.
• Send-as only if paper leaves.
• Probe.
• Rotate on leave.
• Hold extras.
• Exclusive MX.

Conclusion and next action

Set up billing@ without another mailbox by mapping a string to the bookkeeper you already have. MailerZ is the hop. Cut leftovers. Probe. Pay only if the From must be billing@.

Start free. Sign in if invoices are missing and public MX is still Google.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.