VAT Engine @VAT_Engine

@yusuf_devs Thanks, Yusuf, that answers it. Keeping the original rates and totals with each invoice is the detail we were interested in. Appreciate you explaining it!

Today's VAT rate isn't automatically the right rate for an old transaction. Refunds, corrections & migrations need the original transaction date — and ideally the evidence behind the historical rate. vat-engine.app/blog/current-v… #VAT #API #TaxTech

@VatForge I'm building VAT Engine. For imported sales with a VAT number but no recorded business-use decision, do you keep a separate review state? I'm interested in how you preserve that uncertainty in the accountant export.

@FluentCartWP The 1.4.0 section on saving the tax decision stood out. For partial refunds, do you reuse the original line's VAT and rounding if rates or store settings have changed since checkout? We're building VAT Engine and researching this edge case.

@Susmit03514564 For EU invoices, are VAT rates entered manually or looked up by country and tax class? We're building VAT Engine, an EU VAT API, and I'm curious whether that part is something you'd want to automate in InvoiceMaker.

@giubuilt @dudufolio @whop We're building VAT Engine, an EU VAT API. In your custom checkouts, is the gap mainly getting registration IDs and coverage onto invoices, or do you also need a separate VAT calculation service?

@thiagodea_ Estamos construindo o VAT Engine, uma API de VAT para a UE. Você precisa de um MoR para cuidar também da declaração e do pagamento dos impostos, ou consideraria checkout próprio com uma API só para o cálculo? Já vende para clientes na UE?

A VAT calculation record should preserve more than: VAT = €19 You also need the rate, date, tax class, source, calculation version, provenance, and replay status. I wrote about the data model behind explainable VAT calculations: vat-engine.app/blog/what-shou… #API #VAT #Fintech

@Profflow_co Thanks, that's clear. For partial refunds on mixed-rate orders, do you match the refund to specific line items, or allocate it proportionally across the order?

@GlobalLawExpert For non-resident ecommerce sellers, what tends to hold up Czech VAT registration most often in practice: missing documents, or clarifying the planned sales and stock locations?

@hellotax1 When an Amazon seller moves from Pan-EU storage to EFN + OSS, which part of the VAT reporting handover tends to be messiest in practice?

@samboboev Sam, for a small SaaS team selling internationally, what usually tips the choice between a payment + tax stack and a merchant of record: filing admin, fees, or control over checkout?

When reviewing ecommerce VAT data, what information is most often missing from the transaction record? Curious how you handle it in practice. #VAT #TaxCompliance #Accounting

Money should not silently inherit floating-point semantics. €19.99 → 1999 minor units 19% VAT → 1900 basis points Then make rounding explicit. I wrote about why this matters for VAT & financial APIs: vat-engine.app/blog/why-money… #API #Fintech #VAT

VAT-inclusive ≠ VAT-exclusive math. Net → gross: VAT = Net × Rate Gross → net: VAT = Gross × Rate / (1 + Rate) Using Gross × Rate to extract VAT is wrong. I wrote a developer-focused breakdown: vat-engine.app/blog/vat-inclu… #VAT #API #TaxTech

For OSS preparation, what usually takes more time: calculating VAT, cleaning transaction data, or validating the evidence behind it? Curious how you handle it in practice. #VAT #TaxCompliance #Accounting

When reviewing an ecommerce VAT transaction months later, what information do you need to see to trust why that VAT treatment was applied? Curious how you handle it in practice. #VAT #TaxCompliance #Accounting

Selling SaaS subscriptions across the EU? VAT gets complicated fast once renewals, refunds, historical rates, product tax classes, and OSS reporting enter the picture. I wrote a practical use case on how to keep EU VAT logic out of your billing code with an API-first approach: vat-engine.app/use-cases/saas… #VAT #SaaS #TaxTech #API #OSS #EUVAT #subscription #billing #refunds