.jpg)
Ardent Partners' 2025 State of ePayables research puts the fully loaded cost of processing a single invoice at $10.89, with top-performing AP teams closing each one in 3.1 days versus 17.4 days for the industry average (cited in AP benchmarking reports published July 2026).
For finance leaders running creator programs at scale, that math gets painful fast, since every creator paid as an individual supplier becomes a full AP cycle, and the volume compounds until the queue is stuffed with low-value invoices that no automation tool was designed to absorb.
Gigapay is the Merchant of Record for creator payouts, which means Gigapay becomes the single vendor of record on the client side and takes on the compliance, payouts, and creator support so your AP and finance stack does not have to.
Finance and procurement leaders looking at Gigapay now ask a specific question, which is where an MoR actually sits in a stack that already includes Coupa, SAP Ariba, Oracle NetSuite, Workday, Zip, and Tipalti.
This article maps the full answer, explaining what an MoR is, where it plugs in, what it replaces, what it coexists with, and what to look for when evaluating one.
Key Takeaways
- An MoR replaces hundreds of creator supplier records with one vendor entry in your ERP.
- Gigapay handles KYC, DAC7 filing, KSK levy, and self-employment admin on your behalf.
- AP automation moves invoices, and an MoR removes most of those invoices from the queue.
- Gigapay coexists with Tipalti, Coupa, NetSuite, and SAP as the creator payments lane.
- Creator payments flow through the MoR before they ever hit three-way matching.
The AP Stack Was Built for Suppliers, Not for Creators
Every AP and procurement tool in your stack was designed around the same mental model, which is a supplier who has a company, a VAT number, a purchase order, a formal invoice, and payment terms measured in weeks.
- Coupa handles the sourcing and requisition.
- Ariba routes the PO.
- NetSuite or SAP holds the vendor master.
- Workday touches the workforce side.
- Zip runs intake.
- Tipalti or Bill.com pushes the payment out at the end.
That flow works beautifully when you are paying a media agency €80,000 a quarter or a software vendor €30,000 a month.
Creator payments break the model on almost every dimension. A nano-influencer is not a company. A German student micro-creator has no VAT number, no purchase order, and no interest in your two-page vendor onboarding form.
A payout of €400 does not survive a three-week approval cycle because the creator will churn, complain publicly, or refuse the next campaign. And the volume is the killer, because a mid-sized brand running 600 collaborations a year is running 600 new supplier records, 600 tax-form checks, and 600 individual bank details through a stack that was priced and staffed for a supplier base a fraction of that size.
The result is that finance and procurement inherit an operational tax that was never budgeted for. Ardent Partners' research on invoice processing cost tells you what a single invoice cycle costs at industry averages, and multiplying that number by a creator program's transaction count is the point where most CFOs start asking whether the payment layer for creators needs its own lane.
The Compliance Layer That Now Sits Above Every Creator Payment
The problem is not just volume. The compliance environment around creator payments in Europe has changed faster in the last 24 months than any other B2B category, and the finance stack has not caught up.
DAC7 is now live across every EU member state and requires platforms and businesses running seller relationships with individuals to collect verified tax data, report annually to national tax authorities, and offboard sellers who do not provide it. German fines run up to €50,000 per report. Sweden charges SEK 2,500 to SEK 12,500 per unreported seller.
Germany's KSK levy on payments to creators, artists, and journalists is 4.9% on gross fees above €1,000, and the DRV is now running KSK-only out-of-cycle audits with retroactive years and fines running to €50,000. NRW criminal investigators are pursuing roughly 200 proceedings tied to influencer tax evasion. Hamburg's tax office is auditing 140 influencers.
France's Loi Influence requires written contracts above €1,000 per advertiser per year with mandatory clauses on pain of nullity, and French e-invoicing takes full effect on 1 September 2026. The UK's Joint and Several Liability rules for umbrella arrangements have been live since 6 April 2026, and IR35 fee-payer liability now sits with the agency.
The EU Platform Work Directive is transposed by 2 December 2026, which introduces a rebuttable presumption of employment that platforms and creator marketplaces will have to answer for. Spain's IRPF withholding regime (15% or 7%) sits on top of Modelo 111, Modelo 190, and Modelo 238 filings, plus the VeriFactu invoicing-software rules.
None of that shows up as a native feature in Coupa, NetSuite, Ariba, Workday, Zip, or Tipalti. Each of those tools moves the money and generates the paperwork, and each of them leaves the compliance duty sitting with your legal, tax, and finance teams. The Merchant of Record model exists to take that duty off the buyer's stack.
What a Merchant of Record Actually Does Inside Your Flow
A Merchant of Record is a legal counterparty structure, not a payment feature. Gigapay is the counterparty that formally purchases the creator's deliverable and concurrently resells it to your business, which means the paperwork, tax reporting, and creator relationship legally sit with Gigapay rather than with your ERP.
- Your business signs one contract with Gigapay.
- Your business receives one consolidated invoice per campaign or per batch.
- Your business books one vendor record in NetSuite, SAP, or Workday.
The mechanics on the creator side look like this. Gigapay onboards each creator, runs KYC and identity verification, validates tax IDs and VAT numbers where they exist, generates self-billing invoices under the local self-billing rules of each market, files the local platform-reporting duty (DAC7 across the EU, KU14 in Sweden, KSK-relevant records in Germany, Modelo 238 in Spain), and pays each creator instantly on the local rail, which means SEPA Instant in the EU, Faster Payments in the UK, and ACH in the US.
On new plans the client covers the fees, so creators keep what they earn on Gigapay.
The mechanics on your side look like this. You upload a spreadsheet or call the Gigapay API with the list of creators, amounts, and campaign reference. Gigapay pays out. Gigapay sends you one invoice, one line per campaign in the ERP, and one auditable record for the compliance filing.
That is the structural difference between a Merchant of Record and any payment rail, AP tool, or procurement platform in your existing stack, which is that the MoR becomes the vendor, absorbs the compliance duty, and lets your existing stack keep doing what it does best.
Where a Merchant of Record Plugs Into Your ERP
Oracle NetSuite, SAP, and Workday are the three ERPs that carry most of the finance stack pressure at mid-market and enterprise brands. The MoR sits upstream of all three.
Instead of creating a vendor record for each of the 300 creators in a campaign, your NetSuite or SAP vendor master receives one vendor entry called Gigapay Sweden AB. Instead of 300 individual invoices routed through OCR, GL coding, three-way matching, and payment scheduling, your AP team processes one consolidated invoice per Gigapay batch.
The GL entry can be split by cost centre, brand, market, or campaign using the metadata Gigapay carries through the API, which means finance still gets the reporting granularity without inheriting the record volume.
The Goat Agency inside WPPMedia has explained the practical difference in exactly those terms. Their team went from managing hundreds of individual creator payment records to processing a single consolidated invoice per campaign, which is a reduction in ERP maintenance load that shows up directly in the AP team's hours-per-invoice ratio.
The clean rule is this. Your ERP is still the system of record for financial truth. The MoR is the system that stops the ERP from being the system of record for every creator's bank account.
Where a Merchant of Record Plugs Into Your AP Automation
Tipalti, Coupa Pay, Bill.com, and their peers are AP automation platforms. They excel at moving invoices from receipt to payment, running OCR, matching to POs, handling exceptions, and pushing electronic payments across corridors. They do not, however, take on legal counterparty status for the underlying payee. That distinction matters.
The clean coexistence pattern for a stack that already includes Tipalti or Coupa Pay looks like this. Tipalti keeps handling your supplier AP, which is the vendors, contractors, media agencies, SaaS bills, and freelance production houses that are already companies with VAT numbers.
Gigapay handles your creator payments lane, which is the individuals, the micro-creators, the cross-border payouts that fall outside the vendor onboarding model, and the campaigns that carry DAC7, KSK, KU14, or Modelo 238 filing exposure.
In that arrangement Tipalti receives one Gigapay invoice per campaign, exactly the same way it receives an invoice from any other approved vendor, and the compliance layer around 300 creators never touches the Tipalti workflow. The two tools serve different problems, and the cost model reflects that.
Rate-matching an AP automation tool against a Merchant of Record is a category error, because you are comparing a rail to a counterparty structure.
Where a Merchant of Record Plugs Into Your Procurement Stack
Coupa, SAP Ariba, and Zip run the intake, sourcing, contracting, and PO-issuance layer for most enterprise finance stacks. Their vendor onboarding modules assume a supplier who can complete a formal onboarding questionnaire, sign a master services agreement, and hold a business bank account.
An MoR flips the procurement problem into a supplier consolidation problem, which is the vocabulary procurement teams already speak. Instead of onboarding 300 creator vendors through Coupa Supplier Management or Ariba SLP, you onboard Gigapay once as an approved global supplier.
Gigapay runs the creator-side onboarding, the KYC, and the tax and identity verification behind the scenes, and every new creator added to a campaign inherits your existing approved-supplier status through Gigapay. The intake ticket in Zip closes on day one, not on day 45.
The critical reframe for procurement is that the creator category, which has historically been a maverick spend problem hiding under marketing budgets, becomes a managed spend category under a single supplier of record.
That is the language procurement teams need to justify the model internally, because it turns a category of hundreds of low-value micro-vendors into a single strategic supplier with a proper contract, SOC2 documentation, DPA, and insurance evidence.
What the Merchant of Record Replaces Versus What It Coexists With
The clearest way to see where the MoR sits is to draw the boundary between the tools it replaces at the creator-payments layer and the tools it leaves alone.
The pattern in that table is that the MoR removes the highest-friction, lowest-value work from finance and procurement while leaving your investment in AP automation, procurement intake, and the ERP itself completely intact.
What Actually Transfers When the MoR Takes on the Compliance Layer
Buyers reasonably ask what the MoR structure actually transfers, because "compliance" is a word that can be stretched to hide a lot of vagueness. The precise version of the answer is worth writing down.
Gigapay takes on the platform-operator duty for DAC7 across the EU, which means Gigapay collects the seller data, files the annual report to the relevant tax authority, and manages the seller-offboarding rule after two reminders plus 60 days.
- Gigapay runs the KYC and identity verification for every payee.
- Gigapay generates the self-billing invoice under the local self-billing framework of each market, including RD 1619/2012 in Spain and equivalent frameworks in Sweden, Germany, France, and the UK.
- Gigapay records and reports the KSK-relevant creator payments in Germany where applicable.
- Gigapay carries the platform-side onboarding responsibility for creators who are not registered businesses, which is a category most AP and procurement tools cannot process at all.
Two lines about what does not transfer, because being honest here builds the trust that closes finance and procurement deals. Worker classification and misclassification exposure sit within a wider regulatory regime that is still evolving under the EU Platform Work Directive, and the counterparty structure Gigapay provides changes where the exposure sits without promising to eliminate it.
Corporate income tax on the buyer's side does not transfer, because that sits with your business regardless of how the creator is paid. Those are the two boundaries to keep on the whiteboard when you are running the internal case with legal and tax.
The Evaluation Checklist Finance and Procurement Leaders Should Run
If you are running an evaluation against Gigapay or any other creator-payments vendor that describes itself as an MoR, the following checklist is the one your finance and procurement teams should apply.
- Ask the vendor to walk you through a DAC7 filing they have submitted as the reporting platform operator, including the seller-offboarding logic and the fine exposure they assume.
- Ask how a 19-year-old German micro-creator with no company, no VAT number, and no invoicing software gets paid, and who owes the KSK levy on that payment.
- Ask for the written FX schedule and the payout speed by corridor, including the SLA if a payment fails.
- Ask what their platform reporting scope covers in Spain (Modelo 238, IRPF, Modelo 111, Modelo 190), because Spain is the market where most competitors quietly forfeit.
- Ask for their SOC2 report, DPA, insurance evidence, and SIG-Lite pack. If they cannot produce them, the evaluation ends there for enterprise procurement.
- Ask who covers the payment fees on new plans, because a Merchant of Record that pushes fees onto the creator is one that will cost you creator retention.
- Ask them to confirm the consolidation ratio, meaning how many creator invoices collapse into one consolidated invoice against the ERP.
- Ask for a named reference in a comparable brand or agency category, ideally in the same corridor mix you operate in.
- Ask how their MoR structure interacts with an existing Tipalti, Coupa Pay, or Bill.com deployment, because the answer will tell you whether they understand the coexistence model or think they are replacing your entire AP layer.
That checklist filters out the payment rails, the AP tools, and the regional single-country vendors on the first pass, and it forces every remaining vendor to answer the compliance question rather than the rail question.
Conclusion
Gigapay is the Merchant of Record for creator payouts, which means Gigapay becomes the single vendor of record and takes on the compliance, payouts, and creator support that no other layer of your finance stack was designed for.
The AP and finance stack you already own does the work it was built for, which is running the ERP, running AP automation, running procurement intake, and running the payment rails.
The MoR sits above all of it as the counterparty that stops the creator payments lane from turning into a permanent operational tax on the AP team.
If you are mapping the model against your own stack and want to see where Gigapay would slot in, book a demo with the Gigapay team and walk through your specific setup with someone who has already built the answer for teams running the same tools you are.
Read Next:
- Influencer Payment Terms Decoded: Net-30, 50% Upfront, and Milestone Payments
- Paying Creators Globally: Why Gigapay Beats Traditional Payout Providers
- Influencer Payment Tax Compliance in 2026: 1099s, W-9s, and DAC7 Explained
FAQs:
1. What is a Merchant of Record for creator payouts?
A Merchant of Record for creator payouts is a legal counterparty that formally purchases the creator's deliverable and resells it to the client, which means the tax reporting, KYC, self-billing, and platform-reporting duties sit with the Merchant of Record rather than with the client's finance stack.
2. How does a Merchant of Record fit alongside Tipalti in an AP stack?
A Merchant of Record fits alongside Tipalti in an AP stack by coexisting with it, because Tipalti keeps handling supplier AP for vendors with companies and VAT numbers, and the Merchant of Record handles the creator-payments lane and delivers one consolidated invoice per campaign into Tipalti.
3. Which ERPs does Gigapay work with as a Merchant of Record?
Gigapay works with every major ERP as a Merchant of Record, including Oracle NetSuite, SAP, and Workday, because Gigapay appears as a single vendor entry in the vendor master and delivers one consolidated invoice per batch or campaign that is then processed through the client's existing AP workflow.
4. Does a Merchant of Record replace Coupa, Ariba, or Zip?
A Merchant of Record does not replace Coupa, Ariba, or Zip. It coexists with them by being onboarded once as a single approved supplier of record, and every creator paid through the Merchant of Record inherits that approved-supplier status without triggering a new intake ticket in the procurement stack.
5. What compliance duties does Gigapay take on as the Merchant of Record?
Gigapay takes on the DAC7 platform-operator duty across the EU, KU14 reporting in Sweden, KSK-relevant recording of creator payments in Germany, Modelo 238 platform reporting in Spain, KYC and identity verification for every creator, and self-billing invoice generation under local self-billing frameworks in each market Gigapay operates in.
.jpg)
.jpg)
