
Build a records retention index for accounts payable
How to approach: Build a records retention index for accounts payable
A records retention index should tell the team what to keep, where it lives, and when it can be destroyed. Start with the record types the team actually creates. A policy that lists every record in the company is too broad to use. Name the owner in the same line as the action.
Record the owner and the system for each record type. A retention period without a location is hard to apply. The index should be usable by the person who cleans up the shared drive. Write the deadline as a date and a local time.
List the record types
List the invoices, the payment runs, the vendor packets, the approvals, the statements, and the correspondence. Include the records that live in email and the shared drive. A record type that is not listed may be kept forever or deleted too early. Update the template when the same question appears twice.
Group the records by the process they support. A payment run record and an invoice record may have different retention periods. The grouping should match the way the team works. Keep the evidence with the record rather than in a separate log.
Record the owner and the system
Name the person who owns each record type and the system where it is stored. A record with no owner is likely to be duplicated or lost. The owner should know the retention rule. Write the deadline as a date and a local time.
Record the access controls for sensitive records. A vendor bank-detail form should not be in an open folder. The index should show the sensitivity and the approved recipients. Record the date and the source so the next reviewer can repeat the check.
Set the retention and disposal rule
Record the retention period and the trigger that starts it. The trigger might be the end of the fiscal year or the end of the contract. A period without a trigger is ambiguous. Keep the evidence with the record rather than in a separate log.
Record the disposal method and the approver. A deletion should be documented. The index should not allow a record to be destroyed without a named approval. Keep the evidence with the record rather than in a separate log.
Test the index on one record type
Pick one record type and follow it from creation to disposal. Check that the location, the owner, and the retention rule match. A mismatch is a finding about the index, not just the file. Keep the boundary visible in the place where the work is assigned.
Update the index after the test. A short test is more useful than a long policy review. The goal is an index the team can actually follow. Separate what was observed from what was assumed.
Review the index annually
Review the index with the record owners and the legal or compliance contact. Update the retention periods when the requirements change. Record the review date and the approver. Review the first few notes together before the process expands.
Keep the old index versions. A later review may need to see what the rule was at the time. The history is the evidence that the retention program was controlled. Keep the evidence with the record rather than in a separate log.
This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.