Guide / process architecture

Level-one processes in a business management system

Process architecture sorts a business into levels: level one is the handful of end-to-end processes the company exists to run. For a stock-carrying business that is six — and every system you buy should map onto them.

The key facts

  • The convention: level one is the short list of end-to-end processes; level two decomposes each; level three is the tasks and transactions.
  • Level one for a stock business: plan, buy, make or store, sell, deliver, invoice — six, not sixty.
  • The test of a good level-one list: each process has a clear start, a clear end, and one owner.
  • BSimple's mapping: the record runs buy → store → sell → deliver → invoice end to end; planning stays human, fed by reporting.
Diagram — index of this pageThe ground this page covers
  1. 01The key facts
  2. 02The convention, briefly
  3. 03Level one for a stock-carrying business: the six

The convention, briefly

Process architecture — the discipline behind frameworks like APQC's — sorts a business into levels. Level one is the value-chain view: the small number of end-to-end processes that describe what the company does, without organisational detail. Level two breaks each into sub-processes (purchasing splits into requisition, ordering, receipt, reconciliation). Level three is tasks and transactions, where software actually executes. The convention exists because organisations that skip it buy systems that mirror their org chart instead of their value chain — and org charts change.

The level-one test: each process has a clear start and end, and one accountable owner. "Operations" is not a level-one process; "buy: from demand signal to goods received" is.

Genuine BSimple screenThe BSimple reorder screen working against live stock levels.
The BSimple reorder screen working against live stock levels.

Level one for a stock-carrying business: the six

Plan — what will be needed, in what quantity, when: forecasting, budgeting, setting reorder levels. Buy — from demand signal to goods received: purchase orders, supplier reconciliation, receipt into stores. Make or store — production runs where you manufacture; locations, batches and stocktakes where you hold. Sell — capture to commitment: channels, pricing, validation against live stock. Deliver — pick, pack, dispatch, with the record matching the dock. Invoice — the approved handoff to the books, and the mirroring of payment status back.

Notice what the list excludes: HR, IT support, facilities — real functions, but support processes rather than the value chain. Notice also what the list demands of software: the systems you buy should map onto these six, not carve them up by department. We build BSimple, so weigh that: it runs four of the six end to end on one record — buy, store (and make, with recipes and production runs), sell and deliver, invoice — with planning supported by reporting dashboards and reorder automation rather than replaced. From $180/month AUD; the system diagram shows the mapping visually, what a business management system includes the components, and the trial runs your own level-one processes in an afternoon.

DiagramDiagram: spreadsheet data imported into live stock records.
Diagram: spreadsheet data imported into live stock records.

Frequently Asked Questions

What are level-one processes?

The short list of end-to-end processes that describe what a company does — each with a clear start, a clear end and one owner. For a stock business: plan, buy, make or store, sell, deliver, invoice.

How do level two and three differ?

Level two decomposes each level-one process into sub-processes (purchasing into requisition, order, receipt, reconciliation); level three is the tasks and transactions where systems execute. Detail increases; accountability stays anchored at level one.

Which level-one processes does BSimple run?

Buy, store or make, sell, deliver and invoice — end to end on one record. Planning stays human, fed by the reporting and reorder automation the record provides. HR, payroll and MRP scheduling are outside it, stated plainly.

Why should software map to level-one processes?

Because systems that mirror the org chart break at every reorganisation, and systems that carve the value chain by department create the reconciliation seams. Map to the six, and the record stays whole.

How do we check our own level-one list?

Write the six, test each for start, end and owner, then run the trial and see which processes the record already carries — the gaps you find are the honest requirement list.

DiagramOrderPick and packInvoiceXero
Diagram: Order → Pick and pack → Invoice → Xero — how this work moves through BSimple.

BSimple

Get started with BSimple