This research is general operational information, not legal, tax, accounting, employment, benefits, privacy, cybersecurity, insurance, or financial advice.

Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how old open vendor credit memos are at month end. The result would describe the credit memo queue, not the vendor's intent. Name the owner in the same line as the action.
The protocol does not measure whether the credit was valid. It measures whether the credit was applied or left open with an owner. Name the owner in the same line as the action. Use the same format for every handover so the next reader can scan it.
Population and unit of analysis
Define the population as vendor credit memos open on a stated date. The unit is one memo, with the vendor, the amount, the receipt date, and the application status recorded. If the source is unclear, route the question instead of guessing. Ask whether a new reviewer could act on the record without a conversation.
Link the memo to the invoice or account it affects. Write the deadline as a date and a local time. Use the same format for every handover so the next reader can scan it. Review the first few notes together before the process expands.
Definitions and measures
Define age as the working time between receipt and the review date. Define application as the credit being recorded against the correct invoice or account. If the source is unclear, route the question instead of guessing. Separate what was observed from what was assumed.
Report the age distribution and the share of memos older than the review window. Keep the original note beside the corrected version. Write the deadline as a date and a local time.
Evidence standard
Link each memo to the vendor document and the approval. A note that says credit received is not evidence of a valid credit. Record the exception and the person who approved it. Ask whether a new reviewer could act on the record without a conversation.
Keep the original memo and the application record. A later correction should not erase the first date. Keep the boundary visible in the place where the work is assigned. Test the rule on one real transaction before applying it to the run.
Sampling and collection
Use a census of the open memos. If sampling is necessary, stratify by vendor and amount. Select the sample before reviewing age. Ask whether a new reviewer could act on the record without a conversation.
Pilot the review on a few memos and compare the reviewers. Clarify how a disputed credit is treated. A control that depends on memory is not yet a control. Review the first few notes together before the process expands.
Analysis and reporting
Report the age distribution by vendor and amount. Show the memos that have no owner. A long tail is the risk. A control that depends on memory is not yet a control.
Present the results as a description of the queue, not a judgment about the team. Separate what was observed from what was assumed. Keep the original note beside the corrected version. A control that depends on memory is not yet a control.
Limits and sources of error
The memo may have been applied but not recorded. State the evidence used. A control that depends on memory is not yet a control. Name the owner in the same line as the action.
The review date may be after a month-end close, which can change the age. Record the date. Update the template when the same question appears twice. A short note with four fields is easier to use than a long narrative.
Review cadence
Repeat the review after a process change or at the same interval each month. Compare the same age bands. Keep the evidence with the record rather than in a separate log. Write the deadline as a date and a local time.
Assign the follow-up to the AP lead and set a date. The protocol should produce a specific decision about the credit memo rule. Name the owner in the same line as the action. Record the date and the source so the next reviewer can repeat the check.