Accounts Receivable Write-Off & Bad Debt Request — Complete Documentation & Approval Form

Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.

Overall Summary of the Accounts Receivable Write-Off & Bad Debt Request Form

The Accounts Receivable Write-Off & Bad Debt Request Form is an exceptionally well-structured and comprehensive financial control document designed to govern the write-off of uncollectable receivables across an organisation. Spanning twelve detailed sections, the form covers every critical dimension of a write-off decision — from requestor identification and debtor profiling through to invoice-level detail, collection history, accounting treatment, tax implications, supporting documentation, post-write-off tracking, and multi-level approval routing. This breadth of coverage ensures that each write-off request is documented to an audit-ready standard, supporting both internal governance and external regulatory compliance. The form's design reflects a deep understanding of the accounts receivable lifecycle and the multifaceted nature of bad debt recognition.

Among its many strengths, the form excels in its use of conditional logic and follow-up questions, which dynamically tailor the data collection process based on the user's responses. For instance, selecting 'insolvency' as the write-off reason triggers specific fields for liquidator details and proof of debt, while choosing 'fraud' prompts questions about reporting to authorities. This intelligent branching minimises irrelevant data entry while ensuring that critical contextual information is captured whenever applicable. The inclusion of structured tables for invoice schedules, aging analysis, collection activity logs, and approval routing further enhances data quality and consistency. The form also thoughtfully addresses root-cause analysis, credit policy review, and lessons-learned opportunities, elevating it from a mere transactional request to a strategic tool for organisational improvement.

From a data collection perspective, the form gathers highly sensitive financial, legal, and personal information. Debtor details, legal proceedings, tax treatments, and internal control failures are all captured. While this depth is essential for the form's purpose, it raises privacy considerations — particularly regarding debtor personal data and internal compliance matters. The form's inclusion of a records retention confirmation checkbox demonstrates awareness of data governance obligations. The user experience, while demanding due to the form's length and complexity, is well-supported by clear section headings, guidance paragraphs, placeholder examples, and a logical flow from identification through to approval. However, the sheer volume of fields (with a high proportion being mandatory) could present friction for less experienced users or in time-sensitive situations.

Section: Purpose of This Form & How to Complete It

I confirm that I have read the guidance above and that the information provided in this form is complete and accurate to the best of my knowledge.

This confirmation checkbox serves as the foundational attestation for the entire form, establishing the requestor's acknowledgment of the guidance and their commitment to providing accurate information. In the context of an accounts receivable write-off — a financially material event with audit and legal implications — this attestation is essential for establishing the integrity of the submission. It creates a clear starting point of accountability, ensuring that the requestor cannot later claim ignorance of the form's requirements or the organisational policies governing write-offs.

From a design perspective, placing this confirmation at the very beginning of the form is an effective choice. It primes the user to engage seriously with the form and sets expectations for thoroughness and accuracy. The checkbox format is simple and unambiguous, reducing the risk of user error. The guidance paragraphs that precede it are clear and practical, covering key rules such as using one form per debtor, currency conventions, restrictions on disputed amounts, and reconciliation requirements. This upfront clarity significantly reduces the likelihood of incomplete or inaccurate submissions.

The data quality implications are significant: this attestation creates a documented record of the requestor's responsibility for the information provided. In the event of an audit, dispute, or investigation, this checkbox — combined with the formal declaration in Section 12 — forms part of the defensible audit trail. From a user experience standpoint, while mandatory checkboxes can sometimes feel bureaucratic, in this high-stakes financial context, the requirement is entirely proportionate and reinforces the seriousness of the process.

Section 1 — Requestor & Preparer Information

Full name of requestor/preparer

This field is fundamental for identifying the individual responsible for preparing the write-off request. In any financial control process, accountability must be clearly established, and the requestor's name is the primary identifier linking the submission to a specific person. This is critical for audit trails, follow-up queries, and ensuring that the correct individual is contacted during the review and approval process. The placeholder example ('Jordan Alvarez') helps users understand the expected format.

The design choice to make this mandatory is entirely appropriate — a write-off request without a clearly identified preparer would be unverifiable and unaccountable. The single-line text format is efficient and appropriate for a name field. From a data quality perspective, this field ensures that every write-off request can be traced to a responsible individual, which is a core internal control requirement.

Privacy considerations are minimal here, as the requestor is an internal employee acting in an official capacity. The user experience is straightforward — this is typically the first field a user completes, and its simplicity helps build momentum through the form. The field's placement at the top of Section 1 follows a logical flow from identification through to substantive content.

Job title/position

Capturing the requestor's job title provides essential context about their authority, expertise, and role in the write-off process. This information helps reviewers assess whether the requestor has the appropriate knowledge and standing to prepare a write-off request. For example, a request prepared by an Accounts Receivable Supervisor carries different weight than one prepared by a junior clerk. This field also supports the approval routing logic in Section 11, where approval authority is tied to organisational seniority.

The mandatory status of this field is justified — job title is a critical data point for governance and approval purposes. The placeholder ('Accounts Receivable Supervisor') provides helpful context. The field's design is clean and efficient, requiring minimal effort from the user while capturing high-value information.

From a user experience perspective, this field is quick to complete and rarely causes confusion. The data collected supports organisational hierarchy mapping and ensures that the write-off request is appropriately contextualised within the company's structure. This is particularly important in large organisations where approval thresholds are tied to the seniority of both the requestor and the approver.

Department/cost centre

This field identifies the organisational unit responsible for the write-off, which is essential for cost allocation, management reporting, and accountability. In many organisations, bad debt expense is charged back to the originating department (e.g., Sales or a specific business unit), making this field critical for accurate financial reporting. The placeholder ('Finance — Order to Cash') demonstrates the expected level of detail.

Making this field mandatory ensures that every write-off can be attributed to a specific cost centre, supporting budget variance analysis and departmental performance reviews. The field also helps identify patterns — for instance, if a particular department consistently generates write-offs, this signals a need for improved credit controls or sales practices.

The user experience is straightforward, and the field's placement within the requestor information section is logical. Data quality is enhanced by the mandatory status, ensuring complete cost allocation data. This field has minimal privacy implications as it relates to organisational structure rather than personal information.

Employee ID or staff reference number

While not mandatory, this field adds a layer of precision to requestor identification. Employee IDs are unique and unambiguous, reducing the risk of confusion between individuals with similar names. In organisations with robust HR systems, this ID can be cross-referenced to verify the requestor's role, department, and authority level. The optional status is pragmatic — not all organisations use employee IDs, and the name and department fields already provide sufficient identification.

The design choice to make this optional is well-judged, as it accommodates organisational variations without compromising the form's core functionality. For organisations that do use employee IDs, this field enhances data quality and traceability. The placeholder ('EMP-10482') provides clear guidance on the expected format.

From a user experience perspective, this field is low-friction — users who have an employee ID can quickly enter it, while those who don't can skip it without penalty. The data collected supports internal HR and finance system integration, enabling automated verification and routing.

Business email address

The requestor's business email is the primary communication channel for all follow-up queries, clarifications, and approval notifications related to the write-off request. This field is essential for ensuring that the review and approval process can proceed efficiently. Without a reliable contact method, reviewers may be unable to resolve questions or request additional information, leading to delays or rejections.

The mandatory status is entirely appropriate — email is the standard business communication tool, and a write-off request without a contactable requestor would be incomplete. The placeholder ('jordan.alvarez@company.com') reinforces the expectation of a business email rather than a personal one, which is important for data security and professional communication.

Privacy considerations are minimal, as this is a business contact detail. The user experience is simple and familiar. The field's placement alongside other contact information is logical and efficient. Data quality is supported by the mandatory status and the expectation of a business email format.

Business phone/extension

This optional field provides an alternative contact method for urgent queries or situations where email communication is insufficient. In time-sensitive write-off scenarios — such as when a debtor enters liquidation and immediate action is required — having a phone number can be invaluable. The optional status is pragmatic, as email is typically sufficient for most communications.

The design choice to make this optional reflects a balanced approach to data collection. The placeholder ('+00 555 0100 ext. 214') provides clear guidance on the expected format, including extensions. This field enhances the form's completeness without imposing unnecessary burden on the user.

From a user experience perspective, this field is quick to complete and rarely causes issues. The data collected supports multi-channel communication and ensures that the requestor can be reached through multiple means if needed.

Date this request was prepared

The preparation date is a critical timestamp that establishes when the write-off request was created. This date is essential for audit purposes, as it anchors the request within a specific accounting period and helps establish the timeline of events. It also supports the aging analysis and collection history documentation in subsequent sections. The date must be consistent with the aging cut-off date and the accounting period for the write-off entry.

Making this field mandatory is essential — a write-off request without a preparation date would lack temporal context and would be difficult to audit. The date format is unambiguous and standard for financial documentation. From a data quality perspective, this field ensures that every request has a clear timeline, supporting both internal controls and external audit requirements.

The user experience is straightforward — users simply select or enter the date. The field's placement within the requestor information section is logical, as it establishes when the requestor completed their work on the form.

Did you personally handle the collection efforts on this account?

This question establishes the requestor's direct involvement in the collection process, which is critical for assessing the credibility and completeness of the collection history documented in Section 5. If the requestor personally managed the collections, their narrative and assessment carry direct authority. If not, the form appropriately redirects to identify who did handle the collections, ensuring that the right person is associated with the collection history.

The mandatory status is well-justified — understanding who managed the collections is essential for accountability and for validating the collection efforts described later in the form. The conditional follow-up logic is excellent: a 'yes' response triggers a summary of direct involvement, while a 'no' response asks for the name of the responsible party. This branching ensures that the form captures the necessary context regardless of the answer.

From a data quality perspective, this question ensures that the collection history is attributed to the correct individual and that the requestor's role is clearly defined. The user experience is enhanced by the conditional logic, which avoids asking irrelevant follow-up questions. Privacy considerations are minimal, as this relates to internal work responsibilities.

Is this request being submitted on behalf of another department (e.g., Sales, Legal, Operations)?

This question identifies cross-departmental involvement in the write-off request, which is important for understanding the organisational context and ensuring that all relevant stakeholders are aware of and support the request. Write-offs often originate from Sales (e.g., when a customer relationship ends) or Legal (e.g., when a claim becomes unenforceable), and capturing this context helps reviewers understand the broader business implications.

While not mandatory, this question is valuable for organisational transparency. The conditional follow-up asks for the requesting department and sponsoring stakeholder, which provides useful context for the approval process. The design is clean and efficient, with the optional status reflecting the fact that many write-off requests are prepared entirely within Finance.

From a user experience perspective, this question is quick to answer and the conditional logic ensures relevance. Data quality is enhanced by capturing cross-departmental context, which supports stakeholder management and approval routing.

Section 2 — Customer/Debtor Identification

Customer/debtor legal name

The debtor's legal name is the most fundamental identifier in any write-off request. It must match the name used in the accounting records, contracts, and any legal proceedings. Accurate identification is essential for ensuring that the write-off is applied to the correct account and that all related documentation is properly associated. In cases of insolvency or legal action, the legal name must exactly match the name used in official proceedings.

Making this field mandatory is non-negotiable — a write-off request without a clearly identified debtor would be meaningless and potentially dangerous (e.g., writing off the wrong account). The placeholder ('Northwind Trading Holdings Ltd.') demonstrates the expected level of formality and precision. The field's design as a single-line text input is appropriate for a legal name.

Data quality is paramount here, and the mandatory status ensures completeness. The user experience is straightforward, though users must be careful to enter the exact legal name rather than a trading name or abbreviation. This field has minimal privacy concerns as it relates to a business entity.

Trading name/DBA (if different from legal name)

This optional field captures the debtor's commonly used name, which may differ from the legal name. This is important for cross-referencing with sales records, correspondence, and customer relationship management systems where the trading name may be more commonly used. It also helps prevent confusion when the debtor operates under multiple names.

The optional status is pragmatic — many debtors use their legal name as their trading name. The placeholder ('Northwind Logistics') provides clear guidance. This field enhances data completeness without imposing unnecessary burden. From a data quality perspective, it supports accurate identification and reduces the risk of duplicate records.

The user experience is simple, and the field's placement immediately after the legal name is logical. This field is particularly useful in industries where trading names are common (e.g., retail, hospitality).

Customer account/debtor ledger reference

The account reference is the unique identifier that links the write-off request to the specific debtor account in the accounting system. This is essential for ensuring that the write-off journal entry is posted to the correct account and that the sub-ledger and general ledger remain reconciled. Without this reference, the write-off cannot be accurately processed.

Making this field mandatory is essential for data integrity and system integration. The placeholder ('CUS-0023841') demonstrates the expected format. This field is critical for the accounting team to process the write-off and for auditors to trace the transaction. Data quality is directly supported by the mandatory status and the unique nature of the account reference.

The user experience is straightforward — users can easily look up the account reference in their accounting system. The field's placement within the debtor identification section is logical and efficient.

Registration/company/tax identification number

This optional field captures the debtor's official registration or tax identification number, which provides an additional layer of identification beyond the legal name and account reference. This is particularly important for corporate debtors, where multiple entities may have similar names. The registration number is also useful for credit checks, legal proceedings, and insolvency filings.

The optional status is pragmatic — not all debtors will have a registration number (e.g., individual consumers), and the legal name and account reference already provide sufficient identification. The placeholder ('Reg. No. 99887766 / Tax ID 12-3456789') provides clear guidance on the expected format.

From a data quality perspective, this field enhances debtor identification precision. The user experience is simple, and the field's placement within the debtor identification section is logical. This field is particularly valuable for corporate debtors and in jurisdictions where registration numbers are commonly used.

Debtor type

Classifying the debtor type is essential for determining the appropriate accounting treatment, legal approach, and risk assessment. Different debtor types (corporate, individual, government, related party) have different legal frameworks, recovery prospects, and regulatory requirements. For example, related party write-offs may require additional disclosure and approval, while government debtors may have different insolvency procedures.

The mandatory status is well-justified — debtor classification drives multiple downstream decisions. The comprehensive list of options (8 categories) covers the most common debtor types, and the conditional follow-ups for 'Related party' and 'Other' ensure that additional context is captured when needed. The design is clean and the branching logic is well-implemented.

From a data quality perspective, this classification ensures that the write-off is appropriately categorised for reporting and compliance purposes. The user experience is enhanced by the clear options and conditional logic. This field has important implications for tax treatment and regulatory compliance.

Primary contact person at the debtor (name and position)

This optional field captures the key individual at the debtor organisation who was the primary point of contact for collection efforts. This information is valuable for understanding the collection history, for potential legal proceedings, and for future reference if the debtor re-emerges or if recovery becomes possible. The placeholder ('Ms. Lena Fischer, Finance Manager') provides clear guidance.

The optional status is pragmatic — in some cases (e.g., debtor dissolved), no contact person may be available. The field's design as a single-line text input is appropriate for capturing name and position together. Data quality is enhanced by having this information available for reference.

The user experience is simple and straightforward. This field supports the collection history documentation and provides useful context for reviewers assessing the write-off request.

Last known contact email and phone number

This optional field captures the debtor's last known contact details, which are essential for any future recovery efforts, legal proceedings, or insolvency claims. Even after a write-off, the legal claim may be preserved, and having accurate contact information is critical for any subsequent action. The placeholder format ('l.fischer@northwind.example | +00 555 0198') demonstrates the expected input.

The optional status is pragmatic — contact details may be unavailable or outdated. However, when available, this information is highly valuable. The field's design allows for both email and phone in a single input, which is efficient. Data quality is supported by capturing whatever contact information is available.

The user experience is straightforward, and the field's placement alongside other debtor identification fields is logical. This information supports post-write-off recovery tracking and legal claim preservation.

Last known registered/billing address

The debtor's last known address is essential for legal proceedings, insolvency filings, and formal correspondence. In many jurisdictions, legal notices must be served to the registered address, making this information critical for preserving the legal claim after write-off. The multiline text format accommodates complex addresses.

While not mandatory, this field is highly valuable for legal and compliance purposes. The placeholder provides a realistic example of a business address. Data quality is enhanced by capturing this information, even if it may be outdated.

The user experience is simple — users enter the address as they know it. The field's placement within the debtor identification section is logical. This information is particularly important for cross-border debtors where enforcement may require formal service of documents.

Is the debtor still an active trading entity as far as you are aware?

This question is fundamental to the write-off decision. The debtor's trading status directly impacts recovery prospects, the appropriate write-off reason, and the legal approach. An actively trading debtor presents different opportunities and challenges compared to one that has ceased operations or entered insolvency. This question also triggers important conditional logic that captures specific details about the debtor's status.

The mandatory status is essential — the debtor's status is a primary factor in the write-off decision. The conditional follow-ups are comprehensive: a 'yes' response asks for current trading status and recent changes, while a 'no' response triggers a detailed status classification (insolvency, dissolution, etc.) with further follow-ups for each scenario. This branching logic is excellent and ensures that all relevant information is captured.

From a data quality perspective, this question ensures that the write-off is justified by the debtor's actual circumstances. The user experience is enhanced by the conditional logic, which avoids irrelevant questions. This field has significant implications for accounting treatment, tax deductibility, and legal strategy.

Is the debtor currently subject to any legal proceedings initiated by us?

This question identifies whether the organisation has initiated legal action against the debtor, which is critical for understanding the recovery strategy and the legal status of the claim. If legal proceedings are underway, the write-off decision must consider the potential outcome of those proceedings and whether the claim should be preserved. The conditional follow-up captures detailed information about the court, case number, stage of proceedings, and legal representative.

While not mandatory, this question is highly important for legal and compliance purposes. The conditional logic is well-designed, capturing essential details when legal proceedings exist. The placeholder ('District Commercial Court, Case No. CV-2025-8821; judgment obtained, enforcement stage; represented by Hartley & Cole LLP.') provides excellent guidance.

Data quality is enhanced by capturing legal proceedings context. The user experience is straightforward, with the conditional follow-up ensuring relevance. This information is critical for the legal claim preservation decision in Section 10.

Do we hold any security, guarantee, letter of credit, retention of title or collateral against this debt?

This question is critical for understanding the organisation's recourse options and the true exposure of the write-off. If security or guarantees exist, the write-off may be premature or may need to be accompanied by enforcement action against the security. The presence of security also affects the accounting treatment (e.g., whether the allowance for doubtful accounts is sufficient) and the tax deductibility of the bad debt.

The mandatory status is well-justified — the existence of security fundamentally changes the write-off analysis. The conditional follow-ups are comprehensive: a 'yes' response triggers a multiple-choice selection of security types with further follow-ups for guarantees and insurance, while a 'no' response includes a confirmation checkbox. This thorough approach ensures that all recourse options are documented.

From a data quality perspective, this question ensures that no potential recovery avenue is overlooked. The user experience is enhanced by the detailed conditional logic. This field has significant implications for financial reporting, legal strategy, and risk management.

Section 3 — Receivable & Invoice Details

Invoice Schedule & Write-Off Calculation (Table)

The invoice schedule table is the quantitative heart of the write-off request. It captures every invoice included in the write-off, with columns for invoice number, dates, original amount, payments received, outstanding balance (calculated), days past due, and the amount proposed for write-off. This structured approach ensures that the write-off amount is fully supported by invoice-level detail and can be reconciled to the sub-ledger and aging report.

The table design is excellent — the calculated 'Outstanding Balance' column (formula: column4-column5) reduces manual entry errors and ensures consistency. The sample rows demonstrate realistic data with multiple invoices, partial payments, and varying aging periods. This level of detail is essential for auditors and reviewers to verify the write-off amount.

From a data quality perspective, the table format enforces consistency and completeness. The user experience is enhanced by the structured layout, though entering multiple invoices can be time-consuming. The table's placement at the beginning of Section 3 is logical, as it provides the quantitative foundation for the subsequent analysis.

Currency of the receivable (ISO code)

Specifying the currency is essential for accurate financial reporting, especially in multinational organisations where receivables may be denominated in various currencies. The ISO code format ensures standardisation and reduces ambiguity. This field is critical for the exchange rate calculations and the reporting currency conversion that follows.

The mandatory status is well-justified — without knowing the currency, the amounts in the invoice schedule cannot be properly interpreted or converted. The placeholder ('e.g. USD, EUR, GBP, JPY') provides clear guidance. Data quality is directly supported by the mandatory status and the standardised format.

The user experience is straightforward — users simply enter the three-letter currency code. The field's placement within the receivable details section is logical and efficient.

Total outstanding balance in the invoice currency

This field captures the aggregate outstanding balance across all invoices listed in the schedule. It serves as a cross-check against the invoice table totals and the aging report. Accurate reporting of this figure is essential for financial statement accuracy and for the write-off approval process.

The mandatory status ensures that the total balance is clearly stated and can be verified against the invoice schedule. The currency field format is appropriate for monetary values. Data quality is enhanced by requiring this summary figure alongside the detailed invoice table.

The user experience is simple — users sum the outstanding balances from the invoice table. The field's placement within the receivable details section is logical.

Total amount proposed for write-off in the invoice currency

This field specifies the total amount to be written off in the original invoice currency. It may differ from the outstanding balance if only a partial write-off is proposed. This figure is the basis for the accounting entry and the approval threshold determination. Accuracy is critical — any discrepancy between this figure and the invoice schedule would undermine the entire request.

The mandatory status is essential — this is the core financial figure of the entire form. The currency field format ensures precision. Data quality is directly supported by the mandatory status and the requirement for consistency with the invoice table.

The user experience is straightforward, and the field's placement alongside the other summary figures is logical. This figure drives the approval routing in Section 11 and the accounting treatment in Section 7.

Total amount proposed for write-off in the functional/reporting currency

This field captures the write-off amount converted to the organisation's functional or reporting currency. This is essential for consolidated financial reporting, especially in multinational organisations. The conversion ensures that the write-off impact can be assessed at the group level and that the financial statements are accurate.

The mandatory status is well-justified — the reporting currency figure is needed for financial statement preparation and group reporting. The currency field format is appropriate. Data quality is enhanced by requiring both the original and reporting currency figures.