Payroll Finance

Payroll & Finance

What it is: Compensation.

Overview

Works out the smallest useful Payroll & Finance setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 4: Manage. Fits: Starter stage. Table code: n/a.

When to Use This Skill

• payroll tracker
• salary register
• payroll sheet template
• monthly payroll log

Also use it when the user says "compensation", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How many people are on payroll?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

• Payroll - How many people? / Monthly payslip? / Variable pay?
• Components - Which allowances? / Deductions? / Bonus included?
• Process - Who runs it? / Accountant or in-house? / When is cut-off?
• Current process - How is payroll done now? / Software or manual? / What gets missed?
• Outcome - What do you need? / A register, a calculation or an input feed?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

module: payroll-finance
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Payroll": null
  "Components": null
  "Process": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Treat payroll as an input record for finance, not a calculator. If you need calculation, use payroll software and record the result.

Why this one: Payroll is high-risk to compute by hand and cheap to record. Keep this as the register, and let software do the arithmetic.

Workflow: Payroll input → Validation → Payroll run → Register update → Finance and tax

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

Payroll Record,Basic Salary,Bonus,Currency,DA (Dearness Allowance),Deductions,Department,Employee Name,HRA,Month,Net Pay,Notes,Pay Period,Payment Date,Payment Method,Payroll ID,Status,TA (Travel Allowance),Year
PAY-2026-03,650000.00,97500.00,INR,14500.00,82500.00,Delivery,Aarav Sharma,260000.00,2026-03,958700.00,February run reconciled with the accountant; one deduction code was mapped to the wrong head.,2026-03,2026-04-07,Bank Transfer,,Paid,19200.00,2026

CREATE TABLE payroll_finance (
  payroll_record VARCHAR(255),
  basic_salary NUMERIC(14,2) NOT NULL,
  bonus NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  da_dearness_allowance VARCHAR(255),
  deductions NUMERIC(14,2) NOT NULL,
  department VARCHAR(255),
  employee_name VARCHAR(255),
  hra NUMERIC(14,2) NOT NULL,
  month VARCHAR(255),
  net_pay NUMERIC(14,2) NOT NULL,
  notes TEXT,
  pay_period VARCHAR(255),
  payment_date DATE NOT NULL,
  payment_method VARCHAR(100) NOT NULL,
  payroll_id SERIAL PRIMARY KEY,
  status VARCHAR(100) NOT NULL,
  ta_travel_allowance NUMERIC(14,2) NOT NULL,
  year VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_payroll_finance_status ON payroll_finance (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Payroll & Finance",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Payroll Record": { "type": "string" },
      "Basic Salary": { "type": "number" },
      "Bonus": { "type": "number" },
      "Currency": { "type": "string" },
      "DA (Dearness Allowance)": { "type": "string" },
      "Deductions": { "type": "number" },
      "Department": { "type": "string" },
      "Employee Name": { "type": "string" },
      "HRA": { "type": "number" },
      "Month": { "type": "string" },
      "Net Pay": { "type": "number" },
      "Notes": { "type": "string" },
      "Pay Period": { "type": "string" },
      "Payment Date": { "type": "string", "format": "date" },
      "Payment Method": { "type": "string" },
      "Payroll ID": { "type": "integer" },
      "Status": { "type": "string" },
      "TA (Travel Allowance)": { "type": "number" },
      "Year": { "type": "string" }
  },
  "required": [
      "Basic Salary",
      "Bonus",
      "Deductions",
      "HRA",
      "Net Pay",
      "Payment Date",
      "Payment Method",
      "Status",
      "TA (Travel Allowance)"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Payroll Record | Title | Use as the database title |
| Basic Salary | Number (format: currency) | Convert to Number, set format to Currency |
| Bonus | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| DA (Dearness Allowance) | Text | Leave as Text |
| Deductions | Number (format: currency) | Convert to Number, set format to Currency |
| Department | Text | Leave as Text |
| Employee Name | Text | Leave as Text |
| HRA | Number (format: currency) | Convert to Number, set format to Currency |
| Month | Text | Leave as Text |
| Net Pay | Number (format: currency) | Convert to Number, set format to Currency |
| Notes | Text | Leave as Text |
| Pay Period | Text | Leave as Text |
| Payment Date | Date | Convert to Date |
| Payment Method | Select (add options after import) | Convert to Select, add options: "Bank Transfer", "UPI", "Card", "Cash", "Cheque", "NEFT/RTGS" |
| Payroll ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "Submitted", "Approved", "Paid", "Reconciled" |
| TA (Travel Allowance) | Number (format: currency) | Convert to Number, set format to Currency |
| Year | Text | Leave as Text |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference