Cuestionario vinculado a una guía · duro Nivel
Cuestionario de automatización de cierre de fin de mes de IA
Prueba sugerencias de acumulación de datos recibidos no facturados, descomposición de varianzas para análisis de flujo y estrechas dependencias de listas de verificación.
Pregunta 1 de 8
A cleaning contractor's invoice has not arrived by month end. What does the guide say an AI accrual suggestion draws on?
Vista previa de cada pregunta8 preguntas
Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.
- A cleaning contractor's invoice has not arrived by month end. What does the guide say an AI accrual suggestion draws on?
- Received-not-invoiced records and the vendor's recurring monthly pattern
- The prior year's tax return
- Customer remittance advice
- The payroll register only
- Why should a language model's flux explanation be limited to precomputed facts and transaction IDs?
- To make the explanation shorter
- Because a model can write a convincing explanation that the transactions do not support
- Because auditors do not accept written explanations
- To avoid using review thresholds
- Which dependency does the guide use as an example of what close checklist tools track?
- Consolidation must finish before bank reconciliations
- Tax returns must be filed before accruals
- Intercompany reconciliations must finish before consolidation
- Budgets must be approved before payroll
- How does the guide suggest measuring the accuracy of AI accrual suggestions?
- By counting how many accruals were booked
- By asking the vendor to confirm estimates
- By comparing to the budget only
- Through the true-up: comparing each accrual with the actual invoice when it arrives
- Before a model writes a flux narrative, what decomposition does the guide recommend?
- Splitting the variance by fiscal year only
- Converting all amounts to a single currency
- Separating price from volume effects and one-time from recurring items across vendor, department and account
- Rounding all balances to thousands
- According to the guide, who is responsible for AI-proposed journal entries?
- A preparer and a separate reviewer must still approve them
- El proveedor de software
- No one, if the model confidence is high
- Only the external auditor
- Why does the guide recommend logging the model version, edits and approver for AI-assisted close items?
- To reduce storage costs
- So reviewers and auditors can re-perform and test the control
- To train the vendor's public model
- Because ERPs require it to post entries
- Why are flux reviews often triggered only when a change exceeds both a percentage and a dollar threshold?
- Because regulations set those exact thresholds
- Because language models require two thresholds
- Because dollar thresholds do not apply to expenses
- So small accounts with large percentage swings do not flood reviewers