An audit trail should record who did what, to which record, when, and what changed: before and after values for rates, approvals, declines, payouts, role changes and terms acceptances. The goal is to settle a dispute months later without relying on anyone's memory. Skip noise that no one will ever need to reconstruct.
Six months after a rate change, a partner writes in. They believe they were promised 25% and have been paid 20%. You remember the call. You do not remember whether anyone updated the rate, who did, or whether the change applied to existing partners. This is the moment an audit trail either saves an afternoon or leaves you guessing.
What is the one test every entry should pass?
A record is worth keeping if someone, months from now, might need it to answer the question "who did this, and why?" That test removes a lot of noise. You do not need to log that someone looked at a dashboard. You do need to log that someone changed what a partner earns.
Each entry needs at least the person (or the system, the API key or the integration that acted), the action, the record it touched, the time, and the values before and after. Without the before value you can see that a rate changed but not what it changed from, which is half the answer.
Which events belong in the log?
Group them by what could go wrong.
Money rules: creating, editing or deleting a commission trigger, a tier, a product-level condition or a limit. These decide what you owe. A change made on the 14th that applies to sales from the 1st is a classic source of confusion, so the log should show when a change was made, not only when it takes effect.
Money decisions: approving or declining a commission, in bulk or one at a time, and the reason given. Reopening one that was declined. Invoice review and any adjustment before the monthly charge. Refund-related voids and clawbacks, including who accepted a suggested clawback and who overrode it. For why this matters, see how refunds and clawbacks should work.
People and access: roles assigned or removed, permissions changed, new users invited, API keys created or revoked. When a team member leaves, you want to confirm what they could reach and what they did in their last month.
Partner status: application approved or declined, partner suspended, removed or restored, and any manual attribution override. A partner who disputes a removal will ask for the date and the stated reason.
Legal acceptances: which version of the terms each partner accepted, when, and from what account. This one deserves a separate paragraph.
Why are terms acceptances different from other log entries?
Most log entries record what your team did. An acceptance records what a partner agreed to, and it may need to survive a disagreement with someone outside your company.
Suppose you prohibit bidding on your brand in version 3 of your terms, and a partner claims they never saw it. The useful record is not "terms updated." It is the exact text of version 3, the date it was published, and a record that this partner accepted it at a stated time. That is what an acceptance certificate is: the evidence that a specific person agreed to specific words. Affiliate Tabs issues one for signed program terms. Writing terms that partners will actually read helps with the other half, which is making sure they understand what they accept.
What makes an audit trail trustworthy?
A log that anyone can edit proves very little. Three properties matter.
- Append-only. Entries are added, not rewritten. A correction is a new entry that refers to the old one.
- Attributed. Every entry points to an identity. Shared logins defeat the whole idea, so give each person their own seat and role.
- Complete for the events that matter. A log that records approvals but not rate changes will always be missing the entry you need.
Roles and permissions are the other half of control. A log tells you who did something after the fact; a role stops the wrong person from doing it in the first place. Letting the person who creates partners also approve their commissions is a common arrangement in small teams, and it works until the day it does not. If you can separate the two, even by giving finance the approval permission and partner management to someone else, do it.
How long should you keep it, and what should you leave out?
Retention depends on tax rules, contract terms and whatever your counsel says applies to you, so ask your accountant and your lawyer for a number instead of choosing one yourself. Longer is usually safer for records about money and agreements.
Leave out what no one will ever need to reconstruct: page views, searches, filter changes. A log full of noise is harder to search and tempts people to stop looking at it. It also means storing more about people than the purpose requires.
Personal data deserves a thought too. A trail that records who did what inevitably names people, so treat access to it as sensitive, and check privacy rules that apply to your staff and your partners.
How do you use the log in a dispute?
Work backward from the question. For "why was I paid less," find the trigger or tier that applied on the date of the sale, then the commission record, then any edits to either. For "why was I removed," find the status change, the reason, and the notes made at the time. For "I never agreed to that," find the acceptance record.
When you share an answer, share the facts and not the whole log: dates, values and which clause applied. Partners do not need to see who on your team clicked what, and your staff do not need to be named in a partner's email.
Pair the log with the program-level numbers you review anyway. A single odd entry matters more when you see it beside a spike in declines or a jump in one partner's earnings. Which partner program metrics matter covers those.
If you want the log built in, Affiliate Tabs includes an audit log alongside roles and permissions. If you run the program from spreadsheets today, a change log tab with a name, a date, and before and after values gets you a surprising distance.
Common questions
- What is an audit trail in a partner program?
- It is an append-only record of actions taken in the program: who made the change, what it was, when, and the values before and after. You use it to answer questions such as who changed this commission rate, or why this commission was declined.
- How long should I keep audit records?
- Long enough to cover disputes, tax questions and any contract or legal retention period that applies to you. Ask your accountant and counsel for the number. Keeping records is cheap; reconstructing them is not.
- Do I need an audit log if only two people use the program?
- Less urgently, but yes, for money decisions. Even two people forget who changed what. The log matters most when a partner disputes a payment, when a team member leaves, or when you add staff and need to see who did what.
- What does the Affiliate Tabs audit log cover?
- Affiliate Tabs keeps an audit log alongside roles and permissions, and signed program terms come with acceptance certificates. The log is there for reconstructing who changed what and when; it is not a substitute for your own written policies.