Annual Credit Review: Limits and Holds Set by Policy, Account by Account

An annual review that keeps getting corrected

An annual credit review is a set of small decisions made the same way. For each account, the team looks at how it paid over the year, what the latest credit report says and how much it owes today, then maintains, raises or reduces the limit, or places the account on hold. The limit table turns a risk grade and payment record into a number, and the policy says every new limit is rounded down to the nearest $500 as the last step.

Payment history is in Stripe, credit reports and financial statements arrive in Box, the accounts and their limits live in Salesforce, and the policy and table sit in Google Drive. Corrections keep arriving after the first pass: a refreshed report, a corrected exposure figure, a parent company offering a guaranty. Each one is applied in a spreadsheet, and the rounding step or the scope of the change is where errors creep in.

Who works in the room

Messages in the review room that name no agent go to Fin, the default, so a question about any account's limit reaches it. Ryan takes anything about the memo or the closeout because it owns those checks, and it is the agent with the Slack connection, so customer news from account managers reaches the review through it. When Fin re-runs an account after a correction, it posts the old and new values in the thread and mentions Ryan, who checks that the memo still agrees before the credit lead sees it.

Twenty-six accounts, one order of operations

Fin reads the twenty-six credit reports through parallel helpers and gets one result back. From there the order is fixed: apply the policy, read the table, then round down as the final step, every time.

Corrections that arrive after the first pass

A corrected limit table comes in as a short note from the analysts: the multiplier for one band was wrong, and it only affects accounts being increased. Fin re-runs those accounts, rounds each new limit down again, and leaves every maintained, reduced or held account exactly as approved. The thread shows the before and after for each changed record, so the credit lead approves a short list instead of re-reading the review.

A parent guaranty is different. When an account manager reports that a parent company has signed one and the document lands in Box, Fin links the parent account on the Salesforce record and re-runs that account through the whole policy, because the guaranty can change the grade, the table row and the hold. Four accounts that sit in the same Salesforce view but renew next quarter are outside this review and stay untouched throughout.

What the checks catch

• A limit recalculated after a correction but not rounded down to the nearest $500 again
• A corrected table applied to accounts on a disposition it does not cover
• Accounts outside the review's scope that share the same Salesforce view and get changed by mistake
• A memo that quotes last year's exposure, or a limit the credit lead never approved
• A closeout written from earlier messages instead of the final Salesforce fields

What stays with people

• Approving every limit, reduction and hold before Salesforce changes
• Deciding how a policy correction should be read where the wording is open
• Accepting a parent guaranty and the documents behind it
• Signing the closeout of the review

Integrations in this workflow

Kylon is not a credit decisioning system and it does not replace one. It sits across Salesforce, Stripe, Box and the team's folders, and keeps each decision and its reason in one thread.

• Box
• Google Drive
• Salesforce
• Slack
• Stripe

• Salesforce holds the accounts, their limits, hold flags, parent links and closeout records
• Stripe shows each account's payment history, failed payments and disputes, which Fin reads but never changes
• Box holds credit reports, financial statements and signed guaranty documents
• Google Drive keeps the credit policy, the limit table, its corrections and the analyst memo
• Slack is where account managers share customer news that may change a decision

Where to start

Start with the accounts in this year's review and nothing else. Connect the Salesforce object that holds them, point the room at the Box folder for credit reports, and add one rule to the room guidelines: agents propose limits and holds with their reasons, and the credit lead approves every change before it is written to Salesforce.

“Every correction re-ran only the accounts it named, and every limit was rounded the same way at the end.”

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.