From read-only to a live close, one stage at a time.
Written in the order a controller asks about the month-end close: what Solden takes on, what it can touch, when it can write, what you receive, who decides, what controls apply, and what happens when it is wrong.
The sixteen workstreams of the month-end close. Solden does the work. The judgement stays with you.
The whole checklist, with the one decision that stays yours marked on each.
01 Reconciliations
Bank reconciliations
Matched by amount, date and reference
You decide Timing or breakIntercompany
Reciprocal balances matched per pair
You decide Which side is rightBalance sheet
Every in-scope account proved
You decide Stale itemsPayments and processors
Payouts, fees and refunds tied to the ledger
You decide Unmatched payouts02 Subledgers
Accounts receivable
Aged, cash applied, provision computed
You decide Provisions, write-offsAccounts payable
Aged, accrued, duplicates flagged
You decide Estimates without a POFixed assets
Depreciation run, register tied to the GL
You decide Capitalise or expensePayroll
Payroll run tied to the GL by cost centre
You decide One-off payments03 Journals and schedules
Accruals and prepaids
Schedules run, each tied to its source
You decide New accrualsFX revaluation
Revalued at period end, movement explained
You decide Rate disputesTax provisions
VAT, sales tax and income tax per policy
You decide Tax positions and filingsRevenue review
Tied to billings, contracts and delivery
You decide Recognition timing04 Reporting and attestation
Flux and variance
Every line against prior period and budget
You decide CommentaryEliminations
Generated from reconciled balances
You decide Disputed itemsFinancial statements
Assembled, and verified to articulate
You decide DisclosuresAttest and lock
Completeness verified, pack assembled
You decide The attestation itselfFive stages. Four of them write nothing.
Your past closes are the benchmark. Solden reproduces them before it works on a live period.
- Writes: none
Connect
Read-only, least-privilege, every scope shown at grant time. In your ERP, a dedicated integration role with only the permissions you approve.
- Writes: none
Map the work
Your checklist, thresholds, templates and approvers, encoded once and versioned with actor and time.
- Writes: none
Replay history
A close you have already done, run in isolation on Solden's operating ledger and set beside what you reported.
- Writes: none
Shadow mode
Solden closes the current period alongside your team, still read-only, and records how much of your time its close needs.
- Writes: journals
Live
Only after you sign the write activation. Every post passes through review first and is read back from the ERP.
One past close, run again.
Agree the entity, the period, the scope and the deliverables. Solden runs that close on its operating ledger, never your books, and sets its result beside what you reported. You judge it: the test passes when coverage, accuracy and exceptions match what you reported, or every difference is explained with evidence.
A messy live period.
An ERP outage mid-close, or a chart of accounts changed on day two. Shadow mode tests Solden against those on a live period, and a written fallback procedure covers a close that stops halfway.
A close pack, not a dashboard.
You receive the finished close and everything needed to trust it. Attestation is refused while evidence is missing or an exception is open. Once locked, the pack cannot be changed, and it exports as one bundle for your auditors.
Close pack · April 2026 · Locked
Work product
The financial statements, articulated and tied to every workstream.
Completeness checklist
What done meant for this period, each item checked.
Evidence index
Every figure mapped to its source, navigable from any number.
Exception log
Every exception with proposal, resolution, decider and time.
Attestation trail
Who reviewed and decided what, with the policy version each approval was judged under.
Source log
For every record: the system it came from, what produced it, when, and which version.
What stays yours, by design.
Solden goes ahead without you only on routine, reversible work within your policy and below your threshold, and its accountants still review it. Everything else arrives as a judgement call for a named person on your approval matrix: what happened, what Solden proposes, why it needs you, and the evidence.
Posting a material journal
Solden bringsThe draft entry, evidence on every line, the policy version it was judged under.
Controller decidesRevenue recognition
Solden bringsThe contract, the billing and the question.
Controller decidesWrite-offs and provisions
Solden bringsThe aged balance and a proposed treatment.
CFO decidesAccounting policy changes
Solden bringsThe encoded policy and every version of it.
CFO decidesMoney, payroll, filings
Solden bringsThe reconciled figures and their support. Solden never moves money, approves payroll or files a return.
CFO decidesAttesting and locking
Solden bringsThe complete pack, with nothing missing.
Controller decidesThe controls register your security review will ask for.
Every control is designed and written down before any connection is made. The last one is yours to keep.
Read-only until you activate writes
A separate write activation you sign, logged with actor and time.
Review gates every action
Nothing posts to your ERP or locks without passing through it.
Nothing overwritten
Policies, mappings, journals and source records are versioned. Nothing is edited in place.
Dirty data quarantined
Source data that fails mapping becomes an exception, never silently coerced.
Degrades openly
Throttled APIs, partial data and failed extractions are visible, never silent.
Credentials in a vault
Never in application databases. Encryption in transit and at rest.
Each customer's data kept apart
One customer's data can never be reached from another customer's account.
SSO and MFA
Google Workspace or SAML. MFA enforced for every role.
No training on your data
Your ledger, documents and decisions never train a model, ours or a vendor's.
Who at Solden can see it
The reviewers named to your account. Every view is logged and visible to you.
Security review
We complete your security questionnaire and share the controls register before you connect anything.
Statutory responsibility
Solden is not an auditor, a bank or a statutory signatory. That stays with you.
YoursEvery task ends checked and complete, or blocked with a name and a date.
Nothing is left half-done. A blocker says what is wrong, who must act and by when.
A break
Unmatched items, missing support, threshold breaches and duplicates surface as exceptions with a proposal. Never a silent failure.
A challenge
Your controller can challenge any step in any evidence trail. It routes back as an exception with their note attached.
An adjustment
Adjustments create new versions. The original, the change, the reason and the actor are all preserved.
A failed run
The close resumes from the last completed workstream, and the pack records what was run again and why.
An input outstanding on your side
The close cannot be verified while your inputs are outstanding. The pack records whose input each delay waited on.
An error caused by Solden
Re-performed and re-reviewed, a corrected pack version issued, and the cause recorded in the exception log.
Start with your close.
If your close has outgrown your finance team, tell us how it runs today. It starts with a replay.
We are starting with UK companies.
- One monthly price for the close, set by entities and transaction volume. Not seats or hours. Quoted after the replay.
- Read-only access for the replay. No migration, no rollout to your team.
- A reply within two business days, then a short call to scope your replay.
We reply within two business days.
Next is a short call to pick the period and scope for your replay: one close you have already reported, run again and set beside your own figures.
Meanwhile, read why Solden exists, and the order in which it takes on the finance department.