E-Invoicing When the Payee Cannot Issue a Compliant Invoice

E-invoicing mandates are now live in more than 60 countries, and 2026 alone brought new B2B requirements online in Belgium, Croatia, Poland, and France, according to Lasernet's 2026 mandate guide. 

Gigapay is the Merchant of Record for creator payouts that turns hundreds of non-compliant payees into one compliant vendor invoice your AP system can actually process. 

The problem this article addresses is specific: your finance team is investing in electronic invoicing infrastructure while your marketing team pays hundreds of individuals who cannot issue a valid PDF, let alone a structured EN 16931 document. 

This breakdown covers the 2026 mandate landscape, why campaign payees will never join your supplier e-invoicing network, and how the Merchant of Record model resolves the contradiction without slowing down a single payment.

Key Takeaways

• E-invoicing mandates are live in over 60 countries, with major EU rollouts through 2026.
• Most individual creators cannot issue structured invoices and will not join e-invoicing networks.
• The invoice your entity must receive is the Merchant of Record invoice, not creator PDFs.
• Self-billing lets the party that can issue compliant documents handle the payee side.
• Gigapay consolidates hundreds of creator payments into one compliant vendor invoice per campaign.

The 2026 E-Invoicing Mandate Wave in Europe and Beyond

Structured electronic invoicing stopped being a niche tax project and became a standard compliance requirement across the EU. Tradeshift's 2026 compliance report puts Europe's electronic invoice share at 64% and rising, with Latin America ahead at 78% after a decade of continuous transaction controls. 

The EU's VAT in the Digital Age (ViDA) reform, adopted in March 2025, requires structured e-invoicing for intra-EU B2B transactions from July 2030 and harmonization of all national regimes by 2035.

Here is what came into force in the markets where creator marketing budgets are largest:

Spain follows with its Crea y Crece rollout in October 2027 for large taxpayers, and Slovakia's mandatory framework starts in January 2027. Outside the EU, the UAE begins its voluntary pilot in July 2026 with mandatory adoption for large businesses from January 2027, and Australia requires federal agencies to process at least 30% of invoices through the Peppol network by July 2026.

The direction is consistent everywhere: tax authorities want machine-readable invoice data, in real time or close to it, for every business transaction.

Why Finance Teams Are Told Every Invoice Must Be Structured

The instruction landing on AP teams across Europe is simple: PDFs will no longer be acceptable for B2B invoicing in mandated markets. A structured e-invoice is a machine-readable XML or UBL file compliant with the European standard EN 16931. 

• An emailed PDF does not qualify. 
• A scanned paper invoice does not qualify. In clearance-model countries like Poland and Italy, an invoice that never passed through the government platform is not a valid invoice at all.

The consequences of getting this wrong are concrete. 

• In Estonia, a client can refuse to process a traditional invoice and the supplier has no legal recourse on payment terms. 
• In Poland, invoices outside KSeF carry penalty exposure. 

Under ViDA, near-real-time digital reporting will be tied directly to the invoice data, which means the tax authority sees your VAT position before you file it.

So finance leaders are doing the rational thing. They are buying e-invoicing platforms, connecting Peppol access points, mapping ERP fields to EN 16931, and onboarding suppliers into structured invoicing workflows. 

Then the influencer campaign invoices arrive.

The Contradiction: Compliant AP Meets Payees Who Cannot Invoice

Marketing pays a class of supplier that the e-invoicing project was never designed for. A campaign with 200 creators means 200 payees, and most of them are individuals. Many have no registered business. Many have no VAT number. 

• In the Nordics, 59% of creators earn less than €1,000 a month, even though 67% create content full or part-time. 
• In France, influencers below the €36,800 service threshold invoice without VAT entirely. In Belgium, the VAT franchise exemption sits at €25,000. In Austria, the Kleinunternehmer threshold was raised to €55,000 in 2025.

These are not businesses with ERP systems. Many of them struggle to produce a correct PDF invoice with the right legal fields, the right VAT treatment, and the right payment reference. 

Gigapay's 2024 State of Influencer Payments research, produced with Billion Dollar Boy, Meltwater, The Influencer Marketing Factory, and Wild, found payment terms stretching to 120 days, driven largely by exactly this friction between finance requirements and creator capabilities.

The contradiction is now structural. Finance invests in a system where every invoice must be structured. Marketing generates hundreds of payees who cannot meet the standard. Both teams are doing their jobs correctly, and the infrastructure between them fails anyway.

Why Campaign Payees Will Not Join Your Supplier E-Invoicing Network

The default corporate answer is vendor onboarding: require every vendor to register on your e-invoicing network. For a creator payee base, this fails for four reasons.

Creators Are Not Set Up as Compliant Suppliers

A Peppol connection requires an access point, a registered identifier, and software that outputs EN 16931-compliant XML. A nano-influencer doing three campaigns a year will not procure any of that. The cost and effort of becoming a structured invoicing node exceeds the value of the collaboration for most individual payees.

The Rules Change by Country

The invoicing rules your payees face are local. Croatian cross-border invoices are exempt from Fiscalization 2.0. Italian occasional workers without a partita IVA issue paper receipts because FatturaPA does not apply to them. In Bosnia and Herzegovina, VAT law requires the supplier to issue the invoice, so self-billing is not permitted at all. No single onboarding flow covers this variance, and your AP team is not staffed to learn 30 national invoicing regimes.

Enforcement Means Late Payment

If your policy is "no compliant invoice, no payment," the practical outcome is that creators do not get paid on time. Chasing, correcting, and re-issuing invoices is where the 120-day payment terms come from. Late payment damages creator relationships, and creator relationships are the asset marketing is trying to build.

The Exception List Becomes the Rule

Most e-invoicing projects include a "non-compliant suppliers" exception list for edge cases. When marketing runs creator campaigns at scale, that exception list fills up with hundreds of individuals. An exception process handling 200 entries per campaign is not an exception process. It is a parallel AP workflow with none of the controls the e-invoicing project was meant to deliver.

The Way Through: The Merchant of Record Invoice

The resolution is to separate two documents that were being treated as one.

The invoice your entity must receive, and must process through your e-invoicing path, is the invoice from your vendor. When a Merchant of Record sits between you and the creators, your vendor is the MoR. That is one counterparty, with a real finance function, capable of issuing an invoice built to whatever standard your jurisdiction and your AP system require.

The payee-side document is different. It is the record between the MoR and each creator, and it is issued by the party that can actually issue it compliantly. In most markets, that is a self-billed invoice: the MoR generates the invoice on the creator's behalf under a prior written agreement, which is the required condition in France, Belgium, Bulgaria, and most EU markets. 

Where local law prohibits self-billing, the local equivalent applies and the creator issues their own document to the MoR, never to you.

How the Invoice Flow Works With Gigapay

Gigapay operates as the Merchant of Record for creator payouts. Gigapay formally purchases the creator's deliverable and concurrently resells it to your entity, becoming the contractual counterparty on both sides. 

The flow looks like this:

1. Your team uploads a payout batch via CSV or API, covering payees in up to 65+ countries and 50+ currencies.
2. Gigapay runs KYC on every payee and validates tax IDs and VAT numbers where relevant.
3. Gigapay issues one consolidated B2B invoice to your entity per campaign or batch.
4. On the payee side, Gigapay auto-generates self-billed invoices for creators where permitted, or receives the creator's own invoice where local law requires it.
5. Creators get paid instantly over local rails like SEPA Instant, Faster Payments, and ACH.

Because creators invoice Gigapay, a Swedish entity, rather than your company, the cross-border reverse charge system generally applies for registered payees, so no VAT appears on those invoices. Individuals with no registered activity do not invoice at all; Gigapay pays the compensation and reports it to the Swedish tax authority, with exchange of income statements to the payee's local tax authority.

What This Does to Your E-Invoicing Project

Your supplier master goes from 300+ individual creator entries to one vendor entry. Your e-invoicing scope for creator spend goes from hundreds of unstructurable documents to a single invoice from a single counterparty. 

Gigapay's clients see an 80% reduction in invoice volume from consolidation alone. 

For a brand running 600 collaborations a year, the admin load drops from roughly 840 hours to about 60, and the fully loaded cost of the payment process falls from about €139,590 to about €46,350 annually.

Compliance reporting rides along. Gigapay handles DAC7 reporting for EU payees, KU14 reporting for Denmark, and flags obligations like Germany's Künstlersozialkasse, where a 4.9% levy applies to creative payments over €1,000 even for international hires.

What Not to Do When Payees Cannot Issue Compliant Invoices

Four approaches look reasonable and fail in practice.

1. Do not require sole traders to join your e-invoicing network: Requiring 200 individual creators to become Peppol participants means you will not get the invoices, and you will pay late. The compliance rate will be low, the support burden will be high, and the campaign timeline will absorb the damage.
2. Do not OCR your way through it: Scanning 200 creator PDFs into your AP system is not e-invoicing. It digitizes bad data. Every field the creator got wrong still needs a human correction cycle, and none of it satisfies a structured invoicing mandate.
3. Do not treat a payment feed as an invoice: A credit-card statement or a payout platform's transaction export is not an invoice and does not meet any e-invoicing standard. Your auditors and your tax authority need invoice documents with legally required fields, not a list of money movements.
4. Do not let the exception list absorb the problem: If your e-invoicing rollout has a non-compliant supplier list that is mostly people, the fix is structural. That entire list should collapse into one vendor.

How to Prepare Your AP Team for Creator Spend Under E-Invoicing Mandates

A practical sequence for finance teams facing a 2026 or 2027 mandate deadline:

1. Map your payee classes: Separate corporate suppliers, who can join structured invoicing, from individual payees, who cannot. Creator, affiliate, and freelancer spend belongs in the second class.
2. Count the real volume: Pull twelve months of creator-related invoices from AP. If the count is in the hundreds, the exception-list approach will not survive the mandate.
3. Confirm your receiving obligations by market: France's receiving obligation started 1 September 2026. Germany's has been live since January 2025. Your MoR invoice needs to arrive in the format your entity must process.
4. Move creator spend behind a Merchant of Record: One vendor contract replaces the individual onboarding, the invoice chasing, and the exception handling.
5. Verify the e-invoicing delivery path with your vendor: Confirm per entity and per market how the consolidated invoice reaches your AP system, and align it with your mandate timeline before enforcement dates hit.

Why the Merchant of Record Model Fits the Regulatory Direction

Every regulatory signal points the same way. ViDA pushes structured invoicing across all intra-EU B2B transactions by 2030. 

National clearance systems keep tightening: Italy's SdI moves to technical specification v1.9.1 in May 2026, and the revised EN 16931 standard for 2026 adds fields for more complex B2B scenarios without backward compatibility. More than 30 additional countries are expected to introduce mandatory e-invoicing or e-reporting by 2030.

None of that regulation makes individual creators more capable of issuing structured invoices. The gap between what AP must receive and what payees can produce only widens. A model where the compliant counterparty issues the compliant documents on both legs of the transaction is the only structure that scales with the mandates rather than against them. 

Boozt used exactly this structure to triple its creator collaborations without expanding the team, and WPPMedia's GOAT agency cut the time spent managing payments significantly after implementation.

Conclusion

Gigapay gives finance teams one compliant vendor invoice for creator spend that hundreds of individual payees could never produce themselves. 

E-invoicing mandates in Belgium, Croatia, Poland, France, and Germany have made structured invoicing non-negotiable for AP, while the payees marketing depends on remain individuals without VAT numbers, business registrations, or invoicing software. 

The Merchant of Record model resolves that contradiction: your entity receives one invoice built to your e-invoicing path, and the payee-side documents are issued by the party legally able to issue them. 

If your e-invoicing project has an exception list full of people, book a demo and turn that list into one vendor.

Read Next:

• Contingent Workforce Payouts: When You Need a Contractor Stack, Not an Employer of Record
• Procure-to-Pay Breaks on People: Why Services Payees Never Fit the PO–GR–Invoice Model
• W-9, W-8BEN, and 1042-S: The Foreign-Vendor File AP Must Have Before the First Payment

FAQs:

1. What is the best way to handle e-invoicing when a payee cannot issue a compliant invoice? 

The best way to handle e-invoicing when a payee cannot issue a compliant invoice is to route the payment through a Merchant of Record, which issues one compliant vendor invoice to your entity and manages the payee-side documents through self-billing or local equivalents.

2. Does Gigapay send invoices through PEPPOL? 

Whether Gigapay sends invoices through PEPPOL depends on the entity and market involved, since mandate scope for cross-border invoices differs by country, so the delivery path for your consolidated invoice is confirmed per entity during scoping with the Gigapay team.

3. Is a credit-card feed considered e-invoicing? 

A credit-card feed is not considered e-invoicing, because a transaction feed contains no invoice document, no legally required invoice fields, and no structured EN 16931 data that a tax authority or auditor would accept.

4. Does a Merchant of Record replace AP invoice OCR for creator payments? 

A Merchant of Record replaces AP invoice OCR for creator payments by removing the documents that needed scanning, since one structured vendor invoice per campaign replaces the hundreds of creator PDFs your team would otherwise digitize and correct.

5. Which countries made B2B e-invoicing mandatory in 2026? 

The countries that made B2B e-invoicing mandatory in 2026 include Belgium from January 2026 via Peppol, Croatia from January 2026 under Fiscalization 2.0, Poland from February 2026 via KSeF, and France, where every VAT-registered business must be able to receive e-invoices from September 2026.