A bilingual invoice does not mean translating every character twice. Labels can be French and Arabic while the legal name, ICE, IF, RC, number, amounts and references remain single data values. Success is measured on the PDF: the reader finds both parties, follows the lines and confuses neither digits, direction nor total.
The layout in seven decisions
- Choose a primary language and helper translation.
- Keep one legal identity and the same identifiers.
- Present FR/AR labels in pairs.
- Give Arabic genuine right-to-left direction.
- Keep numbers, currency and references unambiguous.
- Limit descriptions so the table does not break.
- Test screen, PDF, print and text extraction.
1. What is translated and what is not
Translate reading aids, not evidence. “Date / التاريخ” helps both readers; a registered legal name must not become a different company. If the business has an official name in multiple scripts, store validated versions instead of improvising on each invoice.
| Element | Treatment | Example |
|---|---|---|
| Title | Bilingual | FACTURE / فاتورة |
| Labels | Short pairs | Client / العميل |
| Legal name | Validated legal version | No free translation |
| ICE, IF, RC | Unchanged | 15-position ICE |
| Number | One value | F-2026-00125 |
| Descriptions | Useful translation if needed | Two controlled lines |
| Terms | Two approved versions | Same date and meaning |
Legal data checks are covered in ICE, IF, RC and business tax. Correct translation cannot repair bad source identity.
2. Build an RTL/LTR layout
A whole page cannot follow two directions without rules. Use blocks: seller identity, customer identity, lines, totals and terms. Each Arabic cell receives true RTL direction; numbers and codes remain visually checked.
- Set A4, margins and a font containing Arabic glyphs.
- Place title and number in a stable area.
- Put seller and customer in two clear cards.
- Pair each French label with Arabic.
- Set RTL direction for Arabic, not merely right alignment.
- Limit descriptions or allow measured line wrapping.
- Align quantities, prices, VAT and totals by column.
- Repeat headers when the table crosses a page.
- Keep stamp and signature away from amounts.
- Export and open the PDF on another device.
| Risk | Test |
|---|---|
| Disconnected Arabic letters | Font and rendering engine |
| Reversed order | Real RTL reading |
| Broken ICE | Compare 15 positions |
| Comma/point | Recalculate amounts |
| Clipped column | Print A4 |
| Different term | Human bilingual review |
Do not shrink text to seven points to fit two languages. Reduce repetition, clarify hierarchy and place long terms in a dedicated block.
3. Lines, digits and VAT
Digits are the most dangerous area because a page can appear correct while changing a decimal separator, negative sign or the visual order of an identifier. Keep one stable numeric convention and run an independent arithmetic check.
| Field | Rule | Check |
|---|---|---|
| Quantity | Same value in both readings | Compare source |
| Unit | Understood label | No ambiguity |
| Price | One explicit currency | Stable decimals |
| Discount | Visible sign and scope | Recompose line |
| VAT | Same base/rate/amount | Totals by rate |
| Gross | One final value | Net + taxes |
If a translated line changes commercial meaning, this is no longer typography. Return to the quote, order and issue process before invoicing.
Bilingual does not mean two invoices
One transaction should retain one number, date, totals and audit trail. Do not issue a French and an Arabic invoice with different numbers for the same sale to solve a presentation problem.
4. Individual or business customer
A business may want Arabic for operations and French for its accountant; a consumer may only need a readable receipt. Choose document and language for the customer without inventing missing identifiers.
Our individual or company guide separates the records. Ask the business customer for its legal name and ICE in the form it validates before issue.
Retain the language of accepted quotes and terms, or document which bilingual version governs commercially. Have important clauses reviewed by a competent person, not machine translation alone.
5. What BelloPOS lets you test
BelloPOS offers interface and printing in French, Arabic and English. Invoices use the same customer, lines, VAT and number; Go creates one from a sale and Pro retains commercial lineage.
| Test | Success | Boundary |
|---|---|---|
| Arabic interface | Readable RTL navigation | Does not validate legal content |
| FR/AR PDF | Glyphs, order, numbers | Translation needs review |
| Company customer | Stable legal name and ICE | No direct OMPIC verification |
| Sale invoice | Go | Direct path |
| Quote→invoice | Pro | Terms require validation |
| Electronic export | Go/Pro | No direct DGI transmission |
Test a ten-line invoice, a long name, a discount, two actually used rates and bilingual terms. The pricing page separates the direct path from document lineage.
Mistakes to avoid
- Freely translating the legal name.
- Creating two numbers for two languages.
- Right-aligning without true RTL.
- Mixing digit styles without testing.
- Compressing the page until unreadable.
- Translating ICE or references.
- Leaving contradictory terms.
- Testing only the screen.
Frequently asked questions
Can an invoice be in French and Arabic?
Yes as a practical presentation, provided applicable data and fields remain accurate and consistent.
Should I translate the legal name?
Use the validated legal form. Do not create a free translation that identifies another entity.
Must ICE be written twice?
No. One clear value is enough; labels can be bilingual.
Which digits should be used?
Choose a readable, stable convention, then check number, identifiers, quantities and amounts on the PDF.
Does BelloPOS print in Arabic?
Yes. Interface and printing are available in Arabic, French and English. Test your actual layout.
Do I need Pro?
Go is enough for an invoice from a sale; Pro is useful when quote, order, delivery, terms and credit must remain linked.
What to take away
A sound bilingual invoice translates reading aids, not legal reality. One identity, number and set of totals; two clear readings; a PDF tested for direction, glyphs and arithmetic.
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
- OMPIC, Common Business Identifier (ICE), read 29 August 2026
- BelloPOS numbered PDF invoices and fields, read 29 August 2026
- BelloPOS quotes, orders, deliveries, invoices and credit notes, read 29 August 2026
- BelloPOS Lite, Go and Pro pricing, read 29 August 2026
Print a real test invoice
Create a company customer, ten lines and FR/AR terms, then review the PDF with two speakers before use.
Read next
Other practical guides on the same subject: