> ## Documentation Index
> Fetch the complete documentation index at: https://agencykey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sales
> Review sales, correct employee credit, and submit or review attribution proposals
Open **Employees → Sales** to review individual sales and who receives reporting credit. With personal access, the page is titled **My sales**.
Sales credit in AgencyKey does not transfer money or change the fan's payment or the model's OnlyFans payout. Access depends on your role's Sales permissions and data scope, including for managers.
## Find a sale
Choose a **Period** of up to **366 days**. Dates use the agency's reporting time zone; the initial period is the current month. Available filters include **Models**, **Employees**, **Category**, **Status**, and **Fan**. Fan search accepts **Name or OnlyFans id**. Use **Credited to nobody** for unattributed sales or **Changed manually** for manual changes.
Model and employee selectors depend on separate list access. Personal scope hides the employee filter. **Reset** clears the filters.
| Column or status | Meaning |
| - | - |
| **Gross / Net** | Full sale amount / amount after the OnlyFans 20% fee |
| **Credited to** | Employee or employees receiving credit; a split row still shows the full sale amount, with your share separately |
| **Attribution** | **By settings** or **Manual** |
| **Confirmed** | Confirmed sale |
| **On hold at OnlyFans** | Sale still on hold; it is already included in the displayed result |
| **Refunded** | Refunded sale, crossed out and excluded from the total |
Categories include tips, paid messages, subscriptions, resubscriptions, paid posts, streams, and other sales. Summary totals cover all pages of the filtered result. **Credited to you** uses your own share rather than the full amount of a split sale.
## Correct reporting credit
### 1. Check your access and select the sale
Your role needs **Sales → Reassign** in the relevant data scope. Click **Credited to** in the sale's row. For several sales, select their checkboxes and use **Credit to…**.
\[Screenshot pending: sales filters, Credited to cell, and bulk action]
The header checkbox selects the current page. Changing the page, filters, or sort clears the selection. Viewing one share of a sale does not necessarily allow changing the whole split: all current participants must fall within your reassignment scope.
### 2. Choose the attribution
Use **To one**, **Split between several**, or **Credit to nobody**. Add any explanation with **Add a comment** before selecting a single employee: that choice applies immediately.
\[Screenshot pending: attribution choices and comment]
A split accepts **2–10 different employees**. Use equal shares or enter percentages totaling **100%**. Each entered share must be between **0.01% and 99.99%**; blank shares receive the remainder equally. Comments accept up to **500 characters**. Review the allocation before applying it.
With **Own Data Only**, reassignment does not let you claim someone else's or an unattributed sale, or create a split. Removing your own credit can also remove your access to the sale and the ability to undo the change. Read the warning first.
### 3. Review the result and history
Check **Credited to** and **Attribution** after the change. The history control next to **Manual** opens **Changes of the sale**, with the employee, time, previous and new shares, and available comment. Older changes may have no history entry.
\[Screenshot pending: updated attribution and sale history]
Use Sales to inspect the recorded allocation. Some Employee and Creator Analytics views still count paid-message earnings by the sender, so they may not reproduce the same split. Do not assume that every report will reconcile to the allocation shown here.
## Propose credit to yourself
A proposal is a request for review; it does not change attribution immediately. Your role needs the separate **Sales → Propose changes** permission, as well as access to the section. It is not automatically granted to every manager or existing role.
### 1. Open the model's sales
Use **Sales of my models** and find an eligible sale from a model currently assigned and accessible to you. **Credited to me** shows your current credit; users with broader scope see **All sales** instead. **My proposals** shows your requests.
\[Screenshot pending: Sales of my models and proposal tabs]
### 2. Prepare and send a proposal
Click **Propose** under **Credited to**. Choose **All to me** or **Split with others**; you remain a participant in a proposed split. Review the percentages and optional explanation, then select **Send for review**.
\[Screenshot pending: proposal shares, explanation, and Send for review]
Refunded sales, sales changed manually, and sources whose effective rule credits **Not attributed** cannot receive proposals. An automatic attribution rule can still allow a proposal. A sale already credited entirely to you cannot be proposed **All to me** again, but a split can be proposed.
### 3. Track, change, or withdraw it
Statuses are **Under review**, **Approved**, or **Rejected**. Hover the status for the proposed shares and available decision details. While pending, use **Change the proposal** or **Withdraw the proposal**. A new submission replaces your pending proposal for that sale; withdrawn proposals are hidden.
\[Screenshot pending: proposal status, change, and withdraw actions]
## Review employee proposals
A reviewer needs **Sales → Reassign** covering the sale and participants. Turn on **Proposals to review**, inspect the proposal and sale context, then use **Approve** or **Reject**. A rejection can include an optional reason visible to the employee.
Approving one proposal rejects other pending proposals for the same sale. Bulk approval applies to selected sales with a single pending proposal; competing proposals need individual review. Bulk rejection does not ask for a reason. If access, sale state, or attribution changes, a proposal may no longer be eligible; refresh and review the current state. Manual reassignment closes pending proposals.
## Read context or open sales from a shift
**Chat** opens a read-only view of messages up to the sale. It is not the working composer. You need access to the sale, the current model, and its messages.
In [Shift History](../shifts/history), an accessible sales amount opens this journal with a **Shift** filter and that row's period and categories. **Show the whole period** removes that filter. Shift editing permission does not grant Sales reassignment.
## Common issues
* **Sales or an action is missing:** ask the Owner to check the separate view, reassignment, and proposal rights and their data scope.
* **A proposal is unavailable:** check current model assignment, refund/manual state, and the effective [Sales Settings](../sales-settings/index) rule.
* **A chat action is missing:** Sales access alone does not grant message access.
* **Figures differ from another report:** check full amounts versus your share, refunds, dates, and that report's attribution rules.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.