Connecting Your Website to SmartBill or Oblio: Automatic Invoices From Orders

If you sell online and still issue every invoice by hand, you're losing time exactly where order volume grows. You copy the customer's name, the products, the VAT, hunt for the right series, save the PDF, email it. At a few orders a day it's fine. At dozens, mistakes and delays creep in.

The good news: both SmartBill and Oblio expose APIs that let your website issue the invoice on its own, within seconds of payment. The customer gets the PDF automatically, everything already shows up in your accounting, and the e-invoice goes to the tax authority without you touching a thing. In this article I'll explain, concretely, how the integration works, what to prepare beforehand, and where things most often break.

What an integration with SmartBill or Oblio actually means

The integration is a bridge between your shop and your invoicing software. When a customer places an order and pays, your site automatically sends everything the invoice needs to SmartBill or Oblio through their API: the buyer, the products, the prices, the VAT rate and, for a company, its tax ID.

The invoicing software generates the invoice on your configured series, assigns a number, and returns the PDF. From there, depending on how we set the flow:

• the invoice lands automatically in the customer's inbox;
• it's saved in your invoicing account;
• it's pushed to e-invoicing (the tax authority).

All of this happens in seconds, with nothing to open. In practice, the order on your site and the fiscal invoice become one motion, not two separate tasks you do by hand in the evening.

SmartBill or Oblio — does it matter which?

Technically, both are solid Romanian solutions with an API and support for mandatory e-invoicing. There's no clear winner; the right decision is the most boring one possible: pick what your accountant already uses or prefers, so the data flows straight into your books.

A few practical things to compare:

• the ready-made plugin ecosystem (for example for WooCommerce) — one may have a more mature integration for your platform;
• the pricing model and the invoice limit in your plan;
• which e-invoicing and credit-note (storno) functions the API exposes.

If you're starting from scratch, ask your accountant first. If you already run one of them, switching just for the integration almost never pays off.

What we prepare before starting the integration

Most problems come not from code but from settings made in a hurry. Before integrating, we lock down a few things:

• The account and API key (token/email) from SmartBill or Oblio.
• A dedicated invoice series for online orders, separate from invoices you issue by hand — otherwise the numbering collides.
• Correct VAT rates on each product (not everything shares the same rate).
• A tax-ID field at checkout for business customers, so the invoice is issued to the company.
• The decision: do we issue a proforma or a fiscal invoice directly?
• The trigger moment: at order placement, at payment, or at shipping.

We make these calls once, at the start. Get them right now and the integration runs for months without intervention.

E-invoicing: why the integration no longer stops at the PDF

In Romania, electronic invoicing through the tax authority's system has become mandatory, first for business-to-business and then extended to individuals too. In practice, it's no longer enough for your site to spit out a pretty PDF — the invoice must also reach the tax system, in XML format.

Here's the upside: both SmartBill and Oblio can forward the invoice into the official system. A properly built integration triggers that step automatically too, not just the PDF.

For it to go through without rejections, the details matter:

• a valid, correctly formatted tax ID for business customers;
• complete identification data;
• VAT rates that match the order total.

That's the difference between an integration that merely produces invoices and one that actually keeps you compliant.

What breaks most often (and how to avoid it)

From experience, this is where nearly all the headaches live:

• Duplicate invoices: if the payment fires the signal twice, you can get two invoices for one order. Fixed with a check that ties the invoice to the order ID.
• Unverified tax ID: the company rejects the invoice because the data doesn't match. We validate the tax ID at checkout.
• VAT rounding: the site total doesn't match the invoice total to the cent. We align the calculation method.
• Exhausted series: you run out of numbers and invoicing stalls. We monitor it.
• Returns and cancellations: the credit note (storno) won't happen on its own unless we plan for it.

The golden rule: we test on a test series, never straight on real invoices.

How we approach the integration at MPO Web Studio

We build websites for local businesses and deliver fully remotely, anywhere in the country — so where you are doesn't matter. On the invoicing side, we start from your real flow: what you sell, to whom (companies, individuals, or both) and what software you already have.

Before any commitment, we can prepare a ready-made demo so you actually see the order-to-invoice-to-e-invoice path rather than just hearing us promise it. Pricing is transparent, agreed up front, with no surprises.

If you want invoices to issue themselves from orders and to stop losing evenings copying data, message us on WhatsApp and we'll tell you honestly what's possible for your shop and how long it takes. No hard sell — first we check whether it's worth it.