Why Flikma

Accounting software was never built for freight.

Most logistics companies run an accounting package with a logistics module bolted on, then spend their lives translating between the two. Flikma was built the other way around: the shipment is the centre, and the ledger simply follows it.

If your biggest cost is a person retyping documents, and your biggest risk is a missed ZATCA deadline, you are using the wrong category of software.

Documents retyped by hand
e-invoicing as a separate add-on
Warehouse features you never use
One platform, freight-first

What we think a logistics ERP should be

The shipment is the source of truth

Not the invoice. Not the spreadsheet. The job file is the record of what happened, and every document, charge and ledger entry hangs off it. When something does not add up, there is one place to look.

Software should do the typing

Humans should verify, not transcribe. Every document entering your business has been transcribed by someone, at some point, usually twice. AI removes that step entirely and leaves the human judgement where it is actually valuable.

Compliance is not a feature

ZATCA Phase 2 is a legal obligation, not a competitive feature to be upsold. It is in the base product, on the free plan, because a Saudi company should never have to ask whether compliance is switched on.

Do not sell what you do not need

Flikma has no warehouse module, because most of our customers do not run one and paying for put-away logic you never touch is a tax on your business. We would rather be a precise fit than a bloated one.

Flikma vs. a typical accounting-plus-logistics setup

The categories below are the ones logistics teams tell us matter most. If your current system handles these well, keep it — genuinely.

Capability
Flikma
Typical alternative
Enquiry to quotation to job
One continuous record
Split across tools
Supplier invoice data entry
AI extracts and pre-fills
Manual retyping
Receipt and expense capture
Photograph → posted
Manual, after the fact
ZATCA Phase 2 e-invoicing
Included on all plans
Often a paid module
Invoice type selection
Automatic from customer
Manual selection, error-prone
Job profitability visibility
Live, per leg
Only after month-end
Airway bill & sea waybill printing
Native, multiple formats
Third-party tool or Word
Multi-entity across the GCC
Built in, consolidated
Separate databases or add-ons
Arabic and English documents
Bilingual throughout
Often English only
Warehouse & stock control
Deliberately not included
Often bundled, often unused
Typical time to first cleared invoice
2–3 weeks
2–6 months

The "typical alternative" column reflects the feedback of forwarders who came to us from other systems. Your mileage will vary — that is what the demo is for.

What changes in the first ninety days

Aggregate figures reported by customers after their first full quarter on Flikma. Individual results vary by volume and process.

70%
Less time on supplier bill entry
18 hrs
Saved per invoice on admin
100%
ZATCA clearance first time
3 wks
Average time to go-live
RK
Operations Manager
Freight forwarder, Riyadh

"The scan feature paid for itself in the first month. Our admin used to spend two full days a week typing carrier invoices. Now she reviews them."

AM
Finance Director
Logistics group, Bahrain

"Month-end used to take nine days. The last close took two, and I did not have to rebuild a single spreadsheet to get there."

SD
Managing Director
Freight forwarder, Dubai

"I can see the margin on a job while it is still moving, not when it is finished. That one change has altered how we price."

Your freight data is commercially sensitive. We treat it that way.

A forwarder's data reveals your customers, your carriers, your rates and your margins. Losing it, or leaking it, is an existential event. These are the controls we run.

  • Tenant isolation — every company gets a scoped data layer; one tenant can never read another's records
  • Role-based permissions at module level, enforced server-side on every request
  • Full activity logging — every change is attributable and time-stamped
  • Two-factor authentication and optional SSO on Enterprise
  • Document isolation — scanned files processed in a separate queue, never used to train shared models
  • Backups and recovery with monitored uptime and restore testing
Private Cloud

Dedicated tenancy in a Saudi-region data centre.

On-Premise

Available on Enterprise for regulated customers.

Audit Logs

Exportable history for internal and external audit.

SSO & 2FA

SAML single sign-on and mandatory 2FA on Enterprise.

Moving is less painful than you think

The scariest part of changing freight software is not the software — it is the fear of losing a decade of job history and outstanding customer balances. That is the part we take off you.

  • Run both systems in parallel for your first month — nothing is switched off on day one
  • Open jobs migrate, not just masters — in-transit shipments keep their history
  • Aging carries over exactly — every open receivable and payable with its original invoice date
  • Trial balance reconciled before we declare the migration done
  • ZATCA onboarding runs in parallel, so your first month of compliant invoicing starts clean
Read about our process
2–3
Weeks to live
1
Month in parallel
0
Data lost

Most forwarders tell us the migration was the least stressful part of the project. The nervous part before it is completely normal.

Convince us you need something else

Bring your hardest workflow to the demo. If Flikma cannot do it, we will tell you — and point you at something that can.