Budget by packages

Type in the planned value for each category in each month. The system compares it with the actual (accrual-based entries, the same basis as the DRE) and shows a deviation traffic light per month.

It generates the budget deviation alert and ties in with the DRE (same actuals basis). The package organization comes from the Category structure screen.

The Recalculate button redoes the consolidation of the packages (the tree of natures) from the grid rows — use it after editing several months, applying an assumption or copying actuals, so the package totals match the rows that make them up again. It recalculates the displayed totals; what is saved, and when, follows the rule described in the "What is saved" item of this same help.

One of the three ways to start the budget: the button brings the year's actuals, category by category and month by month, into the grid as the starting point for the budgeted figures. From there you adjust what changes in the new year — and you can apply an adjustment assumption on top of the copied base (the IPCA that the system already fetches from BACEN shows up as a suggestion). It's the fastest way to budget a year similar to the previous one without typing the whole grid.

The "Center only" column shows what was budgeted in that center; "With children" shows the total including all descendants in the result center tree — and only appears when the center has children. You budget at the leaves and read at the top, without adding anything by hand.

The platform collects IPCA, Selic and exchange rates from the Central Bank's public series. In "Apply assumption" those numbers RECALCULATE the grid — adjusting what is already there, or starting from the previous year's actuals. Each recalculated row keeps a record of what was applied (the % next to the name), and a later manual adjustment clears the mark, because the row no longer belongs to the assumption.

"Compare versions" shows what changed from a version in the history to the current one, nature by nature, biggest change first — identical rows are left out. And the "Spreadsheet template" downloads the grid with the nature's CODE in the first column: it is the same format the import reads back, and the code survives renaming the nature (the name does not).

Type the planned amount directly in the month's cell, on the account's row. The packages (rows in bold) are sums and cannot be typed — they change when the rows inside them change. After editing, use Save: up to this version the grid refused manual editing and crashed the screen on any click.

The grid groups by the tree: PACKAGES (synthetic groups, e.g., IT, People and Management) show automatic subtotals and are not editable; you plan on the LEAVES (analytic categories). Build the hierarchy in "Category structure". The "Recalculate packages" button updates the subtotals without saving.

Green under 5% deviation, yellow under 15%, red from 15% up (based on the size of the deviation between budgeted and actual).

Only the leaves (analytic categories) are persisted; packages are calculated sums. Empty cells are not saved. The actuals come from the accrual data.

In the "Centers and owners" panel, click Build cycle centers: every ACTIVE result center starts to take part in the budget. Set the owner of each one — that person fills in their part and clicks Submit. The cycle closes when all centers are approved, and the scoreboard at the top shows how much is left. Anyone who prefers to budget centrally does not need to do anything: with no centers built, the grid stays company-wide, as it always has been.

Submission uses the platform's approval engine (event "Center budget"). If the company has an authority policy for that event, the center stays SUBMITTED until the approver decides — approving closes it, returning sends it back to the owner WITH the reason (which is mandatory: sending back without saying what to fix helps nobody). If the company has NO authority configured, submitting approves directly, and the message says so — a flow that stalls waiting for an approver who does not exist would be worse than no ritual at all.

From scratch (typing), COPYING the year's actuals, or PROPOSING from history — which fills each nature with the MEDIAN of the last twelve periods. Median and not average on purpose: a single month with an unusual purchase would inflate the next twelve months. A nature with no history stays blank, never zero: "I have no basis" is information.

Instead of typing the payroll amount, plan the HEADCOUNT: role, center, salary, charges and how many people each month. The system calculates the cost (salary × people × charges, plus the monthly provision for 13th salary and vacation) and generates the payroll lines of the budget. What you edit is the headcount: the generated lines stay out of the grid and regenerating replaces only them — what you typed by hand is never touched.

Each slice of the budget can have an owner and a date. The screen shows how many are late (deadline passed and not yet delivered) and how many have no owner — the two classic holes in a budget cycle. The authority decision comes back here by itself: approved, the slice locks; returned, it goes back to the owner with the written reason.

Não sumiram: o pacote é uma árvore de naturezas e o total dele é recalculado a partir das naturezas. Use Recalcular pacotes depois de mexer na árvore. Os valores digitados por natureza e mês ficam; o que muda é a soma do pacote.