EKLAIM
A claim that used to travel as paper.
EKLAIM moved Sekar Laut's claims into one system: raised at a site, approved in role order, posted to Oracle Fusion, and archived where the people who need it can find it.
How a claim runs now
5 steps
- RaiseOpened at a site, with attachments
- CheckSigners follow role order and area
- FormApproval form, with Oracle selections
- PostAP invoice to Oracle Fusion
- PayOracle payment closes the claim
The next claim starts here
Seven claim types, one paper trail.
A claim began at a site: a wage claim, an operational cost, a travel report, a cash advance. The form was filled by hand, signed by a supervisor, put in a folder, and carried to the office. By the time finance saw it, the trail was already thin.
Each claim type moved through its own set of desks. The order lived in people's heads, and a claim could sit for days because the next signer did not know it was waiting.
Nothing could be searched. Status was a phone call. When the claim was finally paid, the same figures were typed again into the accounting system — a second record of the same work.
The paper left. The rules stayed.
The approval order was already real; it was just carried by people. The system keeps that order, and removes the carrying.
Paper form at the site
Online claim
Seven claim types share one front door, with attachments and a period.
Folder carried to the office
Area-scoped queue
A signer sees the claims their area covers, and only at their step.
Sign-off collected by hand
Role-ordered approval
Each claim carries a frozen flow snapshot, so a later org change never rewrites history.
Records filed by hand
Searchable archive
Every claim, attachment and action stays in one record, printable and exportable.
Figures retyped into accounting
Invoice posted to Oracle
The AP invoice is built from the approved claim; the payment sync closes it.
One register, six states.
The claim is the record. Everything else — the signers, the form, the invoice, the payment — hangs off it.
One claim register
Wage, operational, SPPD, LPPD, kasbon, LPK and expedition claims in one list. Filter by period, status, opener and division; export the filtered set to XLSX.
Approval that follows the org
Role-ordered flows, area scoping, reject with a reason, and revert. Every nominal change is appended with its signer, role and note.
The approval form
Opened for printing once pre-approvals are complete, by a finance role, with Oracle accounting selections stored on the claim. Re-printable from the record.
Posting to Oracle Fusion
Post-approval dispatches the AP invoice: supplier, site, distribution set, tax and withholding. Settlement sends a standard invoice or a debit memo.
Payments that close themselves
The Oracle payment list is synced every five minutes; a matching invoice number closes the claim and notifies the opener. Proof of payment stays on the claim.
Reminders that find the gap
Telegram and in-app notices on reject, payment, refund and settled claims, plus month-end checks for travel reports and cash advances still open.
Fitted around Oracle, not over it.
The accounting system stayed. The claim system feeds it, then reads back what it paid.
- Laravel 12 · MySQL
- API, queue, scheduled Oracle sync and master-data refresh.
- Next.js 15
- The interface used at the site, in the office and in finance.
- Oracle Fusion
- AP invoices, debit memos, payment reconciliation, vendors, taxes and distribution sets.
- Backblaze B2
- Claim attachments and payment proofs, stored through the S3 API.
- Telegram
- Claim notifications for the people who act on them.
One record from the site to the payment.
Claims run in one system: searchable, tracked through every stage, and posted to Oracle Fusion without re-typing. The paper trail is no longer the process.
- Six claim states, reversible until a claim is finished or rejected.
- Approval follows the claim's area and role, not a courier.
- The invoice is built from what was approved, not typed from it.
- Payment closes the claim on its own when Oracle reports it paid.
Client
Sekar Laut
A food manufacturer in Sidoarjo. EKLAIM is its internal claims and approval system, used across sites and finance. It has no public product site.
Send one workflow. We'll look at it with you.
Tell us the task that costs your team the most hours, and how it runs.
The first conversation is free, with no commitment.