Agent skill

Purchase Accounting

by sickn33 in sickn33/agentic-awesome-skills

Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance.

MITAuto-check passedBusiness, Finance & HR

Install Purchase Accounting

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

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills purchase-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/purchase-accounting .claude/skills/purchase-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
purchase-accounting
GitHub stars
47k
Used in
1 other repo
Token cost
~5.1k tokens
SKILL.md length
1,697 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Purchase 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

Purchase Accounting is an agent skill from sickn33/agentic-awesome-skills. Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance. Use for purchase accounting.

Its SKILL.md is about 5.1k 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

  • Purchase accounting
  • Tasks that involve Accounting and bookkeeping
  • Tasks that involve Forms and invoices

Example prompts

  • “/purchase-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

Purchase Accounting loads about 5.1k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 1,697 words of instructions outside code blocks.

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

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). 1,697 words, ~5,089 tokens.

Download SKILL.mdSave it as .claude/skills/purchase-accounting/SKILL.md (or your agent's skills folder).
name
purchase-accounting
description
Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance. Use for purchase 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, purchase
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Purchase Accounting

What it is: Verified purchase invoices, booked and traceable to their PO and challan.

Overview

Works out the smallest useful Purchase 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: Growth stage. Table code: n/a.

When to Use This Skill

  • purchase accounting
  • purchase invoice register
  • supplier bill entry tracker
  • purchase vat and tds log

Also use it when the user says "verified purchase invoices, booked and traceable to their PO and challan", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: supplier payment runs, 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 are supplier bills captured 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.

  • Volume - How many supplier bills a month? / How many suppliers?
  • Verification - PO and challan always available? / Who checks the invoice?
  • Taxes and classification - VAT charged? / TDS deducted? / Which sections apply? / Inventory, expense or fixed asset? / Who decides the ledger?
  • Current process - Tracked now? / Software or sheet? / What gets missed?
  • Outcome - What do you need? / A purchase register, a VAT input log 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: purchase-accounting
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Volume": null
  "Verification": null
  "Taxes and classification": null
  "Current process": 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 purchase record per verified invoice, carrying the PO, challan and source document as relations, the VAT and TDS figures, the classification, and a review status - five steps: verify, file, update the Purchase VAT Register, record in software, review against the originals.

Why this one: Purchase errors are verification errors. A record that holds the linked documents and a review status is what makes a misclassified or untaxed bill visible before the return is filed.

Workflow: Invoice verified → Documents filed → VAT register updated → Booked and classified → Reviewed

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
Purchase Number,Supplier,Supplier PAN/VAT,Purchase Order,Delivery Challan,Supplier Invoice Number,Invoice Date,Item/Expense Description,Quantity,UOM,Rate,Gross Amount,VAT Rate %,VAT Amount,TDS Rate %,TDS Amount,Net Payable,Classification,Ledger Account,Source Document,Payment Status,Amount Paid,Balance,VAT Register Updated,Entry Verified,Prepared By,Verified By,Notes,Purchase ID
PUR-2026-0041,Bluepeak Supplies,29ABCDE1234F1Z5,PO-2026-0187,DC-2026-0902,INV-8841,2026-08-14,Corrugated cartons 3 ply,500,Nos,169.00,84500.00,18,15210.00,2.5,2112.50,97597.50,Inventory/Purchase,Purchases - Cartons,DOC-2026-0442,Part Paid,50000.00,47597.50,Done,In progress,Ananya Rao,Vikram Singh,Rate compared against PO-2026-0187; quantity matched with DC-2026-0902.,
sql
CREATE TABLE purchase_accounting (
  purchase_number VARCHAR(255),
  supplier VARCHAR(255),
  supplier_pan_vat VARCHAR(255),
  purchase_order VARCHAR(255),  -- relation -> target record
  delivery_challan VARCHAR(255),  -- relation -> target record
  supplier_invoice_number VARCHAR(255),
  invoice_date DATE NOT NULL,
  item_expense_description VARCHAR(255),
  quantity NUMERIC NOT NULL,
  uom VARCHAR(100) NOT NULL,
  rate NUMERIC(14,2) NOT NULL,
  gross_amount NUMERIC(14,2) NOT NULL,
  vat_rate_pct NUMERIC NOT NULL,
  vat_amount NUMERIC(14,2) NOT NULL,
  tds_rate_pct NUMERIC NOT NULL,
  tds_amount NUMERIC(14,2) NOT NULL,
  net_payable NUMERIC(14,2) NOT NULL,
  classification VARCHAR(100) NOT NULL,
  ledger_account VARCHAR(255),
  source_document VARCHAR(255),  -- relation -> target record
  payment_status VARCHAR(100) NOT NULL,
  amount_paid NUMERIC(14,2) NOT NULL,
  balance NUMERIC(14,2) NOT NULL,
  vat_register_updated VARCHAR(100) NOT NULL,
  entry_verified VARCHAR(100) NOT NULL,
  prepared_by VARCHAR(255),
  verified_by VARCHAR(255),
  notes TEXT,
  purchase_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": "Purchase Accounting",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Purchase Number": { "type": "string" },
      "Supplier": { "type": "string" },
      "Supplier PAN/VAT": { "type": "string" },
      "Purchase Order": { "type": "string" },
      "Delivery Challan": { "type": "string" },
      "Supplier Invoice Number": { "type": "string" },
      "Invoice Date": { "type": "string", "format": "date" },
      "Item/Expense Description": { "type": "string" },
      "Quantity": { "type": "number" },
      "UOM": { "type": "string" },
      "Rate": { "type": "number" },
      "Gross Amount": { "type": "number" },
      "VAT Rate %": { "type": "number" },
      "VAT Amount": { "type": "number" },
      "TDS Rate %": { "type": "number" },
      "TDS Amount": { "type": "number" },
      "Net Payable": { "type": "number" },
      "Classification": { "type": "string" },
      "Ledger Account": { "type": "string" },
      "Source Document": { "type": "string" },
      "Payment Status": { "type": "string" },
      "Amount Paid": { "type": "number" },
      "Balance": { "type": "number" },
      "VAT Register Updated": { "type": "string" },
      "Entry Verified": { "type": "string" },
      "Prepared By": { "type": "string" },
      "Verified By": { "type": "string" },
      "Notes": { "type": "string" },
      "Purchase ID": { "type": "integer" }
  },
  "required": [
      "Invoice Date",
      "Quantity",
      "UOM",
      "Rate",
      "Gross Amount",
      "VAT Rate %",
      "VAT Amount",
      "TDS Rate %",
      "TDS Amount",
      "Net Payable",
      "Classification",
      "Payment Status",
      "Amount Paid",
      "Balance",
      "VAT Register Updated",
      "Entry Verified"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Purchase Number | Title | Use as the database title |
| Supplier | Text | Leave as Text |
| Supplier PAN/VAT | Text | Leave as Text |
| Purchase Order | Relation (link to the target database) | Convert to Relation, link to the target database |
| Delivery Challan | Relation (link to the target database) | Convert to Relation, link to the target database |
| Supplier Invoice Number | Text | Leave as Text |
| Invoice Date | Date | Convert to Date |
| Item/Expense Description | Text | Leave as Text |
| Quantity | Number | Convert to Number |
| UOM | Select (add options after import) | Convert to Select, add options: "Nos", "Kg", "Litre", "Metre", "Set", "Hour", "Box", "Packet" |
| Rate | Number (format: currency) | Convert to Number, set format to Currency |
| Gross Amount | Number (format: currency) | Convert to Number, set format to Currency |
| VAT Rate % | Number | Convert to Number |
| VAT Amount | Number (format: currency) | Convert to Number, set format to Currency |
| TDS Rate % | Number | Convert to Number |
| TDS Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Net Payable | Number (format: currency) | Convert to Number, set format to Currency |
| Classification | Select (add options after import) | Convert to Select, add options: "Inventory/Purchase", "Expense", "Fixed Asset", "Other" |
| Ledger Account | Text | Leave as Text |
| Source Document | Relation (link to the target database) | Convert to Relation, link to the target database |
| Payment Status | Select (add options after import) | Convert to Select, add options: "Unpaid", "Part Paid", "Paid", "Overdue" |
| Amount Paid | Number (format: currency) | Convert to Number, set format to Currency |
| Balance | Number (format: currency) | Convert to Number, set format to Currency |
| VAT Register Updated | Select (add options after import) | Convert to Select, add options: "Not started", "In progress", "Blocked", "Done", "Cancelled" |
| Entry Verified | Select (add options after import) | Convert to Select, add options: "Not started", "In progress", "Blocked", "Done", "Cancelled" |
| Prepared By | Text | Leave as Text |
| Verified By | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Purchase 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
1Purchase NumbertextVARCHAR(255)stringTextPUR-2026-0041
2SuppliertextVARCHAR(255)stringTextBluepeak Supplies
3Supplier PAN/VATtextVARCHAR(255)stringText29ABCDE1234F1Z5
4Purchase OrderrelationVARCHAR(255)stringRelation (link to the target database)PO-2026-0187
5Delivery ChallanrelationVARCHAR(255)stringRelation (link to the target database)DC-2026-0902
6Supplier Invoice NumbertextVARCHAR(255)stringTextINV-8841
7Invoice DatedateDATEstring, format: dateDate2026-08-14
8Item/Expense DescriptiontextVARCHAR(255)stringTextCorrugated cartons 3 ply
9QuantitynumberNUMERICnumberNumber500
10UOMselectVARCHAR(100)stringSelect (add options after import)Nos
11RatecurrencyNUMERIC(14,2)numberNumber (format: currency)169.00
12Gross AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)84500.00
13VAT Rate %numberNUMERICnumberNumber18
14VAT AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)15210.00
15TDS Rate %numberNUMERICnumberNumber2.5
16TDS AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)2112.50
17Net PayablecurrencyNUMERIC(14,2)numberNumber (format: currency)97597.50
18ClassificationselectVARCHAR(100)stringSelect (add options after import)Inventory/Purchase
19Ledger AccounttextVARCHAR(255)stringTextPurchases - Cartons
20Source DocumentrelationVARCHAR(255)stringRelation (link to the target database)DOC-2026-0442
21Payment StatusselectVARCHAR(100)stringSelect (add options after import)Part Paid
22Amount PaidcurrencyNUMERIC(14,2)numberNumber (format: currency)50000.00
23BalancecurrencyNUMERIC(14,2)numberNumber (format: currency)47597.50
24VAT Register UpdatedselectVARCHAR(100)stringSelect (add options after import)Done
25Entry VerifiedselectVARCHAR(100)stringSelect (add options after import)In progress
26Prepared BytextVARCHAR(255)stringTextAnanya Rao
27Verified BytextVARCHAR(255)stringTextVikram Singh
28Noteslong_textTEXTstringTextRate compared against PO-2026-0187; quantity matched with DC-2026-0902.
29Purchase IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (619 more words)Show less

Select Options

UOM

Nos | Kg | Litre | Metre | Set | Hour | Box | Packet

Classification

Inventory/Purchase | Expense | Fixed Asset | Other

Payment Status

Unpaid | Part Paid | Paid | Overdue

VAT Register Updated

Not started | In progress | Blocked | Done | Cancelled

Entry Verified

Not started | In progress | Blocked | Done | Cancelled

Relations

Link fields: Purchase Order, Delivery Challan, Source Document

  • Purchase Order -> the purchase order the invoice was booked against.
  • Delivery Challan -> the delivery challan that evidences receipt of goods.
  • Source Document -> the filed document register row for the invoice and its support.

Examples

Prompt

Supplier bills pile up for a week before anyone checks the VAT on them.

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

Q: How many supplier bills a month? A: Around forty.

Q: Do you always have the PO and challan? A: Usually, not always.

Q: Is TDS deducted on any of them? A: Yes, on a few.

Recommended next step - offered, not built:

One purchase record per verified invoice, carrying the PO, challan and source document as relations, the VAT and TDS figures, the classification, and a review status - five steps: verify, file, update the Purchase VAT Register, record in software, review against the originals.

Workflow: Invoice verified → Documents filed → VAT register updated → Booked and classified → Reviewed

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.
  • 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 compute payroll, tax, leave balances or KPIs.
  • 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 post to the accounting package, pay suppliers, or file the VAT return.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • 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: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • 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 accounting modules.
  • @source-document-filing - files the invoice with its PO, challan and other support.
  • @tds-booking-payment - books and pays the withholding deducted here.
  • @payment-accounting - clears the payable carried in Net Payable and Balance.
  • @expense-accounting - the same flow for bills booked as expense rather than stock.
  • @inventory-stock-reconciliation - checks the stock side of Inventory/Purchase entries.
  • @party-ledger-reconciliation - reconciles the supplier balance against this register.

Reusable Prompt

I want to set up verified purchase invoices, booked and traceable to their PO and challan 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/purchase-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

Purchase 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.

Purchase Accounting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Purchase Accounting this skillsickn33/agentic-awesome-skills47k1 repos~5.1kAutomated 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 Purchase Accounting

What does Purchase Accounting do?

Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance. Purchase Accounting is an agent skill from sickn33/agentic-awesome-skills. Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance.

When should I use Purchase Accounting?

Purchase Accounting fits situations like: purchase accounting; tasks that involve Accounting and bookkeeping; tasks that involve Forms and invoices.

How do I install Purchase Accounting in Claude Code?

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

How do I install Purchase Accounting in Codex?

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

Can I use Purchase 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 purchase-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/purchase-accounting, .gemini/skills/purchase-accounting, .github/skills/purchase-accounting and .opencode/skills/purchase-accounting in your project.

What does Purchase Accounting need to run?

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

Does Purchase 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 Purchase 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 Purchase Accounting use?

Purchase 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 Purchase Accounting use?

About 5.1k tokens (SKILL.md is roughly 20k 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 Purchase Accounting?

Skills that share tags, products or a category with Purchase 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 Purchase 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.