A very small business does not need to begin with an API or a large specification. Begin by making the data reused on every invoice accurate, then test a full cycle: sale, issue, correction, export, backup and restore. Five short actions create more readiness than a rushed purchase presented as mandatory.
Your starting plan
- Have your tax regime and legal category confirmed.
- Clean business identity, business customers, products and rates once.
- Write who issues, corrects, exports and hands files to the accountant.
- Test an invoice, credit, outage and period export.
- Back up to a second medium and perform a real restore.
- Follow DGI sources without buying against an unsourced sales date.
1. Day 1: confirm what applies to your small business
Small business describes size, not a tax regime. An IS company, a person under simplified net income and an auto-entrepreneur may all call themselves small without sitting on the same line of Article 145. Ask the accountant for a one-page sheet: form, regime, VAT, activity, identifiers and applicable text. Our guide to the current obligation explains the categories without inventing a universal date.
| Question | Answer to record | Why |
|---|---|---|
| Who invoices? | Legal name or company | Avoids mixing owner, trade name and company |
| Which regime? | IS or precise IR regime | Determines how the CGI is read |
| VAT? | Liability, rates and validated cases | Stops rates being applied from habit |
| Which activity? | Main and secondary activities | Connects a sector rule |
| Who monitors news? | Named manager or accountant | Prevents decisions from screenshots |
Article 145-IX of the 2026 CGI names IS companies, professionals under actual or simplified net income and VAT taxpayers, with arrangements set by regulation by sector. Paragraph XI excludes individuals under CPU and auto-entrepreneur regimes except for email. Verify status now and whenever it changes.
2. Days 2 and 3: clean six reusable data sets
A small operation has an advantage: the volume to clean is often manageable. Correct before importing. A bad ICE copied to one hundred invoices does not improve because software automated it. Use mandatory invoice fields as the final-document checklist.
- Seller: Legal name, address, ICE, IF, RC, business tax, bank details and validated regime.
- Customers: Legal name, address, business ICE, contact and terms without duplicates.
- Products: Clear label, unit, price, VAT rate and consistent category.
- Numbers: Prefix, optional year, last issued number and separate rule per document.
- Payments: Cash, card, transfer and credit without confusing sale and receipt.
- Owners: Named person for issue, checking, export and backup.
Keep a change log: old and new names, merged duplicate, corrected rate, starting number and approver. This small journal prevents an argument six months later. From Excel, keep a read-only copy and import only useful columns.
3. Day 4: play five scenarios, not five menus
A useful test reproduces a situation from beginning to end and leaves evidence. Use the software-selection grid to record results rather than screen impressions.
- Sell two products to an individual, print the receipt and check payment.
- Turn a sale into a business invoice without re-entering lines.
- Issue an invoice, then correct a quantity through a linked trail.
- Disconnect internet, issue an item and find it in the local queue.
- Export the day, open PDF and structured file and reconcile numbers.
- Back up, restore to a copy and find all operations.
For each test record expected and observed results, screenshot, gap, owner and correction date. A small business needs no project-management suite; one clear sheet is enough and doubles as training evidence for whoever replaces the manager.
Do not let sales urgency choose your timetable
The developed portal, the system duty in the CGI and your operational date are three different things. Require the official source and covered sector. Prepare data now because it is useful; do not buy because a vendor displays a countdown without text.
4. Day 5: write a procedure that fits on one page
State when the invoice receives its number, who checks identity and VAT, how to correct, when to export, where the pack goes and who hands it over. Add the outage rule: checkout continues locally, nobody recreates the same sales later, and the queue is checked when connectivity returns.
- Daily: Check errors and queue before close.
- Weekly: Back up elsewhere and open an export.
- Monthly: Reconcile numbers, VAT, credits and hand-off.
- On every notice: Read source, scope and date and confirm impact.
Separate copies. The live database stays on the computer; a backup goes to another medium; period exports go into dated folders; any official receipt returns to the same folder. Synchronisation is not automatically backup, and a backup never restored remains a hypothesis.
Book thirty minutes monthly with the accountant: number sequence, invoices and credits, VAT totals, payments, export, open errors and new official notices. Bring the same dated pack every time and record each decision, owner and due date. Begin the following month by closing those items. This short loop stops one bad template or rate from repeating all year. It is more realistic than an annual audit assembled in panic.
5. BelloPOS for an offline small business
BelloPOS Go covers a small retailer’s common path: local sale, A4 invoice from the sale, identity and VAT, UBL 2.1, SHA-256, local queue and individual or period ZIP export with CSV manifest. Go is a one-time licence. Pro adds quotes, orders, deliveries, invoices and credits in Documents plus the accounting bridge.
| Small-business step | In BelloPOS | Human check |
|---|---|---|
| Legal data | Compliance screen and customer record | Validate regime and identifiers |
| Issue | Invoice from sale | Check before final number |
| Preparation | UBL and SHA-256 offline | Do not call it DGI validation |
| Hand-off | XML or ZIP with manifest | File through available official channel |
| Continuity | Local database and queue | Test backup and restore |
BelloPOS does not submit directly to the DGI, and UBL 2.1 is its export choice, not a national requirement we attribute to the authority. The business still verifies, exports, hands over or files, then retains evidence. Compare Go and Pro on pricing.
Mistakes to avoid
- Treating small-business size as a sufficient tax regime.
- Importing all old data before cleaning identities and duplicates.
- Letting every employee choose their own number or template.
- Testing only with internet available.
- Backing up to the same disk and never restoring.
- Confusing a prepared export with successful administrative transmission.
Frequently asked questions
Must a Moroccan small business already send invoices to the DGI?
Universal transmission is not an accurate claim. The CGI names categories and refers arrangements to sector regulation. Check regime, sector and applicable text.
Where do I start with little time?
Confirm regime, clean seller identity and ten important customers, then test an invoice, correction, export and restore.
Must I leave Excel immediately?
No. Freeze and retain history, clean data and choose a cutover date. Do not prolong a file that has become uncontrollable.
Who should manage exports?
Name the manager or accountant and write frequency, checking, filing and receipt retention.
Which BelloPOS plan fits?
Go covers invoices from sales and electronic preparation. Pro fits quotes, orders, deliveries, manual credits and accounting.
Does checkout stop without internet?
Not for the local BelloPOS path. Sales, issue and queue continue; external filing waits for the available channel.
What to take away
A small business is ready when it knows its regime, controls six data sets, knows who issues and corrects, can produce a period pack and restore its database. That comes from one disciplined week, not a purchased badge.
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
Prepare invoicing without burdening your small business
See the offline BelloPOS path, then compare Go and Pro depending on whether you need invoices from checkout or a complete document and accounting chain.
Read next
Other practical guides on the same subject: