Separate collection from filing
Bring committed supply events and registration context into review; individual calculator calls are not a filing population by themselves.
Reporting preparation, not filing advice
OSS and IOSS reporting
VAT Engine connects committed supply-event data, registrations, thresholds, exchange-rate normalization, and review states to help teams prepare VAT reporting work.
What this helps you do
Surface missing evidence and produce structured review outputs before an accountant or responsible business user files a return.
- OSS threshold monitoring and registration-aware views.
- Union OSS and IOSS preparation workflows with explicit exclusions and warnings.
- Immutable return/export snapshots after locking.
- VAT Engine does not submit returns or decide legal filing obligations.
How to use it well
Resolve exceptions before lock
Use warnings and excluded records to identify missing destination, classification, or registration evidence before preparing an export.
Choose the scheme with care
OSS and IOSS have different eligibility and reporting conditions; the IOSS scheme concerns certain imported low-value goods up to €150.
Prepare a reporting period for accountant review
A finance team needs to know which committed supplies are included, excluded, or still awaiting evidence before preparing an export.
- Start with committed supply-event records and the business’s registration context. Calculator history alone is not the reporting population.
- Review the selected scheme and period, destination and classification evidence, warnings, and excluded rows. Resolve missing evidence before treating a preview as ready.
- Review the prepared figures and any locked export snapshot with the responsible accountant or business user before filing outside VAT Engine.
Preparation supports a review process. It does not register a business, decide its filing obligations, or submit a return to an authority.
Read the compliance workflow and boundaries