Invoices & Billing

Plan an invoice register with amounts, due dates, payment status and aging. The skill records invoices based on billable time or fixed fees. It leaves the actual invoice document to the accounting package and builds empty templates on request.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an invoice tracker, billing spreadsheet, invoice register or accounts receivable aging. Clarify monthly, milestone or hourly billing, payment terms, retainers, late fees and who follows up.

It does not raise invoices, send them or collect money. The minimum process is a client, amount, due date and status per invoice so someone can follow up. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow is work recorded, invoice raised, status tracked, chased, then paid or overdue. The 26 fields cover invoice number, client, project, issue and due dates, payment terms, currency and Time Entries. Financial fields include subtotal, discount, tax rate and amount, withholding tax, total, Amount Paid and Balance. Payments is a second relation field; Days Overdue and Aging support the record. Payment Status, Status, Sent Date, Prepared By, Approved By, Notes and Invoice ID complete it. Time Entries and Payments link to their corresponding databases. Payment statuses include Draft, Sent, Part Paid, Paid, Overdue and Cancelled; invoice status also allows Issued and Void.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_invoices_billing_status ON invoices_billing (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.