Skip to content
Operating Packs

Build each process once. Fit it to every entity.

Start from a working process, not a blank canvas. Our team fits it to each entity, on the tools you already run. Customers see 45% fewer licenses and 96% fewer execution issues.

All Operating Packs

Month-end close

Cut-off, accruals, reconciliations and sign-off per entity, on one rail, with each control's evidence captured as it runs.

Run this Operating Pack in your trial

The rail

  1. 01Period startTrigger
  2. 02Cut-off and sub-ledgersERP jobs · APIBy WD1
  3. 03AccrualsAI agent proposesBy WD2
  4. 04ReconciliationsAI agent + APIBy WD2
  5. 05Entity sign-offApprovalWD3 12:00
  6. 06Group close and lockGroup sign-off, then lockBy WD5

What it replaces

Intercompany differences argued by email on WD3, and a group team that learns an entity is late when its package doesn't arrive.

What changes

Every entity closes on the same rail. The late one is visible on day one, not day five.

Works with

  • SAP S/4HANA
  • SAP ECC
  • Dynamics 365
  • BlackLine
  • SAP Group Reporting

The close calendar

Each stage has a window in the working-day calendar and a due time. Every entity runs its own case, and its package reaches group by WD3.

  • RPA
  • AI agent
  • People
  • Trigger or API
  • Close
  1. 01 Period start2 steps
    • WD−2 to WD−1Calendar opens
  2. 02 Cut-off and sub-ledgers5 steps · by WD1
    • WD−1 to WD1ERP jobs
  3. 03 Accruals5 steps · by WD2
    • WD1AI agent
    • WD2Sign-off
  4. 04 Reconciliations4 steps · by WD2
    • WD1 to WD2AI agent + API
  5. 05 Entity sign-off3 steps · WD3 12:00
    • WD3Package
  6. 06 Group close and lock4 steps · by WD5
    • WD3 to WD4Group review
    • WD5Locked

Inside each stage

Choose a stage to see who does each step and what it leaves on the case.

Reconciliations

WD1 to WD2 · by WD2
Steps
  1. APIAI agentBank reconciliations Bank files by API, the agent matches
  2. APIPeopleIntercompany agreed Matched by API, disputes owned by group and settled by WD2
  3. AI agentPeopleBalance sheet workpapers Agent prepares, a preparer signs, a reviewer approves
  4. PeopleDifferences routed To the entity controller, with an owner and a due date

Left on the case: a workpaper per account, signed by its preparer and its reviewer.

What your reviewers will ask

IT security, your auditor and the group controller each sign off before go-live. Their first questions, answered.

  • IT security

    Where does ledger data go?

    Nowhere. Optomo runs on-premise, in your network, so ledger data, documents and agent reasoning stay in it. Optomo is ISO 27001 certified.

  • Audit

    Can we rely on the evidence?

    Each control leaves its evidence on the case as it runs: job logs, document numbers and signed workpapers. Enterprise contracts give your auditor direct access to the controls Optomo runs.

  • Group controller

    Who can post and lock?

    Agent proposals wait as parked documents until a person signs. Posting and locking run under separate ERP users, and the period locks only after group sign-off.

Where your data lives

Where your processes differ, we close the gap with you

Inconsistent processes are normal. Our team and our partners map how each version runs and fit the Operating Pack to it.

Included in Enterprise. Our team fits the Operating Pack in the trial and the rollout, at no extra cost.

  1. Optomo team

    Fits the Operating Pack

    • A version per entity or country
    • Stages connected to your systems
    • Thresholds and approvers set as policy
  2. Partner

    Aligns the process

    • The process mapped as it runs today
    • Which differences to keep
    • The change led with the process owners

How an Operating Pack becomes your process

We connect it to your systems, then run real cases in the 5-week trial.

  1. 1

    Map the systems

    Each stage pointed at your systems.

  2. 2

    Set the policy

    Set once, inherited by every case.

  3. 3

    Run it in the trial

    Real cases, with a cost baseline by week 4.