Salary & Wage Accounting

Salary & Wage Accounting defines a Growth-stage Expense & Payroll register for approved payroll figures. Use one record per employee per pay run so attendance, paid days, gross amount, deductions and net amount remain traceable to the person. Payroll software handles arithmetic. The workflow records attendance, prepared wage sheet, approval, payment, carried liability and statutory reconciliation. A named reviewer signs the run before release. Retain contributions as liabilities until the actual deposit, then reconcile against the deposit challan rather than merely the payroll sheet. The empty structure holds what qualified staff decided, paid, deducted and still owe.

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 salary books, wage-sheet records and payroll liability trackers that need a per-person reconciliation trail. It does not calculate payroll, TDS or PF, make payments or deposits, file statutory returns or provide payroll or tax advice. Real salary and employee data belong in the payroll system, not the generated template.

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.

Establish employee count, salaried versus hourly workforce and attendance source; run cutoff, wage-sheet preparer and payment approver; TDS, SSF/PF or equivalent and advance recoveries; deposit and filing owner, reconciliation cadence and outstanding liabilities; and whether a payroll record, liability tracker or both are needed. 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 Run (text); Employee (text); Employee ID (text); Department (select); Period Start (date); Period End (date); Attendance Days (number); Paid Days (number); Gross Salary/Wages (currency); Allowances (currency); Deductions (currency); TDS (currency); SSF/PF Contribution (currency); Other Deductions (currency); Net Salary/Wages (currency); Payment Date (date); Payment Mode (select); Ledger Account (text); Approval Reference (text); Payroll Liability Balance (currency); Statutory Reconciliation Status (select); Source Document (relation); Prepared By (text); Reviewed By (text); Status (select); Notes (long_text); Salary Record ID (id).

Department starts with Sales, Purchase, Accounts, Payroll, Admin, Finance, Operations. Payment Mode starts with Bank Transfer, Cash, Cheque, Digital Payment. Statutory Reconciliation Status starts with Reconciled, Pending, Variance. Status starts with Not started, In progress, Blocked, Done, Cancelled.

Never fill templates with real names, salaries, bank details, identifiers or health information. Synthetic examples use masked account numbers. A run-level total cannot explain an individual deduction variance. Related workflows are expense-accounting for expense entries, payment-accounting for settling net pay, tds-booking-payment for statutory TDS, and source-document-filing for signed sheets and deposit challans. accounting-audit-system-builder routes among these modules.

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_salary_wage_accounting_status ON salary_wage_accounting (status);

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. Personal identifiers and sensitive financial details stay out of generated templates.