DataSynth 4.4.3 — SAP and SAF-T Exports Land

Since we adopted DataSynth 4.2.1 last week, three more upstream releases shipped: 4.3.0 (SAP integration pack), 4.3.1 (SAF-T XML exports), and 4.4.0–4.4.3 (SDK regression fixes). Production is now on 4.4.3 and two new output formats are live for Scale and Enterprise customers.

SAP integration pack — why

SAP consulting shops, audit firms, and ERP migration teams have spent years faking BKPF/BSEG/ACDOCA test data by hand or shelling out for obfuscated client extracts. DataSynth 4.3.0 ships a proper model: 8 tables with foreign-key integrity across the P2P cycle, configurable dialect (classic ECC delimiters vs HANA `IMPORT FROM CSV FILE`-ready formatting), master-data split (LFA1 / LFB1 / KNA1 / KNB1 / MARA / MARD / CSKS / CEPC) from transactional (BKPF / BSEG / ACDOCA), and configurable client / ledger / source-system codes.

YAML configuration

output:
  format: sap
  sap:
    dialect: hana          # or classic
    client: "200"
    ledger: "0L"
    source_system: DATASYNTH
    local_currency: EUR
    include_extension_fields: true
    tables: [bkpf, bseg, acdoca, lfa1, kna1, mara, csks, cepc]

HANA dialect uses semicolon delimiters, comma decimals, ISO dates, and UTF-8 BOM — suitable for direct S/4HANA import. Classic dialect (comma delimiters, period decimals, YYYYMMDD dates) matches legacy ECC expectations. Master-data + transactional split lets you validate GL-to-subledger reconciliation logic separately, which is the part of SAP testing that usually breaks.

SAF-T XML — five jurisdictions, one flag

DataSynth 4.3.1 adds SAF-T output for five OECD jurisdictions: Portugal (SAF-T PT 1.04_01), Poland (JPK_KR 1.0), Romania (D406 3.0), Norway (SAF-T Fin 1.10), and Luxembourg (FAIA 2.01). Each emits a single structurally-valid XML file conforming to its jurisdiction's schema, with header metadata (CompanyID, TaxRegistrationNumber, FiscalYear), master files (GL accounts, customers, suppliers, products), and general-ledger entries (journal transactions with debit/credit lines).

output:
  format: saft
  saft:
    jurisdiction: pt        # pt | pl | ro | no | lu
    company_tax_id: PT123456789
    company_name: "Your Company Ltd"

Delivery model

We deliberately chose not to create separate endpoints or zip downloads for these formats. Both use the existing infrastructure:

• SAP files land at `sap_export/{bkpf,bseg,acdoca,lfa1,kna1,mara,csks,cepc}.csv` inside the job's managed blob manifest.
• SAF-T files land at `saft/saft_{jurisdiction}.xml`.
• `GET /v1/jobs/{id}/files` lists them with full metadata (size, MIME, SAS URL).
• `GET /v1/jobs/{id}/download/sap_export/bkpf.csv` streams any single file.
• `GET /v1/jobs/{id}/download` archives the whole job as a single ZIP, SAP/SAF-T included.

Tier gating and pricing

Both exports require the Scale plan ($499/mo) or Enterprise. Below Scale, the Generate wizard surfaces the options but gates them behind an upgrade CTA. A 0.25× credit multiplier applies to jobs using either format — it covers the incremental serializer cost (CSV dialect formatting, SAF-T XML validation, XSD namespace handling) without penalizing customers for choosing enterprise-grade formats.

Both dialects (HANA and classic) and all five SAF-T jurisdictions are available at the same tier — no double gating. If you're paying Scale, you get the full feature.

What's next

DataSynth 4.5 is on the roadmap for sub-ledger balance tracking (to remove the SAF-T zero-balance caveat) and invoice-level SourceDocuments emission (to support VAT-focused SAF-T variants like Hungary and France). We'll also expand the jurisdiction set to PL / HU / DE / FR. SAP will add SAP CO-PA and SAP BW extractor formats for customers running parallel warehouse testing.

See the full feature documentation under docs → integrations → SAP and docs → integrations → SAF-T. Full API reference: /docs/api-reference#export-formats. To enable these on your account, reach out at support@vynfi.com or upgrade to Scale from the pricing page.