Fiscal security elements
Receive the DEF/DGI code, fiscal signature, and QR code returned through the selected integration mode, and record them in ERPNext without alteration.
DRC / e-Def Module for ERPNextYour invoicing.
Your invoicing.
Connected to ERPNext.
Paavan Infotech’s DGI-approved e-Def Module for ERPNext supports Facture Normalisée in the DRC, with direct e-DEF integration or a physical MCF via MCF Device Control.
For businesses in the DRC implementing ERPNext or extending an existing installation.
Discuss Facture NormaliséeTell us about your ERPNext installation and invoicing needs. We will review the scope with you.
Certified Frappe Partner · Democratic Republic of the Congo
YOUR WORKFLOWS. OUR STARTING POINT.Africa-focused delivery. Conversations in English and French.
Certification built into your invoicing.
Certified records, preserved
ERPNext records, freezes, and archives certified invoice data. Fiscal validation follows receipt of the certified elements from the DGI.
Traceable operations
Keep fiscal processing in ERPNext and hardware communication in MCF Device Control when a physical MCF is used, with traceability across the workflow.
Two integration modes. One ERPNext workspace.
The integration mode is selected for your operating environment and applicable requirements.
Direct e-DEF
- ERPNext
- DGI / e-DEF
ERPNext communicates directly with the DGI e-DEF service. No physical MCF or intermediary application is needed in this mode.
Physical MCF
- ERPNext
- MCF Device Control
- MCF
- DGI
ERPNext exchanges data through MCF Device Control, which handles USB, COM, or network communication with the physical MCF. ERPNext never accesses the device directly.
MCF Device Control is used only in physical MCF mode. It handles device commands, synchronization, device status, and faithful relay of responses; business and fiscal decisions remain in ERPNext.
WHAT TO EXPECT
From discovery to validation.
- Step 1
Share your current setup
Tell us whether you already use ERPNext and how your team handles invoicing today.
- Step 2
Agree the implementation scope
Review requirements, dependencies, and responsibilities before planning the rollout.
- Step 3
Configure for your installation
Plan configuration and integration around the agreed scope and your ERPNext environment.
- Step 4
Validate with your team
Review representative invoicing scenarios and agree the next steps before rollout.
BEFORE WE TALK
A few useful answers.
Is MCF Device Control always required?
No. Direct e-DEF mode connects ERPNext to the DGI without this application. MCF Device Control is used only when the physical MCF integration mode is required.
When is an invoice fiscally validated?
In both modes, fiscal validation takes place only after the certified security elements have been received from the DGI. The returned elements are recorded without modification.
How are hardware and fiscal responsibilities separated?
ERPNext handles business and fiscal processing. MCF Device Control handles only technical communication with the physical device and relays its responses to ERPNext.
Is your Facture Normalisée solution approved by the DGI?
Yes. Paavan Infotech offers a DGI-approved Facture Normalisée solution with ERPNext for the DRC. This approval refers to our solution, rather than to every ERPNext installation.
Can you review our existing ERPNext installation?
Yes. Share your current setup and requirements. We will review the integration scope and dependencies before proposing an implementation.
Can we discuss the project in French?
Yes. Choose French or English when sending your inquiry. Our team will contact you to discuss your project.
YOUR NEXT STEP
Discuss Facture NormaliséeBring Facture Normalisée into your ERPNext project.
Start with your invoicing needs and current setup. We will help you define the next step.