E-invoicing manual
Swifto turns your invoices into legally compliant e-invoices in TEIF format, signs them with your TunTrust certificate (DIGIGO or SEAL / Company ID mode), then files them on the national El Fatoora platform of Tunisie TradeNet (TTN). In return, each invoice receives its TTN reference and its visible electronic-seal QR code.
Overview
E-invoicing is the issuance of an invoice as a digitally signed XML document, filed on the official El Fatoora platform operated by Tunisie TradeNet (TTN). The signature guarantees authenticity (the issuer is properly identified), integrity (the invoice has not been altered) and non-repudiation (the issuer cannot deny having issued it).
Business goal
- Comply with the e-invoicing obligation
- Issue invoices with evidentiary value (signed + time-stamped)
- Obtain the official TTN reference and QR code
- Archive the signed and validated XML of every invoice
Target audience
- Billing / accounting — issuance & tracking
- Administrator — certificate configuration
- Management — regulatory compliance
Where does e-invoicing fit in?
It extends the Sales invoices module: once the invoice is created and validated (not a draft), a dedicated button lets you sign and file it. Certificate configuration is done in the Company profile.
The TEIF format & the El Fatoora platform
TEIF (Tunisian Electronic Invoice Format) is the standardized XML format required by TTN for Tunisian e-invoices. Swifto generates it automatically from the invoice data — there is nothing extra for you to enter: the header (issuer, customer), the item lines, the taxes (VAT, stamp duty…), the excl./incl. VAT totals and the references are all placed in the right spot.
1 · TEIF generation
Swifto produces the compliant XML from the invoice.
2 · Signing
The XML is signed with your TunTrust certificate.
3 · El Fatoora filing
TTN validates and returns the reference + QR code.
Parties involved
ANCE / TunTrust issues the electronic certificates and operates the signing service; Tunisie TradeNet (TTN) operates the El Fatoora platform, which receives, checks and archives invoices. Swifto interfaces with both on your behalf.
Two signing modes: DIGIGO & SEAL
Swifto supports both types of signature offered by TunTrust. The choice is made once and for all in the company profile, depending on your invoice volume and your budget.
DIGIGO (personal)
Signature carried by an individual's mobile certificate. The signer authorizes each signature from their phone (DigiGO app). Ideal for moderate volumes and the least expensive option.
- Signature invoice by invoice (single)
- Holder authorization required (mobile)
- Reduced cost
SEAL / Company ID (seal)
The company's electronic seal, hosted at TunTrust. It signs with no human intervention and allows bulk signing of several invoices at once. More expensive, but ideal for large volumes.
- Bulk signing (multiple selection)
- No manual authorization (automatic)
- Higher cost
| Criterion | DIGIGO | SEAL / Company ID |
|---|---|---|
| Nature | Personal signature (holder) | Company seal |
| Human intervention | Yes — mobile authorization | No — fully automatic |
| Bulk signing | No (one invoice at a time) | Yes (several invoices) |
| Cost | The most economical | Higher |
| Recommended use | Low to medium volume | High volume / grouped invoicing |
Prerequisites
A valid TunTrust certificate — DigiGO certificate (individual) or SEAL / Company ID seal, issued by ANCE and not expired.
Complete tax ID — your company's must be 13 characters long (identifier + check key + VAT code + category code + establishment). The customer's tax ID (legal entity) or national ID/CIN (individual) must also be recorded.
El Fatoora (TTN) credentials — the login, password and filing tax ID provided by TTN must be recorded in the company profile.
Consistent invoice data — correct items, quantities, prices, taxes and totals. Swifto blocks signing if mandatory regulatory information is missing.
Configuration (Company profile)
Setup is done once by an administrator, in Administration → Company profile. That is where you choose the signature type and enter the credentials.
| Parameter | Role |
|---|---|
| Signature type | None, DIGIGO or SEAL / Company ID. Determines the signing button shown in the invoice list. |
| Signer login / password | The credentials for the TunTrust certificate (DigiGO or seal). |
| Seal alias | SEAL only: the alias of the company seal. |
| El Fatoora login / password / tax ID | The filing credentials for the TTN platform. |
| Tax ID & signer | Company tax ID (13 char.); for DIGIGO, the holder's email and mobile number are used for authorization. |
As long as the signature type is "None", no signing button appears. Once a type is chosen, the invoice list shows the corresponding action (single signing for DIGIGO, grouped signing for SEAL).
The signing process, step by step
Whatever the mode, the logical flow is the same: Swifto prepares the document, has it signed, files it, then retrieves the official validation.
flowchart LR A[Validated invoice] --> B[TEIF document
generation] B --> C{Signature
type?} C -->|DIGIGO| D[Authorization
by the holder on mobile] C -->|SEAL| E[Automatic company
seal] D --> F[Document signing] E --> F F --> G[Filing on El Fatoora TTN] G --> H{Validated by
TTN?} H -->|Yes| I[TTN reference
+ QR code] H -->|Not yet| J[Awaiting
validation] J -.retry.-> H
The TTN check can take a few moments. If validation is not immediate, the invoice moves to "Awaiting validation" and you can retry the check later (see Statuses & tracking).
Signing an invoice — DIGIGO mode
- 1
Open the invoice list
Menu Sales → Invoices. The invoice must be validated (not a draft) and not yet signed.
- 2
Start the signing
Click the row's signature icon. Swifto generates the TEIF and prepares the authorization request.
- 3
Authorize on your mobile
You are redirected to DigiGO authorization: the certificate holder approves the signature from their phone (PIN code / app).
- 4
Filing & validation
Swifto signs, files on El Fatoora and retrieves the result. On success, the invoice becomes Signed & validated with its reference and QR code.
Do not close the window during authorization: the signature is tied to this invoice. If you interrupt it, simply restart the signing.
Bulk signing — SEAL / Company ID mode
- 1
Select the invoices
In the invoice list, tick several validated and unsigned invoices.
- 2
Start "Sign invoices"
The grouped button (visible in SEAL mode) triggers TEIF generation and signing by the company seal, with no manual authorization at all.
- 3
Grouped filing & tracking
Swifto files the batch on El Fatoora and displays the result invoice by invoice: validated (reference + QR), pending, or in error (with the TTN reason).
Only the eligible invoices in the batch are processed (validated, unsigned, complete tax IDs). The others are skipped and flagged — you can fix them and then retry.
Invoice statuses & tracking
Each invoice carries a signing status that evolves throughout the process:
Not signed
Eligible invoice not yet signed. The signing button is available.
Filed — pending
Signed and filed with TTN, but validation has not come back yet. To be rechecked later.
Signed & validated
Validated by TTN: TTN reference + QR code available, signed XML downloadable.
Reference & QR code — once validated, the invoice carries the official TTN reference and the QR code (visible electronic seal), printed on the document.
Rechecking — for a "pending" invoice, retry the check: if TTN has validated it in the meantime, it automatically moves to "validated".
XML download — the signed and validated document can be downloaded from the list for archiving.
TTN rejection — if TTN refuses the invoice, the reason is displayed. Fix the data at fault, then restart the signing.
Business rules
No signing while draft — an invoice must be validated before it can be signed; an already-signed invoice cannot be signed again.
Mandatory tax IDs — company tax ID of 13 characters; customer tax ID (legal entity) or national ID/CIN (individual). Otherwise, the invoice is not eligible.
Frozen document — the signature seals the content: any later change would invalidate the signature. An invoice validated by TTN can no longer be edited.
Valid certificate — an expired or revoked certificate makes signing fail; remember to renew it with ANCE / TunTrust before it expires.
Roles & permissions
| Action | Billing | Accounting | Management | Admin |
|---|---|---|---|---|
| Configure the certificate / signature type | — | — | — | ✅ |
| Sign an invoice (DIGIGO) | ✅ | ✅ | ✅ | ✅ |
| Bulk signing (SEAL) | ✅ | ✅ | ✅ | ✅ |
| Recheck / track filings | ✅ | ✅ | ✅ | ✅ |
| Download the signed XML | ✅ | ✅ | ✅ | ✅ |
Indicative matrix — depends on the profiles defined in your company.
Usage scenarios
SME with a personal certificate (DIGIGO)
The manager signs each issued invoice themself, as they go: they click "sign", approve on their mobile, and the invoice comes back validated with its QR code.
High-volume distributor (SEAL)
At the end of the day, the billing team selects all of the day's invoices and starts grouped signing by seal: the batch is signed and filed in a single operation, then tracked invoice by invoice.
Deferred validation
A filed invoice stays "pending" because TTN has not answered yet. The next day, the user retries the check: the invoice becomes "validated" and gets its reference.
FAQ & Tips
DIGIGO or SEAL: which to choose?
Few invoices and a personal certificate? DIGIGO (economical). Many invoices to sign at once with no intervention? SEAL / Company ID (more expensive but automatic and grouped).
The signing button doesn't appear?
The signature type is probably set to "None" in the Company profile, or the invoice is a draft / already signed.
"Invoice rejected by TTN" — what to do?
Read the displayed reason (often a missing/incorrect tax ID or mandatory field), fix the invoice or the third-party record, then restart the signing.
Tip — make third-party records reliable
Carefully fill in customer tax IDs / national IDs upfront: this is the top cause of non-eligibility or signing rejection.