Payroll & Finance

Payroll and Finance defines compensation records for finance. It recommends treating payroll as an input register rather than a calculator: dedicated payroll software performs the arithmetic, and the register stores its result. The proposed process runs from payroll input through validation and the payroll run, then updates the register for finance and tax work. It fits the Manage layer and Starter stage. This structure addresses a process where payroll runs in a spreadsheet and finance has to re-key the information.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it for a payroll tracker, salary register, payroll sheet template or monthly payroll log. It does not calculate pay, deduct tax, transfer money or compute leave balances and KPIs. Calculation belongs in payroll software; this skill records the result.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Intake covers the number of people, monthly payslips, variable pay, allowances, deductions and bonuses. It identifies who runs payroll, whether that work is in-house or with an accountant, the cut-off date, current software or manual process and what gets missed. The desired outcome can be a register, calculation request or input feed. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Payroll Record (text); Basic Salary (currency); Bonus (currency); Currency (text); DA (Dearness Allowance) (text); Deductions (currency); Department (text); Employee Name (text); HRA (currency); Month (text); Net Pay (currency); Notes (long_text); Pay Period (text); Payment Date (date); Payment Method (select); Payroll ID (id); Status (select); TA (Travel Allowance) (currency); Year (text).

Payment Method starts with Bank Transfer, UPI, Card, Cash, Cheque, NEFT/RTGS. Status starts with Draft, Submitted, Approved, Paid, Reconciled.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE INDEX idx_payroll_finance_status ON payroll_finance (status);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.