The Burundi Compliance app seamlessly integrates EBMS(Système de facturation électronique) tax functionalities into ERPNext, empowering users to efficiently manage tax compliance tasks.
Developed on the robust Frappe Framework and ERPNext platform, it streamlines repetitive tasks and simplifies the tax compliance process for businesses.
-
Sales Invoice Tax Tracking:
- Seamlessly send sales invoices to OBR(Office Burundais des Recettes) for meticulous tax tracking, ensuring adherence to regulatory standards and facilitating transparent financial reporting.
-
Stock Movement Monitoring:
- Track stock movements for inventory and sales transactions within ERPNext, enabling comprehensive oversight and compliance with tax regulations governing inventory management.
-
Supplier Registration Verification:
- Automatically verify supplier registration status, ensuring that only registered members are engaged in business transactions, thereby mitigating risks associated with non-compliant suppliers.
-
Real-Time Customer TIN Verification:
- Verify Tax Identification Numbers (TINs) of registered customers in real-time, validating their authenticity and promoting compliance with tax regulations.
-
Automated Compliance Checks:
- Implement automated compliance checks to enforce adherence to tax regulations at every stage of business operations, reducing the risk of non-compliance and associated penalties.
Streamlined Integration: ERPNext Communicating with OBR Server and Database
- English Version: SPECIFICATIONS D'INTERFACAGE EBMS - Eng.docx
- French Version: SPECIFICATIONS D'INTERFACAGE EBMS - ACCUSE RECEPTION.docx
1.Setup
3.Selling
Once the user logs into the system, among the modules, there is Burundi Compliance.
It has a workspace with three shortcuts to various custom doctypes.
The first interface has fields for username, password, and company.
-
Fill in the username and password provided by OBR upon application.
-
The company field will be automatically filled if you have a single company. Otherwise, select the corresponding company.
-
By default, the details are for production. For testing, tick the sandbox checkbox.
This tab contains details related to your organization's taxes. These details are mandatory when sending Invoices.
-Taxpayer's Sector of Activity - This is the company domain
-Taxpayer's Legal Form -
-The taxpayer's commercial register number-This is the company's trade number
-Subject to VAT -
-System Identification- taxpayer system number(computer serial no.)
-Type of Taxpayer -
-Subject to Consumption Tax
-Subject to FlatRate Withholding Tax -
This tab has frequency schedular fields:
-
Maximum Attempts: Enter the number of retries you want the system to attempt when the OBR server is down.
-
Retry Delay: This is the interval between retries. Enter the duration in seconds.
-
Invoice Event Frequency: This option controls how often the system automatically sends invoices to OBR(Office Burundais des Recettes). Choose the frequency that best matches how often you want your invoices to be sent. Consider factors like your sales volume and when you prefer to submit invoices to OBR.
-
Stock Movement Event Frequency: This option sets how often the system sends stock movement data to OBR(Office Burundais des Recettes). Choose a frequency that aligns with your needs for updating OBR on stock changes.
-
Setting a Specific Time for Invoice Sending: If you want to send invoices at a specific time each day, you can use a feature called Cron. When you select this option, another field will appear where you can enter a special format called Cron. You can use a website like Crontab Guru to help you get the timing right. For example, if you want to send invoices every day at 12:00 pm, you would enter "0 12 * * *" in the Cron format field.
-
Allow OBR(Office Burundais des Recettes) to track sales: This setting controls whether the system will send invoices to OBR for tracking purposes. When enabled, invoices will be automatically sent to OBR. When disabled, invoices will not be sent to OBR.
-
Allow OBR(Office Burundais des Recettes) to track stock movement: This setting controls whether the system will track stock movement data and send it to OBR. When enabled, stock movement information will be automatically sent to OBR. When disabled, stock movement will not be tracked or sent to OBR.
If multi-companies are within one site, make settings for each company, since username and password will be different. But only one company per doctype.
This comes with predefined 6 api methods, Incase of new method you can add it as new ebms api method.
This helps in our next doctype
- Create Sandbox and related Endpoint URL:
-
Choose the environment as sandbox.
-
Enter the correct server URL provided by OBR.
-
In the APIs child table, select methods and enter the corresponding endpoint URL ending with a slash (/). Save.
- Create Production with related Endpoint URL:
- Once you have the production endpoints and server URL, create the production environment with corresponding URLs.
This doctype will only have two transactions: sandbox and production.
To ensure accurate tracking by OBR, it's essential to set up the system properly. If an item falls under the classification of goods that OBR monitors, it's important to enable this feature upon creation.
This configuration involves ticking the Allow OBR to track... checkbox, which can be found in two tabs:
-
Inventory: This option enables OBR to track stock movements for items, recording any incoming or outgoing movements.
-
Sales: By default, this option is already ticked. It permits OBR to monitor any sales involving the item.
By activating these checkboxes, you ensure comprehensive tracking of relevant activities by OBR, enhancing overall monitoring and compliance.
-
E-Tracker Checkbox and Re-Submit Button:
-
After saving a document involving stock movements, an E-Tracker checkbox and a Re-Submit button appear.
-
Upon submission, a confirmation pop-up will appear:
"Stock movement sent to OBR"
-
On reload, the E-Tracker checkbox is automatically ticked.
-
Stock Ledger Entry:
-
Similarly, related Stock Ledger Entries have an E-Tracker checkbox.
-
While the request is pending, the E-Tracker checkbox is unticked, and the Re-submit button appears.
-
If the maximum attempts are exhausted, an email notifies(doc owner) about the unsuccessful request. Resend by clicking the Re-submit button.
Purchase Receipt/Purchase Invoice
When purchasing an item that needs to be tracked, the purchase receipt will automatically send data to OBR upon submission.
In cases where a user creates a purchase invoice directly without a purchase receipt, they should tick the Update Stock checkbox to enable tracking for the item.
-
Handling Many Unsent Transactions:
-
If the OBR server is down, two options are available:
-
A scheduler runs every X hours(as set in the stock movement Event Frequency, ebms setting doctype) to send pending stock ledger entries automatically.
-
For transactions like Stock Entry or Stock Reconciliation:
-
Filter transactions with E-Tracker equals "No".
-
Select pending entries, click the Action group button, and choose eBIMS Tracker to send to OBR.
-
It's recommended to rely on the scheduler for handling unsent transactions.
This is where OBR want to track all the company revenues.
On the Tax Tab:
-
Select the appropriate GST Category (e.g., select "Registered" if the customer is registered).
-
Enter the Tax ID/TIN.
-
Upon saving, the Tax ID is sent to OBR for registration confirmation.
-
Confirmation message received:
"NIF du contribuable connu."
-
The "TIN Verified" checkbox is ticked upon successful verification.
-
If the customer is unregistered (selected Unregistered from GST category), simply save without confirmation.
Upon creation of a delivery note, upon submission, it updates the stock and sends a similar payload to OBR.
The document includes an E-Tracker checkbox, which is ticked upon receiving a response.
Updating Stock with Sales Invoice
If a company decides to bypass the delivery note, they can update stock directly in the sales invoice by ticking the Update Stock checkbox. Upon clicking submit, two requests will be sent to OBR: one to add stock movement and the other to add the invoice.
To send your invoice to OBR, follow these steps:
-
Select Customer
-
Add the Items to be sold.
-
Choose the Payment Type from additional normal fields.
-
If the customer is exempted from tax, ensure to tick the corresponding checkbox.
-
Select the tax template Sales Taxes and Charges Template if tax is involved.
-
Save and submit your document.
Upon submission, a pop-up message will appear:
"Invoice sent to OBR"
Check the eBMS Tab:
-
The Read Only tab will display the response from OBR, including:
-
Invoice Registered No.
-
Invoice Registered Date
-
Invoice Identifier
-
eBMS Signature
-
The checkbox eBMS Submission will be ticked.
Print the sales invoice; it will contain the Invoice Identifier (created even when the invoice is yet to reach the OBR).
(Sales Invoice print image)
Credit Note:
- To send a credit note:
-
Click on Create at the top of the respective sales invoice.
-
Choose Return/Credit Note.
-
Enter the reason for creating the credit note (on the eBMS tab).
-
Save and Submit.
Reimbursement Deposit (RC):
- To create a reimbursement deposit (RC):
-
Create a credit note.
-
Enter the reason.
-
Tick the Creating Payment Entry.
-
Save and Submit.
Cancel Sales Invoice:
- To cancel a sales invoice:
-
Enter the reason for cancellation (found in the eBMS Tab).
-
Save and Cancel.
- Response received:
"Invoice cancelled successfully! La facture avec la signature (invoice identifier) a été annulée avec succès!"
Differ Submission to OBR
In case the user doesn't want to send the sales invoice to OBR at the time of submission, simply tick the Differ Submission to OBR checkbox (circled in the sales invoice image - Not allowed by OBR).
Later, one can untick the checkbox and use the Re-submit button to send the invoice to OBR.
When the OBR server is down, the system retries sending requests through a background job while users continue with normal processes.
If the maximum retry attempts are reached, the sales invoice initiator receives an email notification of failure (indicating failure to reach the server). In such cases, contacting OBR for feedback is recommended.
Once the issue is resolved, there are two approaches to send batches:
-
A scheduler runs every as set in the Invoice Event Frequency, ebms setting doctype, automatically sending the requests.
-
Manually, by navigating to the sales invoice list, filtering for eBMS Submission equals "No", selecting the relevant entries, and clicking "Submit to EBMS" from the Action menu.
(Add image of pending batch)
Similar to sales invoice, sends the data to OBR on submit.
The doctype has a section(eBMS) which stores response from the OBR.
It has similar fields like Differ submission, payment type etc.
- Company
-
Check if your company is registered:
-
Save your details in the Company doctype, including Tax ID.
-
Click the Confirm TIN button.
-
If your TIN is valid, it will display the company name.
- Supplier
-
Upon saving a supplier:
-
The system checks if the supplier is registered.
-
If registered, the TIN Verified checkbox is automatically ticked.
- Address
This contains the location information required when sending invoices. Remember to fill all fields with *.
- Rue
- Avenue
- Numero
- Commune
- Quartier
- Town
- Province
-
Integration Request When there's a need to check the status or details of an action like sending an invoice or recording stock movement, all the relevant information is available in this document type. If an invoice or stock movement fails to go through, the status will be marked as "Failed". If the action is successful, the status will be marked as "Completed". Additionally, this document records details about the payload, output and any errors encountered during the process.
-
Error Log: In the event of an action failing and needing more detailed information than what's provided in the Integration Request, the Error Log document comes into play. It contains comprehensive error logs with additional details, assisting in pinpointing exactly where the error occurred and providing more clarity on what went wrong.
| ERPNext | OBR Server | |
|---|---|---|
| Authenticate User | Send user credentials | Receive request for authentication, verify credentials, issue access token |
Endpoint: (/login) |
||
| Add Sales Invoice / POS Invoice | Send invoice details | Receive request to add invoice, process the request, send confirmation |
Endpoint: (/addInvoice_confirm/) |
||
| Add Stock Movements | Send stock movement details | Receive request to add stock movements, process the request, send confirmation |
Endpoint: (/AddStockMovement/) |
||
| Check TIN (Customer, Supplier) | Send TIN for verification | Receive request to verify TIN, check TIN validity, return owner's name |
Endpoint: (/checkTIN/) |
||
| Cancel Sales Invoice | Send invoice ID for cancellation | Receive request to cancel invoice, process the request, send confirmation |
Endpoint: (/cancelInvoice/) |
-
Once bench and ERPNext are installed, add burundi-compliance to your bench by running:
$ bench get-app --branch {branch-name} https://github.com/navariltd/burundi-compliance.git
Replace {branch-name} with the desired branch name from the repository. Ensure compatibility with your installed versions of Frappe and ERPNext.
- Install the burundi-compliance app on your site by running:
$ bench --site {sitename} install-app burundi-compliance
Replace {sitename} with the name of your site.
-
Sign up with Frappe Cloud.
-
Setup a bench.
-
Create a new site.
-
Choose Frappe Version-14/Version-15 or above, and select ERPNext, and Burundi Compliance from the available Apps to Install.
-
Within minutes, the site will be up and running with a fresh install, ready to explore the app's simple and impressive features.
If assistance is needed to get started, reach out for consultation and support from: Navari.
-
If you encounter any errors during installation, refer to the error messages for guidance.
-
Ensure all dependencies are correctly installed and compatible with the versions specified.
- What happens when you tick update stock on POS Invoice, does it send two request to OBR(Office Burundais des Recettes?
GNU General Public License (v3). See [license.txt](https://github.com/navariltd/burundi-compliance/blob/master/license.txt) for more information.Yes, but they dont happen at the same time. First, the invoice will be sent to OBR. Then later when we close the entry for POS, it will create stock ledger entry for items sold, at this point, the schedular will send the stock details to OBR.