mcpField
B
billing-reconciliation-review

billing-reconciliation-review

github.com/sylphxaiData & databases146 installsUpdated today
Repository

About billing-reconciliation-review

Billing Reconciliation Review is a skill for turning a high-stakes billing decision into a measurable, auditable operating artifact. It guides teams through lifecycle mapping, reconciliation rules, exception handling, and the evidence and interfaces needed for review.

Key features

  1. 01Map billing and payment lifecycles
  2. 02Define reconciliation keys and invariants
  3. 03Classify mismatches and repair paths
  4. 04Specify audit evidence and event schemas
  5. 05Design exception queues and support views

Use cases

  1. 01Reviewing billing reconciliation operations
  2. 02Defining mismatch handling and repair workflows
  3. 03Preparing audit-ready billing artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill billing-reconciliation-review

After installing, type/billing-reconciliation-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/billing-reconciliation-patterns.md

Details

From the project README

Billing Reconciliation Review

Use this skill to convert a high-stakes product decision into a concrete, measurable, reviewable operating artifact.

Workflow

  1. Identify money systems, authoritative ledger, payment providers, entitlement source, payout surface, tax/invoice requirements, and support consumers.
  2. Read references/billing-reconciliation-patterns.md.
  3. Map event lifecycle from order/renewal through payment, entitlement, invoice, refund, dispute, payout, and adjustment.
  4. Define reconciliation keys, expected invariants, mismatch classes, retry/repair workflow, and audit evidence.
  5. Produce reconciliation matrix, state machine, exception queue, event schema, and support/admin view requirements.

When not to use

  • Do not use when the job belongs to payment-platform-readiness — Provider integration, webhooks, ledger truth. Reconciliation patterns belong as reference depth inside payment readiness.
  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not use payment provider state as the only source of truth for product access without a derived entitlement model.
  • Do not silently repair money mismatches without audit logs.
  • Do not mix customer-facing credits, accounting adjustments, and promotional balances without clear types.
  • Escalate tax, accounting, and revenue recognition policy to qualified owners.

Output format

Billing context:
Providers / ledger / entitlement source:

Reconciliation matrix:
| Object | Source A | Source B | Key | Invariant | Mismatch action |
| --- | --- | --- | --- | --- | --- |

Exception queue:
- <mismatch> -> <severity, owner, repair, user impact>

Events/support evidence:
- <event/admin field/support macro>

Comments

Markdown supported