An invoice lineage check asks whether each material line can be traced to a source event, approved term, usage record, or documented adjustment. It does not decide whether a service is billable or whether a contract interpretation is correct. Start with invoice version, period, account, source system, and creation event.

Map each line

Record source identifier, event date, quantity, amount, description, rule reference, and any transformation. If an export rounds or groups values, show the aggregation rule. A total that reconciles can still hide one unsupported line and one offsetting error.

Classify traced, timing difference, duplicate candidate, unsupported source, changed after approval, and owner interpretation required. Preserve original and later versions. A support worker may compare fields and draft a packet, but must not invent usage, alter an invoice, decide contract meaning, approve a credit, or release a customer correction.

When sources disagree, show both values and the exact question. A similar customer or adjacent period is not evidence for the current line. If access blocks review, record the search path and route permission through the owner. Close with traced, held, or owner-pending status and preserve later events.

### Control points

  • Preserve invoice versions and identifiers.
  • Map every line to an evidenced event.
  • Show aggregation and rounding effects.
  • Separate preparation from release authority.
  • Keep unsupported lines visible.
  • Retain rejected candidates.
  • Link replacements to originals.
  • ## Operating notes

+1. Write the operating purpose in one sentence before naming a metric, because a number without a decision context can invite the wrong action.

+2. Use the smallest stable identifier available and record where it came from, while keeping unnecessary personal or account details inside approved systems.

+3. Preserve the source wording beside any summary so a later reviewer can distinguish an observed fact from a preparer's interpretation.

+4. Record the date an event occurred, the date it was received, and the date it was reviewed when those moments have different operational meanings.

+5. State the timezone and business-day convention before comparing records created by people or systems working in different locations.

+6. Keep a missing source separate from a source that was not searched, and keep both separate from a source that was found but access-limited.

+7. Describe a calculation with its inputs and formula so another specialist can reproduce it without trusting an unexplained remainder.

+8. Do not borrow a field from a similar record merely because the target record is incomplete; similarity is a search clue, not evidence.

+9. Give every exception a named owner and one bounded question, rather than sending a broad request that hides several unrelated decisions.

+10. Set a next review date that follows the evidence or deadline, and record why that date is appropriate to the source.

+11. Use a carry-forward state when work is incomplete at a cutoff, and preserve the reason instead of counting it as silently finished.

+12. Retain rejected candidate matches because they explain why a plausible alternative was not accepted by the reviewer.

+13. Keep preparation, approval, posting, correction, communication, and release as distinct events in the record.

+14. Make clear which role may inspect, calculate, draft, approve, change, or communicate each part of the workflow.

+15. Treat a later event as an addition to history; do not erase an earlier observation simply because the current state looks cleaner.

+16. Compare periods only after checking that the source population, filter, definitions, and exclusion rules are materially the same.

+17. Report excluded, duplicate-risk, access-blocked, and unresolved items beside completed items so the denominator remains understandable.

+18. Explain a changed category or filter before describing a lower queue count as improvement or a higher count as deterioration.

+19. Use a specific exception status that tells the next person what evidence is missing and what action is permitted next.

+20. Do not use a generic pending label when the queue is waiting for different people, sources, or decisions.

+21. Preserve the source path and capture time for portal checks, exports, correspondence, and generated reports.

+22. Limit copied information to what the next reviewer needs, particularly when a working note could otherwise expose protected data.

+23. Route permission questions through the approved owner path and never use another person's account to complete a check.

+24. Keep a version link when a report, invoice, claim, statement, or source document changes after the first review.

+25. Record the exact event that caused a row to reopen, rather than describing the reopening as a general correction.

+26. Close a row only when its approved result, documented hold, or accountable carry-forward is visible.

+27. Use a short final reconciliation to prove that the opening population did not lose records between intake and disposition.

+28. Review a sample of completed rows for source traceability, boundary compliance, and clear next action before trusting an aggregate measure.

+29. Escalate contradictions early, because a confident summary built on conflicting sources is harder to repair than an explicit unresolved state.

+30. Make the handoff useful to a new shift: source, current state, evidence, owner, question, deadline, and next review should be findable together. ## Additional review note

Lineage review also needs a stated stopping rule. Stop when the source is unavailable, the identifier conflicts, or the proposed change would require contract interpretation. Record the stopping point and route the question rather than extending the search indefinitely. When a line is supported, retain the source reference and comparison date. When it is not supported, retain the evidence of the gap. This makes a later owner decision efficient without pretending that preparation established billability.