Keep a Commercial Covenant Conversation Grounded

A CFO who sees a changing covenant calculation often seeks an immediate interpretation from a commercial banker. A conclusion belongs with the approved review. The banker’s first job is to organize a clear conversation around facts, documents, ownership, and timing. Ask what changed in operations, whether finance reconciled underlying reports, and when a complete reporting package will be ready. Seasonal inventory, a late close, or an accounting adjustment often need context before any review begins.

Process clarity helps a CFO move forward without mistaking preparation for a decision. Explain confirmed submission timing. Identify where reports should go. Name the contact responsible for updates. Do not interpret agreement terms or state what the bank will decide. A careful response keeps the discussion useful even when the financial conclusion is pending. The customer needs a dependable path for preparing material and receiving the next communication.

In a fictional practice situation, Maya is CFO of a regional distributor. Her finance team sees a changed figure after an adjustment near year end. During a call, Maya asks her commercial banker, Andre, “Does this mean we are out of compliance?” Andre replies, “I cannot make a determination here. Please include the adjustment, the related reports, and supporting records for the review team.” His answer avoids a conclusion while giving Maya a concrete action.

Andre follows with questions about the adjustment. What entry changed? Which report first showed the difference? Has the finance team reconciled the report to its source records? Who prepared the adjustment explanation? When will the reporting package be complete? Each question has a purpose. Maya explains an inventory count finished after the initial close. Her controller updated an entry after reviewing count records. The team expects a completed package on the ninth business day of the next month.

Andre does not decide whether Maya’s explanation changes a covenant result. He records a neutral description from Maya. He records the controller as owner of the supporting explanation. He records the expected reporting date as a customer estimate. Then he explains how Maya should send the package through their established process and who will acknowledge receipt. A written follow up should repeat confirmed process details, not untested analysis from the call.

The distinction between a fact and an interpretation matters. “The finance team posted an inventory adjustment after the initial close” is a reported fact. “The adjustment resolves the covenant concern” is an interpretation. The banker should preserve the first statement in notes and leave the second question for approved review. This approach prevents a hurried phrase from becoming a mistaken promise in a later email or meeting.

A complete package usually needs more than a single figure. The finance team should decide which reports and explanations belong together under its existing reporting process. A bare figure often creates basic follow up questions: What period does this cover? Which source records support a change? Who prepared the report? Maya’s controller owns answers about finance records. Andre owns clear communication about submission and the next update point. Each person contributes without crossing into an underwriting conclusion.

Timing deserves careful language. Ask when reports will be complete, then ask when the customer expects to send them. Those dates sometimes differ. Maya might finish reconciliation on a Tuesday and send the package on Thursday after an internal review. Andre should write both dates if Maya provides them. He should avoid describing either date as an approval deadline unless an approved owner has confirmed one. A precise timeline prevents unnecessary alarm.

The banker should also ask who needs to receive updates inside the customer organization. Maya might want her controller copied on a receipt notice. Her chief executive might only need an update after the review team responds. Names and communication preferences reduce confusion. Do not assume every internal participant needs every document. Ask Maya who will coordinate questions and who should receive status messages.

In the fictional distributor example, Maya says the controller will gather records, while she will provide a plain operating explanation. Andre asks her to separate confirmed facts from business expectations. Maya writes: “Inventory counts concluded after the initial close. The controller reconciled resulting adjustments to count records.” She avoids a prediction about the review result. Her operating explanation gives the review team a starting point for any follow up without presenting a requested conclusion as settled.

Pressure often appears through informal questions. A CFO says, “Between us, does this look fine?” A banker should use the same disciplined response as in a formal meeting. “I cannot give a conclusion before approved review. I will help confirm what your team plans to submit and when you should expect the next update.” Repeating a clean boundary once is enough. Move promptly into the information needed for the process.

Written records need similar care. After Maya’s call, Andre sends a brief note: “Maya expects a reporting package, including an adjustment explanation and supporting records, by the ninth business day next month. The controller will coordinate source records. Please send material through the established reporting channel. I will confirm receipt and share the next update point.” The note does not say the package is complete until receipt. The note does not suggest an outcome.

Coaching should look for accidental interpretations hiding inside helpful language. “You should be fine” is an assurance. “This adjustment fixes the issue” is a conclusion. “The review team will approve this” is a promise. Replace those phrases with a question about documents, an owner for an explanation, or a date for a status update. The banker’s value comes from helping customers produce a coherent record and understand what happens next.

Suppose Maya’s controller calls two days later and says a supporting report will arrive late. Andre asks for the revised expected date and who will send the report. He updates Maya’s contact record with the customer provided timing. He does not speculate about effects on a review. He explains any confirmed submission logistics and states when he will check whether the full package has arrived. The conversation stays calm because each next action belongs to a named person.

For practice, use Maya’s situation. Start with her question about compliance. State the limit in one sentence. Ask what changed, which report supports the change, who owns reconciliation, and when the complete package should arrive. Then write a follow up using only confirmed details. Remove any phrase predicting a decision. Read the note as though a review teammate will see no context beyond your words.

On the ninth business day, Maya sends the package through the established channel. Andre confirms receipt to Maya and her controller, then records the submission time and the name of the review contact. His next message tells Maya when he expects to provide a status update, using only timing confirmed through the process. He sets a calendar reminder for the date, opens the customer record, and adds one question for his next contact: whether any further documentation request has reached Maya’s team.