Clients & Accounts

Clients & Accounts works out a minimal register for client contacts, terms, ownership and amounts owed. Its recommended workflow is to record a client, assign an owner, log activity on that same record, set a next action and review. Keeping activity notes with the client avoids a separate log, while ownership helps prevent stale contact details.

The skill distinguishes advice, a review, a requested build and conversion of an existing process. Advice normally receives a short recommendation and an offer to build. It asks one missing question at a time about active clients, relationship owners, billing contacts, linked contracts, activity, current tools or the desired result. Previously answered questions are skipped; unknown facts remain unknown.

Money has an explicit basis. Tax Basis remains Not confirmed until the user confirms whether amounts are tax-inclusive or tax-exclusive. Currency, country, registration numbers and amount size do not establish that basis or a tax rate. Tax tracking fields are added only if requested. Outstanding is calculated rather than accepted as a typed value:

Outstanding = Total Invoiced - Total Paid

Round once at the end to two decimal places and reuse that result. Missing totals leave Outstanding empty. Credits, write-offs or part payments that explain a discrepancy belong in Notes; Total Paid must not be altered to force agreement.

Use it for a client database, customer records, a client account tracker or an accounts receivable list, including processes currently spread across inboxes. It fits the Starter stage of operations. A request to review an existing process receives a review rather than an unsolicited system build.

It does not calculate payroll or taxes, file returns, send invoices, contact clients or manage relationships. Templates remain empty unless synthetic examples are explicitly requested. Legal, tax and HR decisions still require the relevant human review. Sensitive material supplied for a review should be repeated only where needed.

Inputs are confirmed business context and requested formats. The shared field list covers client identity and type, industry, contact details, billing address, Tax ID, currency, tax basis, payment terms, account manager, project and invoice labels, invoiced and paid totals, outstanding balance, portal access, status, notes and Client ID. Client type and status choices are starting sets rather than mandatory business terminology.

Requested outputs can include CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Display names stay consistent across formats, SQL identifiers are documented, and money and number types remain appropriate. Excel-compatible CSV uses UTF-8 with a byte order mark and names the columns requiring formatting; a workbook is created only when requested.

Notion output is routed to notion-manual-import for mapping, import instructions and verification. Manual artifacts require no connection; workspace changes require verified access, the actual target and authorization. A mapping alone is not a completed workspace build.

Projects and Invoices deliberately remain comma-separated text labels, not relations to invented databases. Their separate owning tables remain the source of truth. The skill supplies no automation, reminders or synchronization.