Prodigy Software + SAF-T D406: how to reconcile dimensions with tax authority analytics SAF-T D406 requires precise mapping between Prodigy dimensions (store, season, category) and the analytics required by ANAF (the Romanian tax authority). Technical guide + Smart Layer reconciler. Ionut Mihaescu — Full Stack Developer Azuvio · 2026-06-28 · 9 min · ERP & Integrations The Challenge Prodigy operates on native dimensions (store, season, brand, category). SAF-T D406 requires specific analytical structures for the tax authority (account × sub-account × analytic × sub-analytic). Manual mapping equals 18-32h/month of effort + risk of inconsistencies. The Solution: Smart Layer Reconciler Smart Layer SAF-T Reconciler = a configurable mapping engine that: Reads Prodigy dimensions (SQL extract or API) Applies versioned mapping rules per fiscal period Generates SAF-T D406 according to the OECD + ANAF (tax authority) schema Automated reconciliation with the monthly trial balance (drift < 0.05%) 7-year audit trail for tax audits Typical Result Manual effort: 28h/month → 3h/month Reconciliation errors: -94% Audit ready: full trail for the tax authority See «Prodigy + Smart Layer».