AiStaffo

Microsoft invoices from pageroonline.com: real or phishing?

Stock photo: desk, invoices, laptop, documents
Photo: https://kaboompics.com/ / Pexels

The reported facts point to a real invoice sent through a service provider, not an automatic fraud. Microsoft Germany started sending some B2B invoices as electronic invoices in November 2026, as a test run ahead of the German mandate. Where a customer has no Peppol endpoint on file, the invoice arrives as an email attachment from pageroonline.com, the domain of the provider Pagero. Some recipients took this for phishing. Before you pay any invoice from an unfamiliar sender, check three things: the invoice matches a purchase or a known service, the bank details match your vendor record, and any change to those details is confirmed by phone on a number you already hold. A new sender address alone is not proof of fraud, and a familiar address is not proof of safety. The steps below set this check up so that a person sees every change.

In short

  • The reported facts are that Microsoft Germany sends some B2B invoices through Pagero from pageroonline.com, with an email fallback when no Peppol endpoint is set up.
  • A new sender domain is a reason to check, not proof of fraud, and a familiar sender is no guarantee of safety.
  • Never accept a changed bank account from an email; confirm it by phone on a number already in your vendor record.
  • Set the system to hold any invoice with a new IBAN, a mismatched total or an unapproved sender for a person to review.
  • Keep the decision to change a bank account with a person, even when the rest of the process runs automatically.

What is reported and what is only a concern

In early November 2026, German readers began writing to the technology press about Microsoft invoices that did not come from a Microsoft address. Heise reported on 12 November 2026 that Microsoft Deutschland sends B2B invoices as electronic invoices through the service provider Pagero, and that the emails come from a no-reply address at pageroonline.com. Several readers thought the emails were phishing.

The reported facts are narrower than the headlines. Heise found that the amounts were correct and the PDF attachment had no obvious errors. It also noted that the invoices did not contain a notice of automatic payment by the credit card on file. Microsoft told heise that it had informed customers by email in early October 2026 and had published an FAQ on the change. That FAQ names the fallback route: if no Peppol endpoint is found for a customer, the XML e-invoice is delivered as an email attachment to the address Microsoft has on file. Pagero has been part of Thomson Reuters since 2024, according to the same reporting.

What is only a concern is the question of whether the sender is trustworthy in the wider sense. Phishing does exist in this area. A security report from June 2026 described criminals who manipulate Microsoft 365 tenant settings and display names to hide phishing links inside invoice-style emails, which can get past standard checks such as SPF, DKIM and DMARC. That report describes a different campaign. It does not show that the pageroonline.com emails are fraudulent, and no authority has said so. Equally, the November invoices being genuine does not clear the next scam, which is often a genuine-looking invoice with a changed bank account.

The distinction matters for a business owner. The question for your accounts payable team is not whether pageroonline.com is a known sender. It is whether this invoice is for something you bought, at the amount you expected, to the bank account you already hold for that supplier.

Why this costs money

The direct cost of an unfamiliar invoice is staff time. A typical invoice takes a person several steps: opening it, matching it to an order or a contract, checking the bank details, getting approval and paying it. Benchmark studies usually price the full manual process in dollars per invoice. A 2025 Ardent Partners AP study, as summarised by vendors that cite it, puts a fully loaded manual invoice at about $10.89, while the best-in-class automated process comes in at about $2.78. Other compilations of the same kind give manual ranges of $10 to $22 and $15 to $40, depending on how many manual touches an invoice needs. These are benchmarks from vendor-compiled summaries, not audited figures, so use them only as a starting point and measure your own cost per invoice.

The larger cost is a wrong payment. The risk that matters most is a genuine supplier invoice carrying a changed IBAN, or a fake invoice that copies a real supplier's layout. Once money goes to the wrong account, recovering it is slow and often impossible. A verification step that takes a few minutes per changed bank account is cheap by comparison.

Germany adds a practical reason to get this right now. Since 1 January 2025, every business established in Germany must be able to receive structured e-invoices, according to the mandate summaries from Sovos and Avalara in 2026. The duty to issue e-invoices starts on 1 January 2027 for businesses with prior-year turnover above EUR 800,000, and on 1 January 2028 for the rest. Your receiving process will therefore see more structured invoices from more suppliers. Without a defined check, each new sender becomes a judgement call made by whoever opens the inbox.

Manual check versus automated check

The table compares how the same invoice is handled in the two setups. The automated column does not remove the human decision. It moves the routine work to a queue and puts the decisions in front of a person.

TaskManual wayAutomated way
Spotting a new senderSomeone notices the address by chance, or it is missed in a spam folderA rule compares the sender domain with an approved list and flags any new domain
Reading the invoiceKeying the amount, date, invoice number and bank details by handStructured XML is read directly; a PDF without structured data goes through document extraction
Checking the bank detailsCompared by memory or not at allThe IBAN is compared with the vendor record; any difference is held
Confirming a changeOften done by replying to the email that contains the new detailsA draft request goes to the contact in your vendor record, and a person calls back on a number already on file
Approval and paymentForwarded internally by email, sometimes without a recordLogged, routed to the approver, and released only after the check is cleared

How to set up the check, step by step

Start with the inbox. Create a dedicated invoice address for suppliers, for example an address in your Microsoft 365 or Google Workspace tenant, and tell your top suppliers, including Microsoft, to use it. Make sure the mail filters do not send supplier invoices to spam, because the Microsoft notice itself was reportedly lost in filters at some recipients.

  1. Build an approved sender list. For each supplier, record the domains that legitimately send invoices, such as the supplier's own domain and known service providers like pageroonline.com for Microsoft. Keep this list in the spreadsheet or the accounting system that holds your vendor master data.
  2. Read structured invoices directly. A German e-invoice in XRechnung or ZUGFeRD format carries machine-readable data. Your accounting software or ERP, for example Microsoft Dynamics 365 Business Central, DATEV or your current bookkeeping tool, should import these fields rather than rely on a PDF picture. Check with your software vendor which formats it accepts.
  3. Use document extraction only for PDFs with no structured data. Optical character recognition, or a large language model used only to pull out fields such as supplier name, invoice number, total, VAT and IBAN, handles these. Treat its output as a draft. Any field it cannot read with confidence goes to a person.
  4. Compare the bank details. Match the IBAN and supplier name against the vendor record. If they match, the invoice can move to the normal approval queue. If they differ, stop the payment.
  5. Hold any new IBAN for a call-back. The AI worker drafts a message to the contact already stored in your vendor record, never to the address or phone number printed on the invoice, asking the supplier to confirm the change. A person then calls the number on file and records the outcome.
  6. Log every decision. Keep the sender, the check result, the person who approved and the date in one record. German businesses must keep invoices they issue and receive for eight years, so the log should be stored with the invoice.

Two checks belong to people, not to a rule. A person should look at the first invoice from any new sender before it is paid, and at any invoice that asks for urgent payment. The Federal Office for Information Security (BSI) lists checking the sender as the first step in recognising phishing, and that check cannot be fully handed to software.

What breaks, and how to prevent it

The most common failure is a false alarm. A legitimate new sender will be flagged until someone adds it to the approved list. That is intended, but it can build a backlog if nobody owns the list. Assign one named person to review new domains each week.

The second failure is trusting the sender domain too much. A domain match is necessary but not enough. Scammers can copy a layout, reuse a real invoice number or send from a compromised mailbox. The European Commission's e-invoicing framework does not stop that. Your control is the bank-detail check and the call-back, not the look of the email.

The third failure is extraction error. A PDF misread can turn a euro amount into the wrong figure or drop a digit from an IBAN. Set the system to refuse to pay when the total, IBAN or VAT figure does not agree with the purchase order or the contract. Do not let it guess.

The fourth failure is the rule that approves too much. Where a vendor is on your approved list and the IBAN matches, the invoice may be released automatically in some setups. Keep a limit on the amount and the frequency, and keep every change of bank details manual. The official text of the German mandate does not require full automation of processing. Your own controls decide how much of the flow runs without a person.

The last failure is complacency about the law. Receiving structured invoices is a legal duty; the way you check them is your own decision. The Federal Ministry of Finance (BMF), as summarised by a 2026 compliance update, has clarified that an email inbox may generally suffice for receiving e-invoices, and that a duty to process them fully automatically does not exist in general. The controls described here are good practice, not a legal requirement in themselves.

This explains the rule in general terms; it is not legal or tax advice for your case.

When not to automate this

If your business receives only a few invoices a month, a written checklist and a phone list may serve you better than any software. A two-person office that pays three suppliers by standing order does not need an AI worker to read invoices. The effort of setting up an approved list, extraction rules and a hold queue only pays off when the volume of new or changed suppliers is steady.

Do not automate the decision to change a bank account. The software can hold the payment, draft the request and record the answer. It should not accept a new IBAN from an email, and it should not release payment on its own. Where a supplier insists on urgent payment to a new account, the right step is a person's call, not a faster workflow.

Do not automate the first contact with a new sender if you have no way to verify them. In that case the correct action is to ask the existing contact at the supplier, and the software should only record the request.

What it typically takes

For a small business, setting up the approved sender list, the inbox rules and the IBAN comparison is a matter of days of work for one person, plus a few weeks of watching the hold queue to tune the rules. The time is mostly spent deciding which suppliers you trust and which contacts are on file. For a larger group, the work is in the vendor master data: many entities, many suppliers, and older records with no reliable phone number.

Expect the first month to show more holds than you want. That is the check working. Each hold should be resolved by a person and fed back into the approved list. After that, the queue should shrink to new suppliers and genuine bank changes, which are the cases that need a human anyway.

The Microsoft invoices themselves need little more than the approved sender list. Add pageroonline.com as a known route for Microsoft, confirm the amount against the Microsoft account, and keep the bank details tied to the vendor record. Results depend on your own invoice volume and your own cost per invoice, which the free automation audit measures.

How AiStaffo would automate this

AiStaffo would connect your invoice mailbox, your approved sender list and your accounting records, so that every incoming invoice is read and compared before anyone opens it. Structured German e-invoices would be read directly, and PDFs without structured data would go through document extraction. Invoices from known senders with matching bank details would move to the normal approval queue, while any new sender, new IBAN or amount mismatch would be held. The AI worker would draft a confirmation request to the contact already stored in your vendor record, and a person would make the call and approve the change. Your team still owns the approved list, the call-back and every bank detail change. Book a free automation audit.

Questions people ask

Are the Microsoft invoices from pageroonline.com real?
Heise reported on 12 November 2026 that Microsoft Deutschland sends some B2B invoices through the provider Pagero, from a pageroonline.com address. Microsoft told heise that it announced the change in early October 2026, and that customers without a Peppol endpoint receive the invoice as an email attachment. Compare the amount and invoice details with your Microsoft account before paying.
Why did the Microsoft invoice not come from a microsoft.com address?
According to the reporting, Microsoft Dynamics 365 Business Central can use Pagero to create and send electronic invoices, and the emails therefore come from Pagero's domain. The fallback applies when a customer has no Peppol endpoint registered. The change is a delivery route, not a change of supplier.
What should I check before paying an invoice from a new sender?
Check that the invoice matches a purchase, a contract or a service you use. Compare the IBAN and supplier name with the record you already hold. If the bank details have changed, confirm the change by phone on a number from your existing records, never on one printed on the invoice.
Is a PDF invoice by email still valid in Germany?
A standard PDF is generally treated as another invoice under German VAT rules, not as a structured e-invoice. Since 1 January 2025 every business established in Germany must be able to receive structured e-invoices, and issuing them becomes mandatory on 1 January 2027 for businesses above EUR 800,000 prior-year turnover. This explains the rule in general terms; it is not legal or tax advice for your case.
Can software decide whether an invoice is phishing?
Software can flag new senders, mismatched IBANs and amounts that differ from an order, but it cannot prove that a sender is genuine. Scams can copy a real layout or use a compromised mailbox. The final decision on a changed bank account should stay with a person.
How much does manual invoice checking cost?
Vendor-compiled benchmarks citing Ardent Partners' 2025 AP research put a fully loaded manual invoice at about $10.89, and automated processing at about $2.78. These figures are not audited, and your own cost depends on your staff time and invoice volume. Measure your own cost per invoice before you rely on any benchmark.

Book a free automation audit

Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

We use these details only to reply to this request and prepare your audit, and keep them for up to two years. We send no marketing unless you tick the box above. Privacy policy

accounts payableinvoice processinge invoicingvendor riskemail triagegermany