Solution skill
Metronome invoice mismatches: check cents vs dollars, SUM aggregation, and missing overrides
Complete solution
On a disputed invoice, first confirm the rate unit: a $100-looking line from a rate of 100 is actually $1.00.
Metronome invoice mismatches: check cents vs dollars, SUM aggregation, and missing overrides
TL;DR
On a disputed invoice, first confirm the rate unit: a $100-looking line from a rate of 100 is actually $1.00. Then compare the invoiced quantity to a manual event count; a big gap with SUM aggregation usually means a property value is inflating the total. Add the missing contract override and void/regenerate rather than editing the invoice.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Official docs (Metronome billing diagnostics reference, metronome-industries org): documents a diagnostic playbook for wrong invoices: compare line item quantities against a manual event count, verify the rate card rate is in cents (a rate of 100 means $1.00), check whether SUM aggregation is multiplying by a large property value, look for missing contract overrides, and check credit balances before assuming overage is wrong.
Evidence
Source: Official docs (Metronome billing diagnostics reference, metronome-industries org): documents a diagnostic playbook for wrong invoices: compare line item quantities against a manual event count, verify the rate card rate is in cents (a rate of 100 means $1.00), check whether SUM aggregation is multiplying by a large property value, look for missing contract overrides, and check credit balances before assuming overage is wrong.
Verified resolution: On a disputed invoice, first confirm the rate unit: a $100-looking line from a rate of 100 is actually $1.00. Then compare the invoiced quantity to a manual event count; a big gap with SUM aggregation usually means a property value is inflating the total. Add the missing contract override and void/regenerate rather than editing the invoice.
Source URL: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/references/diagnostics.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_RBwIanWq4eFY5AUKrmqnzw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Metronome invoice mismatches: check cents vs dollars, SUM aggregation, and missing overrides <span>— Vectle</span></a>