One front door for documents and internal claims.
A visible stage, a named approver, one record.
For finance and operations teams handling travel claims, cash advances, reimbursements, and the internal documents that need a signature before anything is paid.
How an internal claim can run
5 steps
- RaiseOpened once, with its own fields and attachments
- CheckThe next signer sees it at their step
- PrepareFinance sets vendor and tax, then prints
- PostThe invoice is posted to the accounting systemAutomated
- CloseThe payment closes the claimAutomated
The next claim starts here
Illustrative example
The paper trail is the process.
A claim starts on a form at a site, or in a message with a photo of a receipt. Each kind of claim has its own fields and its own approvers, and the order lives with the people who handle it.
The form is signed, put in a folder, and carried to the office. By the time finance sees it, the trail is already thin. A claim can wait because the next signer does not know it is there. Not every company runs it this way, but the shape is common.
Nothing is searchable. Status is a phone call. When the claim is paid, the same figures are typed into the accounting system, so the business keeps two records of one expense.
The claim moves. Your ledger does not.
Horulabs builds the front door and the route around the systems you already use. It does not replace your accounting or ERP system, and it does not ask finance to approve in two places.
Stays in your systems
Your accounting or ERP system
The approved amount is posted to the system finance closes the books in. Suppliers, tax, and payments stay there.
Your approval order
Who signs, in what order, and for which area is your rule. Each claim keeps the route it was opened under.
Your archive
The claim, its attachments, and every action stay in one searchable record. The accounting entry remains the financial record.
Built around it
One register
Every internal claim, whatever its kind, in one list with the fields and route its kind needs.
A visible stage
The opener and the approver both see where a claim is waiting, and who has it.
The post and the close
Finance completes the amount and posting details; the payment closes the claim when the system reports it.
Seven claim types, one record.
EKLAIM replaced a paper trail at Sekar Laut: claims raised at sites, approved in role order across sites, and posted to Oracle Fusion as AP invoices. The case file covers the flow and what it replaced.
Start with one claim or document type.
The first task is one flow end to end: the form, the approval order, and the record finance works from. Other claim types follow once the first one runs.
- We map one claim type as it runs, including the exceptions handled outside the form.
- The flow is tested on real claims before it goes live.
- The handover covers the form, the approvers, and the record.
A short description is enough. No employee records or attachments.
The first conversation is free, with no commitment.
Questions before you start
- Do we need a documented process?
- No. The approval order is usually real even when it is not written down. We map it with the people who carry it.
- Does this replace our accounting system?
- No. Approved claims post into the system finance already uses. The claim records the request; the ledger records the money.
- What about employee and claim data?
- Tell us the flow in a short description first. Please do not send employee records, receipts, or attachments in the first message.