Reading your transaction history
Every credit movement — purchase, completed-interview deduction, refund — shows in the Billing page's transaction list. Here is how to read it.
Key takeaways
- Billing page → Transactions section. Newest first.
- Each row: timestamp, type (credit / debit), amount, balance after, reason.
- Use it to verify a specific interview consumed the expected number of credits.
- Export not yet available; screenshot for reports.
Before you start
Every change to your credit balance is recorded. The Transactions section of the Billing page is the audit trail.
Reading a row
Each transaction has:
- Timestamp — when it happened.
- Type — Credit (added to balance) or Debit (removed).
- Amount — how much.
- Balance after — what your total was right after this transaction.
- Reason — Purchased credits, Interview completed for X, Resume scan, etc.
- Actor — which team member triggered this (for debits).
Common transaction types
- Credit purchases — when you buy a pack.
- Interview deductions — 0.5 / 0.75 / 1.0 per completed interview.
- Resume scan deductions — 0.05 per resume.
- JD scan deductions — 0.05 per JD parsed.
- Trial credit grants — only appear on new accounts.
- Refunds — manual credits back if the platform operator approved a refund request.
Finding a specific spend
Looking for the cost of a particular interview? Open the candidate's profile → Interviews tab → find the row → click View. The interview detail page shows the credit cost in the Interview Details right rail.
Frequently asked questions
Can I see who in my team caused each deduction?
Yes — each transaction row shows the user who took the action (e.g. *Interview completed for Priya Nair, sent by anika@nextmantra.ai*). Useful for understanding spend distribution across the team.
My balance does not match my mental math — what now?
Check the transactions for the last day or two. The most common discrepancy is forgetting that resume/JD scans cost 0.05 credits each — a 100-resume bulk upload silently consumed 5 credits.