For Morocco

Operations that satisfy your customer's auditor, not just your own books

We are not a Moroccan-plan accounting package, we do not file with the DGI, and our interface is in English. What we run is the operations layer an exporter or a group subsidiary needs: traceability both directions, governed procurement, and margin measured in the currency the contract was signed in.

The subject: The audit that actually interrupts your week comes from your customer, not from the DGI — and it is one question pointed in one of two directions, answered from one set of records or from two days of reconstruction.
Interface language: English only. No French, no Arabic, no right-to-left. In Morocco this is frequently decisive, it is a build rather than a setting, and it leads our scope section rather than hiding in it.
Statutory accounts: Not us, and we will not file with the DGI. The local chart and the statutory presentation belong with your expert-comptable, who is licensed for it and carries the liability. We feed them a defensible operational record.
Not a QMS: We hold the movements, consumption, certificates and approvals a quality system draws on. Specifications, non-conformance and corrective actions are a different product — run one alongside us rather than expecting this to be both.

Trace it both ways Talk to us about Morocco

One set of links, read from either end

The same question, asked from both ends, answered from one set of records

The audit that interrupts a Moroccan exporter's week comes from the buyer in Lyon, not from the DGI, and it is always one question pointed in one of two directions. Neither column below is a feature. They are the same movements read forwards and backwards, which is the entire reason both take minutes — and the reason an operation that captures issues to production but never links them to despatches can answer neither.

Forward — the recall

This input lot was defective. Where did it go?

The receipt that brought that lot in, with its supplier, date and certificate attached.

Every issue of that lot to production, with quantity, date and the person who issued it.

The batches those issues went into.

Every despatch from those batches.

The customers who received them, and how much each one has.

A list of customers to call, with quantities, before anybody calls you.

Backward — the complaint

Your customer says this delivery was defective. What went into it?

The despatch that delivery came from.

The batch it was drawn out of.

Every input issued into that batch, with quantities and dates.

The receipts those inputs arrived on, with their suppliers.

The certificates attached to those receipts.

A supplier, a lot number and a document — which is what the customer is actually asking for.

One qualification that belongs here rather than under it. This is not a quality management system. It holds the movements, the consumption, the certificates and the approvals that a QMS and a customer auditor both draw on; it does not manage specifications, non-conformance workflows or corrective actions. If that is what you are shopping for, buy one and keep this underneath it — the two are complementary and we would rather you ran both than expected this to be both.

Operations in Morocco

A Moroccan exporter is audited by their customer more often than by their tax authority.

The DGI answer is above and it stays with your practitioner. The audit that actually interrupts a Moroccan exporter's week comes from the buyer in Lyon or Barcelona, and it is one question in two directions: this lot was defective, where did it go, and what went into it. Answering that from delivery notes and a production log is a two-day exercise; answering it from the record that created the movements is a filter. That is the layer below.

Inventory

Traceability that runs in both directions

From an input lot forward to every customer that received it, and from a customer complaint backwards to what went into the batch. Both directions are the same records read two ways, which is why the answer is minutes rather than days.

Inventory adjustments

Consumption recorded across sites as it happens

Issues to production carrying a reason and a person, blind counts with valued variance, and the same discipline at every site rather than at the one with the best supervisor.

Procurement

Change control that finally leaves an inbox

Requisition, refusing threshold, RFQ comparison with losing quotes retained, purchase order and three-way match. When a customer asks who approved a substitution of a specified input, the answer is a record rather than an email thread somebody still has.

Document vault

Certificates against the thing they certify

Supplier documents, certificates of analysis, contracts and delivery notes attached to the transaction and previewable in place, with expiry tracked on supplier records. The customer audit asks for these in a sequence, and the sequence is the transaction.

Project cost

Margin measured in the currency the contract was signed in

Cost coded to site, order and customer at entry, and foreign-currency transactions holding both amounts and the real rate — so a euro contract's margin is explainable a year later rather than recalculated from a rate nobody recorded.

Assets

Plant and equipment with a custodian per item

Named custodian, location, condition at every hand-off and movement history across sites — custody rather than depreciation, which is the register your group parent and your customer both ask about.

A boundary worth stating inside this section rather than under it: this is not a quality management system. It holds the movements, the consumption, the certificates and the approvals that a QMS and a customer auditor both draw on. It does not manage specifications, non-conformance workflows or corrective actions, and if that is what you are shopping for you should buy one and keep us underneath it.

Recognisable, we hope

Four things a customer audit finds first

A trace you can only run backwards

You can show what went into a finished unit. You cannot say, in the room, which customers received a defective input lot — which is the question that actually costs money.

Margin measured in the wrong currency

Revenue in euros, inputs in euros and dollars, conversion cost in dirhams, and a management report in dirhams that cannot separate an operational bad month from a currency cross.

Change control that lives in an inbox

A supplier substitution everyone agreed was sensible, approved verbally, discovered by an auditor eighteen months later with nothing written down.

An accountant reconstructing the year

A fiduciaire working from receipts and recollection is doing an expensive job slowly. The same accountant working from governed operational records is doing a cheap job quickly.

Scope in Morocco, and the three refusals are in the first sentence of the page

Running in the product today

Two-way lot traceability — forward from an input to every customer that received it, backwards from a complaint to what went into the batch.
Consumption and issues recorded across sites with a reason and a person, blind counts and valued variance.
Procurement with refusing thresholds, RFQ comparison with losing quotes retained, purchase orders and three-way matching.
Certificates and contracts attached to transactions, previewable in place, with expiry tracked on supplier records.
Cost coded to site, order and customer at entry, and foreign-currency transactions held at the rate actually applied with both amounts retained.
Asset registers with named custody, movement history and condition on hand-off.
MAD as your base currency, with euro and dollar contracts held in their own currency and never silently converted in a report.

More we can add — on the roadmap, and commissionable now

French or Arabic interface, and no right-to-left layout. Documents are produced in English. In Morocco this is frequently decisive, and it is a build rather than a setting.
DGI transmission or Moroccan e-invoicing connection. Our transmission layer is Kenya's eTIMS and it is Kenya-only.
Moroccan statutory payroll. The maintained statutory engine covers Kenya only. Employee records, attendance, leave and cost allocation are real; CNSS and IR calculation is not.
Bank statement reconciliation — for any market, in whatever form the bank exports.

What we would decline, and would rather say now

We will not be your Moroccan-plan accounting package and we will not file with the DGI. Statutory accounts in the local chart belong with your expert-comptable, who is licensed for it and carries the liability. We feed them a defensible operational record; we do not replace them, and a vendor claiming to would be selling you a professional service in a software licence.
We will not be a quality management system. Specifications, non-conformance handling and corrective actions are a different product with different users. We hold the evidence a QMS and a customer auditor draw on, and we integrate with whichever one you run.

The middle column is work rather than positions, and each is commissionable now on a written specification, a timeline and a price agreed before any money moves — and for French we would show you a customer-facing document before you signed anything. Kenya is the evidence that this is a real offer: its eTIMS transmission and its statutory payroll engine were both built exactly this way by clients who needed them.

Language first, everything else second. If your site supervisors and your store staff work in French, weigh that row above every capability on this page — a Moroccan vendor already shipping it starts where we would be finishing, and we would rather write that here than lose your third month to it.

How this starts

Three moves, and the first is one lot

Decide whether you should be buying locally

If your team works in French and your need is statutory, a Moroccan vendor is the better purchase and we will tell you so in the first call. This step is genuinely first.

Instrument the receiving dock

Lot identity created at the door is what makes every downstream trace possible. It is the cheapest step and the one most often deferred until it cannot be applied retroactively.

Agree the handover to your fiduciaire

What they receive, in what form, how often — settled with them before go-live rather than discovered afterwards. It is a short conversation and skipping it is the main source of friction in a split arrangement.

Read before you shortlist

Guides for this market

Africa Business Guides

ERP Software in Morocco: A Practical Buyer's Guide (2026)

Moroccan buyers are usually choosing between a French-language local incumbent and an English-language international product, and the deciding question is rarely features. Who reads the screen, who reads the contract, and who answers the phone.

Sep 6, 2025 · 12 min Read

Africa Business Guides

Manufacturing & Export Operations in Morocco: Built to Someone Else's Standard

When your customer is in Europe, their audit is your operating system. Traceability that survives a client visit, consumption recorded against the job, and the difference between records that satisfy you and records that satisfy them.

Sep 7, 2025 · 11 min Read

Africa Business Guides

Multi-Currency Operations in Egypt & Morocco: Two Very Different Problems

The Egyptian pound and the Moroccan dirham are both "local currency" and almost nothing else about them is alike. Why one demands rate discipline per transaction and the other demands discipline about the euro.

Sep 5, 2025 · 11 min Read

Assets & Equipment

From Maintenance Records to Preventive Schedules

Maintenance is recorded here as a movement: what happened, to which asset, on what date, by whom — a real history you can read. Preventive schedules that generate the next visit from that history are the layer above, and one we can add for you.

Jun 12, 2026 · 12 min Read

Point of Sale

A Discount Nobody Had to Authorise

A discount at this till is four columns: the sale, the line, a free-text description and an amount. No approver, no reason code, no limit and no user. It is a record of what happened, not a control over whether it should have.

Jun 9, 2026 · 11 min Read

HR & Payroll

The Numbers You File Under

This payroll engine computes statutory deductions correctly and cannot store the reference numbers those deductions are filed under. Two such columns exist in our database and are read by nothing — not a form, not a payslip, not an export.

Jun 5, 2026 · 11 min Read

Questions we are asked in Casablanca

Straight answers, and where your fiduciaire's work begins

Is the interface available in French or Arabic?

No. The interface is English only, there is no right-to-left layout, and documents are produced in English. We do not ship translation files and this is not a setting waiting to be enabled. For a domestic Moroccan business whose staff work in French or Arabic, that is usually a sufficient reason to buy from a local vendor and we say so routinely. Export manufacturers and group subsidiaries whose teams already operate in English generally find it workable — but test it with the people on the floor rather than the finance director. That is on the roadmap rather than a boundary, and it is commissionable now. French is interface text and document templates; Arabic is that plus right-to-left layout, which is engineering and gets priced as engineering. Ask and we will scope it with a specification, a timeline and a price. The honest caveat: a vendor already shipping the language starts where we would be finishing, so if it is your first requirement rather than your third, buying locally is the rational move and we would rather write that sentence than lose your third month to it.

Do you produce Moroccan statutory accounts or file with the DGI?

No to both. We are not a Moroccan-plan accounting package, we produce no statutory financial statements to local conventions, we have no DGI integration and we file nothing. Morocco has been moving toward electronic invoicing requirements and you should confirm the current position and your own obligation with the DGI or your adviser. AWRA is the operations layer alongside whatever keeps your statutory books — a local package, or your fiduciaire. This one is a boundary rather than a backlog — it does not change with a commissioned build, at least for the accounts half, and the reason is worth having: a statutory presentation to the Moroccan plan is your fiduciaire's work and their signature goes on it, so software generating it would insert us between you and the person accountable for it. We hold the costed detail those accounts are built from. The DGI pipeline is a different matter and is buildable — if electronic invoicing to a published Moroccan specification is what you need, ask and we will scope it. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself.

Can you trace a defective input lot forward to our customers?

Yes, provided the discipline is in place: lot identity created at receipt, consumption recorded against the job rather than against a department, finished output carrying its own batch linked to its inputs, and the batch carried through dispatch. Note the wording — against the job, not against a production order, because there is no production order object here. That does not weaken the traceability, which is genuinely both-directional; it means the link is an issue charged to a job rather than a run with an expected quantity behind it. Bring a real lot to the demo and time us.

Is this a quality management system?

No. There is no CAPA workflow, no non-conformance process, no inspection planning and no certified document control, and we do not manage or maintain certifications. What we provide is the evidence infrastructure a quality system relies on — material genealogy, approvals with dates and names, documents attached to transactions, measured yield. No auditor accepts software in place of a quality system, and any vendor implying otherwise is setting you up to fail an audit. This one is a boundary rather than a backlog — it does not change with a commissioned build, CAPA workflow, non-conformance handling, inspection planning and certification management are a different product category with their own auditors, and bolting a thin version onto an operations system is how businesses end up with a QMS that fails its first external audit. Traceability of lots and batches — the part that touches stock — we do today.

Does it handle the dirham and Moroccan VAT?

The dirham and a Moroccan value added tax rate ship as built-in presets, and every line separates net, tax and gross at the point of capture. More useful for most exporters is that transactions stay in their original currency, so a euro contract, euro and dollar inputs and dirham conversion costs can each be held as denominated and margin measured in the contract currency. We ship one maintained VAT preset rather than a maintained rate history.

What about Moroccan payroll?

Not ours. Our maintained statutory payroll engine covers Kenya only — Moroccan income tax withholding and social contributions are not calculated, produced or submitted for you. AWRA holds employee records, attendance, leave and payroll cost allocation to jobs, projects and cost centres, and a Moroccan payroll specialist or your fiduciaire handles the statutory layer.

Where does support come from?

Nairobi, with remote onboarding and live training in English. Morocco is two hours behind us, so most of your working day overlaps ours. If support in French is a requirement, that is another good reason to buy locally and we would rather say it here.

Bring one lot and one contract

We will trace the lot in both directions on the clock and cost the contract in the currency you are paid in — then tell you honestly whether a local vendor would serve you better.

Talk to us about Morocco See plans & pricing