Skip to content
Arthiva
Products

Arthiva Supply Chain

Run operations
on one record.

Overview
PurchasingBudget to invoice, one connected record. InventoryStock you can audit. Vendor managementEvery supplier on the record. Logistics & returnsShipments, returns, and replacements on one lifecycle. ProductionFrom BOM to build. Coming soon.
Recovery

Arthiva Recovery

Recover value
from your records.

Sales & use taxOverpaid tax, found and recovered. Section 48E incentivesSection 48E clean energy credits. Tariffs & dutiesTariff and duty recovery reviews.
Maya AI
Resources

Arthiva Resources

News from the team.
Read the latest.

NewsProduct updates and announcements. SupportAdmin guides for the platform.
Book a demo

Budgets

Cost centres and budget periods

← All documentation

In this article

  1. Overview
  2. Cost centres
  3. Budget periods

Overview

Two pieces of master data underpin budgeting, both in Settings → Module settings → Purchasing: cost centres (who owns spend) and budget periods (the fiscal windows spend is authorised in). Viewing budgets needs the "View budgets" permission; changing anything here needs "Manage budgets".

Cost centres

A cost centre is the internal owner of a budget, a team or project. Every requisition names exactly one; purchase orders deliberately carry none. Click Add cost centre and set:

  • Code and Name: e.g. CC-100, Engineering.
  • Budgets in: the currency this centre's budgets are denominated in. It locks once the centre holds budget, because every ledger entry is denominated in it.
  • Owner: a real person. The owner matters beyond labeling: approval workflows can route a step to the cost centre owner of whatever requisition is being approved.

Cost centres are never deleted, only deactivated, history stays whole. Requisitions can't be raised until at least one active cost centre exists.

Budget periods

Periods are org-wide, so "FY26-Q1" means one thing across the company. Click Add period and give it a code, name, and start/end dates.

  • A requisition finds its budget through the open period covering its need-by date, so open periods may not overlap: the app refuses an overlap and names the colliding period.
  • Closing a period stops new allocations and reservations but never touches money already committed, open orders don't disappear at rollover. See The budget ledger, period close, and rules.

Related guides

BudgetsSetting and reading budgets→ BudgetsThe budget ledger, period close, and rules→ Single sign-onSetting up SAML single sign-on→

Products

PurchasingInventoryVendor managementLogistics & returnsProductionMaya AI

Recovery

Sales & use tax48E clean energy incentivesTariffs & duties

Resources

NewsSupportContact

Legal

PrivacyTerms
Copyright © Arthiva, Inc. 2026. All Rights Reserved.