Electronic-invoicing readiness does not start with buying a connector. It starts by making every invoice identifiable, calculable, correctable, exportable and retrievable. This checklist can be printed and dated. It announces neither a mandatory timetable nor a future DGI specification. It prepares useful data and ownership today, while leaving a separate line for the official channel, national format and acknowledgement whenever authoritative documentation applies.
Eight workstreams
- Legal identity and merchant details validated.
- Business customers cleaned with ICE and address.
- Numbering, dates, currency, VAT and rounding tested.
- Credit notes and corrections linked to the original.
- PDF and structured data consistent.
- Archive, backup and restore proven.
- Issue, submission, monitoring and incident owners named.
- End-to-end test completed with file, fingerprint, export and a real acknowledgement from the available channel.
1. Identity, customers and settings
Tick only after checking a source controlled by the business, not because an old invoice already displays the value.
| Box | Verify | Evidence |
|---|---|---|
| ☐ Entity | Exact legal name and form | Legal or tax record |
| ☐ Address | Issue address and contacts | Reviewed setting |
| ☐ ICE | Complete untruncated value | Test invoice |
| ☐ B2B customers | Name, address, ICE and contact | Ten-record sample |
| ☐ Products | Label, unit, price and rate | Exported catalogue |
| ☐ Bank/payment | RIB and methods when shown | Test PDF |
| ☐ Languages | Useful French/Arabic labels | Print test |
Review mandatory invoice fields against current CGI and your accountant. Present does not mean correct, and absent does not mean required in every case.
2. Document, number and calculation
Test a simple invoice, discount, two rates if used, company buyer, deferred payment and credit note. Use a validated real case rather than choosing a rate to pass.
- Define invoice, credit note and non-fiscal documents used.
- Write the numbering rule and validation rights.
- Test issue date, due date and MAD currency.
- Calculate quantity, price, discount and net by line.
- Group taxable base and VAT by rate.
- Check rounding, gross and amount payable.
- Compare PDF with structured data.
- Link credit note to corrected invoice.
- Prevent silent change or deletion after issue.
- Have the cases approved by the accountant.
| Scenario | Expected | Failure to address |
|---|---|---|
| B2B invoice | Correct customer, ICE and final number | Incomplete record |
| Two rates | Reconciliation and correct total | Different global rounding |
| Partial credit | Reference and bounded quantities | Credit exceeds original |
| Offline | Local issue and visible state | Confused with transmission |
| Re-export | Same XML and same hash | Changed bytes |
| Restore | Documents and states recovered | Unusable backup |
Read PDF versus structured invoice, then open a UBL 2.1 example. UBL is BelloPOS’s export choice here, not a declared mandatory national profile.
3. Export, submission and monitoring
An invoice is not finished because a file exists. Know who exports, where it is submitted, how acknowledgement returns and what happens when it does not.
| Box | Operational question | Owner |
|---|---|---|
| ☐ Export | Do one XML and a period pack open? | Invoicing |
| ☐ Integrity | Can SHA-256 be reproduced? | IT/vendor |
| ☐ Submission | Which official channel is actually available? | Tax |
| ☐ Acknowledgement | Where are code, time and reference? | Accounting |
| ☐ Rejection | Who diagnoses without changing original? | Invoicing + accountant |
| ☐ Escalation | When and to whom? | Named lead |
| ☐ Continuity | What does the counter do without internet? | Operations |
The XML/ZIP export guide explains manifest control. The rejected-invoice checklist avoids inventing a message’s meaning.
Leave unknowns visible
If the national format, timetable, portal or a code is not officially published for your case, write to be confirmed with an owner and review date. A rumour ticked as complete is more dangerous than an explicit unknown.
4. Archive, backup and retrieval
CGI 2026 Article 211 provides ten-year retention for the documents it covers. Define the retained original; where PDF, XML, manifests, acknowledgements and corrections live; who can access them; and how a request is returned.
Use 3-2-1 as a practical discipline for multiple copies, different media and a remote or disconnected copy according to risk. It is not a legal formula; restore is the decisive test. Follow the Moroccan archive guide.
Tick: ☐ dated backup; ☐ copy away from POS PC; ☐ encryption or access control; ☐ periodic restore; ☐ search by number; ☐ loss procedure; ☐ exit route if software changes.
5. How BelloPOS covers the checklist
BelloPOS Go issues invoices, creates UBL 2.1, calculates SHA-256, retains a local outbox and exports XML or ZIP with manifest. Checkout works offline. Direct DGI transmission is not enabled, so submission and acknowledgement remain with the business or accountant through the available official channel.
| Need | BelloPOS | Limit |
|---|---|---|
| Identity/customer | Settings and ICE records | Input still needs validation |
| Issue | Number, PDF and UBL from Go | No automatic fiscal approval |
| Integrity | Local SHA-256 | Neither signature nor DGI acceptance |
| Period | ZIP and CSV manifest | Submission not connected |
| Correction | Credits and full lineage in Pro | Tax decision needs review |
| Archive | Local data and backups | Owner organizes external copies |
Test Go before cutover; choose Pro when quote, order, delivery and linked credits are needed. Licences are one-time purchases. Compare plans and write the limit into your checklist.
Mistakes to avoid
- Buying before cleaning data.
- Ticking an unsourced mandatory date.
- Confusing BelloPOS UBL with an official DGI format.
- Testing only one invoice without credit or rejection.
- Forgetting who submits and monitors.
- Calling SHA-256 a signature.
- Backing up without restoring.
- Leaving the only export on the till PC.
Frequently asked questions
Is electronic invoicing already mandatory for everyone?
Do not generalize without an official text applying to the case. This checklist prepares data without announcing an unconfirmed date or scope.
Does this guarantee DGI compliance?
No. It organizes data, controls and evidence. An official specification and channel must be applied when available for the case.
Is UBL 2.1 mandatory?
We do not present UBL as a required national format. It is the structured format BelloPOS exports.
Who signs the checklist?
At least invoicing, operations and accounting owners, with vendor or IT for export and backup.
How often should it be reviewed?
After legal, software or organizational change and before each new deployment phase.
Does BelloPOS send invoices to DGI?
No. It prepares and exports; direct submission is not connected today.
What to take away
A ready business knows its data, calculations, corrections, export, submission, acknowledgement and restore. Print the list, leave unknowns open, assign every box and test the whole path.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- Moroccan General Tax Code 2026, DGI, read 29 August 2026
- Official Universal Business Language 2.1 specification, OASIS
- BelloPOS electronic invoicing and UBL export, read 29 August 2026
- BelloPOS Lite, Go and Pro pricing, read 29 August 2026
Run an end-to-end test
Issue a simple case and a credit, compare PDF and UBL, verify the hash, export a period and restore the backup before signing off.
Read next
Other practical guides on the same subject: