Finance playbook · AI Employee: Fin

New Cost Center & GL Setup

Cost centre live in one day

Install this playbookBack to marketplace
The problem

New cost centers and GL accounts are administrative bottleneck. New team forms, business unit launches, project starts requiring separate tracking — each needs a cost-center code, GL mapping, budget owner assignment, approval chain configuration, downstream propagation to expense tools, procurement systems, HRIS. Finance operations spends hours on each; requests wait days; new teams operate against generic codes until setup completes, corrupting reporting.

At a glance
Trigger
Form
Approvals
Controller approval
What it does
Writes to your systems
Systems
NetSuite
How it feels in production

An hour-by-hour walkthrough.

COO messages Fin: "Setting up a new product team for Project Titan, need cost center + GL codes." Fin drafts the setup packet: - Cost center code: CC-TITAN (following naming convention) - Parent hierarchy: Product → Titan - Budget owner: VP Product (Sarah) - Approval chain: standard product tier (manager → VP → CFO by threshold) - GL account mapping: standard R&D expense mapping (salaries, tools, travel, cloud) - Downstream systems to update: NetSuite, Concur, Coupa, Ramp, HRIS, budgeting tool - Employees to assign: from Sarah's team list (12 people) - Effective date: 2026-10-01 (start of new fiscal month for clean reporting) COO reviews + approves. Fin executes across every system: - NetSuite: create cost center + GL mappings - HRIS: reassign 12 employees to CC-TITAN effective 2026-10-01 - Concur / Coupa / Ramp: create cost center + approval chain - Budgeting tool: create tracked entity + initialize budget Reports next fiscal month automatically include CC-TITAN as separate reporting entity. No manual reclassification; no reporting gaps.
How it works

Step by step.

  1. 01

    Intake cost center request with business context

    Request specifies: purpose, parent hierarchy, owner, expected budget, timing. Fin drafts the setup packet.

    Slack · Web form · Cost center naming convention
  2. 02

    Draft configuration across every system

    Cost center code, GL mappings, approval chain, employee assignments, downstream system updates. Complete config drafted.

    NetSuite · SAP · Chart of accounts
  3. 03

    Approval by CFO / controller

    New cost center approved per policy. Ensures naming consistency + reporting clarity + budget allocation.

    Approval flow · Web UI
  4. 04

    Execute atomically across every system

    NetSuite + HRIS + Concur + Coupa + Ramp + budgeting tool all updated simultaneously. Reports include from effective date.

    Financial systems · Expense platforms · Budgeting tools · HRIS
  5. 05

    Verify + notify + audit

    Verification of each write. Owner + team notified of code activation. Audit trail for compliance.

    Audit log · Slack notification
Systems and wiring

What you connect to make this run.

NetSuite · SAP · Sage · QuickBooks

read+write

Chart of accounts + cost center hierarchy + GL mapping. Master financial structure.

Concur · Coupa · Ramp · Airbase

read+write

Expense + procurement systems. Cost center + approval chain configuration for spend routing.

HRIS · Workday · BambooHR

read+write

Employee cost center assignment. Effective-dated for clean payroll allocation.

Budgeting tool (Anaplan · Adaptive · Cube)

read+write

Budget entity creation + initial allocation. Tracking from effective date.

What changes

Before and after, honestly.

Time from request to cost center live
Before
3-10 business days
After
Same day (routine)
Finance hours per new cost center
Before
2-6 hours
After
10-20 minutes
Reporting gaps from delayed setup
Before
10-30% of periods post-launch
After
Zero
Systems out of sync post-setup
Before
20-40%
After
Under 2%
Related

Playbooks that pair with this one.

Finance

Vendor Intake & Onboarding

Cost center required for vendor spend allocation.

HR

Role & Manager Changes

Team formation may trigger new cost centers and role changes together.

Finance

Month-End Close Coordination

New cost centers included in month-end close from effective date.

Frequently asked

Answers about this playbook.

What about temporary cost centers (project-based)?

Project cost centers with sunset date. Auto-inactivation at project end; reporting continues for historical periods.

How does it handle cost center hierarchy changes (reorgs)?

Hierarchy restructuring per approval. Historical reporting preserved; new hierarchy from effective date.

What about intercompany cost centers?

Multi-entity cost centers with clear intercompany allocation rules. Charge-back mechanics configured at setup.

How does it interact with the budgeting cycle?

New cost center inherits budget allocation methodology; specific budget set by finance leadership + owner.

Can we retire unused cost centers?

Yes — inactive cost centers detected by absence of activity. Retirement workflow with reallocation of any remaining activity.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Finance playbooks