Financial close implementation: configuring task management, consolidation, and certification

What is financial close management?

Financial close management is the disciplined process of completing all accounting activities required to produce accurate financial statements at the end of a reporting period. Whether it is month-end, quarter-end, or year-end, the close follows a repeatable sequence: import transactions, reconcile accounts, post journal entries, match intercompany balances, consolidate entities, certify results, and lock the period.

In practice, most organizations manage this sequence through a combination of spreadsheets, emails, and institutional memory. Controllers maintain checklists. Accountants track their own tasks. Status updates happen in Slack threads and stand-up meetings. The result is a close process that technically works but lacks visibility, accountability, and repeatability.

A task-based close management system replaces that ad hoc coordination with structured workflows. Every activity becomes a tracked task with an owner, a deadline, dependencies, and a status. The controller sees the entire close on a single dashboard instead of chasing updates across teams.

The building blocks

Arvexi's close management module is built around four core concepts:

• Tasks - the atomic unit of close work. Ten task types cover the full spectrum: reconciliation, journal entry, intercompany matching, flux analysis, certification, review, approval, data import, report generation, and custom. Each task moves through an eight-status workflow: NOT_STARTED, IN_PROGRESS, PENDING_REVIEW, IN_REVIEW, CHANGES_REQUESTED, APPROVED, COMPLETED, and SKIPPED.
• Templates - reusable task definitions that deploy automatically each period. Define the task once - owner, day offset, dependencies, frequency - and it appears in every applicable close cycle.
• Dependencies - relationships between tasks that enforce sequencing. A journal entry task cannot start until the reconciliation it depends on is complete. Separation of duties rules prevent the same person from preparing and approving the same work.
• Periods - the time containers that hold each close cycle. A period moves through OPEN, IN_CLOSE, LOCKED, and ARCHIVED statuses. Once locked, no further changes can be made without explicit reopening.

The close workflow

Every close follows the same high-level sequence, regardless of whether it is a monthly soft close or an annual hard close with external audit:

1. Import - pull trial balances, subledger data, and transaction feeds from ERPs and source systems
2. Reconcile - match account balances to supporting documentation. Flag variances that exceed materiality thresholds.
3. Journal posting - record accruals, adjustments, reclassifications, and eliminations. Every journal entry links to the task and the supporting reconciliation.
4. Intercompany matching - match intercompany receivables against payables across entities. Identify and resolve mismatches before consolidation.
5. Consolidation - roll up entity-level trial balances into a consolidated view. Apply currency translation, ownership adjustments, and elimination entries.
6. Certification - entity owners formally attest that their close is complete and financials are accurate. Reviewer chains validate the attestation.
7. Lock - freeze the period. No further journal entries or adjustments can be posted. The close is final.

Gantt chart visualization

Arvexi renders the entire close as a Gantt chart: every task plotted against the close window with dependencies shown as connecting lines. The Gantt view answers the question every controller asks during close week: "What is blocking us right now?" Tasks on the critical path are highlighted. Overdue tasks surface immediately. The controller sees not just what is late, but what downstream tasks will be affected by the delay.

Predictive bottleneck analysis

Beyond showing current status, Arvexi analyzes historical completion patterns to predict which tasks are at risk of missing their deadlines. If the AP reconciliation has taken an average of 2.3 days in the last six closes and it has not started by day 2 of the current close window, the system flags it as at risk - before it becomes a problem. This predictive layer turns the close dashboard from a rearview mirror into a windshield.

Phase 1: Define your close calendar

The close calendar is the foundation. Before creating any tasks or templates, you need to define when periods open, when the close window begins, and when it must end.

Period management

Each period in Arvexi moves through four statuses:

• OPEN - the period is active for normal transaction processing. Subledger data flows in. Journal entries can be posted. No close tasks are deployed yet.
• IN_CLOSE - the close window has begun. Task templates deploy and populate with computed due dates. The Gantt chart becomes active. Status tracking begins.
• LOCKED - the close is complete. All tasks are finished. All certifications are signed. No further journal entries or adjustments can be posted to this period.
• ARCHIVED - the period has been archived for long-term retention. Data is read-only and available for audit and historical reference.

Close window configuration

The close window defines the working days available for close activities. For a typical month-end close:

• Close window start - often the last business day of the month or the first business day of the following month
• Close window end - the target completion date, typically business day 5 to 10 of the following month depending on organizational maturity

All task due dates are computed as offsets from these dates. A task with a day offset of +2 from the close window start is due on business day 2 of the close. This relative dating means templates work across any period without manual date adjustment.

Business day calendar

Not every calendar day is a working day. Arvexi supports custom business day calendars that account for weekends, public holidays, and company-specific non-working days. When a task due date falls on a non-business day, the system automatically adjusts to the next available business day. Multi-jurisdiction organizations can configure separate calendars for different entities.

Phase 2: Build task templates

Task templates are the core of a repeatable close. Each template defines a close activity that will be deployed automatically every applicable period. The goal is to encode your entire close checklist - every reconciliation, every journal entry, every review step - as a template so that nothing is forgotten and nothing depends on one person's memory.

Template anatomy

Each task template includes:

• Name and description - clear, specific identification. "Reconcile cash - operating account (4521)" is better than "Cash recon."
• Task type - reconciliation, journal entry, intercompany matching, flux analysis, certification, review, approval, data import, report generation, or custom
• Owner - the person or role responsible for completing the task
• Day offset - when the task is due, expressed as business days from the close window start or end. A day offset of +1 from start means the task is due on the first business day of the close.
• Priority - critical, high, medium, or low. Priority affects sort order on the dashboard and determines which tasks surface in bottleneck alerts.
• Entity assignment - which legal entity or entities the task applies to. A single template can deploy across all entities or target specific ones.

Dependencies

Dependencies enforce the natural sequencing of close activities. Arvexi supports two dependency types:

• FINISH_TO_START (F2S) - the most common type. The successor task cannot begin until the predecessor task is complete. Example: the revenue journal entry cannot start until the revenue reconciliation is finished.
• FINISH_TO_FINISH (F2F) - the successor task cannot complete until the predecessor task is complete. Example: the controller review cannot be marked complete until all underlying reconciliations are finished.

When a task's predecessors are not yet complete, the task appears as "blocked" on the dashboard. The Gantt chart shows the dependency chain visually, making it immediately clear which upstream tasks are holding up downstream work.

Parent-child hierarchy

Complex close activities can be broken into parent and child tasks. The parent task represents the overall activity (for example, "Complete all AP reconciliations"), while child tasks represent individual sub-activities (reconcile AP aging, reconcile AP clearing, reconcile AP accrual). When all child tasks reach COMPLETED status, the parent auto-completes. This hierarchy keeps the high-level dashboard clean while preserving granular tracking underneath.

Frequency settings

Not every task runs every period. Arvexi supports seven frequency options:

• Monthly - deploys every close period
• Quarterly - deploys only during quarter-end closes (Q1, Q2, Q3, Q4)
• Semi-annual - deploys twice per year
• Annual - deploys only during the year-end close
• 4-4-5 - follows the 4-4-5 fiscal calendar pattern common in retail and manufacturing
• Custom - user-defined schedule for non-standard reporting cycles
• One-time - deploys once and does not repeat. Useful for transition tasks, audit requests, or special projects.

A quarterly tax provision task only appears in quarter-end closes. An annual goodwill impairment test only appears in the year-end close. Monthly reconciliations deploy every period. The frequency system ensures each close contains exactly the right tasks - no more, no less.

Phase 3: Configure consolidation

For organizations with multiple legal entities, consolidation is the most technically demanding part of the close. Consolidation takes individual entity trial balances and produces a single set of consolidated financial statements, accounting for ownership structures, intercompany transactions, and currency differences.

Entity hierarchy

The first step is defining your legal entity structure. Arvexi models entities in a tree hierarchy: the ultimate parent at the top, with subsidiaries nested below. Each parent-child relationship includes an ownership percentage that determines the consolidation method:

• Full consolidation (typically >50% ownership) - 100% of the subsidiary's balances are consolidated, with a non-controlling interest recorded for the minority share
• Equity method (typically 20-50% ownership) - the investor records its share of the investee's net income as a single line item
• Cost method (typically <20% ownership) - the investment is carried at cost with dividends recognized as income

The hierarchy can be as simple as a single parent with three subsidiaries or as complex as a multi-tier holding structure spanning dozens of jurisdictions. Arvexi handles both.

Currency translation rules

When subsidiaries report in different functional currencies, their balances must be translated to the parent's reporting currency before consolidation. Arvexi applies the standard translation methodology:

• Balance sheet accounts - translated at the ending (closing) rate for the period
• Profit and loss accounts - translated at the average rate for the period
• Equity accounts - translated at historical rates

The difference between translating net assets at the ending rate and translating income at the average rate creates a currency translation adjustment (CTA). Arvexi calculates the CTA automatically and posts it to accumulated other comprehensive income (AOCI) in equity. When the ending rate is unavailable for a given currency pair, the system falls back to the most recent historical rate and flags the substitution for review.

Intercompany elimination rules

Intercompany transactions - revenue and expense between related entities, intercompany receivables and payables, intercompany dividends - must be eliminated during consolidation. Arvexi supports rule-based elimination:

• Automatic matching - intercompany receivables and payables are matched by counterparty entity and currency. Matched pairs eliminate automatically.
• Threshold-based matching - small differences (within a configurable tolerance) eliminate automatically with a rounding adjustment
• Manual resolution - mismatches above the tolerance threshold surface as exceptions requiring manual investigation and resolution before consolidation can proceed

Elimination entries are generated automatically during the consolidation run. Each elimination links back to the source intercompany transactions, creating a complete audit trail from consolidated statements to entity-level detail.

Phase 4: Set up entity certification

Certification is the formal attestation that an entity's close is complete and its financials are accurate. It replaces the informal "we're done" email with a structured, auditable sign-off process.

Multi-level review chain

Each entity can be configured with a review chain of one or more levels. A typical structure:

1. Preparer - the accountant or analyst responsible for completing the entity's close tasks
2. Entity owner - the accounting manager who reviews task completion, validates key reconciliations, and submits the certification
3. Reviewer - the controller or senior manager who reviews and approves the certification
4. Final approver - for critical entities, an additional approval level (VP of Finance, CFO) before the period can be locked

The number of review levels is configurable per entity. A small domestic subsidiary might need only one reviewer. A large international entity generating material revenue might require three levels of sign-off.

Certification checklist

Before submitting certification, the entity owner must confirm a set of checklist items. These are configurable per entity type and might include:

• All reconciliations are complete and reviewed
• All journal entries are posted and approved
• Intercompany balances are matched and confirmed
• Flux analysis is complete and variances are explained
• No open items remain that could materially affect the financial statements

The checklist creates a consistent standard for what "close complete" means across the organization. It prevents the situation where one entity certifies after completing reconciliations but before posting adjusting entries, while another entity waits until every last task is finished.

Separation of duties

Arvexi enforces separation of duties (SOD) at the certification level. The person who prepared the underlying work cannot be the same person who certifies it. The person who submits the certification cannot approve it. These constraints are enforced by the system, not by policy - if a user attempts to approve their own certification, the system blocks the action and explains why.

Period lock enforcement

Once all entities in a period are certified and approved, the period transitions to LOCKED status. In a locked period:

• No journal entries can be posted
• No reconciliations can be modified
• No task statuses can change
• No data imports can overwrite existing balances

Reopening a locked period requires explicit authorization (typically controller-level or above) and creates an audit log entry documenting who reopened the period, when, and why. This prevents the common audit finding of post-close adjustments made without proper oversight.

Phase 5: Deploy your first period

With your calendar, templates, consolidation rules, and certification workflow configured, you are ready to run your first close cycle on Arvexi.

Deploy templates

When a period transitions from OPEN to IN_CLOSE, Arvexi deploys all applicable task templates. The deployment process:

1. Evaluates each template's frequency setting against the period type (monthly, quarterly, annual)
2. Creates a task instance for each template that matches the period
3. Computes each task's due date by applying the day offset to the close window start or end date, adjusted for the business day calendar
4. Wires all dependency relationships between the deployed tasks
5. Marks tasks whose predecessors are incomplete as "blocked"
6. Sends notifications to task owners with their assigned tasks and due dates

Running the close

Once tasks are deployed, the close is in motion. Task owners see their assigned work on the dashboard. They complete tasks, attach supporting documentation, and move tasks through the status workflow. As predecessor tasks complete, blocked successor tasks automatically unblock and their owners are notified.

The controller monitors progress through the Gantt chart and the close readiness score. The readiness score is a weighted composite:

Readiness = (50% x task completion) + (30% x certifications) + (20% x journal entries posted)

A readiness score of 100% means all tasks are complete, all entities are certified, and all journal entries are posted. The controller uses this metric to communicate close progress to leadership and to identify where remaining effort is concentrated.

First close expectations

Your first close on Arvexi will not be your fastest. The purpose of the first cycle is to validate that templates, dependencies, and workflows match your actual close process. Expect to make adjustments:

• Some tasks will need their day offsets adjusted - a reconciliation that takes longer than expected, a journal entry that can start earlier than planned
• Missing dependencies will surface - a task that should have waited for another but was not configured to do so
• New tasks will emerge - activities that were handled informally and never made it into the template library
• Some tasks will be unnecessary - activities that were historically done but add no value in a structured close

Plan to hold a retrospective after your first close. Document what worked, what did not, and update your templates before the next period. Most organizations reach a stable, optimized close process after three to four cycles.

Optimizing the close

Getting the close running on a structured platform is step one. Optimizing it - compressing the timeline, reducing manual work, and improving accuracy - is the ongoing work that compounds over time.

Predictive bottleneck analysis

After three or more close cycles, Arvexi has enough historical data to predict bottlenecks before they occur. The system analyzes each task's completion time across prior periods and compares it to the current cycle's progress. If a task that historically takes 1.5 days has not started by day 3 of a 5-day close window, it is flagged as at risk.

Bottleneck analysis also identifies structural issues in your close design. If the same task is consistently the last to complete and has four downstream dependencies, the system recommends breaking it into parallel sub-tasks or moving its day offset earlier in the window. These recommendations are based on your actual data, not generic best practices.

Close readiness score trends

Track your close readiness score over time. The trajectory tells you whether your close is improving or degrading. A healthy pattern shows the readiness score reaching 80% earlier in each successive close window. If the score plateaus or regresses, dig into which component - task completion, certifications, or journal entries - is the drag.

Arvexi Cortex integration for close tasks

Arvexi's Cortex connects close task management to the broader accounting platform. When data changes occur that affect the close - a late-arriving invoice, a corrected trial balance, an updated intercompany allocation - Cortex events trigger automatic re-scoring of affected tasks and their dependencies.

For example, if a subledger feed updates after a reconciliation task has been marked complete, Cortex flags the reconciliation for re-review. If an intercompany balance changes after IC matching is done, Cortex re-evaluates the elimination entries. This event-driven architecture ensures that the close status always reflects reality, not a snapshot from when someone last checked.

Continuous improvement metrics

The close management module tracks metrics that drive improvement over time:

• Days to close - elapsed business days from close window start to period lock. The benchmark goal is to compress this by one day per quarter.
• Task on-time rate - percentage of tasks completed by their due date. Target 90%+ for a mature close.
• Certification cycle time - hours from certification submission to final approval. Long cycle times indicate reviewer bottlenecks.
• Reopened periods - number of locked periods that had to be reopened for post-close adjustments. Target zero.
• Late journal entries - entries posted after the close window was supposed to end. These indicate upstream process failures that should be addressed at the source.

Review these metrics in each post-close retrospective. Small improvements compound. An organization that reduces its close by one day per quarter saves 12 business days over three years - and the team time that comes with it.

See how Arvexi's close management capabilities compare to standalone close tools, or book a demo to walk through configuration with your actual entity structure.