Arakma
Solutions · Insurance claims

A complete claim file the moment the documents arrive

A claim is a bundle: the constat amiable, the repair estimate, the medical invoices, photos and a policy number someone has to look up. Arakma reads the whole bundle, checks it against the policy, and routes the claims that need an adjuster.

For insurers, mutuals, brokers and third-party administrators.

Where the time goes today

The work behind every insurance claims document

Claims arrive as a pile

Handwritten accident reports, garage estimates, hospital bills and photos, sent by the customer, the broker and the garage at different times and in different formats.

Handlers re-key before they assess

Before anyone looks at the claim itself, someone types the policy number, the dates and the amounts into the claims system. The customer waits for that, too.

Inflated estimates hide in the detail

A total that does not match its lines, a labour rate above the agreed one, a part billed twice. These are easy to miss when the job is typing.

How Arakma handles it

From the inbox to your system, with a person where it counts

The same four steps for every document, set up with your fields, your checks and your thresholds during a pilot on your own files.

  1. 1

    The bundle comes in

    Through your portal, a broker's email or a garage. Arakma groups the documents that belong to one claim, whatever order they arrive in.

  2. 2

    Every document read for its fields

    Both sides of the constat amiable including the hand-ticked boxes, estimate lines, medical acts and fees, and the policy and plate numbers.

  3. 3

    Checked against the policy and itself

    Cover on the incident date, the same vehicle on every document, estimate lines that add up, and rates against the ones you agreed with your garage network.

  4. 4

    Fast-track or an adjuster

    Simple, consistent claims go straight to settlement. Anything uncertain or above your limits goes to an adjuster with the reason already written.

What goes in

The documents your team already handles

Scanned, photographed or born digital, in Arabic, French or English. If yours is not listed, it is not a special case: describe the fields and we read it.

  • Constat amiable (accident report)
  • Repair estimates
  • Garage invoices
  • Medical invoices and prescriptions
  • Police reports
  • Policy schedules
  • Vehicle registration
  • Damage photos

Where it goes

In a format the system you already run imports

Excel, CSV or JSON, laid out to match your import template. A direct connection is built when your system allows one.

  • Guidewire
  • Duck Creek
  • Your claims system
  • Your broker portal
  • Your own API

What changes

Your team decides. It stops typing.

Claims opened on arrival

The claim file exists, complete and coded, before a handler first looks at it.

Adjusters on the claims that need them

Simple claims settle without manual handling, so your experts spend their time on the complex and the suspicious ones.

Leakage caught in the numbers

Totals, rates and duplicate lines are checked on every claim, not on the sample someone had time for.

Questions

What insurance claims teams ask first

Anything else, including security questionnaires, we answer before a pilot. How we handle data.

Can it read a handwritten constat amiable?

Yes, including the ticked circumstance boxes and the sketch area's labels. Handwriting it is less sure about is scored lower and checked by a person.

Does it decide whether a claim is paid?

No. It assembles and checks the file and routes it by your rules. Settlement decisions stay with your team.

Can we use our own garage and tariff rules?

Yes. Agreed rates and limits are part of the checks we configure with you during the pilot.

Bring ten of your own insurance claims documents

We run them through Arakma with your fields and show you the output, scores and review decisions in a call. If it works on yours, we scope a pilot.

Or write to contact@arakma.com. We reply within one business day.