Agent skill

Receipt Accounting

by sickn33 in sickn33/agentic-awesome-skills

Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected.

MITAuto-check passedBusiness, Finance & HR

Install Receipt Accounting

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill receipt-accounting -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills receipt-accounting --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/receipt-accounting .claude/skills/receipt-accounting && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
receipt-accounting
GitHub stars
47k
Used in
1 other repo
Token cost
~5.5k tokens
SKILL.md length
2,136 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Receipt and sales-income accounting
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Receipt Accounting is an agent skill from sickn33/agentic-awesome-skills. Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected. Use for receipt and sales-income accounting.

Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR, covering Accounting and bookkeeping and Forms and invoices. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Receipt and sales-income accounting
  • Tasks that involve Accounting and bookkeeping
  • Tasks that involve Forms and invoices

Example prompts

  • “/receipt-accounting”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Receipt Accounting loads about 5.5k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 2,136 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 2,136 words, ~5,512 tokens.

Download SKILL.mdSave it as .claude/skills/receipt-accounting/SKILL.md (or your agent's skills folder).
name
receipt-accounting
description
Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected. Use for receipt and sales-income accounting.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, accounting, audit, finance, database, csv, notion, sql, receipts, reconciliation
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Receipt Accounting

What it is: Money received, allocated to the right account, and reconciled to cash or bank.

Overview

Works out the smallest useful Receipt Accounting setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 3: Record. Fits: Starter stage. Table code: n/a.

The rule this table exists to enforce: a receipt is not sales income. Money can arrive as collection of an existing receivable, as an advance from a customer, as a loan received, or as capital contribution. Each of those lands in a different ledger, and only one of them is income. This is why Receipt Type and Treats as Sale Income are fields and not conventions, and why Amount Allocated and Unapplied Amount are both captured - the difference between the gross received and the part that clears an invoice stays visible instead of quietly inflating revenue.

When to Use This Skill

  • receipt register
  • receipt voucher book
  • money received log
  • collections tracker
  • bank receipt reconciliation sheet

Also use it when the user says "money received, allocated to the right account, and reconciled to cash or bank", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: raising sales invoices, making payments, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How do you record money received today?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Receipts - How many in a month? / Cash, bank, cheque or digital? / Any part-payments?
  • Allocation - Allocated to invoices? / Advances or loans mixed in? / Who allocates it?
  • Evidence - Receipt voucher or bank advice? / Issued to the customer? / Filed where?
  • Reconciliation - Bank reconciled how often? / Cash counted? / Differences handled how?
  • Outcome - What do you need? / A receipts register, a reconciliation view or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: receipt-accounting
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Receipts": null
  "Allocation": null
  "Evidence": null
  "Reconciliation": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One receipt record carrying the mode, the gross received, the receipt type, the invoice it clears and the unapplied balance, and post it to income only when the type says it is a sale.

Why this one: The trap on this table is that money in gets treated as revenue out. Forcing the type and the allocation before the entry closes is what keeps an advance or a loan out of the sales book.

Workflow: Money received → Mode and source recorded → Typed as collection, advance, loan or capital → Allocated to an invoice or held unapplied → Reconciled to bank or cash

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

csv
Receipt Number,Receipt Date,Received From,Receipt Mode,Cash/Bank Account,Reference (Cheque/UTR/ID),Gross Amount Received,Receipt Type,Treats as Sale Income,Sales Invoice Allocated,Amount Allocated,Unapplied Amount,Adjust Against,TDS Collected on Receipt,Voucher Number,Ledger Account,Source Document,Reconciliation Status,Prepared By,Verified By,Entry Verified,Notes,Receipt ID
RCP-2026-0312,2026-08-19,Greyson Foods,Bank,HDFC Current ****0042,UTR-2026-0819,140000.00,Receivable Collection,No,SAL-2026-0033,130712.40,9287.60,Customer Advance - Greyson Foods,1307.12,VCH-2026-1027,Bank - HDFC Current,DOC-2026-0461,Unreconciled,Ananya Rao,Sneha Iyer,In progress,"Part collected against INV-2026-0733; TDS of 1307.12 remitted from this receipt; balance held as advance, not income.",
sql
CREATE TABLE receipt_accounting (
  receipt_number VARCHAR(255),
  receipt_date DATE NOT NULL,
  received_from VARCHAR(255),
  receipt_mode VARCHAR(100) NOT NULL,
  cash_bank_account VARCHAR(255),
  reference_cheque_utr_id VARCHAR(255),
  gross_amount_received NUMERIC(14,2) NOT NULL,
  receipt_type VARCHAR(100) NOT NULL,
  treats_as_sale_income VARCHAR(100) NOT NULL,
  sales_invoice_allocated VARCHAR(255),  -- relation -> target record
  amount_allocated NUMERIC(14,2) NOT NULL,
  unapplied_amount NUMERIC(14,2) NOT NULL,
  adjust_against VARCHAR(255),
  tds_collected_on_receipt NUMERIC(14,2) NOT NULL,
  voucher_number VARCHAR(255),
  ledger_account VARCHAR(255),
  source_document VARCHAR(255),  -- relation -> target record
  reconciliation_status VARCHAR(100) NOT NULL,
  prepared_by VARCHAR(255),
  verified_by VARCHAR(255),
  entry_verified VARCHAR(100) NOT NULL,
  notes TEXT,
  receipt_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Receipt Accounting",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Receipt Number": { "type": "string" },
      "Receipt Date": { "type": "string", "format": "date" },
      "Received From": { "type": "string" },
      "Receipt Mode": { "type": "string" },
      "Cash/Bank Account": { "type": "string" },
      "Reference (Cheque/UTR/ID)": { "type": "string" },
      "Gross Amount Received": { "type": "number" },
      "Receipt Type": { "type": "string" },
      "Treats as Sale Income": { "type": "string" },
      "Sales Invoice Allocated": { "type": "string" },
      "Amount Allocated": { "type": "number" },
      "Unapplied Amount": { "type": "number" },
      "Adjust Against": { "type": "string" },
      "TDS Collected on Receipt": { "type": "number" },
      "Voucher Number": { "type": "string" },
      "Ledger Account": { "type": "string" },
      "Source Document": { "type": "string" },
      "Reconciliation Status": { "type": "string" },
      "Prepared By": { "type": "string" },
      "Verified By": { "type": "string" },
      "Entry Verified": { "type": "string" },
      "Notes": { "type": "string" },
      "Receipt ID": { "type": "integer" }
  },
  "required": [
      "Receipt Date",
      "Receipt Mode",
      "Gross Amount Received",
      "Receipt Type",
      "Treats as Sale Income",
      "Amount Allocated",
      "Unapplied Amount",
      "TDS Collected on Receipt",
      "Reconciliation Status",
      "Entry Verified"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Receipt Number | Title | Use as the database title |
| Receipt Date | Date | Convert to Date |
| Received From | Text | Leave as Text |
| Receipt Mode | Select (add options after import) | Convert to Select, add options: "Cash", "Bank", "Cheque", "Fonepay/QR", "Other Digital Payment" |
| Cash/Bank Account | Text | Leave as Text |
| Reference (Cheque/UTR/ID) | Text | Leave as Text |
| Gross Amount Received | Number (format: currency) | Convert to Number, set format to Currency |
| Receipt Type | Select (add options after import) | Convert to Select, add options: "Sale Collection", "Receivable Collection", "Advance from Customer", "Loan Received", "Capital Contribution", "Other" |
| Treats as Sale Income | Select (add options after import) | Convert to Select, add options: "Yes", "No" |
| Sales Invoice Allocated | Relation (link to the target database) | Convert to Relation, link to the target database |
| Amount Allocated | Number (format: currency) | Convert to Number, set format to Currency |
| Unapplied Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Adjust Against | Text | Leave as Text |
| TDS Collected on Receipt | Number (format: currency) | Convert to Number, set format to Currency |
| Voucher Number | Text | Leave as Text |
| Ledger Account | Text | Leave as Text |
| Source Document | Relation (link to the target database) | Convert to Relation, link to the target database |
| Reconciliation Status | Select (add options after import) | Convert to Select, add options: "Unreconciled", "Reconciled", "Difference" |
| Prepared By | Text | Leave as Text |
| Verified By | Text | Leave as Text |
| Entry Verified | Select (add options after import) | Convert to Select, add options: "Not started", "In progress", "Blocked", "Done", "Cancelled" |
| Notes | Text | Leave as Text |
| Receipt ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

#FieldTypeSQLJSON SchemaNotionCSV example
1Receipt NumbertextVARCHAR(255)stringTextRCP-2026-0312
2Receipt DatedateDATEstring, format: dateDate2026-08-19
3Received FromtextVARCHAR(255)stringTextGreyson Foods
4Receipt ModeselectVARCHAR(100)stringSelect (add options after import)Bank
5Cash/Bank AccounttextVARCHAR(255)stringTextHDFC Current ****0042
6Reference (Cheque/UTR/ID)textVARCHAR(255)stringTextUTR-2026-0819
7Gross Amount ReceivedcurrencyNUMERIC(14,2)numberNumber (format: currency)140000.00
8Receipt TypeselectVARCHAR(100)stringSelect (add options after import)Receivable Collection
9Treats as Sale IncomeselectVARCHAR(100)stringSelect (add options after import)No
10Sales Invoice AllocatedrelationVARCHAR(255)stringRelation (link to the target database)SAL-2026-0033
11Amount AllocatedcurrencyNUMERIC(14,2)numberNumber (format: currency)130712.40
12Unapplied AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)9287.60
13Adjust AgainsttextVARCHAR(255)stringTextCustomer Advance - Greyson Foods
14TDS Collected on ReceiptcurrencyNUMERIC(14,2)numberNumber (format: currency)1307.12
15Voucher NumbertextVARCHAR(255)stringTextVCH-2026-1027
16Ledger AccounttextVARCHAR(255)stringTextBank - HDFC Current
17Source DocumentrelationVARCHAR(255)stringRelation (link to the target database)DOC-2026-0461
18Reconciliation StatusselectVARCHAR(100)stringSelect (add options after import)Unreconciled
19Prepared BytextVARCHAR(255)stringTextAnanya Rao
20Verified BytextVARCHAR(255)stringTextSneha Iyer
21Entry VerifiedselectVARCHAR(100)stringSelect (add options after import)In progress
22Noteslong_textTEXTstringTextPart collected against INV-2026-0733; TDS of 1307.12 remitted from this receipt; balance held as advance, not income.
23Receipt IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)

Select Options

Receipt Mode

Cash | Bank | Cheque | Fonepay/QR | Other Digital Payment

Receipt Type

Sale Collection | Receivable Collection | Advance from Customer | Loan Received | Capital Contribution | Other

Treats as Sale Income

Yes | No

Reconciliation Status

Unreconciled | Reconciled | Difference

Entry Verified

Not started | In progress | Blocked | Done | Cancelled

Relations

Link fields: Sales Invoice Allocated, Source Document

Sales Invoice Allocated points at the sales book, so the receipt and the invoice it clears can be read side by side. Source Document points at the filing register, so the bank advice or receipt voucher is one lookup away. Neither link substitutes for Receipt Type - a receipt can be fully allocated and still be an advance.

Show full SKILL.md (903 more words)Show less

Examples

Prompt

Money comes in and we post all of it as sales. At month end the numbers never agree
with the bank.

Context first - one question per message, nothing already answered:

Q: How many receipts in a month? A: About forty.

Q: Cash, bank, digital? A: Mostly bank. Some Fonepay.

Q: Do you allocate receipts to invoices? A: Sometimes. The rest we just leave.

Recommended next step - offered, not built:

One receipt record carrying the mode, the gross received, the receipt type, the invoice it clears and the unapplied balance, and post it to income only when the type says it is a sale.

Workflow: Money received → Mode and source recorded → Typed as collection, advance, loan or capital → Allocated to an invoice or held unapplied → Reconciled to bank or cash

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Never let a receipt become income on the strength of money arriving. Set Receipt Type first, then Treats as Sale Income, then allocate.
  • Keep the arithmetic visible: gross received = amount allocated + unapplied amount, every row. A row that will not balance means the allocation is still open.
  • TDS Collected on Receipt is a slice of the money received, not an addition to it. It is the part of the allocation that is remitted to the government, so gross received still equals amount allocated plus unapplied amount.
  • An unapplied amount is a live question, not a rounding item. Carry it forward until it is identified as an advance, a loan, capital or an error.
  • Record the mode on every receipt. Cash, bank, cheque and digital reconcile through different routes and a mixed-up mode is the most common source of differences.
  • Record Cash/Bank Account masked - the bank and the last four digits is all a register needs, and the full number is what turns a register into a target.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not post entries, raise invoices or compute tax.
  • The type fields do not decide the accounting treatment for you. The ledger, the tax position and the period all matter, and a qualified accountant confirms that.
  • Unapplied amounts need a follow-up process. This table records them; it does not chase them.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not connect to a bank feed or move money.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, bank details or customer financials. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • A receipt register is a target for fraud and for someone asking for a copy of a customer's bank reference. Do not paste live UTR or cheque images into a chat.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: every receipt posted as sales because the money arrived. Solution: Receipt Type and Treats as Sale Income are fields, not assumptions. Fill them before the entry, not at month end.
  • Problem: the unapplied balance is quietly dropped so the row balances. Solution: hold it in Unapplied Amount and carry it forward until it is identified.
  • Problem: the mode is left blank, so cash and bank never reconcile separately. Solution: Receipt Mode is required; a receipt with no mode cannot be reconciled.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.
  • @accounting-audit-system-builder - routes to this skill and the other 15 modules.
  • @sales-accounting - the invoice side of Sales Invoice Allocated.
  • @payment-accounting - the other half of the cash and bank movement.
  • @source-document-filing - holds the Source Document target.
  • @party-ledger-reconciliation - proves the debtor balance after allocation.
  • @day-book - the daily book these receipts land in.
  • @tds-booking-payment - carries TDS Collected on Receipt through to the return.
  • @petty-cash-management - the same receipt-versus-income question in cash.
  • @monthly-closing-statements - where the unapplied balance either clears or gets written off.
  • @credit-cycle-analysis - uses the unallocated balance to age the debtors.
  • @audit-preparation - the receipt register is an audit-trail item.
  • @expense-accounting - the receipt side that is not income at all.

Reusable Prompt

I want to set up receipt accounting - every rupee received, its mode, its type, its
allocation against an invoice and its reconciliation to cash or bank - for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema and a Notion property mapping. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/receipt-accounting of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Receipt Accounting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Receipt Accounting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Receipt Accounting this skillsickn33/agentic-awesome-skills47k1 repos~5.5kAutomated safety check: PassMIT
Odoo Month End Closeerpipe-org/mcp-odoo421—~753Automated safety check: PassMIT
Journalkazukinagata/shinkoku365—~2.3kAutomated safety check: PassMIT
Invoice Organizerdavila7/claude-code-templates33k12 repos~2.9kAutomated safety check: PassMIT
Compte De ResultatWellApp-ai/Well345—~602Automated safety check: PassMIT
Invoice Po Reconciliationpnp/sharepoint-skills133—~1.4kAutomated safety check: PassMIT

Similar skills

  • Odoo Month End Close

    erpipe-org/mcp-odoo

    Drive a month-end accounting close on Odoo through odoo-mcp — AR/AP aging, open-item and draft-invoice review, reconciliation checklists, and chatter documentation — with human sign-off at every…

    421 GitHub stars~753 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Journal

    kazukinagata/shinkoku

    This skill should be used when the user wants to record bookkeeping entries (仕訳), import transaction data from CSV files, receipts, or invoices, or manage their general ledger.

    365 GitHub stars~2.3k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Invoice Organizer

    davila7/claude-code-templates

    Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders.

    33k GitHub starsUsed in 12 repos~2.9k tokens
    Business, Finance & HRAuto-check passed
  • Compte De Resultat

    WellApp-ai/Well

    Build a profit & loss statement (compte de résultat / income statement) from a Well workspace.

    345 GitHub stars~602 tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Invoice Po Reconciliation

    pnp/sharepoint-skills

    Reconciles one or more user-selected invoice files against matching purchase orders in the Purchase Order library.

    133 GitHub stars~1.4k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Month End Close

    WellApp-ai/Well

    Run a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed.

    345 GitHub stars~567 tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Receipt Accounting

What does Receipt Accounting do?

Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected. Receipt Accounting is an agent skill from sickn33/agentic-awesome-skills. Receipt register: payer, mode, gross amount received, invoice allocation, unapplied amount and TDS collected.

When should I use Receipt Accounting?

Receipt Accounting fits situations like: receipt and sales-income accounting; tasks that involve Accounting and bookkeeping; tasks that involve Forms and invoices.

How do I install Receipt Accounting in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill receipt-accounting -a claude-code`. Or copy the skill folder (skills/receipt-accounting in sickn33/agentic-awesome-skills) into .claude/skills/receipt-accounting in your project. Claude Code loads it when a task matches its description.

How do I install Receipt Accounting in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill receipt-accounting -a codex`. Or copy the skill folder (skills/receipt-accounting in sickn33/agentic-awesome-skills) into .agents/skills/receipt-accounting in your project. Codex loads it when a task matches its description.

Can I use Receipt Accounting in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill receipt-accounting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/receipt-accounting, .gemini/skills/receipt-accounting, .github/skills/receipt-accounting and .opencode/skills/receipt-accounting in your project.

What does Receipt Accounting need to run?

SKILL.md names no scripts, command-line tools or credentials: Receipt Accounting is instructions for the agent only.

Does Receipt Accounting access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Receipt Accounting safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Receipt Accounting use?

Receipt Accounting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Receipt Accounting use?

About 5.5k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Receipt Accounting?

Skills that share tags, products or a category with Receipt Accounting: Odoo Month End Close (erpipe-org/mcp-odoo, 421 stars), Journal (kazukinagata/shinkoku, 365 stars), Invoice Organizer (davila7/claude-code-templates, 33k stars) and Compte De Resultat (WellApp-ai/Well, 345 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Receipt Accounting?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.