Processes customer credit memos and refunds, vendor credit notes and refunds, sales returns, chargebacks and goodwill credits: identifies the type, validates the credit against the original invoice or bill (existence, balance, period, currency), checks that the tax reversal mirrors the original, proposes the journal entry for each type, tracks application, and surfaces unapplied credits in both directions, vendor credits first. Reads credits, refunds and the originals through a connected Mosofin workspace when the user agrees, or works from uploaded documents and exports. Use when the user asks to issue a credit memo, process a refund, record a vendor credit note or sales return, apply a credit against an invoice, or handle a chargeback, or uploads a credit memo. Do not use for extracting data from invoices (use invoice-data-extractor) or for preparing new invoices (use customer-invoicing). Read-only: produces a credit register, proposed entries and a coverage sheet, and issues, applies or posts nothing.
Prepares customer invoices with the content the jurisdiction requires (seller and customer details, sequential number, tax point, lines, tax by rate, totals, statutory wording) and the matching AR / revenue / tax entry, or validates invoices already issued against the same rules: mandatory fields, line checks, arithmetic, duplicate numbers and gaps in the sequence. Reads customers, items, prices, tax codes, terms and the existing invoice sequence through a connected Mosofin workspace when the user agrees, or works from uploaded lists and invoices. Use when the user asks to create an invoice, a batch or an invoice template, or to check issued invoices, including multi-currency, progress billing and reverse charge. Do not use for parsing vendor invoices (use invoice-data-extractor), subscription scheduling (use recurring-transaction-builder) or credits and refunds (use credit-memo-and-refund-handler). Read-only: produces draft invoices, a proposed entry and a coverage sheet, and posts, numbers or sends nothing.
Scans the accounts payable register for likely duplicate invoices and payments — the same invoice resubmitted, the same amount paid through two channels, altered invoice numbers, vendor-name variants, and vendor credits never applied — rates each cluster's confidence, quantifies exposure, puts unpaid duplicates first and proposes recovery. In a group, also finds one invoice paid by two entities. Reads bills, payments and the vendor master through a connected Mosofin workspace when the user agrees, or works from an uploaded AP register and payment history. States that the same-bank-account rule cannot run without vendor bank details. Use when the user asks to check for duplicate invoices or payments, scan AP for duplicates, detect invoice fraud or 'have we paid this twice', or uploads a payment history or AP register. Do not use for general fraud detection across all transaction types. Read-only: produces a duplicate-suspect workpaper with evidence, a rules-run sheet and coverage sheet, and posts nothing.
Processes employee expense reports from any T&E tool (Concur, Expensify, Brex, Ramp, Pleo, Spendesk, Soldo) or a pasted report: validates each line against the user's own policy, codes it to the real chart of accounts, flags personal and duplicate claims, calculates what each employee is owed, and prepares the GL posting inputs. Jurisdiction-agnostic: mileage rates, per-diems, receipt thresholds and deductibility rules come from the user, never from memory. Reads the books through a connected Mosofin workspace when the user agrees, so claims are checked against card charges already posted, or works from uploaded exports. Use when the user uploads an expense report, asks to review expense claims, check a report against policy, code employee expenses, or work out mileage, per-diems or T&E reimbursements. Do not use for vendor invoices (use invoice-data-extractor) or petty cash. Read-only: produces a policy-checked, coded workpaper, posting inputs and a coverage sheet, and approves, pays or posts nothing.
Builds a complete set of financial statements from a trial balance: Balance Sheet, Income Statement, Comprehensive Income, Cash Flows and Changes in Equity, with comparatives, current and non-current classification and US GAAP, IFRS or local GAAP format, then proves the seven cross-statement tie-outs on the statements it built, each with its difference. Reads the trial balance and comparative period through a connected Mosofin workspace when the user agrees, or works from an uploaded trial balance. Never defaults the framework, the current portion of debt, rounding or a share count. Use when the user asks to build financial statements from a TB, produce a P&L and balance sheet, a monthly financials package, GAAP, IFRS or investor financials, or uploads a trial balance and asks for statements. Do not use to fix an unbalanced trial balance (use closing-entries-and-trial-balance) or for footnotes. Read-only: produces a statement package, tie-outs and a coverage sheet, and posts nothing.
Maintains the fixed asset (PP&E) register and computes depreciation under US GAAP, IFRS or local GAAP: derives additions and disposals from the ledger movements, scans repairs and maintenance for capital items at or above the threshold, computes period depreciation by the policy method, compares the implied rate with policy lives, proposes depreciation, capitalization and disposal entries, and reconciles the register to the GL in both directions. Reads the books through a connected Mosofin workspace when the user agrees, or works from uploaded trial balances, GL detail and an asset listing. Always asks for useful lives, the capitalization threshold and the convention, which the books do not hold. Use when the user asks to add or dispose of an asset, capitalize a purchase, compute depreciation, build a depreciation schedule, reconcile fixed assets or review for impairment. Do not use for intangibles or leases. Read-only: produces a register workpaper and proposed entries, and posts nothing.
Suggests the general ledger account, expense category and tax code for each transaction from its vendor, description and amount, against the entity's real chart of accounts, and grounds each suggestion in how this entity has actually coded the same vendor before — with the count and recency. Rates confidence, separates clear items from ones to review, and flags possible capex, personal use, splits, transfers, related-party and cross-border items and inconsistent history. Reads the books through a connected Mosofin workspace when the user agrees, or works from an uploaded bank or card export plus a chart of accounts. Use when the user asks 'what account should this go to', 'code these expenses', 'categorize these transactions' or 'suggest a GL account for…', or has uncoded transactions. Do not use to design the chart of accounts itself, or to post entries (use journal-entry-builder). Read-only: produces a coded transaction list with confidence, reasoning, evidence and a coverage sheet, and posts nothing.
Reconciles the inventory subledger and physical count to the general ledger inventory accounts: first establishes whether the subledger and the GL are two systems or one (which agree by construction), then compares GL, subledger and count, classifies variances as shrinkage, overage, cut-off, wrong location or damage, lists every negative quantity, tests cut-off, ties the reserve roll-forward and trends shrinkage. Reads the books through a connected Mosofin workspace when the user agrees, or works from uploaded GL balances, item listings and count sheets. Always asks for the physical count, the only test that the goods exist, which no ledger read can supply. Use when the user asks to reconcile inventory to the GL, explain a physical or cycle count variance, investigate shrinkage or tie inventory to the balance sheet. Do not use for choosing or applying a costing method (FIFO, LIFO, weighted average). Read-only: produces a reconciliation workpaper and proposed cleanup entries, and posts nothing.
Extracts structured, accounting-ready data from vendor invoices — PDFs, scans, photos, single or batch — vendor, tax ID, invoice number, dates, terms, line items with service periods, totals and tax by rate, then validates each invoice against the books: duplicate invoice number for the vendor, already paid, known vendor, Bill-To entity, terms, PO and currency. Reads the vendor master and posted bills through a connected Mosofin workspace when the user agrees, or works from uploaded invoices plus a vendor list and bill listing. Use when the user says 'extract the data from this invoice', 'pull the fields from this bill', 'parse these invoices' or 'turn this PDF into a row I can post', or uploads a vendor invoice, bill, receipt or supplier statement to capture. Do not use for OCR alone (it extracts semantically) or to post the entry (use journal-entry-builder). Read-only: produces a structured row per invoice with line items, tax detail, validation results and a coverage sheet, and posts nothing.
Builds balanced, import-ready journal entries for any accounting event — standard, accrual, deferral, adjusting, correcting, reclass, reversing, intercompany or closing — against the entity's real chart of accounts, and validates each one: debits equal credits, every account exists, signs match account types, the period is open, and no open accrual, open invoice or control account makes the entry wrong. Reads the books through a connected Mosofin workspace when the user agrees, or works from an uploaded chart of accounts, trial balance or GL export. Use when the user says 'book a JE for…', 'create a journal entry to record…', 'how do I record this transaction', 'make me an accrual JE', 'reclass these entries' or 'reverse this entry', or asks for an import-ready JE file. Do not use for GL coding decisions only (use gl-coding-assistant) or a full period close (use month-end-close-checklist). Read-only: produces proposed entries with narration, validation results and a coverage sheet, and posts nothing.
Reviews a population of journal entries for risk, propriety and anomalies through a control and audit lens: screens every entry against timing, account-combination, amount and people-and-process indicators measured against the entity's history, risk-scores the flags and leads with patterns such as recurring period-end adjustments and reserves that move with earnings. Reads the entries through a connected Mosofin workspace when the user agrees, or works from uploaded journal or GL exports. Reports the approval-based indicators as not run where approval data is not available, and treats every flag as a question, never a finding of fraud. Use when the user asks to review journal entries, run JE testing, find unusual journal entries, test JEs for fraud indicators or assess journal entry controls. Do not use for building entries (use journal-entry-builder) or for a full forensic investigation. Read-only: produces a risk-scored review workpaper, follow-up items and a coverage sheet, and posts nothing.
Reconciles a payment processor — Stripe, Square, PayPal, Braintree, Adyen, Shopify Payments — to the general ledger: gross sales, fees, refunds, chargebacks and payouts, with the clearing account rolled forward and aged. Tests the most common error, revenue recorded net of processor fees. Reads the books through a connected Mosofin workspace when the user agrees, or works from uploaded exports — processor payout and transaction CSVs, GL detail or a trial balance. Use when the user asks to reconcile Stripe or Square to the books, process processor settlements, explain why payouts do not match revenue, check merchant fees, or uploads a processor export. Do not use for bank reconciliation alone (use bank-reconciliation) or for applying customer payments (use cash-application). Read-only: produces a reconciliation, proposed entries and a coverage sheet, and posts nothing.
Plans, runs and audits a monthly close: builds the close task list with owners, deadlines, dependencies and status, scopes it to the entity (no inventory, single entity, cash basis, industry tasks), applies materiality, tracks open items and runs the final tie-out, including an inter-period continuity check per balance sheet account. Reads the books through a connected Mosofin workspace when the user agrees, using posted entries as evidence of what has and has not been done, or works from uploaded exports such as a trial balance. Use when the user asks to run the month-end close, wants a month-end checklist or close calendar, asks what is left to close, or wants to organise or coordinate the close for a month. Do not use for an individual close task: a bank reconciliation (use bank-reconciliation), an accrual (use accruals-and-deferrals) or a single journal entry (use journal-entry-builder). Read-only: produces a close workpaper, a final tie-out and a coverage sheet, and posts nothing.
Reconciles the payroll control accounts — payroll clearing, payroll suspense, and each withholding, employer-charge, benefit and garnishment liability — at month end: rolls each forward, compares it to its expected balance, ages every balance, tests whether it behaves like its remittance cadence, and finds the stale balances that never clear, including unclaimed pay that may be escheatable. Reads the books through a connected Mosofin workspace when the user agrees, or works from uploaded GL detail, payroll registers and remittance records, treating the register as external unless a payroll platform is connected. Use when the user asks to reconcile payroll clearing or suspense, clear payroll liabilities, or why payroll clearing is not zero. Do not use for the payroll journal itself (use payroll-journal-entry-builder) or a full register-to-GL and bank tie-out (use payroll-reconciliation). Read-only: produces a reconciliation workpaper, proposed cleanup entries and a coverage sheet, and posts nothing.
Builds the journal entries that record a payroll run from its payroll register: gross pay, employee withholdings, net pay, employer costs, net pay funding, department and cost-centre allocation, capitalised labour and the period-end accrual. Ties every line to the register's totals, the test that catches employer contributions mixed with employee deductions, and compares the run to prior runs before anything is posted. Reads the chart, dimensions and prior runs through a connected Mosofin workspace when the user agrees, or works from uploaded files — the register, a chart of accounts, prior journals. Use when the user asks to book the payroll journal, record a payroll run, accrue payroll, split payroll across departments, or turn a payroll register into entries. Do not use for reconciling payroll to the GL after posting (use payroll-reconciliation) or the payroll clearing account (use payroll-clearing-reconciliation). Read-only: produces proposed entries, a workpaper and a coverage sheet, and posts nothing.
Reconciles payroll across its four sources of truth — register, general ledger, bank, and remittances and filings: register to GL, net pay to bank, each withholding and employer liability rolled forward, quarter- and year-end filings and wage statements, and each tax to its taxable wage base. Flags manual adjustments, negative liabilities and overdue remittances. Reads the GL side through a connected Mosofin workspace when the user agrees, or works from uploaded registers, GL detail, bank and remittance records, and reports the wage-base check as not performed without a register. Use when the user asks to reconcile payroll, tie the register to the GL or payroll to the bank, reconcile payroll liabilities, or do a quarter- or year-end payroll tie-out. Do not use for building the payroll journal (use payroll-journal-entry-builder) or clearing-account zeroing only (use payroll-clearing-reconciliation). Read-only: produces a reconciliation workpaper, proposed corrections and a coverage sheet, and posts nothing.
Builds, maintains and audits a prepaid expense amortization schedule — insurance, SaaS, rent and other costs paid in advance: finds prepaid candidates, applies the user's materiality threshold, amortizes each item over its coverage period, drafts the entries, and ties the schedule to the GL prepaid balance. Audits the account from the ledger alone: missed amortization runs, prepaids expensed in one month, expired residue, deposits or fixed assets coded to prepaid, recoverable tax inside the asset. Reads the books through Mosofin when the user agrees, or works from uploaded GL detail, and always asks for the coverage dates, which no ledger holds. Use when the user asks to set up or reconcile a prepaid schedule, amortize a prepaid, prepare the monthly prepaid entry, or find prepaids never set up. Do not use for deferred revenue (use accruals-and-deferrals) or the whole close (use month-end-close-checklist). Read-only: produces a schedule workpaper, proposed entries and a coverage sheet, and posts nothing.
Designs and validates recurring journal entries, bills, invoices and subscription schedules: computes every future occurrence (calendar rolls, escalations, memo variables), checks each account, counterparty and tax code against the live chart, checks whether the recurrence already exists, finds manually repeated transactions worth automating, and audits whether existing recurring entries actually ran. Reads the chart, counterparties, tax codes and posting history through a connected Mosofin workspace when the user agrees, or works from details the user supplies. Use when the user asks to set up a recurring entry or bill, generate the next 12 months of entries, automate a monthly entry, build a subscription invoice template, check whether a recurring entry ran, or asks what to automate. Do not use for one-off entries (use journal-entry-builder) or prepaid amortization (use prepaid-amortization-schedule). Read-only: produces a schedule specification for a person to load, and creates, posts or schedules nothing.
Matches a vendor invoice to its purchase order and goods receipt before payment: header checks, then every line for quantity, price and item, your tolerance applied, fifteen exception tests from price creep to an unapproved order, and a Pay, Hold or Reject recommendation with the matched and disputed amounts. Counts the legs it actually has and says plainly whether it ran a three-way or a two-way match. Reads bills and purchase orders through a connected Mosofin workspace when the user agrees, or works from uploaded POs, delivery records and invoices. Use when the user asks whether an invoice should be paid, wants to match invoices to purchase orders or receipts, mentions overbilling, short shipments or goods received not invoiced (GRNI), or uploads a PO, receipt or invoice. Do not use for finding duplicate payments alone (use duplicate-invoice-detection) or for reconciling a vendor statement (use vendor-statement-reconciliation). Read-only: recommends, posts nothing, pays nothing.
Reconciles a supplier's statement to the AP subledger and general ledger: matches by document number, then amount and date, then PO, then description, recording the tier, and explains every difference: missing invoices (candidate unrecorded liabilities), missing credits owed back, payments in transit, misapplied payments, duplicates and disputes, each with an owner, next action and target date. Ranks which vendors most need reconciling, including any never reconciled or overpaid. Reads the AP ledger and payment register through a connected Mosofin workspace when the user agrees, or works from uploaded exports; always asks for the statement, which no accounting system holds. Use for a vendor statement recon, AP statement tie-out, supplier statement mismatch, cleaning up AP, unrecorded liabilities or unclaimed credits. Do not use for bank accounts (use bank-reconciliation) or matching invoices to POs (use three-way-match). Read-only: produces a reconciliation, exceptions and proposed entries, and posts nothing.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.