billing@ vs accounts@ vs invoices@: Set Up Money Email Properly

Money mail is the category most likely to cost you real cash when it goes missing: a supplier invoice buried under newsletters becomes a late fee, a customer's remittance advice that nobody sees becomes a chased payment and an awkward apology. The fix is to stop sending it to a person and start sending it to a role. This guide shows which addresses to create, who should read them, and how to keep invoice fraud out.

Quick summary

• billing@ — outbound. The address your invoices are sent from and the one customers reply to with payment queries. Publish it on every invoice.
• accounts@ (or accounts-payable@ / ap@) — inbound. The address suppliers send their invoices to. Give it to every vendor when you set up an account.
• invoices@ — optional catch-all for the confused. Many suppliers guess it, so create it as an alias that forwards to accounts@.
• remittance@ — only if you pay many suppliers by bank transfer and want your remittance advices sent from a separate address that is never used for anything else.
• On OquMail each of these is a free mailbox or alias on your domain, so a three-person company can run the full set without paying per seat.

Which addresses to create

• billing@ — outbound. The address your invoices are sent from and the one customers reply to with payment queries. Publish it on every invoice.
• accounts@ (or accounts-payable@ / ap@) — inbound. The address suppliers send their invoices to. Give it to every vendor when you set up an account.
• invoices@ — optional catch-all for the confused. Many suppliers guess it, so create it as an alias that forwards to accounts@.
• remittance@ — only if you pay many suppliers by bank transfer and want your remittance advices sent from a separate address that is never used for anything else.
• On OquMail each of these is a free mailbox or alias on your domain, so a three-person company can run the full set without paying per seat.

Why separate outbound and inbound money mail

Mixing the two in one mailbox is what causes misses. Outbound billing@ is busy with customer conversations: "can you resend invoice 1042", "we paid on Tuesday", "please update the PO number". Inbound accounts@ needs to be quiet and boring so that every new message is, by definition, something to be paid or queried. When the bookkeeper opens accounts@ on Friday and sees twelve unread messages, all twelve go into the payment run. That simplicity is the whole point.

Set it up in six steps

1. Create billing@ and accounts@ as real mailboxes; add invoices@ and ap@ as aliases into accounts@.
2. Give billing@ the display name "[Company] Billing" and set its signature with your bank details, VAT or tax number, and payment terms in plain text.
3. In your invoicing tool (QuickBooks, Xero, Zoho Books, Wave or a spreadsheet plus PDF), set the sending address and reply-to to billing@yourdomain.com. If the tool sends through SMTP, use your OquMail mailbox credentials on port 587 with STARTTLS so the invoices are authenticated by your own SPF and DKIM.
4. Email every supplier once: "Please send all future invoices to accounts@yourdomain.com. Invoices sent to personal addresses may be delayed." Add the same line to your purchase orders.
5. In accounts@, create folders "To pay", "Paid - [month]" and "Query". Move each invoice on arrival; the inbox should be empty after each payment run.
6. Give the bookkeeper their own login to accounts@ over IMAP or webmail instead of forwarding invoices to them one by one.

Fraud checks that belong in accounts@

Invoice redirection fraud, where a criminal emails "we have changed our bank details" from a lookalike domain, is the most common financial scam against small businesses. Put three rules on the accounts@ mailbox and stick to them: any change of bank details is confirmed by phone on a number you already had, never one in the email; any invoice from a new supplier is checked against a purchase order or a named colleague who ordered the goods; and any message that pressures you to pay today is treated as suspicious. Check the sending domain letter by letter. Your own DMARC record (v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com) stops people spoofing your domain to your suppliers, and it is worth asking your key suppliers whether they have one too.

Mistakes that cost money

• Sending invoices from a personal Gmail so customer finance teams cannot match the sender to your company.
• Using billing@ as a no-reply address. Payment questions are the replies you most want.
• Letting supplier invoices arrive at the founder's inbox and get "dealt with later".
• Deleting paid invoices instead of filing them; most tax authorities expect you to keep them for five to seven years.
• Not telling suppliers when the bookkeeper changes, so invoices keep going to a former employee's address.

Common questions

Do I need billing@ if I am a freelancer?

It is still worth it. billing@ keeps payment threads out of your client conversations, and when you hire a part-time bookkeeper you hand over one login instead of your whole inbox.

Can my invoicing software send from my domain?

Most tools can either send via your SMTP account or use their own servers with your address as the sender. SMTP through your own mailbox is cleaner: the mail is signed by your domain and shows up in your Sent folder, and OquMail records a per-message delivery log so you can prove an invoice was delivered.

Should statements and reminders come from a different address?

Keep them on billing@ so the customer's finance team sees one consistent sender. Vary the subject line, not the address.