|
WORKFLOW |
How to automate audit evidence requests inside Sage Intacct
Intacct's dimensional ledger and REST API make it possible to pull exactly the transactions auditors want - without rebuilding a request list from scratch each year.
Audit evidence requests have a reliable failure mode: the auditor sends a list, the controller forwards it to four people, three of them interpret it differently, and the team spends two weeks assembling a folder that still has gaps. The underlying problem is not that the documentation does not exist inside the ERP - it usually does - but that pulling it requires manual navigation through accounts, entities and periods with no repeatable path. Sage Intacct's dimensional ledger and its configurable reporting layer change that calculation.
BY THE NUMBERS
|
83/100 AF SCORE, SAGE INTACCT |
2 to 3 months TIME TO LIVE, AS REVIEWED |
STEP BY STEP
Audit evidence requests in Sage Intacct, step by step
This workflow covers building a repeatable audit evidence package inside Sage Intacct - from scoping the request list against dimension filters through delivering a clean file to auditors. Run it once to build the saved reports; reuse them each audit cycle.
1 |
Obtain the auditor's request list and map each item to a Sage Intacct dimension combination - entity, location, department, project or custom dimension - so every request has an explicit filter before any report is opened. |
2 |
Inside Sage Intacct, open the general ledger reporting module and create a saved report for each major request category, applying the dimension filters mapped in the previous step and locking the date range to the audit period. |
3 |
Add the transaction-level detail view to each saved report so that journal entry references, amounts and posting dates are visible without a secondary drill-down step. |
4 |
Verify that source documents - invoices, approvals, contracts - are attached at the transaction or journal entry level for the accounts in scope; for any transaction missing an attachment, flag it for remediation before the package is assembled. |
5 |
Run each saved report and cross-check the row count against the auditor's population description; if the count is materially different from what the auditor expects, revisit the dimension filter or date boundary before proceeding. |
6 |
Use the Intacct REST API (generally available as of 2025 Release 1) or a scheduled export to push the report output and attached documents to the shared audit workspace, keeping file naming consistent with the auditor's request numbering. |
7 |
Paste the following prompt into an AI assistant connected to the exported data to produce a request-by-request index: 'You are reviewing a set of Sage Intacct transaction exports organized by audit request number. For each file, identify the request number, the dimension filters applied, the date range, the number of transactions, and any transactions that have no attached supporting document. |
8 |
Deliver the index alongside the export files and confirm receipt with the audit team; document which saved reports produced which deliverables so the same reports can be reused next cycle. |
The Audit Friendly review of Sage Intacct scores the platform 83 out of 100, with the dimensional general ledger among the features assessed. Because every transaction can carry location, department, project, customer and custom dimension tags, a controller can build a saved report that returns exactly the population an auditor would sample - filtered, dated and tied to the underlying journal entries - rather than exporting a full trial balance and trimming it in a spreadsheet afterward. The Audit Friendly review of Sage Intacct also notes that the REST API reached general availability in 2025 Release 1, meaning document and transaction data can be pushed programmatically to a shared audit workspace without a manual export step.
Where the workflow tends to break is dimension design. If location, department and project dimensions were mapped without reference to the reports auditors actually need, the saved filters will not align cleanly to the request list, and someone will still be doing a manual reconciliation at the end. The go-live watchout is straightforward: dimension modeling has to be done against real report requirements, not an idealized chart of accounts. Get that right first and the annual audit package becomes a matter of running a set of saved reports, attaching source documents that are already stored against transactions, and exporting a clean file.
Measure the workflow by how many auditor follow-up requests arrive after the initial package is delivered. A well-configured dimensional filter should reduce back-and-forth to questions about judgment calls and estimates, not missing transaction detail. If the follow-up list looks similar year over year, the saved reports need tighter scoping - either the date range is too broad, the dimension filter is not matching what auditors sample, or attachments are inconsistently stored at the transaction level.
WHAT TO TAKE FROM THIS
| Confirm dimension tags on transactions match the categories auditors sample before building saved reports. | |
| The REST API (GA in 2025 Release 1) enables programmatic export - test it against a real request before audit fieldwork begins. | |
| Scope follow-up request volume after delivery; repeat questions signal a filter or attachment gap, not an auditor preference. |
SPONSORED
QUESTIONS THIS ANSWERS
Does Sage Intacct support attaching documents directly to transactions?
The Audit Friendly review of Sage Intacct notes document storage at the transaction level as part of the platform's audit trail capability. Attachments stored there are retrievable when assembling an evidence package.
Can Sage Intacct export audit data without a manual download?
The Intacct REST API reached general availability in 2025 Release 1 and is now where all new objects and features ship. That API can be used to push transaction and document data programmatically to an external audit workspace.
Does multi-entity setup affect how audit evidence is pulled?
Yes. Sage Intacct is built for multi-entity consolidation, with intercompany eliminations handled automatically. Audit reports need to be scoped to the correct legal entity or consolidation level before they are delivered to auditors.
SOURCES
Where this comes from
Agent readiness, pricing and go-live watchouts.
GO DEEPER
Go deeper
An original workflow written for practitioners. Replicate it in a sandbox first; nothing here replaces your review.
The modern accounting tech stack: tools, automations and workflows shaping the next generation of finance operations.
Modern Accounting · Audit Friendly Data · Accounting & Finance Jobs
Audit Friendly · accountingstack.ai