MosoFin

ar-aging-and-collections

Use the confirmed Mosofin workspace and its connected accounting datasource to pull live A/R, build and reconcile an aging, prioritize collections, calculate receivables metrics, and draft review-only reminders. Trigger for 'run an AR aging,' 'who owes us money,' 'prioritize collections,' 'calculate DSO,' or 'draft overdue-invoice reminders.' Workspace-scoped: require the Mosofin workspace and an active connection, discover which read-only tools are enabled, and resolve every task against that capability map before reading data. Do not use for cash application, bad-debt write-offs, invoice creation, or sending reminders.

bank-reconciliation

Use this skill whenever the user needs to reconcile a bank account (cash GL) to bank statements for a period, working from their Mosofin workspace. Triggers include: bank recon, reconcile bank, cash reconciliation, bank statement tie-out, unreconciled items, outstanding checks, deposits in transit, or investigating recon differences. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then builds the complete book side from live ledger data and prepares the bridge — while stating plainly that the bank statement is outside any accounting datasource and must be supplied before a reconciliation can actually be completed. Produces a recon output, variance explanations, a clean list of required journal entries or corrective actions, and a coverage sheet.

duplicate-invoice-detection

Use this skill whenever the user wants to detect duplicate or fraudulent invoices in AP from their Mosofin workspace. Triggers include: 'check for duplicate invoices', 'find duplicate payments', 'scan AP for duplicates', 'detect invoice fraud', 'have we paid this twice', uploading a payment history or AP register, or any AP control review focused on payment integrity. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then runs the detection rules directly against live bills, payments and the vendor master — nine of the ten rules are pure queries. The bank-account rule cannot run, because Mosofin deliberately does not expose vendor bank details. Do NOT use for general fraud detection across all transaction types — use fraud-detection-and-forensics. Outputs a duplicate-suspect list with confidence ratings, supporting evidence, and a coverage sheet.

expense-report-processor

Use this skill whenever the user wants to process, review, or post employee expense reports against their Mosofin workspace. Triggers include: uploading an expense report export (Concur, Expensify, Brex, SAP Concur, Pleo, Spendesk, Soldo, or any other T&E tool), pasting an expense report, 'review these expense claims', 'check this expense report against policy', 'code these employee expenses', 'post the expense report to the GL', or any reference to T&E (travel & entertainment) reimbursements. Also trigger for per-diem calculations, mileage reimbursements, and corporate card reconciliation tied to employee submissions. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then codes against the real chart of accounts, matches claims against transactions already posted, and checks the reimbursement and card-clearing balances. Do NOT use for vendor invoices — use invoice-data-extractor. Do NOT use for petty cash — use petty-cash-managemen

financial-statement-builder

Use this skill whenever the user wants to build a complete set of financial statements from their Mosofin workspace — Balance Sheet, Income Statement, and Statement of Cash Flows, with comparatives. Triggers include: 'build financial statements from this TB', 'produce a P&L and balance sheet', 'monthly financials package', 'GAAP financial statements', 'IFRS financial statements', 'investor financials', or uploading a trial balance and asking for statements. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then pulls the trial balance and the comparative period directly, reclassifies into framework presentation, and proves the seven cross-statement tie-outs on the statements it built. Do NOT use for just the cash flow statement — use cash-flow-statement-indirect-method. Do NOT use for footnotes — use notes-to-financial-statements. Outputs a complete statement package with comparatives, classifications, tie-outs, and a coverage sheet

gl-coding-assistant

Use this skill whenever the user wants to assign GL account codes, expense categories, or tax codes to transactions in their Mosofin workspace. Triggers include: pasting a list of transactions and asking 'what account should this go to', 'code these expenses', 'categorize these transactions', 'suggest a GL account for [vendor/description]', or uploading a bank/credit card export that needs categorization. Also trigger when the user mentions an uncoded transaction, an unclassified vendor, or asks Claude to map descriptions to accounts. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then codes against the real chart of accounts and grounds every suggestion in how this entity has actually coded the same vendor before. Do NOT use for building the chart of accounts itself — use chart-of-accounts-designer. Do NOT use for posting actual journal entries — use journal-entry-builder. Outputs a coded transaction list with confidence ratings

invoice-data-extractor

Use this skill whenever the user uploads a vendor invoice (PDF, image, or scanned doc) and wants structured data extracted, validated against their Mosofin workspace. Triggers include: 'extract the data from this invoice', 'pull the fields from this bill', 'parse these invoices', 'turn this PDF into a row I can post', or uploading any vendor invoice with implicit intent to capture it. Also trigger for bills, receipts, purchase invoices, and supplier statements where the goal is to convert visual document data into structured fields. Workspace-scoped on the validation side: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then checks each extracted invoice against the vendor master, the posted transaction history and the Bill-To entity — catching duplicates before they are paid. Do NOT use for OCR alone — extract semantically. Do NOT use for posting the JE — pair with journal-entry-builder. Outputs a structured row per invoice with vendor, dates, amo

journal-entry-builder

Use this skill whenever the user wants to construct, format, or validate a journal entry against their Mosofin workspace. Triggers include: 'book a JE for...', 'create a journal entry to record...', 'how do I record this transaction', 'make me an accrual JE', 'reclass these entries', 'reverse this entry', or any request involving debits and credits to specific accounts. Also trigger for adjusting entries, correcting entries, closing entries, intercompany entries, and import-ready JE files for accounting systems. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then builds entries against the real chart of accounts and validates them against the books — checking that accounts exist, signs match account types, the period is open, and no prior accrual already covers the item. Mosofin never posts: every entry is a proposal for a person to post. Do NOT use for GL coding decisions only — use gl-coding-assistant. Do NOT use for full perio

month-end-close-checklist

Use this skill whenever the user wants to plan, run, or audit a monthly close against their Mosofin workspace. Triggers include: 'run the month-end close', 'month-end checklist', 'what's left to close', 'close calendar', 'organize the close for [month]', 'close coordination', or any orchestration of the periodic close process. Workspace-scoped: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then scopes the checklist from the entity's actual chart of accounts, pre-populates the status of every task that leaves ledger evidence, and runs the final tie-out including inter-period continuity. Do NOT use for an individual close task (a specific reconciliation, accrual, or JE) — use the corresponding specific skill. Outputs a comprehensive close checklist with owners, deadlines, dependencies, status tracking, a final tie-out workpaper, and a coverage sheet.

three-way-match

Use this skill whenever the user wants to perform a three-way match between purchase orders, goods receipts and vendor invoices against a connected Mosofin workspace. Triggers include: 'three-way match these documents', 'verify the invoice against the PO and receipt', 'match PO to receipt to invoice', 'PO matching', 'GRN matching', 'run the match across all open invoices', uploading a PO + receipt + invoice trio, or any AP control task involving PO-to-invoice verification. Do NOT use for invoice extraction alone — use invoice-data-extractor. Do NOT use for duplicate detection — use duplicate-invoice-detection. Where the workspace holds purchase orders and item receipts, this runs across the full population every period rather than document by document. Outputs a match result with line-by-line comparison and exception list. Proposes only — Mosofin pays nothing and releases nothing.

multi-entity-forecast-dashboard

Build an interactive, single-file cash forecast dashboard for a multi-entity business (several QuickBooks company files) in a fixed "quiet analytics" visual style, with per-entity and consolidated views, P10/P90 forecast band, accounts/receivables detail, and a paper-style report. Pulls live data through the MosoFin connector when the user agrees, or falls back to a manual CSV upload when they opt out or have no connector. Use this whenever the user asks for a cash flow forecast, runway, cash dashboard, multi-entity or group consolidation view, "how much cash will we have", or a forecast for their MosoFin / QuickBooks workspace — even if they don't say "dashboard". Also use it to refresh or restyle an existing forecast dashboard so it stays visually consistent.