B2B and B2C do not change the underlying sale, but they change the identity requested, document expected and customer controls. A business needs a complete invoice identifying it, while an individual buying merchandise may receive a receipt under Article 145-III. Any future electronic-transmission scope must remain tied to the applicable official text.

The essential differences
- B2B: legal name, address, ICE, references and complete invoice.
- B2C merchandise: detailed receipt without a named record on every visit.
- Authority: complete invoice plus purchase or contract references required by its process.
- Paper or PDF does not by itself define a structured electronic invoice.
- Count a sale once even when several documents represent it.
- Publish no B2B/B2C transmission scope or date without a precise official text.
1. The decision table before issue
The best data is requested before the final number. Configure a checkout question, a business-customer record and a late-request rule. The retail receipt and invoice guide shows how to retain one source sale.
| Recipient | Current document | Customer identity | Priority control |
|---|---|---|---|
| Individual, merchandise | Receipt that may stand as invoice | No named record by default | Seller, date, lines, quantities, prices and possible VAT |
| Business | Complete invoice | Legal name, address and ICE | Identity, series, VAT, payment and references |
| Authority | Complete invoice for its file | Entity, ICE and contacts | Order, commitment or requested reference |
| Foreign customer | Invoice suited to transaction | Identity and address | Currency, export and validated tax treatment |
| Intermediary or platform | Depends who legally buys | Contract and debtor identity | Do not invoice the wrong party |
This is an operating table, not an announcement of the DGI portal’s final scope. As at 29 August 2026, cited sources confirm portal development and the system duty for named categories but do not support a universal B2B/B2C timetable here.
2. B2B: identity is accounting data
Ask for legal name, invoicing address and ICE before issue. Do not reconstruct them from a logo, card or trade name said on the phone. An error can prevent purchase reconciliation, delay payment and force correction. Use mandatory invoice fields as the final control.
- Legal name: The buying entity’s legal name, distinct from trade name or establishment.
- Address: The invoice address confirmed in the record.
- ICE: The identifier supplied and verified by the business customer.
- Internal reference: Order, contract, project, cost centre or requester when required.
- Due date: Agreed date and terms, distinct from issue date.
- Recipient: The person receiving the document and the payer can differ.
Set an approval rule for a new record or ICE change and retain the customer’s request. An old invoice keeps the identity with which it was issued; the updated record serves new documents. Do not rewrite history for information received later.
In B2B credit, separate invoice and payment. The invoice creates the amount due; each payment reduces the balance with date and method. A grouped payment can cover several invoices and requires reconciliation, not changed totals.
3. B2C: a useful document without systematic collection
For products or merchandise sold to an individual, the final passage of Article 145-III allows a receipt to stand as invoice subject to its conditions. Do not infer that every service, sector or future transmission follows the same rule. The electronic-invoicing FAQ separates medium, structure and filing.
- Configure seller identification and identifiers once.
- Make labels understandable and quantities and prices recomputable.
- Apply validated rates to products and show VAT where required.
- Assign a controlled receipt number and retain digital history.
- Ask before payment whether an invoice is required in a business name.
- If yes, move to the B2B record and invoice from the same sale.
- If no, do not collect identity, ICE or address without another legitimate need.
An individual may still request a named invoice, for warranty or reimbursement. Your procedure can produce one when data is correct and the sale remains the source. Individual does not force a receipt; it permits a lighter path in the defined case.

Authority does not mean one national rule
A public customer may require an order, commitment number, platform or format in its process. Verify those contractual or operating needs with the customer. Do not present them as the DGI rule for every Moroccan invoice.
4. Design one data model, then two paths
Both paths share seller, date, lines, quantities, prices, VAT, total, payment and source sale. B2B adds legal identity and references. B2C avoids a named record when a receipt suffices. This prevents empty fields and a fake customer called “individual” repeated thousands of times.
- Shared: Seller, date, lines, VAT, total, payment and source.
- B2B only: Legal customer identity, ICE, due date and references.
- Light B2C: Receipt without named record by default.
- Electronic: Structured invoice, queue state, export and possible receipt.
For electronic output, generate structured data from the issued invoice, never by reading a PDF with recognition. PDF and XML must share numbers and totals. If a future official schema differs, clean source data lets the serializer change without rebuilding sales.
Test path changes: B2C becomes B2B before payment; late request after receipt; wrong ICE after invoice; partial return; part payment; invoice grouping deliveries. Decide document, right, correction and accounting impact for each.
5. B2B and B2C in BelloPOS
BelloPOS Lite covers B2C checkout with sale, stock and receipt. Go adds an A4 invoice from a B2B sale and UBL 2.1 preparation with SHA-256, local queue and period export. Pro adds quote, order, delivery, invoice, credit and accounting bridge for longer professional relationships.
| Path | BelloPOS feature | Edition |
|---|---|---|
| B2C merchandise | Receipt from sale and history | Lite |
| B2B at checkout | Customer with ICE and invoice from sale | Go |
| Structured B2B | UBL, sealing and queue | Go |
| Ordered B2B | Quote, order, delivery, invoice and credit | Pro |
| Accountant hand-off | Documents, entries and exports | Pro |
BelloPOS does not submit directly to the DGI. Its queue covers issued invoices and credits; it does not automatically turn every B2C receipt into an electronic invoice. UBL 2.1 is its export format. Compare paths on pricing and have activity-specific tax rules validated.
Mistakes to avoid
- Creating a fake miscellaneous customer with invented ICE.
- Waiting until issue to ask if the customer is a business.
- Rewriting an old invoice after the record changes.
- Creating a second sale for the B2B invoice.
- Collecting every individual’s identity without need.
- Presenting one public customer’s requirement as a universal DGI rule.
Frequently asked questions
What is the B2B versus B2C invoice difference in Morocco?
B2B identifies the customer business and ICE and carries full fields. For certain merchandise sales to individuals, a compliant receipt may stand as invoice.
Is an individual’s ICE required?
Not by default for an ordinary B2C purchase. ICE notably identifies the business customer on its invoice.
Is an authority B2B?
It generally needs a complete invoice and its own references. Verify its process rather than inferring a national rule.
Will B2C be excluded from electronic invoicing?
Claim neither general inclusion nor exclusion without the applicable official text. Operational scope must come from the authority.
Can receipts and invoices share a series?
Separate series are usually easier to control. Whatever validated organisation is used, link the sale and never reuse a number.
Which BelloPOS path matches?
Lite for B2C receipts, Go for invoice-from-sale and preparation, Pro for the full B2B chain and accounting bridge.
What to take away
B2B needs more identity and reconciliation; B2C can stay light in the defined cases. The system should share the economic data without duplicating sales, protect privacy and keep future transmission rules configurable until officially published. Measure late requests and identity errors to see whether the checkout question and customer record need improvement.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- 2026 General Tax Code, articles 145 and 211, read 29 August 2026
- DGI 2025 activity report, electronic-invoicing portal, published 1 July 2026
- Ministry of Economy and Finance, suspension of implementation measures in 2019
- Ministry of Justice, Law 53-05 on the electronic exchange of legal data
- BelloPOS electronic invoicing, DGI connection limits and UBL 2.1 export, read 29 August 2026
- BelloPOS Lite, Go and Pro pricing, read 29 August 2026
- BelloPOS, A4 invoices from a sale, read 29 August 2026
One sales engine, two customer paths
See how BelloPOS handles B2C receipts, B2B invoices from the sale and offline structured export, then choose the edition matching your documents.
Read next
Other practical guides on the same subject: