Skip to main content
An operation is the kind of transaction you are recording: a sales invoice, a payment voucher, a warehouse receipt, a transfer. Every document you record in Fail Fast comes from an operation, and the operation decides how it is numbered, whether it posts to accounting, and whether it needs authorization.

Where to find it

The Operation screen sits in the configuration of the app the operation belongs to. Each module — purchasing, sales, treasury, inventory, transport — has its own operations.

The operation form

The first tab, Operation Form, defines the operation itself.

Consecutive type

  • Manual — you type the number on each document.
  • Perpetual — numbering runs without ever resetting.
  • Yearly — numbering starts over each year.
With yearly numbering, the Consecutive Operation tab lets you see and adjust the Consecutive for each Year.

Summarize accounting

Affects accounting decides whether there is a movement; Summarize accounting decides how it looks. Summarized groups the document into a few lines; detailed keeps one line per document line. On high-volume documents, summarizing is the difference between a readable movement and one with hundreds of lines.

Operation accounts

The Operation Account tab defines which accounts the movement generated by the operation posts to. Each row combines:
  • Form and Operation — which document the rule applies to.
  • Account and Account nature — the account affected and whether it posts as a debit or a credit.
  • Stakeholder, Cost center and Business unit — the dimensions it is recorded under, when the account requires them.
  • Mode of affectation and Value percentage — whether the line takes a percentage of the document or a fixed value.
  • Weight adjustment — for operations settled by weight.
  • Allow edit — whether whoever records the document can change the proposed account.

Multibook

If your workspace uses multi-book accounting, the operation shows a Multibook section with a single field: Excluded books. There you pick the secondary books this operation must not reach. The field only offers active books that are not the main one, because an operation always reaches the main book.
What you configure here is applied when the document is recorded and is stored with the movement. If you later change the operation’s excluded books, movements that are already complete do not change: they keep the configuration they had when they were recorded. Only provisional movements and movements in error recalculate it while they stay in that state.
This is deliberate: accounting history is not rewritten because someone adjusts a setting months later. If your workspace does not use multi-book, the section does not appear and every operation reaches the single book there is.