--- title: "Gifts and Entertainment Register Review | Kylon" description: "How a compliance team reviews its quarterly gifts and entertainment register, tracks totals per counterparty and tender windows, and keeps every status with a person." url: "https://kylon.io/use-cases/gifts-and-entertainment-review" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Gifts and Entertainment Review: A Quarterly Register That Adds Up by Counterparty Use Case7 min read # Gifts and Entertainment Review: A Quarterly Register That Adds Up by Counterparty The quarterly gifts and entertainment review runs in one Kylon room. Agents check each Notion declaration against Outlook pre-approvals, tender windows on Google Calendar and running totals per counterparty, and a compliance officer sets every final status. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Declarations that look fine one at a time Most gifts and entertainment declarations are small and routine. The review gets hard where items interact: three lunches from the same broker that pass the quarterly limit together, a gift from a counterparty that is in a live tender, an item above the limit whose pre-approval sits in a department head's mailbox. The policy is clear on each of these. Applying it across a whole quarter of declarations is where things slip. Declarations sit in a Notion register. Pre-approvals are emails in Outlook, tender windows are on the procurement team's Google Calendar, staff send questions to the compliance inbox in Gmail, and the policy lives in Google Drive. A late value correction, or a counterparty reclassified as a public official, changes the status and the hold reason, and those changes rarely reach every place they should. ## Who works in the room People - Compliance officer Owns the quarterly review, sets every final status and signs the department pages - Department heads Pre-approve declarations above the limit and answer follow-up questions - Procurement lead Keeps the tender calendar and confirms which counterparties are in a live tender - Internal audit Requests the audit extract and reviews it Agents - NovaRegister reviewer Reads each declaration in Notion, matches it to its Outlook pre-approval and the tender calendar, and proposes a status with its reason [Notion](https://kylon.io/integrations/notion)OutlookGoogle CalendarGoogle Drive - MycoTotals and extracts Keeps the running totals per counterparty, builds the audit extract and drafts the department closeout pages [Notion](https://kylon.io/integrations/notion)Google Drive - FinStaff correspondence Drafts replies to staff questions and pre-approval follow-ups for a compliance officer to send [Gmail](https://kylon.io/integrations/gmail)Outlook[Slack](https://kylon.io/integrations/slack) The compliance team keeps one room for the register. Nova is the default agent, so a question about a declaration's status goes to it. Myco owns the counterparty totals and the audit extract, so a question about either reaches Myco without anyone naming it. When Nova changes a status, it hands the affected counterparty to Myco in the thread, so the totals and the department pages stay in step. Every agent turn that uses a tool keeps a step-by-step run history, which is what internal audit asks to see. ## Inside a quarterly review Withdrawn declarations are out of scope at every step. The room guidelines say so, and the agents leave those rows exactly as they are. ```mermaid flowchart TD reg([The quarter's declarations
sit in the Notion register]) withdrawn([Withdrawn declarations are
left exactly as they are]) status["Nova checks each declaration against
the limit, pre-approval and tenders"] ok1["Compliance officer approves every
status before Notion changes"] totals["Myco totals each counterparty for
the quarter, item by item"] extract["Myco builds the audit extract
from the current register"] release["Compliance officer releases it,
internal audit accepts it"] change([A committee memo, a corrected value
or a reclassified counterparty]) rerun["Nova re-runs the status and
hold reason for each item it covers"] rebuild["Myco rebuilds the totals
for that counterparty"] reply["Fin drafts a reply on the
employee's own Gmail thread"] ok2["Compliance officer approves each
change and sends the reply"] pages["Myco drafts one page per department,
even those with no escalations"] sign["Compliance officer signs each page"] reg --> status withdrawn -.- status status --> ok1 --> totals --> extract --> release --> rerun change --> rerun rerun --> rebuild & reply rebuild & reply --> ok2 --> pages --> sign class status,totals,extract,rerun,rebuild,reply,pages agent class ok1,release,ok2,sign person class reg,withdrawn,change event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Status pass | Each live declaration is checked against the value limit, its Outlook pre-approval and the tender calendar | Nova | The compliance officer approves every status before Notion changes | | Cumulative report | Totals per counterparty for the quarter, listing every item that counts toward each | Myco | The compliance officer reviews counterparties at or over the limit | | Audit extract | The rows internal audit asked for, built from the current register | Myco | The compliance officer releases it and internal audit accepts it | | Policy memo | A clarification from the compliance committee is applied to the declarations it covers | Nova | The compliance officer confirms the reading | | Value and type corrections | A corrected value or a reclassified counterparty re-runs the status, the hold reason and the totals | Nova, then Myco | The compliance officer approves each change | | Closeout | Five department pages in Notion, including departments with no escalations | Myco | The compliance officer signs each page | Stages of a quarterly gifts and entertainment review. Declarations, counterparties and values in this example are illustrative. ## Corrections that ripple through the register A value correction looks like one number. A dinner first declared per head is restated as a total for the table, and the new figure pushes that counterparty past the quarterly limit. Nova re-runs the declaration and proposes a new hold reason, and Myco updates the counterparty's total along with every other item that now counts toward it. Fin drafts a reply on the employee's own Gmail thread with the assessed value in dollars, and a compliance officer sends it. A reclassification reaches further. When a counterparty is reclassified as a public official, the lower limit for that type applies to every item from it this quarter, not just the one that prompted the change. Nova lists each affected declaration with its old and new status, Myco rebuilds the totals, and nothing moves in Notion until the compliance officer approves. ## What the checks catch - Withdrawn declarations edited along with live ones because they share a counterparty - A gift that clears on value but comes from a counterparty inside a live tender window - Counterparty totals that pass the limit only when several small items are added together - A value correction that changes the status but leaves the old hold reason or the old total in place - A closeout with four department pages because one department had nothing escalated ## What stays with people - Setting the final status of every declaration in Notion - Sending every reply to staff, which Fin prepares as a draft in Gmail or Outlook - Reading a committee memo where the wording leaves room for doubt - Signing the five department pages at closeout ## Integrations in this workflow Kylon is not a compliance case system and it does not replace one. It connects to the register, the mailboxes and the calendar the team already keeps, and holds the review between them. - [Gmail](https://kylon.io/integrations/gmail) - Google Calendar - Google Drive - [Notion](https://kylon.io/integrations/notion) - Outlook - [Slack](https://kylon.io/integrations/slack) - **Notion** holds the declarations register and the department closeout pages - **Outlook** holds the pre-approval emails from department heads - **Google Calendar** carries the tender windows that procurement keeps current - **Gmail** is the compliance inbox for staff questions, answered through drafts a person sends - **Google Drive** keeps the policy, the committee memos and the audit extract - **Slack** is where procurement posts tender changes and department heads answer quick questions ## Where to start Take one quarter's register. Connect Notion, give Nova a lasting grant to read the pre-approval mailbox, approved by the mailbox owner, and put one rule in the room guidelines: agents propose a status and a reason for every declaration, and a compliance officer approves before anything changes in Notion. > “The totals move whenever a value moves, so the hold reason and the number always agree.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our gifts and entertainment review desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail, Google Calendar, Google Drive, Notion, Outlook and Slack. Tell me which ones still need connecting, including the lasting grant to read the pre-approval mailbox approved by the mailbox owner. 2. Ask me who works this desk: the compliance officer, the department heads who pre-approve declarations, the procurement lead who keeps the tender calendar and internal audit who requests the extract. Help me invite them to this Room. 3. Build a Gifts Register App with columns Declared, Under review, Escalated and Cleared, one record per live declaration. Pull from Notion and leave every withdrawn row exactly as it is. 4. Check each live declaration against the value limit, its Outlook pre-approval and the tender window in Google Calendar. Add up totals per counterparty across the full quarter. Propose a status and a reason for each and show me the ones that need a closer look. 5. Draft replies to staff as drafts in Gmail or Outlook. The compliance officer approves every status before Notion changes, reviews counterparties at or over the threshold we set, releases the audit extract and signs each department closeout page. 6. Write our rule order and who approves what into this Room's guideline so every quarterly review follows it. 7. After one clean quarter, offer to turn the status pass into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Annual Credit Review: Limits and Holds Set by Policy, Account by Account Twenty-six credit accounts, one limit table and a steady stream of corrections. Agents in one Kylon room read Stripe payment history and Box credit reports and propose each limit and hold for Salesforce, and the credit lead approves every change before it is written. Financial servicesFinance operationsApprovals & reviews ](https://kylon.io/use-cases/customer-credit-review)[ ### Insider Trading Preclearance: Clearances That Respect Tier, Blackout and Restricted List Personal trade preclearance requests are reviewed in one Kylon room. Agents check each requester's insider tier in Outlook, blackout windows on Google Calendar and the restricted list, and a compliance officer issues every clearance. Financial servicesCompliance & riskApprovals & reviews ](https://kylon.io/use-cases/insider-trading-preclearance)