Invoicing API for Marketplaces
Automated dual invoicing in a single call
Manage your marketplace invoicing professionally. Issue two simultaneous invoices: professional to end customer and marketplace to professional. All with a single API call.
Why does your marketplace need automated invoicing?
In a marketplace, each transaction creates two distinct business relationships that require independent tax documentation.
Mandatory dual invoicing
The professional must invoice the end customer for the service provided, and the marketplace must invoice the professional for the commission. These are two distinct tax operations that occur simultaneously.
Critical synchronization
Both invoices must be issued at the same time to maintain accounting consistency. A timing error can create tax discrepancies for your professionals and your platform.
Regulatory compliance
Each invoice must comply with VeriFactu, income tax, VAT and all Spanish regulations. A receipt or payment confirmation is not enough — you need fiscally valid invoices.
Model scalability
With hundreds or thousands of daily transactions, manually generating two invoices per operation is unfeasible. Automation is not optional — it is essential for growth.
Data segregation
Each professional should only see their own invoices. The marketplace manages commissions separately. The API maintains this separation naturally and securely.
User experience
Your professionals expect everything to work automatically. Confirming a job, getting paid and receiving the invoice without manual intervention improves retention and satisfaction.
How the integration works in your marketplace
A simple flow that integrates with your payment system and order management.
Customer hires a service on your platform
The customer chooses a service or product offered by a professional on your marketplace. They accept the price and confirm the booking.
- Your system records the transaction with all details
- You calculate your commission based on your business model
- You store customer, professional and order IDs
Payment processor confirms the charge
Stripe, PayPal or your payment gateway processes the charge to the customer. The money enters your marketplace account.
- You receive the payment confirmation webhook
- You have the processor transaction ID
- The service is ready to be executed
Your system calls the BeeL. API (2 invoices)
In your confirmed payment webhook, you make two API calls: one for the professional-to-customer invoice, and another for the marketplace-to-professional invoice.
- First call: professional invoices the customer for the full service
- Second call: marketplace invoices the professional for the commission
- You use X-Idempotency-Key to prevent duplicates if the webhook retries
Invoices issued, PDFs sent automatically
BeeL. generates both invoices with sequential numbering, VeriFactu compliance, and sends the PDFs by email to the end customer and the professional.
- Invoice 1: Customer receives PDF from the professional with the service breakdown
- Invoice 2: Professional receives PDF from the marketplace with the deducted commission
- Both invoices registered and available via API for reporting
Reporting and reconciliation
All invoices remain accessible via API. You can list, filter and download for your dashboards, accounting or audits.
- GET /invoices endpoint with filters by date, customer, status
- Export data for your commissions dashboard
- Data ready to hand over to your accountant or bookkeeper
Benefits of automating with the BeeL. API
You don't just save time. You reduce legal risks, improve your professionals' experience and scale without friction.
Built-in idempotency
If your webhook fires twice due to a restart, invoices won't be duplicated. The API recognizes the idempotency key and returns the original invoice.
Guaranteed compliance
VeriFactu, income tax, VAT, sequential numbering... all Spanish tax complexity handled automatically. You focus on growing the marketplace.
Zero maintenance
Regulations change constantly. We update the API to maintain compliance. Your code keeps working without changes.
Real scalability
Whether you issue 10 or 10,000 invoices per month, the API is designed to grow with you with no performance degradation or code changes.
Frequently asked questions about marketplace invoicing
Does each professional need their own BeeL. account?
Yes. Each professional who invoices through your marketplace needs their own BeeL. account and API key. This ensures each one manages their own invoices, taxes and fiscal compliance independently. The marketplace has its own account for invoicing commissions.
Can I issue both invoices in a single call?
Not directly. They are two distinct tax entities (the professional and the marketplace), so they require two API calls with different API keys. However, you can execute them in parallel from your backend in the same process, making the operation virtually instantaneous.
What happens if a professional doesn't have a BeeL. account?
You need to onboard your professionals so they sign up for BeeL. and activate the API plan. You can offer technical support or even subsidize the cost as part of your value proposition. Without an active account, they won't be able to issue legal invoices through your platform.
How do I handle refunds or cancellations?
Use credit notes. The API allows you to create credit notes that void or modify previously issued invoices. Simply reference the original invoice and specify the reason for the correction. The system automatically handles the invoice chain.
Does the API support variable or tiered commissions?
Yes. You calculate the commission in your system according to your business rules (fixed percentage, volume tiers, etc.) and send the final amount to the API. BeeL. doesn't need to know your commission logic — it just receives the amount to invoice.
Ready to automate your invoicing?
Integrate BeeL.'s API and start invoicing in minutes.