Aksha
Aksha
Business Software

Documentation

Expense Categories

Expense Categories turn business-language choices such as Travel, Hamali or Repairs into governed accounting, tax, receipt and payment defaults.

Finance administratorsExpense administratorsImplementation teams
Last updated: 01-09-2026

Purpose

Expense Categories are the foundation of day-to-day expense entry. A category gives users a business-friendly choice while Finance controls the default expense account, tax treatment, receipt expectations and which payment responsibilities are allowed.

Open Expense Management -> Setup -> Expense Categories (menu wording can vary by role/menu configuration), then use Create or open an existing category.

Save, Apply and Close

Save validates and saves the category, then returns to the list.

Actions -> Apply saves the same category but keeps the record open so you can continue working or verify the result.

Close leaves the workspace without performing a new save.

Quick Reference

Core fields

FieldRequirementBusiness meaning
OrganizationHard-save mandatory; locked after creationOwns the category and its downstream availability.
Category CodeHard-save mandatory; locked after creationStable code used to identify the category.
Category TypeHard-save mandatoryControls special behavior such as General, Mileage or Per Diem.
Category NameHard-save mandatoryUser-facing business label.
Parent CategoryOptionalBuilds a reporting/administrative hierarchy.
DescriptionOptionalExplains intended use.
Default Expense AccountOperationally important / accounting-dependentSeeds expense accounting where the transaction supports category defaulting.
Input Tax EligibleOptional controlIndicates whether recoverable input tax may apply.
Recoverable %ConditionalPercentage eligible for recovery; must be 0–100.
Receipt RequiredOptional controlMarks receipts as expected by category.
Receipt ThresholdConditionalThreshold amount for the receipt rule; cannot be negative.
Effective From / ToOptional validity controlLimits when the category should be used.
ActiveOperational controlInactive categories should not be selected for new transactions.

Payment and use eligibility

Eligibility flags

ControlMeaning
Allow Employee PaidCategory can be used for employee-paid claims.
Allow Company PaidCategory can be used for company-paid expenses.
Allow Petty CashCategory is eligible for Petty Cash use.
Allow Corporate CardCategory can be marked eligible for company-card scenarios.
Allow Advance SettlementCategory can be used when settling a Cash Advance.
Allow Project ChargebackCategory permits project chargeback context where used.
Allow Customer ChargebackCategory permits customer chargeback context where used.
Allow CapitalizationCategory can be designated as capitalization-eligible where the downstream accounting process uses it.

Category Types

GENERAL is the normal category type for ordinary expenses.

MILEAGE makes My Expenses use the Mileage Details tab and configured Mileage Rate calculation.

PER_DIEM makes My Expenses use the Per Diem Details tab and configured Per Diem Rate calculation.

Other values can exist only when they are configured and supported by the current implementation; do not create business meaning from a label alone.

Accounting and tax defaults

Default Expense Account is a controlled default, not permission to ignore the Accounting & Dimensions tab. The final posting uses the transaction's saved accounting data.

Tax defaults can seed the transaction's tax context. Recoverable and non-recoverable amounts are separated at posting where applicable.

Default TDS/withholding context can be retained for Direct Expenses when withholding is applicable.

  • Organization, Category Code, Category Name and Category Type are required.
  • Recoverable tax percentage must be between 0 and 100.
  • Receipt threshold cannot be negative.
  • Effective To cannot be earlier than Effective From.
  • At least Employee Paid or Company Paid must be allowed.
  • Changing Organization/Code is protected after creation.

Good practice

  • Use one stable business meaning per category; do not reuse a category later for a materially different cost.
  • Prefer deactivation/effective dating over rewriting historical meaning.
  • Review categories before a mass rollout to branches so operators see a short, understandable list.
  • Use Expense Policies for timing/amount/receipt compliance instead of encoding every rule into the category itself.

Related pages

Frequently asked questions

Should users select a GL account for every expense?

Not necessarily. A category can seed the default account, while Finance can review/adjust accounting distributions where permitted.

Can I use one category for both employee and company-paid expenses?

Yes when both eligibility flags are enabled and the business meaning is the same.

How should I stop using an old category?

Prefer deactivation/effective dating so historical transactions retain their original category.

Continue reading