Find by challenge

Start from the problem you have.

Eight problems Japanese back offices and IT teams know well, each with what Kurahi does about it and who keeps the decision. Everything listed is in Kurahi 2.5.0 today.

  1. 01

    Internal approval requests stall on paper and in email

    Requests circulate by mail or on paper, and nobody can see whose approval is pending.

    What Kurahi does

    • Files each request as a case in the department's work queue, with its source and approval history
    • Staged approval route for spending: department manager, finance review from JPY 100,000, director approval from JPY 1,000,000, with delegation and escalation after 72 hours
    • Asks for a fresh authentication before an approval and records when and how the person signed in (2.5.0)

    Who decides: The approvers on the route

  2. 02

    Checking invoices and expense claims takes too long

    Qualified-invoice items, amounts and tax are checked by hand, one document at a time.

    What Kurahi does

    • Checks vendor, invoice number, registration number (T + 13 digits), amount and tax against the purchase order and the qualified-invoice items
    • Matches expense claims to receipts and checks calculation and rounding
    • Flags suspected payment fraud and holds payment when bank details change; Kurahi makes no payments

    Who decides: Accounting staff and approvers; payments are always made by people

  3. 03

    Competitive quotes and purchase orders take hours

    Collecting quotations, comparing them and writing the order is slow and hard to evidence.

    What Kurahi does

    • Checks purchase requests and whether the required competitive quotes are there
    • Compares supplier quotations like for like
    • Drafts the purchase order in Word and Excel once a person has chosen the supplier; never orders before approval

    Who decides: A person chooses the supplier and places the order

  4. 04

    Shared inboxes and request mail pile up

    Just routing inquiries and requests to the right team takes someone's whole morning.

    What Kurahi does

    • Files each new email as a case in the right department's queue
    • Prepares a polite reply draft in Outlook for clean routine mail
    • Sends suspicious mail (look-alike domains, bank-account changes, credential requests) to a person, with no draft

    Who decides: A person always sends the reply

  5. 05

    Keeping overtime within the legal limits (the 2024 problem)

    Overtime that will exceed the limits of the Article 36 overtime agreement (Japan's Labour Standards Act) is noticed only at the end of the month.

    What Kurahi does

    • Compares actual hours, the month-end forecast and the applicable limit (default 45 h/month, 360 h/year, special clause of the Article 36 overtime agreement)
    • Forecast above 36 h warns, above 45 h needs a second approver and HR review, above 80 h cannot be approved in the queue
    • Prepares an approver note with actual, forecast, limit and status, and the reasons

    Who decides: The manager and HR; Kurahi makes no decisions about people

  6. 06

    Legacy systems have become a black box

    Fewer people understand the COBOL or PL/I, and nobody can say what a change will affect.

    What Kurahi does

    • Analyses COBOL and JCL, PL/I, FORTRAN, Java, SQL and PLC code with deterministic analysers
    • Writes a design document in Word in which every fact cites path:line; what the code cannot tell is marked [to confirm]
    • Compares the code with a stored baseline every night and prepares the changes for review

    Who decides: The lead engineer and the reviewers

  7. 07

    Security reviews and audits ask how AI is controlled

    Customers' security checklists and internal audits want evidence of what the agents did.

    What Kurahi does

    • A security questionnaire of about 60 questions (English and Japanese), each answer citing its source, and the security overview
    • Signed evidence for every job, verifiable offline, and a hash-chained audit log
    • A signed AI inventory of every agent with its models, tools and policy rules

    Who decides: Your information security and audit teams

  8. 08

    Ransomware and malware on shares and attachments

    Shared folders and mail attachments are the way in, and findings need to be handled and recorded.

    What Kurahi does

    • Decoy files and mass-encryption detection stop every agent; on the company shares you list, a trip also opens a security incident case
    • Nightly scans of the shares (ClamAV, Microsoft Defender, YARA) and quarantine and scanning of mail attachments
    • Nightly checks such as a backup test restore; every finding becomes an incident case. It complements your EDR; it does not replace it

    Who decides: IT security decides what to do; Kurahi never deletes files

Four steps, at your pace.

Start wherever suits you. Starting free needs no sales contact.

  1. Download materialsProduct, security and editions overviews as PDF.
  2. Contact & demoA workflow demonstrated on a process like yours.
  3. Get a quoteEnterprise and the first workflow activation, fixed in writing.
  4. Start freeDownload and evaluate on your own. No sales contact needed.

Digital staff at L2 and L3, the data governance suite, air-gapped deployment and SLA support are by written agreement.