Ledgerline · Audit-ready books, on demand - Vertical Agent Spec
One-line definition
An agent that runs the period-end close checklist, routes reconciliation exceptions to named owners, and assembles audit-ready workpapers for Controllers at mid-market companies with active SOX or IRS compliance obligations.
The workflow it owns end-to-end
- Trigger: Controller or period-end calendar fires the close kickoff. Agent pulls the current trial balance and prior-period comparatives from the connected ERP.
- Reconciliation sweep: Agent maps each account to its sub-ledger source, calculates variance, and assigns every exception above the configured materiality threshold to a named account owner with a due date.
- Evidence intake: As owners upload support documents (bank statements, invoices, contracts), agent confirms the document type matches the account category and timestamps the workpaper entry.
- Sign-off routing: Agent compiles the close package and routes it sequentially to preparer, reviewer, and Controller for electronic signature via DocuSign.
- Archive: On final sign-off, agent deposits the package to the designated storage location and posts a close-complete summary to the team Slack or Teams channel.
What it knows that a generic LLM doesn't
- SOX Section 302 and 404 control documentation requirements: what constitutes sufficient evidence for a key control versus a non-key control, and what combination of gaps triggers a material weakness disclosure.
- GAAP reconciliation formats by account type: cash needs a bank confirmation, prepaid needs an amortization roll-forward, accrued liabilities need the specific memo structure that Big 4 reviewers expect in the workpaper binder.
- Materiality calculation under AS 2101, including the distinction between overall materiality, performance materiality, and the trivial threshold for individual misstatements at different company revenue sizes.
- IRS response formats for CP2000 notices, 4564 IDRs, and correspondence examination, including the exhibit sequencing IRS agents expect when a response package arrives.
- ERP-specific behaviors: NetSuite multi-book reconciliation variance, SAP posting period lock errors, Oracle Fusion subledger accounting entries that produce unexplained offsets when not configured correctly.
- The workpaper convention distinction between a preparer comment and a reviewer comment, which becomes a PCAOB inspection finding when the two are mixed in the same cell.
What it explicitly declines
- Tax positions. The agent can format an IRS response package, but it will not recommend a legal tax position or calculate tax liability. That requires a licensed CPA or tax attorney.
- Audit opinions. The agent organizes evidence; it does not conclude on whether controls are operating effectively or whether financials are fairly stated.
- GL posting. The agent can draft a journal entry with attached support, but it will not post to the ERP or approve entries without an explicit human sign-off step in the workflow.
- Outbound correspondence to auditors or tax authorities. The agent drafts; a credentialed human reviews and sends.
Tools and integrations required
- ERP: NetSuite SuiteAnalytics, SAP BAPIs, Oracle Fusion REST APIs, QuickBooks Online for smaller in-scope subsidiaries.
- Document storage: SharePoint Online, Google Drive, or Workiva for versioned workpaper archiving with rollback.
- E-signature: DocuSign or Adobe Acrobat Sign for preparer and reviewer sign-off on the close package.
- Messaging: Slack or Microsoft Teams for exception routing notifications and close-status updates.
- Calendar: Google Calendar or Outlook for period-end task scheduling and overdue-assignment tracking.
- Identity: SAML SSO via Okta or Azure AD, with role-based permissions mapped to the company's segregation-of-duties control matrix.
Trust escalation: when it pings a human
- Any exception above the materiality threshold that remains uncleared 48 hours before the close deadline. Agent pauses the package and notifies the Controller directly rather than routing around the gap.
- Any support document that does not match the expected type for its account category (an internal memo submitted where a third-party bank confirmation is required). Agent flags it and holds the workpaper line.
- Any inbound communication identified as IRS or external auditor correspondence. Agent extracts the response deadline, routes immediately to Controller and CFO, and does not draft a response until explicitly instructed.
- Any proposed journal entry crossing an unusual-transaction threshold: round numbers above a dollar limit, weekend postings, entries with no attached support document. Agent holds the close package and requests human review before routing for sign-off.
Pricing model
The agent charges per completed close cycle: $3,500 per quarter-end close for companies with up to 10 legal entities, and $6,500 for 11 to 30 entities. IRS response packages bill separately at $800 per IDR or CP-series notice. At $20,000 to $30,000 in annual spend, a company runs four quarter-end closes plus several IRS responses, which is a plausible budget for a Controller who currently bills two staff-weeks of labor per close period. The honest caveat: buyers at SOX-scoped companies will not approve any tool that touches audit evidence without a SOC 2 Type II report, and that certification requires a 12 to 18 month observation window. Until that report exists, this pricing schedule is theoretical.
Differentiation from a generic LLM wrapper
A Controller who pastes a reconciliation into Claude gets a plausible-looking document with no ERP connection, no materiality configuration, no role-based sign-off enforcement, and no audit trail that a Big 4 reviewer will accept as evidence. The value here is not the language model; it is the pre-built connectors to NetSuite and SAP, the workpaper templates formatted the way external auditors actually review them, the segregation-of-duties logic enforced in the approval chain, and the immutable log showing who approved what and when. That combination takes 12 to 18 months to build, certify, and validate with reference customers. The real competitive threat is not a generic wrapper; it is FloQast and Blackline, which already have those connectors, those templates, and those reference lists from hundreds of existing customers. This agent wins only in the mid-market segment where FloQast is overbuilt and overpriced, which is a narrow opening but a real one.