commit
3cde3e5e72
1 changed files with 158 additions and 0 deletions
@ -0,0 +1,158 @@ |
|||
<br>Learning how to back up accounting data securely before a loan review means freezing a clean copy of your books, protecting it properly, and proving you can restore it. Done well, the lender gets complete, dated files, your team answers questions without rebuilding anything, and nobody has to guess which spreadsheet is the current one.<br> |
|||
|
|||
What a loan review will actually ask for |
|||
|
|||
<br>First things first: a loan review is a request for evidence, and the request list changes from lender to lender. Some want several years of annual statements. Others focus on the trailing twelve months and a current balance sheet. Ask for the list in writing before you touch any file, because a backup built for the wrong period wastes days.<br> |
|||
|
|||
<br>Most requests fall into a few families. There are financial statements and the general ledger detail behind them. There are bank and card statements that tie to the cash balance, and accounts receivable and payable agings. Debt schedules, covenant calculations and the forecast that supports repayment usually come next. Tax returns, payroll summaries and revenue schedules round out the list. If your customers pay on multi-year terms or milestones, the revenue schedules matter more than people expect, because ASC 606 ties the timing of revenue to performance obligations, and a lender will test whether the numbers hold together.<br> |
|||
|
|||
<br>Here is a hypothetical example. A company with a bank line of credit, two payment processors and an outside payroll provider receives a request for two years of monthly statements plus a current aging. If the team exports only the general ledger, it misses the bank-level detail the lender will compare line by line. The fix is to write the request list first, then assign each family to a source.<br> |
|||
|
|||
<br>Pay attention to the wording of the request too. "Monthly statements" can mean internal management reports or statements issued by a third party. "Audited" and "reviewed" are different levels of assurance, and a lender may reject a set that mislabels them. Confirm which version you have, when it was finished and who approved it. A backup that stores the wrong version is still a wrong backup.<br> |
|||
|
|||
<br>Think about the period too. A loan that closes mid-year may need interim statements that line up with the most recent month-end, not the last fiscal year-end. Write down the as-of dates the lender named. Each date becomes a lock point later, so the backup can show what the books looked like on each one.<br> |
|||
|
|||
<br>Build the request list as a one-page checklist with columns for owner, source, period and status. Keep it in the same folder as the backup, so the record of what was requested travels with the data. This is a short task, and it prevents a problem that comes up often in these reviews: a team that backs up everything and still cannot find the one schedule the lender wants.<br> |
|||
|
|||
Map every place your accounting data lives |
|||
|
|||
<br>Accounting data rarely sits in one system. The ledger may live in QuickBooks, NetSuite or Sage Intacct, but the numbers feeding it come from bank feeds, card processors, payroll, billing tools, a shared drive of invoices, email attachments and the forecast spreadsheet the owner updates on Sundays. A backup of the ledger alone leaves most of the evidence behind.<br> |
|||
|
|||
<br>Start with a map. List every system that creates, changes or stores a number that will reach the lender. For each one, write down who administers it, how data leaves it and whether anyone else holds a copy. This is the most useful document in the whole process, because every gap you find here is a gap that would otherwise surface in the middle of the review.<br> |
|||
|
|||
|
|||
SourceTypical ownerWhat to captureCommon gap |
|||
Accounting platformController or bookkeeperFull company file, trial balance, reports by periodOnly the current-year exports are saved |
|||
Bank and card feedsBookkeeperStatements and reconciliations, as PDF and dataReconciliations not saved after the close |
|||
Payroll providerPayroll administratorPayroll registers and tax filingsAccess held by one person who has left |
|||
Billing or invoicing toolBilling leadInvoice history, aging, credit memosAging saved only as a screenshot |
|||
Shared drive and emailWhoever sent the fileInvoices, contracts, supporting schedulesFiles kept in personal inboxes |
|||
Forecast modelOwner or CFOCurrent and prior versions with assumptionsOverwritten with no version history |
|||
|
|||
|
|||
<br>The common gap column is where the work hides. A screenshot is not a report, and a PDF of an aging cannot be re-run with the same filters. If a source can export data in a usable format, take the export. If it cannot, record the settings used so someone can reproduce the report later.<br> |
|||
|
|||
<br>Email attachments deserve their own step. Many supporting documents, such as signed loan agreements or vendor invoices, exist only as attachments in one person's inbox. Move the originals into the controlled folder, keep their file names and dates, and note in the map where each came from. Do not forward them around to create copies that slowly drift apart.<br> |
|||
|
|||
<br>Include the spreadsheets people treat as informal. The budget model, the cash forecast and the debt tracker often hold the assumptions the lender will question. Save each version with a date in the file name, and keep the assumptions tab intact. A forecast without its assumptions is a set of numbers nobody can defend.<br> |
|||
|
|||
<br>Once the map is done, give it a quick review with whoever administers each system. Ask them what they would need to rebuild their part from scratch. Their answers often reveal a dependency nobody wrote down, such as a payroll tax login that only one person knows or a billing report that depends on a saved filter.<br> |
|||
|
|||
Close the period before you copy anything |
|||
|
|||
<br>Here's the order: close the period, reconcile, lock, then back up. A backup taken while transactions are still being entered is a moving target. The file you save on Tuesday may not match the one you save on Thursday, and a lender will notice when two final copies disagree by a few entries.<br> |
|||
|
|||
<br>Set a cutoff date and tell everyone with posting rights what it is. After that date, changes to the closed period should go through a documented adjusting entry, not a quiet edit. Most platforms let you lock periods or restrict backdated entries. Turn that on, then test it by trying to post to the closed period with a test user, so you know the period lock actually holds.<br> |
|||
|
|||
<br>Reconciliations come next. Bank accounts, credit cards, payroll liabilities, sales tax and loan balances should tie to statements for the same dates. Unreconciled items are not a reason to skip the backup, but each one belongs in a short memo that states the amount, the cause and who is working on it. A lender prefers a known open item to a surprise.<br> |
|||
|
|||
<br>Once the period is locked and reconciled, run the reports the lender will see: trial balance, balance sheet, income statement, cash flow statement and agings. Save them as PDFs and as data exports, with the period and run date in each file name. Record the report parameters, such as accrual or cash basis and any consolidation settings, in the same folder. Two people who run the same report under different settings will produce different numbers.<br> |
|||
|
|||
<br>Last step before the copy: note the timestamp, the person who locked the period and the version of the books. This is the anchor for everything that follows. Without it, you cannot show which numbers the backup represents, and the rest of the process rests on a date nobody can verify.<br> |
|||
|
|||
Pick a backup method and keep a frozen copy apart from working files |
|||
|
|||
<br>A backup is not one thing. A native platform backup captures the application data in its own format, which helps when you need to restore the system. An export captures reports and data in open formats, which are easier to read years later. A frozen archive is a read-only copy of the final package, kept apart from anything people can edit. You need the first two for recovery and the third for the lender.<br> |
|||
|
|||
<br>Use this list to decide what goes into each layer:<br> |
|||
|
|||
|
|||
A native backup of the accounting platform, taken right after the lock and stored with the vendor [What Is A Outsourced Cfo In New York City](https://gitlab.1337.at/hectordriskell/donette2008/wiki/How+to+handle+working+capital+adjustment+disputes+fairly%253F) or on company-controlled media. |
|||
Exports of the trial balance, general ledger detail and subledgers in CSV or Excel, with report settings recorded. |
|||
PDFs of the financial statements and the lender package, approved and initialed by the person who signed off on them. |
|||
A read-only archive of all of the above, with a manifest listing every file and its checksum. |
|||
|
|||
|
|||
<br>Keep the frozen archive apart from working files. If it sits in the same folder as the working spreadsheets, someone will open a file, save over it, and the archive stops being frozen. Use a separate location with write permissions removed for everyone except the archive owner. Many teams use a dated folder inside a document management system, which also records who opened [what is a outsourced CFO in New York City](https://Venturegrowthpartners.com/locations/new-york-new-york-city-outsourced-cfo-services/) and when.<br> |
|||
|
|||
<br>Platform choice is part of this. If your company is evaluating an ERP or a new accounting system, ask the vendor how data exports, how native backups are scheduled, how long history stays available and whether the data can leave the system in a standard format. Those answers tell you more about future reviews than the feature list does. Ask the same questions of your current tools before a review arrives.<br> |
|||
|
|||
<br>Do not rely on one copy. The working system, the native backup and the frozen archive should live in at least two places, and one of them should sit outside the system the team uses every day. This protects against ransomware, accidental deletion and a vendor outage. It also guards against a quieter risk: a single copy becomes the only copy after the person who made it leaves.<br> |
|||
|
|||
Lock down access, encryption and storage |
|||
|
|||
<br>Security is where many backups fail quietly. The files are complete and correct, but anyone with a shared login can open them, and nobody records who did. Lenders care because the backup often holds bank details, payroll records and tax identification numbers, the kind of data that causes real harm when it leaks.<br> |
|||
|
|||
<br>Start with least privilege. Only the people who need the backup should have access, and most of them need read access, not write access. Give the archive owner a separate account from their daily login, require multi-factor authentication on every account that can reach the backup, and remove access as soon as someone leaves. Review the access list before the review starts, not during it.<br> |
|||
|
|||
<br>Encrypt in transit and at rest. Use the encryption built into your storage provider or a file-level tool the whole team can open. Keep passwords in a managed password vault, not in a spreadsheet next to the backup. Avoid sending the package by personal email or messaging apps. If the lender needs the files, use the secure upload portal the lender provides, or an encrypted share with an expiring link.<br> |
|||
|
|||
<br>New York companies should check their obligations under the New York SHIELD Act, which sets reasonable safeguard expectations for private information, including Social Security numbers and account numbers. A payroll export or a vendor file with bank details can fall into that category. Counsel or an IT security adviser can confirm what applies to your business, but the habit is the same: know what personal data sits in the backup, limit who sees it, and be able to say what safeguards you used.<br> |
|||
|
|||
<br>Keep a simple access log for the backup folder and the archive. Record who opened it, when and why. You do not need a complex system. A dated entry in a shared log is enough for most small and mid-sized teams, and it answers a question that lenders and auditors tend to ask: who has touched this data since it was closed?<br> |
|||
|
|||
<br>Plan for an access problem, too. Write down what happens if the archive owner is unavailable on the day a lender asks for a file. Name a backup person, make sure that person can open the archive, and test the handoff once. A review rarely waits for one person's vacation.<br> |
|||
|
|||
Test the restore before anyone outside the company relies on it |
|||
|
|||
<br>A backup you have never restored is a hope, not a control. The test is simple: restore the backup to a separate environment, then check that the restored numbers match the locked report package. If they match, you have evidence the backup works. If they don't, you have found the problem with weeks to spare instead of hours before a lender call.<br> |
|||
|
|||
<br>Use a short sequence. Restore the native backup to a sandbox or a separate company file. Run the trial balance and balance sheet, then compare the totals with the PDF package. Pick five to ten transactions across different periods and trace each one to its source document. Check that the subledgers tie to the general ledger. Write down every difference, even small ones, and explain each before you call the test complete.<br> |
|||
|
|||
<br>Verify the archive too. Recompute the checksum for each file and compare it with the manifest. A mismatch means a file changed after the manifest was written or was copied incorrectly. Either way, you need to know which file and why. Opening a file and seeing that it looks fine is not the same as proving it is unchanged.<br> |
|||
|
|||
<br>Document the test. Record who performed it, the date, the source backup, the sandbox used, the comparison results and the sign-off. Keep this record with the archive. The lender may never ask for it, but when a question comes up about a figure, the record shows that the team had already checked the data against the books.<br> |
|||
|
|||
<br>This is where internal controls meet audit readiness. Segregation of duties matters here: the person who closes the books should not be the only person who signs off the restore test. A second reviewer, even a part-time one, gives a better check than someone verifying their own work. Small teams often cannot split every task, but they can split this one.<br> |
|||
|
|||
Assign ownership across bookkeeper, controller and CFO roles |
|||
|
|||
<br>Backup responsibility often falls between roles. The bookkeeper assumes the controller handles it, the controller assumes the system administrator does, and the owner assumes the outsourced accounting firm keeps copies. Before the review, name one owner for each step. The roles below differ in scope, and the difference shows up when something goes wrong.<br> |
|||
|
|||
|
|||
RoleTypical scopeBackup responsibilityReview responsibility |
|||
BookkeeperDaily transactions and bank reconciliationsExports and source filesReconciliation memos |
|||
ControllerClose process, financial statements, internal controlsPeriod lock, reports, frozen archiveRestore test results |
|||
Outsourced accountingBookkeeping and close executionNative backups and access logs, if contractedConfirmation that close tasks were completed |
|||
Outsourced CFOStrategic finance, capital raising and lender relationsSets the backup policy and retention rulesPackage checked against the lender's request list |
|||
In-house CFOThe same scope, with daily presenceOwns the policy and checks complianceFinal sign-off on the lender package |
|||
|
|||
|
|||
<br>An outsourced CFO differs from a bookkeeper or an outsourced accounting firm in where the attention goes. A bookkeeper records transactions. An outsourced accounting team closes the books and prepares reports. A CFO-level advisor decides what the lender must see, what the company can defend and which risks the package leaves open. The backup policy should come from that last role, even when someone else carries out the steps.<br> |
|||
|
|||
<br>Write the split into a responsibility matrix and keep it short. Each row is a task, each column is a person or firm, and each cell says who does, reviews or approves. Five tasks cover most of it: export, lock, archive, restore test and access review. Keep the matrix with the request list so a reviewer can see who did what without asking.<br> |
|||
|
|||
<br>Watch for conflicts. If the person who posts journal entries also approves the backup and the restore test, nothing gets checked independently. If an outside firm holds the only native backup, make sure the company holds a copy too, and that the contract states how the data is returned when the engagement ends. These details matter most when the relationship changes.<br> |
|||
|
|||
<br>Ownership also has to survive turnover. Record the admin credential owner, the vault location and the backup schedule in a runbook. A new person should be able to run the process from the document alone. If they cannot, the process lives in one person's head, and that is the risk a lender will ask about.<br> |
|||
|
|||
Set retention rules that outlast the review |
|||
|
|||
<br>A loan review ends, but the data has to stay available longer. Lenders may request follow-up documents after closing, auditors may look back at prior periods, and tax authorities have their own record-keeping expectations. Your retention rules should cover all of these before the review starts, not after the first question arrives.<br> |
|||
|
|||
<br>The IRS publishes record-keeping guidance that most tax preparers can explain for your situation. In general, records supporting a tax return are kept for a period that depends on the type of return and the issues involved, and some situations require longer retention. Ask your tax preparer to confirm the period for your entity and for each record type, then get the answer in writing.<br> |
|||
|
|||
<br>Build a retention schedule that lists each record type, its retention period, where it is stored and how it is disposed of. Include the frozen archive, native backups, exports, restore test records, access logs and signed lender packages. Set a review date each year, so the schedule does not drift away from what the business actually needs.<br> |
|||
|
|||
|
|||
Frozen archives and signed lender packages: kept for the longest period your tax preparer and counsel confirm. |
|||
Native backups: kept for the period needed to restore the system to any locked date you may be asked about. |
|||
Exports and reconciliation memos: kept alongside the archive for the same period. |
|||
Restore test records and access logs: kept long enough to show the controls worked during any period a lender or auditor might ask about. |
|||
|
|||
|
|||
<br>Disposal matters as much as keeping. Once a retention period ends, delete the data from every location, including backups, shared drives and personal devices, and record the disposal date. Keeping everything forever creates its own exposure: more personal data stored, more systems to secure and more files a future request can surface.<br> |
|||
|
|||
<br>Plan for changes in the lender relationship. If you refinance, add a line of credit or move to a new bank, the new lender may ask for periods the old one never did. A retention schedule that covers prior periods and the current archive lets you respond without rebuilding history from memory or from a bank portal that may not keep everything indefinitely.<br> |
|||
|
|||
<br>Keep the schedule with the runbook. The best retention rule is useless if nobody knows it exists when a disposal date arrives or a request lands in the inbox. A one-page schedule in the same folder as the archive answers both questions at once.<br> |
|||
|
|||
Questions to confirm with a professional before you decide on the backup plan |
|||
|
|||
<br>Before you lock the plan, put a short set of questions to the people who can answer them. Each one should get a written answer, because a verbal yes is hard to point to when a review gets tense. Here's the order I would work through, starting with the parties whose answers change the design.<br> |
|||
|
|||
|
|||
Lender: which periods, statement basis and file formats do they want, and do they accept management-prepared statements or only reviewed or audited sets? |
|||
Tax preparer: what retention period applies to each return and supporting record for your entity? |
|||
Counsel: which New York privacy and safeguard duties apply to the personal data in your exports, and what must the outside provider's contract say about returning data? |
|||
IT security adviser: are multi-factor authentication, encryption and access logging configured the way your policy states, and does the restore test cover the native backup? |
|||
Outsourced accounting or CFO candidate: who will hold admin rights, who signs the backup policy, and how will they document the close and the restore test? |
|||
|
|||
|
|||
<br>When you talk to a provider, ask about fit before price. Outsourced CFO services differ by stage, size and industry. A provider used to supporting early-stage fundraising may approach a lender review differently from one used to mid-sized operating businesses with inventory and multiple entities. Ask for a general description of work done for companies like yours, then check that the proposed scope matches what you need. Do not accept a promised outcome in place of a defined scope.<br> |
|||
|
|||
<br>Judging whether the service is worth the cost is harder, and it should be done without relying on promised results. Track your own measures before and after: how many days the close takes, how many reconciliation items are still open at the lender deadline, and how often a lender asks for a file you cannot produce within a day. These are your numbers, measured on your books. If they move in the right direction, you have evidence. If they do not, you have a question to bring back to the provider.<br> |
|||
|
|||
<br>Know when to move from an outsourced model to an in-house CFO. If backup oversight needs daily attention, if lender requests arrive every month instead of once a year, or if the business needs finance input in every planning meeting, the outsourced arrangement may stop fitting. There is no fixed threshold. The signal is workload: when the same people spend more time managing the finance function than running the business, a full-time hire is worth pricing out.<br> |
|||
|
|||
<br>Last, keep this list with the archive and the runbook. Date it, record the answers you received and note who gave them. When the next review starts, anyone on the team should be able to see what was decided, who decided it and what still needs confirmation. That record protects the company as much as any single backup file does.<br> |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue