Personal and Corporate Tax Compliance Case Studies
Finance5 Case StudiesUpdated Sep 2026
Tax compliance rarely fails in the forms themselves. It fails in the gaps between documents: a ledger that disagrees with a bank statement, a payroll register that drifts from the quarterly filing, a personal return the client cannot support. The five cases below involve fictional practices and their household and business clients. Each asks the same four things: what the records show, how much exposure a gap creates, what the controls left as evidence, and where the firm should set its decision thresholds. Treat the thresholds as examples of reasoning, not settings to copy.
Case Study 1
Payroll tax liabilities that refused to agree
Ashgrove Print and Finish, a regional commercial printer with three plants and roughly 140 employees
The situation
Ashgrove Print and Finish ran a quarterly payroll for roughly 140 people across three plants. When Priya, the outside bookkeeper who handled its tax filings, began the close for the final quarter, she pulled three figures side by side: the withholding total in the payroll register, the liability balance in the general ledger, and the amounts reported on the most recent employer return. The register showed 218,460 in withheld taxes. The ledger carried 214,905. The filed return reported a third figure, 217,130. None of the three matched, and the gaps did not look like rounding.
The challenge
The register was the natural anchor. But the ledger entries had been posted by hand from a summary someone else had prepared, and the return had been drafted from the ledger, not from the register. Two versions were in circulation, and the filing deadline was close enough that a payment could go out on the wrong number. Priya had to decide which figure was right, how far the gap reached, and whether it was large enough to take to Gareth, the controller, before anything was paid.
Analysis
Teams grounded in Personal and Corporate Tax Compliance start a variance with the document carrying the most evidential weight, not the one easiest to open. The payroll register sat closest to the wage data, so Priya used it as the reference. She traced the ledger gap first. The posted total was short by 3,555 against the register, and the entries showed a manual journal that had netted a bonus accrual against a reversal from the prior period. The filed return differed from the register by 1,330, which pointed to a timing issue in how one plant's late corrections were keyed. Two separate causes, each with its own paper trail, beat one vague gap.
Exposure was not the 3,555 itself. A short remittance on withheld taxes carries penalties and interest that grow with time, and an inaccurate return invites a notice that asks for the supporting detail. Priya set a working threshold: any variance above 1,000 that could not be traced to a documented entry within two business days would go to the controller with a recommendation to hold the payment and amend the return. Variances under that line could be corrected through a dated adjusting entry, provided the support was attached. It was a judgment about how long the team could afford to be wrong.
Actions taken
- Priya rebuilt the register-to-ledger bridge line by line, tagging each difference with its journal number and pay period. The bonus accrual was reversed and reposted in the correct period.
- Before any payment left the account, the controller approved an amended return for the 1,330 difference and documented the timing cause in the file. The amendment and its support went into the permanent workpapers.
- The firm added a monthly three-way check that compares register totals, ledger balances, and the return draft before any filing is locked. A mismatch above 500 blocks the lock until someone signs the difference.
- Manual journals to payroll liability accounts now require a second reviewer and a linked source file. Priya reviews a sample of ten each month and keeps the sign-off log as control evidence.
Results
By the end of the quarter, the three figures agreed to the penny. The amended return raised no notice, and the payment reflected the corrected liability. The three-way check flagged two smaller mismatches in the following close, both traced to the same keying habit at one plant. That plant now uses a locked entry form. Gareth gets the bridge report with every close package, and the team no longer argues about which document is right before it starts looking.
Questions for discussion
- Which of the three documents should anchor a variance investigation when they disagree, and what would change that choice?
- How would you set a variance threshold for a client whose ledger is maintained by someone outside the firm?
- What evidence would convince you that a manual journal is a one-time correction rather than a recurring habit?
Case Study 2
Estimated tax payments against a shrinking quarter
Corvane Lumber Holdings, a family-owned wholesaler with two distribution yards and nine delivery trucks
The situation
Corvane Lumber Holdings is a family-owned wholesaler with two distribution yards and nine delivery trucks. Its quarterly estimated tax payments are set from a forecast of taxable income, which the owner, Dolores, built at the start of the plan on the strength of a large regional contract. By the middle of the second quarter, billed revenue was running 18 percent under plan, and the contract's first delivery had slipped twice. Cash on hand covered payroll and suppliers, but not a full estimated payment at the planned amount. Her accountant, Mateo, had flagged the concentration risk in the first review but the plan kept the contract at full weight.
The challenge
The forecast was not wrong in an obvious way. It was simply out of date, and every downstream number leaned on it: the estimated payment, the reserve for a possible shortfall, and the decision about whether to draw on the equipment line. Dolores needed a revised forecast she could defend to the bank and to the tax authority, and she needed it before the next payment date, which was about five weeks away.
Analysis
The first step was to rebuild the forecast from the records, not from the plan. Billing history by customer and the delivery log gave a base case that reflected what had actually happened. Three scenarios were built on that base. In the expected case, the contract ships in full but two months late. In the downside, a second customer pauses orders and the contract is cut by a third. In the severe case, the contract is cancelled and the seasonal volume does not recover until the next quarter. Each scenario was tied to a cash line, so the assumptions could be checked against bank activity as weeks passed.
The exposure sat in the estimated payment. Underpaying in one quarter can bring a charge calculated on the shortfall, while overpaying ties up cash the business needs for suppliers. Mateo set two thresholds before any payment was revised. If the downside case left less than four weeks of operating cash after the payment, the payment would be reduced to the lower amount permitted under the prior-period method, and the difference would be paid with the next installment. If the expected case held, the planned amount would stand and the revised forecast would go into the file as the basis.
- 1Rebuild from recordsBase case uses billing history and the delivery log.
- 2Build three scenariosExpected, downside, and severe cases each carry a cash line.
- 3Test cash floorDownside case below four weeks of cash triggers a reduction.
- 4Revise estimated paymentPay the prior-period amount and settle the difference later.
- 5File the basisMemo records thresholds, cash position, and the reason.
Actions taken
- Dolores replaced the single forecast with three scenarios, each with its own cash line and trigger date. The downside case was reviewed first, since it set the payment.
- Mateo reduced the estimated payment to the prior-period amount and wrote a one-page memo stating the cash position, the thresholds, and the basis for the reduction.
- The equipment line stayed undrawn until the downside case showed cash below the four-week floor for two consecutive weeks. Drawing earlier would have added interest without solving the timing gap.
- Dolores set a weekly review of billed revenue against the downside line, and the operations lead reports slipped deliveries within one day. Two contracts were split so one slip could not stall everything.
Results
The revised plan showed taxable income about 40,000 below the original forecast, which Dolores absorbed by consolidating one of the two yards rather than drawing new debt. The reduced payment drew no penalty notice, and the difference went out on schedule with the next installment. Billings recovered in the final weeks of the quarter, closer to the expected case than the downside. Dolores now keeps a standing scenario set in the close package and no longer treats a single forecast as the plan.
Questions for discussion
- When a forecast and the bank balance disagree, which one should drive a payment decision, and why?
- How would you choose the cash floor that triggers a change in the estimated payment for a business with seasonal volume?
- What would you need to see in a customer's billing history before you trusted a contract as the base case?
Case Study 3
Wash sale indicators in a brokerage loss claim
Halvorsen Pike Tax Partners, a six-person firm preparing returns for about 310 individual clients
The situation
Halvorsen Pike Tax Partners prepares individual returns and reviews investment statements for about 310 clients, most of them salaried professionals. Ines, a pharmacist, sent her consolidated brokerage statements in the last month of the tax period, along with a request to report net losses to offset a capital gain from a property sale. The statements showed 22 sales at a loss in one holding, each followed within a few days by a purchase of the same security in a separate account her husband controlled. The total realized loss was 47,380. Nothing in her summary mentioned the repurchases.
The challenge
The losses were booked and confirmed by the brokerage, and the gain they would offset was large enough to change her tax bill by a wide margin. Rafael, the partner handling the file, had to decide whether the return could be prepared as requested, what the repurchases meant for each loss, and whether the firm needed to step back from the engagement altogether. The answer depended on facts the client had not yet supplied.
Analysis
Three indicators stood out, and each one was visible in the records before anyone looked for it. The repurchase timing fell inside the thirty-day window that governs whether a loss is allowed, so the firm had to assume disallowance for every matched pair until the facts said otherwise. The purchases went to an account in another person's name, which meant the firm could not verify the holder or the intent from its own files. And the summary omitted the repurchases entirely, which is a control failure on the client side and a reason to request the full transaction ledger rather than the monthly statements alone.
Exposure has two parts. The first is the disallowed loss, which moves the gain back into taxable income and adds interest on the underpayment. The second is the preparer's own position: a return built on a summary that omits material transactions is not one the firm can sign. The firm's internal line was simple. If the full ledger confirmed a matched repurchase in a related account, the return would not be prepared with the losses included, and the partner would decide whether to withdraw. Smaller, isolated wash sales without a related party could be adjusted and disclosed in the workpapers.
- Final weeks of periodStatements arrived showing 22 losses in one holding.
- Day one of reviewSummary omitted repurchases, so matching started from the trade files.
- Second weekFull ledger confirmed 19 related-account pairs and three own-account pairs.
- Before filingSecond signatory cleared the return, and counsel was consulted.
Actions taken
- Rafael asked Ines for the complete transaction ledger for both accounts and written confirmation of who controlled the second account. The request went out in writing with a response date.
- The firm held the return and told the client in writing which items it could not yet support. No losses were reported until the matching was complete.
- Once the ledger arrived, the team matched each sale to its repurchase and tagged every pair with the account owner, the days between trades, and the disallowed amount.
- Partner review went to a second signatory outside the engagement team, who checked the indicators against the firm's written escalation thresholds before any withdrawal decision.
Results
The ledger showed 19 of the 22 sales matched to repurchases in the related account. The other three were repurchased in her own account, which still disallowed those losses but raised no related-party question. The firm prepared the return with every matched loss disallowed, and documented each pair in the workpapers. Rafael would not sign a schedule that relied on the second account, and referred the question to outside counsel. The file now carries a second-signatory note on every brokerage review.
Questions for discussion
- Which indicator in this file would you treat as enough on its own to stop preparation, and which would only require more documents?
- How should a preparer weigh a client's explanation of a related account when the explanation cannot be checked against third-party records?
- What belongs in a written escalation threshold so that two partners reading the same file reach the same decision?
Case Study 4
Credit facility for a kitchen equipment supplier
Marlow Ridge Community Lending Fund, a small commercial lender serving businesses in its home region
The situation
Marlow Ridge Community Lending Fund makes small commercial loans to businesses in its region. Brightwater Kitchens, a commercial kitchen equipment supplier with twelve employees and two warehouses, asked for a 250,000 facility, split between an equipment term loan and a working capital line. The owner, Hamid, provided three years of filed business returns, quarterly payroll filings, and an internal profit and loss statement for the current period. The reported operating cash flow was strong, and the lender's own guidelines required that cash flow be supported by filed returns before any approval.
The challenge
The internal statement showed operating cash flow of 186,000 for the trailing period, which would comfortably cover the proposed payments. The filed returns told a flatter story, and the payroll filings for the latest quarter did not match the wages in the profit and loss statement. Tamsin, the credit analyst, had to decide whether the gap reflected timing and presentation, or whether the business was weaker than its owner believed, and what the lender should require before committing.
Analysis
Filed returns carry less optimism than management accounts, and that difference is the reason to start there. The three returns showed net business income that averaged well below the internal figure, and the gap appeared in every year. Tamsin reconciled the latest payroll filings to the profit and loss statement and found wages reported internally at 61,200 against 52,900 on the filings, with the difference traced to accrued bonuses that had not yet been paid. The bonuses were real, but they changed when the deduction would appear, which moved the cash picture. Control evidence was thin: no bank statements had been reconciled to the ledger for the latest period.
Downside scenarios started from the filed numbers rather than the internal ones. The base case used the filed income with the bonus accrual included. The stress case removed one of the two warehouses for six months and cut sales by a fifth, which is the scenario Tamsin treated as the planning case. Under that stress, debt service on the full facility would consume most of the operating cash, leaving a thin margin. The lender's threshold was a minimum debt service coverage of 1.25 in the stress case. The equipment term loan alone cleared it; the working capital line did not, unless its draw was capped.
Actions taken
- Tamsin requested the filed returns from the client's tax preparer directly, with the client's written consent, and compared them line by line to the statements provided.
- The bank statements for the latest period were reconciled to the ledger before any approval, and the open reconciling items were listed as a condition of closing.
- The equipment term loan was recommended at the requested amount, while the working capital line was capped at 60,000 and tied to a borrowing base of receivables.
- Approval required the payroll filings to reconcile to wages within a tolerance of 2 percent, with any bonus accrual documented in a signed owner memo.
Results
The committee approved the equipment term loan at the requested amount, subject to the bank reconciliation and a signed owner memo covering the bonus accrual. The working capital line was approved at 60,000 with the borrowing base in place. Brightwater's payroll filings reconciled to within 1.4 percent once the accrual was documented, and the first quarterly payment came through without delay. The owner has since asked for a larger line, and the committee has asked for two more filed quarters first.
Questions for discussion
- Which gap between filed returns and management accounts would you accept as timing, and what documents would prove it?
- How would you set the stress scenario for a business whose largest asset is a single warehouse?
- Should a lender ever accept a bonus accrual as support for cash flow before the payment has been made?
Case Study 5
Ranking tax control findings for closure
Penrose Hill Hospitality Group, a nine-hotel operator with a four-person corporate tax team
The situation
Penrose Hill Hospitality Group owns and operates nine hotels across three states, with a corporate tax team of four people and a shared services group that handles sales and use tax filings. The internal audit function reviewed the tax process over the last quarter. The review tested a sample of 60 exemption certificates, 35 fixed asset additions, and the access logs for the tax provision workbook. It found 14 exceptions in total, and the audit committee wanted them ranked, owned, and closed with evidence rather than with a memo saying the issue was fixed.
The challenge
Fourteen exceptions can look like a list of equal problems, and they are not. Some touch the amounts on the return, some touch only the documentation behind a position, and a few are about who can change the numbers. Ruth, the head of internal audit, asked the tax director, Solomon, to rank them by potential misstatement and to name one accountable owner for each, with a closure test that a reviewer outside the tax team could run.
Analysis
Materiality here was not a single dollar line. The team ranked each exception by the tax it could move, the penalty and interest that would follow, and whether it could recur. The fixed asset exceptions ranked highest: 35 additions were sampled, and four had depreciation classes that did not match the asset register, which put deduction timing at risk across several years. Exemption certificates came next, because three hotels had accepted certificates that were expired at the time of sale. The workbook access issue scored lower on dollars but higher on control evidence, since the audit log could not show who had changed a locked cell.
A closure test has to be something a stranger could repeat. For the asset register, the test was a re-performance of depreciation on the four mismatched assets plus a fresh sample of twenty additions, with no exceptions allowed. For certificates, the test pulled every certificate on file, checked each expiration against its sale date, and required a replacement for any that had lapsed. The workbook finding closed only when the audit log named an editor for every locked cell and an outsider had reviewed the exception report. Any finding that could move the return by more than 25,000 went to the audit committee before its owner closed it.
- Rank by exposure Score each exception by tax moved, penalty risk, and recurrence.
- Assign one owner Each finding has one named owner in the tax or shared services team.
- Re-perform the test Closure requires a repeated sample with zero exceptions, reviewed independently.
- Report and retest Open items past two cycles escalate, and closed items are sampled again later.
Actions taken
- Solomon owns the asset register correction. The four mismatched classes were reset, and depreciation was recomputed for each affected year, with the workpapers signed by him.
- Nadia, the shared services lead, owns the certificate fix. Every hotel gets a lapse report each month, and a sale cannot be filed without a current certificate on record.
- Gideon, the senior tax accountant, restricts edit rights to named users and turns on logging for every locked cell. Changes above 10,000 require a second signature.
- Ruth schedules the closure tests with an outside reviewer and reports open items to the audit committee each quarter. Any item open past two cycles is escalated.
Results
Of the 14 exceptions, the fixed asset and certificate items closed first, each with the required re-performance and no further exceptions. The workbook finding closed in the following cycle, after the logs showed named editors for the full period. One finding, a late estimated payment at a single hotel, stayed open for an extra cycle because the owner could not produce the bank confirmation, and it was escalated as the process requires. Solomon now reports closure evidence rather than status, and the committee receives the ranked list each quarter.
Questions for discussion
- How would you rank a finding that is small in dollars but leaves no audit trail for who changed the numbers?
- What evidence would you accept as proof that a certificate lapse did not affect any sale?
- When should an open finding move from the owner to the audit committee, and who should decide?
Learning Resources
Finance CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.