Use cases

The full process, step by step.

Each function is documented with the same Process Template we use in every Petakan report — then every step is moved up the Solution Ladder.

In-depth case study

An F&B chain with 100+ outlets.

Three functions that buckle first as a chain grows: finance & accounting, purchasing, and the store manager. Each is mapped with the same Process Template, then every step climbs the Solution Ladder.

Use case

Coffee & food chain · 120 outlets · 1 central kitchen · head office in Jakarta

Process Template — the same format in every Petakan report
Process→Trigger→Actors→Systems→Steps→Exceptions→Outcome measure

Daily close & sales reconciliation across 120 outlets

Trigger
Every outlet closes its evening shift; monthly close at month-end.
Actors
Cashiers, store managers, HQ finance (cash & AR), accountants.
Systems
POS, bank accounts, QRIS/EDC, GoFood · GrabFood · ShopeeFood, spreadsheets, accounting system.
Exceptions
Cash variances, refunds & cancellations, platform commission/promo deductions, late deposits.
  1. 01Close the shift at the outlet

    Cashier counts cash, photographs receipts, posts to a WhatsApp group.

    Standardise

    Standard shift-close form on POS/phone: cash count, every variance needs a reason, deposit photo.

  2. 02Daily outlet report to HQ

    Store manager rebuilds the numbers in Excel and sends them nightly.

    Remove

    Manual report removed — sales data comes straight from the POS.

  3. 03Match sales vs money received

    3–4 finance staff match POS vs bank vs QRIS vs delivery payouts in Excel, done by D+3.

    AutomateL4 approval

    Automatic reconciliation every morning per outlet per channel; matches are recorded straight away.

  4. 04Chase variances

    Finance phones outlets one by one about each variance.

    AI agentL2 approval

    AI agent classifies the cause (commission, promo, refund, cash) and drafts the question to the store manager on WhatsApp.

  5. 05Journal into accounting

    Hundreds of lines keyed in by hand every day.

    AutomateL2 approval

    Journal drafts generated from reconciliation; the accountant reviews and posts.

  6. 06Outlet P&L

    Monthly, ready by D+15 — too late for decisions.

    AutomateL3 approval

    Weekly per-outlet P&L generated automatically, plus an anomaly summary for management.

Mix of improvements
Remove · 1Standardise · 1Automate · 3AI agent · 1

Most improvements aren't AI. AI agents are used where a step needs to read free text, classify, or draft — always with approval.

Outcome measures
Monthly close
D+15→
D+5
Unexplained variance
Rp 180m/mo→
< Rp 20m/mo
Finance reconciliation hours
~480 h/mo→
~120 h/mo

In-depth case study

Accounts Payable: from a pile of invoices to on-time payment.

A process every business has — and one of the biggest drains on finance hours. Mapped with the same Process Template, in three stages.

Use case

Multi-entity distributor · 3 legal entities · 400+ active suppliers · ~3,000 invoices a month

Process Template — the same format in every Petakan report
Process→Trigger→Actors→Systems→Steps→Exceptions→Outcome measure

Invoice arrives → recorded in the system

Trigger
Supplier invoices arrive by email, WhatsApp, courier, or handed to sales reps.
Actors
AP admin, purchasing, warehouse, suppliers.
Systems
Email, WhatsApp, paper documents, spreadsheets, accounting system.
Exceptions
Duplicate invoices, wrong legal entity, missing tax invoice, no PO number.
  1. 01Receive invoices

    Scattered across personal inboxes, WhatsApp and paper piles.

    Simplify

    One email address and one WhatsApp number for invoices; paper is scanned at the front desk.

  2. 02Forward to AP admin

    Purchasing or sales forward them by hand, often late.

    Remove

    Forwarding step removed — every channel lands straight in the AP queue.

  3. 03Key in invoice data

    Admin types number, date, amount and VAT one by one.

    AI agentL2 approval

    AI agent reads PDF/photo invoices and tax invoices and fills a draft; the admin checks anything flagged as uncertain.

  4. 04Check duplicates & entity

    Relies on the admin's memory.

    AutomateL4 approval

    Automatic duplicate check (supplier + number + amount) and entity/tax-ID match.

  5. 05Document completeness

    Missing tax invoices or delivery notes surface only at payment time.

    Standardise

    Required-document checklist per supplier type; gaps become exceptions automatically.

Mix of improvements
Remove · 1Simplify · 1Standardise · 1Automate · 1AI agent · 1

Most improvements aren't AI. AI agents are used where a step needs to read free text, classify, or draft — always with approval.

Outcome measures
Invoices recorded ≤ 1 working day
~40%→
> 95%
Data entry time per invoice
~6 min→
< 1 min
Duplicate invoices paid
~4/mo→
0

Start with one process.

Two weeks, fixed price. The process map and recommendations are yours.

Map one process →