VAT Return Preparation and Filing Pack

The problem with VAT returns out of SAP Business One

SAP Business One captures the raw material for a VAT return correctly. Tax codes sit on A/R Invoice and A/P Invoice lines, tax groups map to rates, and the tax amounts post to the control accounts. The system will give you a tax report.

What it will not give you is your return. Your return is a jurisdiction-specific set of boxes with a jurisdiction-specific definition of what belongs in each one, assembled from posted documents that include reverse charge purchases needing to appear on both the output and input side, imports valued on a customs figure rather than the supplier invoice, partially exempt input tax needing an apportionment, credit notes needing to land in the right period, and adjustments for bad debt relief or prior-period corrections.

So the return gets built in a spreadsheet. Somebody exports the tax report, pivots it, cross-references a second export for the reverse charge entries, applies the apportionment percentage from a third sheet, keys the totals into the tax authority portal, and files. The working papers live on one person's drive. When the authority asks how box four was derived, or requests a transaction-level audit file, the reconstruction starts from scratch — and if a document was posted with the wrong tax code, nothing in the process catches it before it becomes a filed error.

Many jurisdictions have also moved from portal keying to mandated digital submission and standardised audit files. That turns a manual spreadsheet process from inefficient into non-compliant.

What ECOSIRE builds

ECOSIRE builds a SAP Business One add-on that assembles, validates, files and archives the VAT return for the jurisdictions you operate in.

Return assembly from posted documents

The add-on reads posted A/R Invoices, A/P Invoices, credit memos, Journal Entries and the tax tables directly, and maps every taxable amount to a box on your return through a configurable mapping held in a User-Defined Table. The mapping is by tax code, tax group, document type and, where the return requires it, Business Partner attributes such as country or registration status.

Because the mapping is data rather than compiled logic, a rate change or a new tax code is a configuration change, not a rebuild. Every mapped figure retains a link back to the documents that produced it, so any box on the return drills down to a transaction list and from there into the document itself.

Reverse charge and cross-border treatment

Reverse charge is handled explicitly rather than being left to whoever remembers it. Purchases subject to reverse charge are identified from the tax code and Business Partner registration data, and are placed on both the output and input side of the return as your jurisdiction requires, with the notional output tax and the recoverable input tax shown separately so the net effect is auditable. Import VAT, domestic reverse charge on specified supply categories, and zero-rated or exempt cross-border supplies each get their own mapping treatment.

Partial exemption, adjustments and corrections

Where input tax must be apportioned, the apportionment method and percentage are configured in the add-on and applied to the relevant input tax pools during assembly, with the calculation shown in the working papers rather than hidden. Manual adjustments — bad debt relief, prior-period corrections, annual adjustments — are entered as adjustment records against a specific return period, each requiring a reason and, where you want it, an approval through a SAP Business One approval procedure. Adjustments never overwrite the assembled figures; they sit alongside them so the return shows both the system-derived amount and the adjustment that moved it.

Validation before filing

The return runs through a validation pass before it can be marked ready. Checks include tax control account reconciliation against the assembled return, documents in the period carrying no tax code or an inactive one, tax amounts on documents that do not agree with the rate for their tax code, Business Partners missing a registration number where the return requires one, credit memos falling outside their invoice period, and documents posted into a period already filed. Each failure names the document so it can be corrected at source rather than patched on the return.

Digital submission and audit files

The add-on produces the submission format your jurisdiction mandates — the structured file or API payload defined by your tax authority — generated from the validated return, and the transaction-level audit file where that is required. Formats are built to the specification in force for your jurisdiction, as confirmed during scoping. Where the authority exposes an API, submission can be made from within SAP Business One and the acknowledgement or reference stored against the return period; where it does not, the file is produced for upload.

Archive and working papers

Every filed period is locked and archived with its assembled figures, its supporting transaction detail, its adjustments and reasons, its validation results, the submitted file, and the authority's acknowledgement. That archive is the working paper set. It is stored in your company database and reproducible on demand, which is what an audit request actually needs.

Reports ship as Crystal Reports layouts inside SAP Business One: the return itself in the authority's box layout, the box-to-transaction reconciliation, the control account reconciliation, the validation exception list, and the adjustment register.

Who this is for

Businesses registered for VAT in one or more jurisdictions running SAP Business One as the book of record. Groups filing several returns across several company databases. Businesses facing a newly mandated digital submission or audit file requirement. Any finance team whose VAT working papers are a spreadsheet only one person can explain.

Technical approach

The add-on targets SAP Business One 10.0 on SQL Server and SAP HANA, on-premise or cloud-hosted. Assembly reads posted documents and tax tables through views and queries appropriate to your platform; adjustment records, box mappings, return periods and archives are held in User-Defined Objects, Tables and Fields inside your company database; any posting the return process requires is made through the DI API or Service Layer. Submission calls, where supported by your authority, run over HTTPS from the add-on with credentials held in your environment, never embedded in the build.

How delivery works

1. Scoping call. We identify every jurisdiction you file in, the exact box definitions and submission format in force, your tax code and tax group setup, your reverse charge and import treatments, whether partial exemption applies, and which company databases are in scope. 2. Fixed quote. You receive a written scope naming the jurisdictions, box mappings, validation rules, submission formats and audit files the build will cover, at a fixed price. Additional jurisdictions are quoted separately. 3. Build. ECOSIRE builds to that scope. Typical lead time is two to four weeks from sign-off; multiple jurisdictions or a mandated audit file specification sits at the upper end. 4. Install into your test company. We install into your test or sandbox company database and assemble returns for periods you have already filed, so you can reconcile the add-on's output against your submitted figures box by box. You sign off on that reconciliation before production. 5. Install into production. After sign-off we install into the live company database, configure mappings, adjustments and submission credentials, and run the first live period alongside your team. 6. Support. A support window is included from go-live, covering defect fixes, configuration questions and support through the first live filing.

This is a build-to-order product. Nothing is downloaded and nothing is pre-built. ECOSIRE builds it for your jurisdictions and your tax configuration after the quote is accepted, and the scope states exactly which return formats are covered. It prepares and files the return from what is posted in SAP Business One; it is not a substitute for advice from your tax adviser on how a transaction should be treated.