GEO-RaaS Billing Manager

Problem: Inconsistent RaaS Billing for GEO Services

GEO service providers often charge by outcome metrics such as mention_rate, first_recommend_rate, or traffic growth, but metric definitions, billing periods, and invoice templates can be scattered across spreadsheets and chat records. This skill moves billing plans, actual metrics, and invoice templates into structured configuration files to reduce manual reconciliation.

How It Works: From Configuration to Invoice

• Billing plan parsing: reads RaaS plan templates from references/billing_plans.json and maps brands, billing models, and metric weights into computable rules.
• Billing calculation: scripts/billing_engine.py applies the configured rules to input values such as mention_rate and first_recommend_rate.
• Invoice and report output: scripts/invoice_generator.py combines billing results with references/invoice_templates.json, then can produce PDF through ReportLab / WeasyPrint or Excel through Openpyxl.

Boundaries

It is oriented to Coze workflows and cloud-function-style execution, making it suitable for internal GEO provider settlement or comparing billing models. It does not collect live GEO metrics and should not replace formal finance workflows for auditing, invoicing, or contract management.