Guides & comparisons Invoicing Retail in Morocco

Electronic invoicing for Moroccan SMEs: the operational roadmap

Governance, master data, testing, responsibilities, mixed activities, accountant hand-off and cutover without a false timetable.

By BelloCommerce

·

August 29, 2026

An SME should treat electronic invoicing as a process change, not a button installation. Success is an invoice passing through sale, approval, correction, payment, accounting, export and archive with the same data. This roadmap moves forward without assuming a date or schema the authority has not published for your sector.

Electronic invoicing roadmap for a Moroccan SME.

Six workstreams

Name a sponsor, process owner and tax approver.
Map B2B, B2C, activities, entities, series and exceptions.
Clean sellers, customers, products, taxes, payments and accounts.
Test errors, credits, outages and recovery.
Pilot a controlled scope before general cutover.
Reconcile every period and retain files, logs, backups and evidence.

1. Governance: one decision, four owners

Projects fail when everyone thinks the accountant or IT owns them. Name one person per decision, even if one person holds several roles. Management accepts risk and budget; sales describes reality; finance validates tax and reconciliation; IT protects availability and data. Start from the obligation analysis, then confirm your own case.

Role	Decision	Deliverable
Sponsor	Scope, budget and internal date	Mandate and arbitration
Invoicing owner	Flow, numbers, exceptions and rights	Operating procedure
Tax owner	Identity, VAT, documents and text	Validated rules
Technical owner	Availability, export, backup and recovery	Tests and continuity plan
Accountant	Accounts, period, format and checks	Agreement on hand-off pack

Add a decision register: question, options, source, owner, decision, date and review condition. Link every decision to the affected process, screen, template and training. A new rule is operational only once those four items are updated and a case passes. Retain the previous version and withdrawal date so two periods with different settings can be explained. When the DGI publishes an applicable specification or timetable, you will know which decisions to reopen instead of rebuilding from memory.

2. Map flows that do not follow the ideal path

The main flow is easy. Exceptions reveal maturity: a B2C sale followed by a B2B invoice request, partial delivery, a customer with establishments, a credit against a closed period, grouped payment, outage or activity with another series. Use the B2B and B2C guide to separate customer data.

Channels: Checkout, sales, received order, delivery, import and possible recurring invoice.
Entities: Companies, establishments, trade names, warehouses and tills.
Documents: Receipt, quote, order, delivery, invoice, credit and payment with lineage.
Series: Numbering authority, prefixes, issue date and recovery rule.
Exceptions: Return, cancellation, identity error, disputed quantity, partial payment and debt.
Outputs: Customer PDF, structured file, journal, accounting pack, archive and possible receipt.

For every flow draw trigger, input, control, issued document and destination. Circle re-entry, a priority error source. Integration that copies bad data faster is not progress.

3. Build master data and the test matrix

Freeze a baseline copy, measure duplicates and blanks, then assign every field to an owner. Separate legal customer name, trade name, invoice address, ICE and establishments. Products need labels, units, prices and VAT rules. Payment methods feed controls without changing the invoice.

Sample twenty customers per channel and correct identity, ICE and addresses.
List products by rate and have finance validate exceptions.
Define series, issue rights and incident recovery.
Create B2B, B2C, cash, credit, discount, multiple-rate and validated-exemption cases.
Add wrong customer, partial return, full credit, part payment and attempted duplicate.
Test offline work, backup, restore, period export and accounting import.
Obtain business, tax, technical and accountant sign-off on resolved gaps.

The fifty-question FAQ supplies more cases. Do not validate that a screen opens. Reconcile bases, VAT, total, numbers, hashes and manifest file counts.

Operational invoicing roadmap.

Do not block the project on false precision

You can clean data, secure numbers, test credits and prepare exports before knowing the final schema or sector date. Isolate parameters that may change. Do not encode an unpublished claim about UBL, clearance, real time or sanctions in twenty procedures.

4. Pilot, cutover and thirty days of control

Choose a representative but reversible pilot: one establishment, series or team with enough B2B and exceptions. Set entry and exit criteria, support, rollback and contacts. A week without a visible error is not enough; reconcile data behind screens.

Pilot entry: Clean data, passed tests, backup and available owners.
Pilot exit: Critical gaps resolved and reconciliation accepted.
Cutover: Old series frozen, date communicated and rights checked.
Stabilisation: Daily board, weekly review and updated procedure.

At cutover, freeze old series, back up, export balances and open documents, communicate the starting point and prevent double issue. Parallel control means comparing results, not producing two legal invoices for one transaction.

For thirty days track internal rejects, missing numbers, duplicates, issue time, queued documents and user requests daily. Weekly, reconcile sales, invoices, credits, payments and exports. Also compare incomplete records, customer changes after issue and corrections made outside procedure. Classify gaps as tax, financial, customer or continuity risk, then treat causes rather than symptoms. Finally perform a restore, replay an export and hand a complete pack to the accountant.

5. Where BelloPOS fits an SME roadmap

BelloPOS Go prepares sales invoices: A4 PDF, UBL 2.1, SHA-256 seal, local queue and period exports. Pro adds quotes, purchase orders, delivery notes, invoices and credits, then an accounting bridge with editable CGNC chart, balanced entries, journals, ledger and Sage, XLSX, CSV, PDF and audit exports.

Workstream	Feature	Limit or decision
Continuity	Local offline database and queue	Organise backup and recovery
Documents	Full hub in Pro	Define rights, states and series
Electronic	UBL, SHA and period pack from Go	No direct DGI transmission
Accounting	Entries and exports in Pro	Accountant validates mapping
Purchasing	Order, receipt, landed costs and journal	Since 3.0 each purchase line carries its own rate and deductible VAT is posted; the accountant still validates the qualification

The bridge does not replace an accountant. UBL is BelloPOS’s export choice, not a national requirement we claim. Use pricing to decide whether Go covers sales or Pro is justified by documents and accounting, then validate a real pack.

BelloPOS

All the features

Mistakes to avoid

Leaving the project to IT without a business owner.
Testing only the perfect path.
Importing master data without measuring quality.
Issuing two invoices during supposed parallel running.
Encoding an unpublished date or schema.
Calling cutover complete before reconciliation and restore.

Frequently asked questions

How long does SME preparation take?

It depends on entities, flows and data. Measure duplicates, series, exceptions and integrations, then plan cleaning, test, pilot and stabilisation with exit criteria.

Must we wait for the final text?

Not for durable work: identities, customers, products, numbers, rights, credits, exports and backup. Keep unpublished regulatory elements configurable.

Who should lead?

A business process owner backed by management, finance, technical staff and accountant.

How do we manage mixed activities?

Map identity, VAT, series, documents and owner per activity. Separate or combine only after fiscal and operational validation.

Does BelloPOS support several terminals?

Pro includes multi-terminal operation. Test architecture, rights, continuity and backup for your sites.

Does BelloPOS submit and account for everything?

It does not submit directly to the DGI. Pro generates an accounting bridge for accountant validation and, since version 3.0, posts deductible purchase VAT from the rate carried by each purchase line; the tax qualification still belongs to the accountant.

What to take away

An SME is ready when a process owner governs, data is measured, exceptions pass tests, a pilot reconciles and a restore proves continuity. Software executes that model; it does not replace tax decisions or governance.