Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Business and entity profile.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of business and entity profile, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for business and entity profile. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Business and entity profile”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting policies intake.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting policies intake, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for accounting policies intake. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting policies intake”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Chart of accounts design.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of chart of accounts design, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for chart of accounts design. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Chart of accounts design”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Opening balances checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of opening balances checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for opening balances checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Opening balances checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Source document request.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of source document request, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for source document request. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Source document request”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting software migration plan.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting software migration plan, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for accounting software migration plan. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting software migration plan”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Month-end responsibilities matrix.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of month-end responsibilities matrix, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for month-end responsibilities matrix. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Month-end responsibilities matrix”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting workflow map.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting workflow map, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for accounting workflow map. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting workflow map”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Client access permissions.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of client access permissions, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for client access permissions. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Client access permissions”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting engagement scope.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting engagement scope, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Document the business type, accounting basis, reporting currency, fiscal period, stakeholders and existing controls.
3. Build a practical step-by-step procedure specifically for accounting engagement scope. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting engagement scope”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Transaction classification rules.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of transaction classification rules, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for transaction classification rules. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Transaction classification rules”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Expense coding review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of expense coding review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for expense coding review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Expense coding review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Revenue recognition intake.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of revenue recognition intake, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for revenue recognition intake. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Revenue recognition intake”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Receipt capture workflow.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of receipt capture workflow, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for receipt capture workflow. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Receipt capture workflow”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Journal entry draft.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of journal entry draft, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for journal entry draft. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Journal entry draft”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: General ledger exception scan.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of general ledger exception scan, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for general ledger exception scan. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “General ledger exception scan”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Petty cash register review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of petty cash register review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for petty cash register review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Petty cash register review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Intercompany transaction tracking.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of intercompany transaction tracking, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for intercompany transaction tracking. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Intercompany transaction tracking”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Duplicate entry detection.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of duplicate entry detection, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for duplicate entry detection. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Duplicate entry detection”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Bookkeeping daily checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of bookkeeping daily checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Work only from transaction-level evidence; specify proposed account, rationale, confidence and exceptions.
3. Build a practical step-by-step procedure specifically for bookkeeping daily checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Bookkeeping daily checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Bank reconciliation workbook.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of bank reconciliation workbook, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for bank reconciliation workbook. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Bank reconciliation workbook”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Unmatched transaction investigation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of unmatched transaction investigation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for unmatched transaction investigation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Unmatched transaction investigation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Credit card reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of credit card reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for credit card reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Credit card reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Outstanding checks register.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of outstanding checks register, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for outstanding checks register. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Outstanding checks register”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Deposit in transit analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of deposit in transit analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for deposit in transit analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Deposit in transit analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Merchant processor payout tie-out.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of merchant processor payout tie-out, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for merchant processor payout tie-out. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Merchant processor payout tie-out”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Cash drawer reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of cash drawer reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for cash drawer reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Cash drawer reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Reconciliation discrepancy memo.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of reconciliation discrepancy memo, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for reconciliation discrepancy memo. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Reconciliation discrepancy memo”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Multi-currency bank review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of multi-currency bank review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for multi-currency bank review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Multi-currency bank review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Monthly reconciliation sign-off.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of monthly reconciliation sign-off, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Show statement dates, opening/closing balances, cleared items, timing differences and unexplained variances.
3. Build a practical step-by-step procedure specifically for monthly reconciliation sign-off. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Monthly reconciliation sign-off”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Vendor onboarding checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of vendor onboarding checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for vendor onboarding checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Vendor onboarding checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Invoice data extraction plan.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of invoice data extraction plan, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for invoice data extraction plan. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Invoice data extraction plan”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Three-way match review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of three-way match review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for three-way match review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Three-way match review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounts payable aging analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounts payable aging analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for accounts payable aging analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounts payable aging analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Duplicate vendor invoice review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of duplicate vendor invoice review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for duplicate vendor invoice review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Duplicate vendor invoice review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Payment run approval pack.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of payment run approval pack, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for payment run approval pack. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Payment run approval pack”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Vendor statement reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of vendor statement reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for vendor statement reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Vendor statement reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Purchase order exception report.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of purchase order exception report, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for purchase order exception report. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Purchase order exception report”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Expense reimbursement controls.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of expense reimbursement controls, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for expense reimbursement controls. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Expense reimbursement controls”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounts payable month-end close.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounts payable month-end close, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Verify supplier identity, invoice fields, approval status, due date, duplicate risk and audit trail.
3. Build a practical step-by-step procedure specifically for accounts payable month-end close. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounts payable month-end close”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Customer invoicing checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of customer invoicing checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for customer invoicing checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Customer invoicing checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Invoice template and terms.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of invoice template and terms, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for invoice template and terms. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Invoice template and terms”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounts receivable aging.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounts receivable aging, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for accounts receivable aging. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounts receivable aging”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Customer payment matching.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of customer payment matching, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for customer payment matching. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Customer payment matching”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Collections email sequence.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of collections email sequence, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for collections email sequence. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Collections email sequence”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Credit memo review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of credit memo review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for credit memo review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Credit memo review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Bad debt assessment worksheet.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of bad debt assessment worksheet, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for bad debt assessment worksheet. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Bad debt assessment worksheet”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Customer statement reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of customer statement reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for customer statement reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Customer statement reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Deferred revenue schedule.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of deferred revenue schedule, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for deferred revenue schedule. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Deferred revenue schedule”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounts receivable close checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounts receivable close checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Use invoice dates, payment references, terms, receipts and outstanding balances; do not invent contact or payment history.
3. Build a practical step-by-step procedure specifically for accounts receivable close checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounts receivable close checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: QuickBooks account setup checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of quickbooks account setup checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for quickbooks account setup checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “QuickBooks account setup checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Xero account setup checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of xero account setup checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for xero account setup checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Xero account setup checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Bank feed rule specification.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of bank feed rule specification, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for bank feed rule specification. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Bank feed rule specification”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Import mapping and validation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of import mapping and validation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for import mapping and validation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Import mapping and validation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Tax code mapping review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of tax code mapping review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for tax code mapping review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Tax code mapping review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Recurring transaction controls.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of recurring transaction controls, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for recurring transaction controls. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Recurring transaction controls”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: User role permission audit.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of user role permission audit, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for user role permission audit. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “User role permission audit”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting app integration map.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting app integration map, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for accounting app integration map. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting app integration map”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Software migration reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of software migration reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for software migration reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Software migration reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting software troubleshooting.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting software troubleshooting, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Describe UI steps generically and request current software/version details; do not claim live access or executed changes.
3. Build a practical step-by-step procedure specifically for accounting software troubleshooting. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting software troubleshooting”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Transaction cleaning formula plan.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of transaction cleaning formula plan, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for transaction cleaning formula plan. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Transaction cleaning formula plan”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: SUMIFS reporting template.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of sumifs reporting template, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for sumifs reporting template. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “SUMIFS reporting template”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: XLOOKUP reconciliation model.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of xlookup reconciliation model, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for xlookup reconciliation model. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “XLOOKUP reconciliation model”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Pivot table expense analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of pivot table expense analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for pivot table expense analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Pivot table expense analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Conditional formatting control flags.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of conditional formatting control flags, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for conditional formatting control flags. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Conditional formatting control flags”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Power Query transformation plan.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of power query transformation plan, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for power query transformation plan. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Power Query transformation plan”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Spreadsheet error audit.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of spreadsheet error audit, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for spreadsheet error audit. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Spreadsheet error audit”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: CSV import validation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of csv import validation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for csv import validation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “CSV import validation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Financial workbook documentation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of financial workbook documentation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for financial workbook documentation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Financial workbook documentation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Spreadsheet handoff checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of spreadsheet handoff checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Provide reproducible formulas, field names, sheet layouts, sample test rows and error checks.
3. Build a practical step-by-step procedure specifically for spreadsheet handoff checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Spreadsheet handoff checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Month-end close calendar.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of month-end close calendar, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for month-end close calendar. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Month-end close calendar”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Trial balance review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of trial balance review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for trial balance review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Trial balance review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Profit and loss commentary.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of profit and loss commentary, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for profit and loss commentary. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Profit and loss commentary”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Balance sheet variance analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of balance sheet variance analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for balance sheet variance analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Balance sheet variance analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Cash flow statement mapping.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of cash flow statement mapping, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for cash flow statement mapping. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Cash flow statement mapping”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accrual schedule draft.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accrual schedule draft, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for accrual schedule draft. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accrual schedule draft”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Prepaid expense amortization.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of prepaid expense amortization, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for prepaid expense amortization. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Prepaid expense amortization”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Fixed asset roll-forward.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of fixed asset roll-forward, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for fixed asset roll-forward. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Fixed asset roll-forward”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Management reporting pack.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of management reporting pack, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for management reporting pack. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Management reporting pack”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Close review and sign-off.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of close review and sign-off, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Reconcile source schedules to trial balance and state the period, basis and materiality thresholds.
3. Build a practical step-by-step procedure specifically for close review and sign-off. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Close review and sign-off”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Annual operating budget.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of annual operating budget, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for annual operating budget. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Annual operating budget”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Departmental budget template.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of departmental budget template, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for departmental budget template. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Departmental budget template”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Budget versus actual analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of budget versus actual analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for budget versus actual analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Budget versus actual analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: 13-week cash flow forecast.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of 13-week cash flow forecast, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for 13-week cash flow forecast. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “13-week cash flow forecast”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Revenue scenario planning.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of revenue scenario planning, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for revenue scenario planning. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Revenue scenario planning”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Cost reduction opportunity review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of cost reduction opportunity review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for cost reduction opportunity review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Cost reduction opportunity review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Working capital dashboard.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of working capital dashboard, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for working capital dashboard. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Working capital dashboard”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Break-even analysis.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of break-even analysis, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for break-even analysis. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Break-even analysis”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Cash runway stress test.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of cash runway stress test, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for cash runway stress test. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Cash runway stress test”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Forecast assumption register.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of forecast assumption register, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Identify assumptions, sensitivity cases, arithmetic checks and decisions supported by the analysis.
3. Build a practical step-by-step procedure specifically for forecast assumption register. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Forecast assumption register”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Internal controls walkthrough.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of internal controls walkthrough, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for internal controls walkthrough. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Internal controls walkthrough”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Segregation of duties matrix.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of segregation of duties matrix, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for segregation of duties matrix. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Segregation of duties matrix”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Expense policy compliance review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of expense policy compliance review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for expense policy compliance review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Expense policy compliance review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Sales tax document checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of sales tax document checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for sales tax document checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Sales tax document checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Payroll input reconciliation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of payroll input reconciliation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for payroll input reconciliation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Payroll input reconciliation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Audit evidence index.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of audit evidence index, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for audit evidence index. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Audit evidence index”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Fraud red-flag escalation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of fraud red-flag escalation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for fraud red-flag escalation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Fraud red-flag escalation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Data retention and access review.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of data retention and access review, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for data retention and access review. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Data retention and access review”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Tax preparer handoff package.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of tax preparer handoff package, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for tax preparer handoff package. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Tax preparer handoff package”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting error correction log.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting error correction log, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Prepare evidence for an authorized accountant/tax adviser; flag jurisdiction-specific rules instead of guessing them.
3. Build a practical step-by-step procedure specifically for accounting error correction log. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting error correction log”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Invoice OCR verification rubric.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of invoice ocr verification rubric, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for invoice ocr verification rubric. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Invoice OCR verification rubric”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Bank-feed automation specification.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of bank-feed automation specification, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for bank-feed automation specification. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Bank-feed automation specification”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: AI categorization confidence rules.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of ai categorization confidence rules, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for ai categorization confidence rules. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “AI categorization confidence rules”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Human approval gate design.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of human approval gate design, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for human approval gate design. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Human approval gate design”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Automated exception alerts.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of automated exception alerts, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for automated exception alerts. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Automated exception alerts”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Reconciliation automation test cases.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of reconciliation automation test cases, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for reconciliation automation test cases. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Reconciliation automation test cases”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: LLM financial hallucination test.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of llm financial hallucination test, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for llm financial hallucination test. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “LLM financial hallucination test”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Sensitive data redaction workflow.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of sensitive data redaction workflow, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for sensitive data redaction workflow. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Sensitive data redaction workflow”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting AI prompt evaluation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting ai prompt evaluation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for accounting ai prompt evaluation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting AI prompt evaluation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Automation rollback and monitoring.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of automation rollback and monitoring, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Define human approval, audit log, safe failure, validation samples, false positives and rollback.
3. Build a practical step-by-step procedure specifically for automation rollback and monitoring. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Automation rollback and monitoring”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Client onboarding email.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of client onboarding email, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for client onboarding email. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Client onboarding email”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Weekly bookkeeping update.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of weekly bookkeeping update, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for weekly bookkeeping update. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Weekly bookkeeping update”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Monthly client report summary.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of monthly client report summary, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for monthly client report summary. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Monthly client report summary”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Accounting SOP documentation.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of accounting sop documentation, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for accounting sop documentation. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Accounting SOP documentation”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Service package scope and pricing.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of service package scope and pricing, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for service package scope and pricing. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Service package scope and pricing”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Portfolio case study with synthetic data.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of portfolio case study with synthetic data, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for portfolio case study with synthetic data. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Portfolio case study with synthetic data”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Remote bookkeeper resume bullets.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of remote bookkeeper resume bullets, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for remote bookkeeper resume bullets. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Remote bookkeeper resume bullets”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Freelance proposal draft.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of freelance proposal draft, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for freelance proposal draft. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Freelance proposal draft”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Client handover checklist.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of client handover checklist, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for client handover checklist. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Client handover checklist”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.

Act as an experienced bookkeeping and finance-operations assistant. Help me complete this specific assignment: Professional development roadmap.

CONTEXT TO FILL IN
- Business type, accounting jurisdiction and entity: [INSERT]
- Accounting basis and reporting period: [CASH/ACCRUAL; DATES]
- Reporting currency and software/version: [INSERT]
- Available source documents or de-identified transaction data: [PASTE]
- Applicable chart of accounts, policies and approval owners: [INSERT]
- Desired output format and reader: [INSERT]
- Materiality/tolerance and deadline: [INSERT]

TASK-SPECIFIC INSTRUCTIONS
1. First clarify the goal of professional development roadmap, required inputs, source-to-output mapping and decision owner. Identify missing fields as [NEEDS CONFIRMATION]; never fabricate balances, vendors, dates, rates or supporting transactions.
2. Clearly distinguish simulated portfolio exercises from actual client engagements; specify deliverables and professional boundaries.
3. Build a practical step-by-step procedure specifically for professional development roadmap. Include required columns or data fields, ownership, review checkpoints and examples based only on supplied facts; use clearly labeled synthetic examples if illustration is needed.
4. Return a usable working artifact: a checklist, table, spreadsheet layout, formula, journal-entry proposal, report outline, message draft or test plan appropriate to this task. Show any calculations and reconciliation logic so a reviewer can reproduce them.
5. Add five task-relevant QA checks, likely exceptions, suggested remediation and an explicit reviewer/approval step. Do not post entries, file returns, initiate payments, change accounts or send messages without explicit authorization and actual tool access.
6. Explain uncertainties, privacy controls, limitations and what must be verified with the bookkeeper, qualified accountant or tax adviser. Never present jurisdiction-dependent tax, payroll or accounting treatment as universal advice.

FINAL OUTPUT
Title the deliverable “Professional development roadmap”. Provide (A) assumptions and missing evidence, (B) ordered workflow, (C) copy-ready template/output, (D) verification checklist, (E) escalation points and next steps. Keep it accurate, concise and client-ready.