Enterprise · ComplianceNeural Software Solutions, SRL

DGII e-CF Electronic Invoicing System

An end-to-end compliance pipeline connecting ERPNext to the Dominican Republic's DGII tax authority. From a single user action to a signed, submitted, and tracked electronic invoice — across Azure Functions, Logic Apps, and the DGII's own endpoints. Covers all 10 mandated e-CF invoice types with a pre-validation layer that catches format errors before they reach DGII, protecting scarce government-issued NCF sequences.

Architecture

System flow

ERPNEXTAZUREDGIIERPNEXTERPNext — sales invoiceUser triggers submission · pre-validation runsPre-validation layerTax indicators · payment mode · invoice referencesAzure Functions — orchestrationNCF assignment · environment detection · instance routingAzure Logic App — processing hubPayload transform · token management · response parsingINVOICE TYPE ROUTINGE-31E-32E-33E-34E-41E-43E-44E-45E-46E-47XML generation + digital signingType-specific structure · cryptographic signatureStandard e-CF9 of 10 invoice typesSummary flowE-32 below thresholdDGII response → ERPNextStatus · security code · real-time user notificationHourly scheduler monitors pending invoices and flags unresolved submissions for operator follow-up
My role

Full design and implementation, end to end — from the ERPNext server scripts and client-side validation, through the Azure Function orchestration layer, to the Logic App workflows and final DGII submission.

What it solves

Dominican law requires every taxable transaction to be submitted to the DGII as an e-CF. Failed submissions consume government-issued NCF numbers that can't be recovered — so pre-validation and reliable delivery matter significantly. Most invoices clear DGII in under 5 seconds.

Stack
C# / Azure FunctionsAzure Logic AppsERPNextPythonXSLT / XML