Solden
Request an invite
Menu
How it works

How responsibility transfers, 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, who decides, what controls apply, and what happens when it is wrong.

01 What Solden takes on

Sixteen workstreams of the month-end close. Solden does the work. You decide where judgement stays human.

Every workstream your controller signs today, with the one decision that stays yours marked on each.

01 Reconciliations

Bank reconciliations

Matched by amount, date and reference

You decide Timing or break

Intercompany

Reciprocal balances matched per pair

You decide Which side is right

Balance sheet

Every in-scope account proved

You decide Stale items

Payments and processors

Payouts, fees and refunds tied to the ledger

You decide Unmatched payouts

02 Subledgers

Accounts receivable

Aged, cash applied, provision computed

You decide Provisions, write-offs

Accounts payable

Aged, accrued, duplicates flagged

You decide Estimates without a PO

Fixed assets

Depreciation run, register tied to GL

You decide Capitalise or expense

Payroll

Payroll run tied to GL by cost centre

You decide One-off payments

03 Journals and schedules

Accruals and prepaids

Schedules run, each tied to its source

You decide New accruals

FX revaluation

Revalued at period end, movement explained

You decide Rate disputes

Tax provisions

VAT, sales tax and income tax per policy

You decide Positions, filing sign-off

Revenue review

Tied to billings, contracts and delivery

You decide Recognition timing

04 Reporting and attestation

Flux and variance

Every line against prior period and budget

You decide Commentary

Eliminations

Generated from reconciled balances

You decide Disputed items

Financial statements

Assembled, and verified to articulate

You decide Disclosures

Attest and lock

Completeness verified, pack assembled

You decide The attestation itself
02 What you can touch, and when you can write

Five stages. Four of them write nothing.

Your prior closes are ground truth. Every capability earns its place by reproducing them before it touches the present.

  1. Writes: none

    Connect

    Read-only, least-privilege, every scope shown at grant time. On NetSuite, an integration role with permissions you approve.

  2. Writes: none

    Map the work

    Your checklist, thresholds, templates and approvers, encoded once and versioned with actor and time.

  3. Writes: none

    Replay history

    A close you have already done, run in isolation on Solden's operating ledger and set beside what you reported.

  4. Writes: none

    Shadow mode

    Solden closes the current period alongside your team, still read-only. Your review-time baseline is set.

  5. Writes: journals

    Live

    Only on your signed activation. Every post passes through review first and is read back from the ERP.

The buying test

Replay a close you have already done.

Agree the entity, the period, the scope and the deliverables. Solden runs that close on its operating ledger, never your books, and compares its result with what you reported. It passes when coverage, accuracy, exceptions and pack completeness match yours, or every difference is explained with evidence.

What replay does not prove

A messy live period.

An ERP outage mid-close, a chart of accounts changed on day two. Those are covered by shadow mode, by execution that degrades openly with clear status and resume, and by a documented fallback procedure for when execution stops mid-cycle.

03 What you receive

Solden delivers packs, not figures.

You do not receive a number, a report or 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 is immutable and 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 lineage, 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.

  • Lineage manifest

    Producer, timestamp, source system and version for every record.

Prepared bySolden
Reviewed bySolden reviewer
Attested byYour controller
04 Who decides

What stays yours, by design.

Solden acts alone only on routine, reversible, policy-governed work below a threshold. Everything else arrives as a case 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 decides

Revenue recognition

Solden bringsThe contract, the billing and the question.

Controller decides

Write-offs and provisions

Solden bringsThe aged balance and a proposed treatment.

CFO decides

Accounting-policy changes

Solden bringsThe encoded policy and every version of it.

CFO decides

Money, payroll, filings

Solden bringsNothing. Solden never moves money, approves payroll or files.

CFO decides

Attesting and locking

Solden bringsThe complete pack, with nothing missing.

Controller decides
05 Controls

The 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 activation you sign, logged with actor and time.

Review gates every action

Nothing posts, pays, files or locks without passing through it.

Nothing overwritten

Versioned policies, mappings, journals and lineage. A correction is a new version.

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.

Tenant isolation at the data layer

One customer's data is never queryable from another's context.

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 questionnaire and share the controls register, subprocessor list and DPA before any connection is made.

Yours

Statutory responsibility

Solden is not an auditor, a bank or a statutory signatory. That stays with you.

06 What happens when it is wrong

Finance has no partial credit. A blocker is a normal, owned state.

A job ends as a verified result or an exact, owned blocker with a date on it. There is no third ending.

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 degraded source

Throttled APIs and partial data show with a clear status and a resume path. A failed run resumes from the last completed workstream.

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.

Request an invite.

If your close has outgrown your finance team, we would like to talk. It starts with a replay of a close you have already done.

Request an invite The department, function by function