A Usage Export Finance and Engineering Can Both Read

Customer usage export fields: what to decide

Customers often reconcile billing outside your product. A CSV that contains internal IDs and unexplained numbers pushes that work onto their engineers. A small data dictionary can make the export useful to both analysts and finance.

Define timestamp timezone, period boundaries and whether rows are raw events or aggregates. Explain correction rows and duplicates. If the export is paginated or filtered, include enough context to prove which population was downloaded.

How this works in practice

An hourly aggregate export lists UTC hour, workspace, successful requests and rate version. A customer comparing it to local-time logs needs the UTC definition and boundary convention. Otherwise, matching totals can still look wrong by day.

What can go wrong

Changing column meaning without versioning breaks customer automation. Adding a new column is different from changing quantity from single units to thousands. Treat exports as a customer-facing data contract.

Questions for your team

• Publish column definitions and units.
• Preserve stable identifiers and timestamps.
• Document aggregation and correction semantics.
• Test opening large exports in common analysis tools.