E-commerce Accounting Integration — Invoicing on Autopilot [2026]

E-commerce accounting integration automates what most stores still do by hand: creating invoices from orders, recording payments, handling credit notes and returns, and passing data to the accounting office. At a few dozen orders a month that is a dozen hours of work; at a few hundred — a full-time job. This guide covers exactly what gets automated, which systems are involved (Fakturownia, iFirma, Comarch, accounting-office software), what it costs and how to avoid the mistakes that get expensive in your books.

Key takeaway: E-commerce accounting integration creates invoices automatically from orders, records payments, handles credit notes and returns, and exports data to the accounting office. Typical flows: store → Fakturownia/iFirma/Comarch (documents), payment gateway → accounting (statuses), accounting → store (document statuses). Cost: from 1,500 PLN for a simple scenario to 8,000+ PLN for full automation with marketplaces and multiple VAT rates. Delivery: 3–10 business days.

What can be automated in store accounting

The scope of automation is wider than most people assume. Here are the flows that run without a human in mature stores.

• Invoices from orders — the document is created the moment an order is paid, with the customer's data and order lines, numbered according to the series.
• Company invoices — an order with a tax ID requires an invoice to company details, often with reverse charge or a 0% rate for exports.
• Payment statuses — the payment gateway notifies accounting that the order is paid; no document waits for manual confirmation.
• Receipts and receipt-to-invoice conversion — for retail sales and post-purchase invoice requests.
• Credit notes and returns — a store return generates a correcting document without manually finding the original invoice.
• Marketplace documents — selling on Allegro or Amazon requires its own documents and commission accounting.
• Reports for the accounting office — exporting orders and documents in a format the office accepts without re-typing.

A store that automates accounting gains more than time: consistency. The document always matches the order, and the gap between sales and bookkeeping stops being a "we'll check it someday" item.

Accounting systems and integration models

The market has a few clear groups of solutions — the choice depends on where documents are created today.

The integration model follows whoever runs your books.

• Store with its own online accounting (Fakturownia, iFirma) — API integration; invoices appear immediately and payment statuses return to the store. The simplest and most common scenario.
• Store with an accounting office — automation is usually limited to exporting data and documents in the office's format; full API integration is rarely possible, but the export still eliminates re-typing.
• Store with an ERP (Comarch, Subiekt, enova) — accounting is part of the ERP integration; the ERP issues documents and the store receives statuses and files. I cover this in the e-commerce ERP integration guide.

Automatic invoicing in practice

The scenario I deliver most often looks like this.

• The customer places and pays for an order (BLIK, Przelewy24, PayU, card).
• The payment gateway confirms payment by webhook; the order changes status.
• The integration creates the document in the accounting system: buyer details, lines, VAT rates, payment method.
• The accounting system returns the document number; the store saves it with the order and attaches the PDF to the customer email.
• Credit notes and returns generate correcting documents automatically, based on the original order.
• Once a day, a reconciliation report compares store orders with accounting documents and flags differences.

That last point is the key element. Automation without reconciliation is automation that quietly generates errors — and errors in accounting are more expensive than anywhere else in a store.

Accounting integration pitfalls

These problems cost the most because they surface during an audit or month-end close.

• VAT rates and procedures — exports, reverse charge, OSS for cross-border consumer sales. Rate mapping must be explicit and tested, not "default".
• Tax point timing — invoice on payment or on dispatch? It is a tax decision; the integration must implement the agreed process, not the other way around.
• Duplicate documents — a repeated webhook without idempotency can create two invoices for one order. Every flow must be idempotent.
• Customer data — typos and incomplete addresses end up on documents. Validate tax IDs and addresses in checkout, before the order reaches accounting.
• Amendments after order changes — changing order lines after a document is issued requires a proper credit-note process, not an edit "in place".
• Accounting office in the chain — if the office runs its own software, the integration ends at the export; agree the format and the delivery rhythm.

The security of these flows (queues, retries, event logs, alerts) is covered in designing resilient API and webhook integrations.

How much accounting automation costs

Ranges depend on the number of scenarios and systems.

• Simple scenario (store → Fakturownia/iFirma: invoice from order, payment statuses) — from 1,500 PLN net.

• Extended scope (company invoices with tax IDs, credit notes, returns, receipts, office export) — 3,000–6,000 PLN net.

• Full multi-channel automation (store + marketplaces + ERP + accounting, reconciliation reports) — 8,000 PLN net and up, usually as part of an ERP integration.

• Maintenance — from 400 PLN net per month when the integration needs monitoring and API-change response.

• For comparison: manual invoicing takes 2–5 minutes per document. At 300 orders a month, that is 10 to 25 hours of work. Automation pays back within the first months — and the cost of errors (credit notes, interest, your accountant's time) does not occur at all.

Frequently asked questions

How much does store-to-accounting integration cost?

A simple scenario (automatic invoices from orders and payment statuses) starts at 1,500 PLN net. An extended scope with company invoices, credit notes and accounting-office export runs 3,000–6,000 PLN net. Full multi-channel automation with reconciliation reports starts at 8,000 PLN. Maintenance from 400 PLN net per month.

Does it work with an accounting office that uses its own software?

Usually yes — in export mode. The store prepares documents and data in a format agreed with the office (most often import files for tools such as Rachmistrz or WAPRO), and the office imports them without re-typing. Full API integration is only possible when the office software exposes an API — worth asking before the project.

When is the invoice created — on order or on payment?

It is a tax decision made by your accountant or tax adviser, and the integration implements it. The most common variants are issuing on payment (online retail) or on dispatch. Regardless of the choice, the data flow is the same — only the trigger moment differs.

Will automation handle company invoices and cross-border sales?

Yes, but it requires explicit design: buyer details with tax IDs, reverse charge, 0% rate for exports, OSS for consumer sales within the EU. This is the area where cutting corners on analysis hurts most — a mistake in rate mapping can cost more than the entire delivery.

What happens if the integration creates a wrong document?

A well-designed integration has an event log and a reconciliation report — the error surfaces the same day, not at year-end close. A wrong document is corrected through the credit-note process, like any other. The key is idempotency: a repeated event must not create a second document.

Can the integration issue receipts and convert them to invoices?

Yes. For retail sales, receipts can be automated (with a system that supports them), and for customers who request an invoice after purchase — the invoice is created from the order data without manually searching the system.

Can I start with just invoicing and add the rest later?

Yes, and it is a sensible start. Automatic invoices from orders are usually the single biggest gain (a dozen hours a month) with the smallest delivery scope. Later stages — credit notes, returns, marketplace accounting, office exports — are added to a working foundation.

Sources and tools

• Fakturownia — API documentation
• iFirma — integrations and API
• Comarch ERP Optima — documentation
• Przelewy24 — developer documentation
• Polish Ministry of Finance — e-Invoicing (KSeF)

👉 Want invoices that create themselves? See e-commerce integrations and APIs — automatic documents, payment statuses and marketplace accounting. Write through the contact form or at kontakt@informatix.com.pl.

📖 See also: e-commerce ERP integration, marketplace integration and how much an e-commerce integration costs.