What does this integration do?
With the BirFatura integration, an e-archive or e-invoice document is created automatically for Shopify orders, sent to the customer, and the invoice number written onto the order. Shipping and accounting steps can run in the same flow.
The data it synchronises
e-Archive / e-Invoice creation
Invoice number written back
Customer detail matching
Credit notes
Bulk invoicing
VAT and tax rules
How the data flows
01
The buyer type is checked
Whether the buyer is registered for e-invoicing is checked from their tax/national ID number. Registered buyers get an e-invoice, others an e-archive document. If that split is not automatic, documents are issued in the wrong form.
02
The document is created
The document is prepared with order lines, shipping charge and discount distribution; VAT rates are applied per product.
03
The tax authority process runs
The document is submitted and its status monitored. A follow-up list is kept for rejected or failed documents; a document that fails silently is the worst case.
04
The number is written to the order
The invoice number and document link are written onto the Shopify order, so the customer can reach it from the order page.
05
Returns and corrections
A credit note is issued on returns. On partial returns, which line was returned and for how much is reflected accurately on the document.
What we watch for in this integration
The buyer check must be automatic; where it is left to manual selection, the wrong document type is inevitable
If products with different VAT rates are in the same cart, discounts must be distributed proportionally by rate
Export invoicing for international sales is a separate flow and cannot use the same template
If document statuses are not monitored, faulty documents surface as a mass problem at month end
The trading name and address on the invoice must come from a single source: the billing address or the delivery address
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
BirFatura account and integration credentials
Your e-invoice / e-archive registration status
VAT rates per product
Whether you sell internationally
Your preference on when the invoice is issued