General ledger and close

Nucleus records balanced and auditable financial effects for its authoritative accounts. The institution’s approved chart, recognition, currency, date and reporting policies determine the concrete posting mappings.

Financial event and journal

Finance owns the accounting policy and reviewed chart. A domain operation produces the approved subledger and general-ledger effects atomically under its actual contract. Each currency balances independently. Historical corrections retain the original event and add a linked compensating entry.

The source includes /glaccounts, /journalentries and report operations. Generic journal endpoints require their own permissions, approval policy and posting scope. Their presence must not substitute for a controlled customer-account operation.

Manual adjustment

Use the institution’s approved adjustment workflow in a named local or sandbox environment. Bind reason, evidence, office, currency, value/business date and exact account roles to the proposed journal. Independent approval applies where the policy requires it. Retain the authoritative result, journal identity and audit record.

Check the exact request and error schemas in the reference. Amounts are decimal values and the total debit and credit must agree. The institution selects account codes and role mappings.

Reconcile and close

Reconcile internal controls, external positions, suspense and retained cash evidence before closing. Scheduled jobs need stable occurrence identity, rerun safety and owned failures. The current source snapshot includes governed close, cash proof and rehearsal routes. Inspect their exact scope and qualify actual behavior in the selected environment.

A failed or interrupted close retains the same run identity and evidence. Business-date advancement must respect the institution instance’s calendar, outstanding controls and approved close decision. Restore or rollback must preserve accepted financial effects.

Acceptance evidence

Record journals and control totals by currency, calculation/configuration versions, source operation identities, reconciliation results, unresolved items, approvals and the resulting business date. Test unbalanced requests, duplicate accrual, partial jobs, late events, interrupted close and recovery. Report generation and regulatory acceptance need their own evidence.