Yes, a business can prepare an electronic invoice without internet when software retains the data, numbering, structured file and trail on the workstation. Remote-channel transmission can wait for connectivity; recording the sale should not. Technical capability and administrative permission remain separate: if a future scheme requires real-time authorization, its exact official text determines allowed behavior.
What works and what waits
- Sale, customer identity, number and PDF can be produced locally.
- UBL 2.1 and SHA-256 can be created without a network.
- A local outbox keeps the document and its state.
- Individual and period export need no connection in BelloPOS.
- Remote filing, authentication and receipt need the available channel.
- Offline does not mean without backup, access controls or recovery procedure.
1. Break electronic invoicing into stages
The phrase covers several operations and an outage affects each differently. This table supplements the guide to choosing electronic-invoicing software.
| Stage | Possible locally? | Expected evidence |
|---|---|---|
| Record sale | Yes | Saved transaction |
| Assign number | Yes with local engine | Duplicate-free series |
| Create PDF | Yes | Readable copy |
| Create UBL XML | Yes | Structured file |
| Calculate SHA-256 | Yes | Retained fingerprint |
| Place in outbox | Yes | Visible local state |
| Transmit to portal | No without link | Remote receipt |
| Receive validation | No without link | Official state |
An outbox must not hide behind a badge. It should show waiting count, numbers, dates, types and errors. An honest locally sealed list is more useful than an unexplained green status.
2. An invoice’s path during an outage
Prepare for outage deliberately in a test database.
- Identify the customer and check fields without a remote directory.
- Record sale and payment locally.
- Issue once and note its number.
- Generate PDF and UBL XML from the same data.
- Calculate fingerprint and place it in the local outbox.
- Print or give the readable view to customer.
- Export XML if the process uses controlled media.
- When connectivity returns, perform the remote action and attach its receipt.
A reprint must not consume another number or create a second outbox invoice. Do not repair tax or customer errors by editing XML. Correct the document according to status and create the proper credit or trace.
3. Risks specific to local work
Cloud independence keeps checkout running, but puts responsibility on shop hardware.
| Risk | Measure | Test |
|---|---|---|
| PC failure | Backups on separate media | Quarterly restore |
| Two PCs issue same number | One controlled numbering source | Simultaneous outage |
| User deletes outbox | Permissions and log | Restricted cashier account |
| Wrong clock | Date and time control | Startup alert |
| Forgotten export | Named owner and frequency | Closing checklist |
| Lost USB | Encryption and hand-off register | Copy inventory |
Name the person responsible for deferred filing, deadline, channel, retry and escalation. Until official rejection codes apply to your case, use neutral states: prepared, sealed, exported, delivered, then the exact response returned by the channel.
Never show DGI validated without a DGI response
A locally created and hashed file is locally sealed. Software cannot infer receipt, validation or an administrative reference from no connection. Those states require an authentic response from the relevant service.
4. Continuity and compliance are not opposites
Continuity protects the sale and series during outage. Compliance protects identity, calculations, corrections, retention and restitution. A good system does both: it does not block the customer and does not hide unfinished work.
Define an operational limit when delay grows: who decides to continue, how the accountant is informed, which controlled medium is used and when a dependent function stops. Any applicable official sector rule also governs that choice.
Keep the issued document and later receipt under one reference. CGI 2026 requires covered taxpayers to retain invoice or receipt duplicates and accounting records for ten years. The invoice retention guide turns that duration into procedure.
5. What BelloPOS does offline
BelloPOS stores sales, customers, products and invoices on the Windows PC. Go and Pro locally create UBL 2.1, calculate SHA-256 and place invoices in an outbox. Users export one XML or ZIP with manifest without connectivity, so checkout continues.
| Feature | Offline availability | Limit |
|---|---|---|
| Sale and receipt | Lite, Go, Pro | PC must work |
| Invoice from sale | Go, Pro | Customer identity needs review |
| UBL and hash | Go, Pro | BelloPOS choice, not proof of mandated DGI schema |
| Commercial documents | Pro | Wider workflow |
| DGI transmission | Not connected | External filing through available channel |
BelloCommerce does not receive the local database and cannot restore it for you. Schedule backups, protect media and test restores. A lifetime license and no subscription do not remove that security work.
Mistakes to avoid
- Confusing local issue with successful transmission.
- Hiding the outbox from responsible users.
- Assigning a new number on reprint.
- Editing XML after seal.
- Running two independent number sources without a rule.
- Waiting for failure before testing restore.
- Copying customer data to unprotected USB.
- Marking a document validated without receipt.
Frequently asked questions
Can I issue without Wi-Fi in BelloPOS?
Yes. Go and Pro work locally and produce invoice, UBL, hash and outbox without internet while the workstation and database operate.
Is it sent automatically when connectivity returns?
Not in the current version. BelloPOS exports files; the merchant or accountant uses the available official channel.
Does numbering remain valid offline?
The local engine assigns the series. Test your organization when several workstations can issue so concurrent sources do not collide.
What does sealed mean?
XML was created, hashed and stored locally. It does not mean received or validated by DGI.
What if the PC fails?
Restore a tested backup, reconcile recent numbers and outbox, and document any loss. CGI also provides a notification process for lost records.
Will future rules always allow offline preparation?
The technology can prepare locally, but future law may set deadlines or controls. Verify the scheme applicable when used.
What to take away
Electronic invoices can be prepared offline because entry, numbering, XML, hashing and export are local operations. Transmission and receipt form a second chain. Honest continuity shows where every document is and what remains to be done.
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
- BelloPOS electronic invoicing and UBL export, read 29 August 2026
- BelloPOS Lite, Go and Pro pricing, read 29 August 2026
Test one day without internet
Install BelloPOS, deliberately disconnect a test environment, issue an invoice and verify UBL, fingerprint, outbox and restore.
Read next
Other practical guides on the same subject: