Tax Register

Tax Register defines a Starter-stage Protect workflow for taxes collected, taxes paid, withholding and filing deadlines. Keep period boundaries, supplied amounts and filing status in the register while the accountant or filing tool performs arithmetic. The workflow opens a period, records source data, enters confirmed amounts, files through the responsible person or system and reconciles. Filing and payment references, preparation and review ownership and status create a record of the process. Net Tax Payable and Days to Due are supplied values, not a promise of built-in calculations.

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 tax register, GST tracker, VAT record or filing calendar where confirmed figures and filing progress need a consistent structure. It does not calculate tax, file returns or give tax advice. Tax-type choices are a starting vocabulary, not a determination of the business’s obligations.

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 registered taxes, periods and entities; invoice-data availability, location and missing receipts; filing owner, internal versus external responsibility and recurring deadlines; current tracking and omissions; and whether a register, data extract or both are requested. 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 Tax Record (text); Tax Type (select); Tax Period (text); Period Start (date); Period End (date); Tax Collected on Sales (currency); Tax Paid on Purchases (currency); Withholding Tax Deducted (currency); Withholding Tax Paid to Us (currency); Net Tax Payable (currency); Currency (text); Filing Due Date (date); Filed Date (date); Payment Date (date); Filing Reference (text); Prepared By (text); Reviewed By (text); Days to Due (number); Status (select); Notes (long_text); Tax ID (id).

Tax Type starts with GST, VAT, TDS, TCS, Service Tax, Income Tax, Withholding. Status starts with Draft, Filed, Paid, Overdue, Amended.

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_tax_register_status ON tax_register (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.