Technical assurance
Tested through connected business scenarios.
SynqLedger Core was evaluated through an internal validation programme using realistic fictional business data, covering migration, connected operations, period close, reporting and consolidation, as set out in the supporting records.
Validation
How it was tested
One fictional company, run end to end.
The scenarios used a fictional operating company with customers, suppliers, stock, production, fixed assets, employees and financial records, later joined by fictional group companies. Transactions were simulated on test data; no real customer data was used and no live money moved.
What was tested
Six stages, run in sequence.
Each stage answered a practical question before the next began.
- Stage 1
Migration to go-live
Can a legacy business move in without losing financial integrity?
- Exercised
- Historical financials, opening balances, open customer, supplier, stock, asset and employee positions, cutover.
- Outcome
- Migrated positions reconciled before go-live readiness was confirmed.
Record:MVT1-R13
- Stage 2
Native business operations
Can the migrated company then run day to day?
- Exercised
- Simulated sales, purchasing, stock, manufacturing, fixed assets, payroll and bank activity on fictional data.
- Outcome
- Customer, supplier, stock, work-in-progress and asset records agreed with their ledger control accounts.
Record:MVT2-FINAL-R2MVT2-HR-R1MVT2-MFG
- Stage 3
First native period close
Can finance close the first periods under control?
- Exercised
- January to March closed in sequence, with reconciliations and adjustments.
- Outcome
- Closed periods refused new postings; no balancing entries were used.
Record:MVT3-R2
- Stage 4
Comparative continuity
Can management compare across the legacy-to-native boundary?
- Exercised
- Prior-year history, the opening position and native periods, with drill-down.
- Outcome
- Migrated, opening and native figures stayed distinguishable and continuous.
Record:MVT4-R5
- Stage 5
Group and enterprise
Can separate companies be reported as a group?
- Exercised
- Five fictional companies, currency translation, intercompany and acquisition accounting.
- Outcome
- Group reports balanced without changing any company's own records.
Record:MVT5-R2
- Stage 6
Final integrated validation
Does the complete Core hold together as one product?
- Exercised
- A read-only review of accounting, subledgers, close, consolidation and access controls at the closing state.
- Outcome
- The final validation run passed its defined checks.
Record:MVT6-R6
What passed
Final release result.
The Core 1.0 release decision was based on this run.
- Validated baseline
- SynqLedger Core 1.0
- Run
- MVT6-R6
- Date
- Baseline recorded 18 August 2026 (run date not separately recorded)
- Result
- 85 of 85 checks passed, 0 failed
- Scope
- Accounting balance, subledger-to-ledger agreement, period close, group figures and access controls, read at the validated closing state
- Type
- Internal product validation
The result applies to the identified checks and baseline. Passing a defined set of checks does not mean the whole product is free of defects.
Core 1.0 is change-controlled: validated behaviour is changed only through a recorded correction and a repeat of the affected validation. Public claims mapped in our internal claims register are linked to the records that support them.
How findings were resolved
Failures were fixed, then retested.
The programme found genuine defects. The records show each run repeated under a new run number until its checks passed.
- 01
Find
A check fails and the run does not pass.
- 02
Investigate
The cause is traced from the recorded evidence.
- 03
Correct
The product is corrected, not the check.
- 04
Add a regression check
A check for the defect is added where recorded.
- 05
Retest
The programme is run again under a new run number.
Reconciliation
At the closing state, customer, supplier, stock, work-in-progress and asset records agreed with their ledger control accounts, and operated bank accounts reconciled. No balancing entries, manual balance edits or status overrides were used in the validation runs.
Financial history
Where a correction was needed, posted records were not edited. Migrated, opening and native figures stayed distinguishable, so each reported figure can be traced back to its source.
Coverage
Areas exercised in the programme.
Taken from the original programme records. Later work is not added here.
- Implementation and migrationLegacy history, openings and cutover
- Customers and revenueSales through to receivables
- Purchasing and payablesPurchase through to supplier balances
- InventoryStock movements and valuation
- ManufacturingProduction, work in progress and cost
- Fixed assetsCapitalisation, depreciation and register
- People and payrollEmployment, payroll and pay costs
- Cash and bankBank reconciliation and clearing accounts
- Payments (recorded)Supplier and payroll payments recorded and reconciled; no live money moved
- Finance and closeLedger, period close and statements
- Comparative reportingPrior-year, opening and native periods
- Group and multi-entityCurrency, intercompany and acquisition accounting
- Access controlsCompany boundaries and anonymous access checks
How a buyer can review it
Validation records.
Each programme has a written record. We can walk your team through the records that are appropriate to share; there are no public downloads.
| Record | What it shows |
|---|---|
| Scope | The company, periods and areas each programme covered. |
| Run and release reference | Run numbers (for example MVT6-R6) and the Core 1.0 baseline. |
| Date | Recorded where available; the Core 1.0 baseline is dated 18 August 2026. |
| Expected outcomes | The checks each run had to meet. |
| Findings | Defects found during a run and their causes. |
| Corrections and regression checks | What was changed and the checks added, where recorded. |
| Final result | Checks passed and failed for the final run. |
Limits of the evidence
Internal validation, not independent certification.
This is SynqLedger's own product-validation programme. It does not establish an independent certification, an independent audit opinion or regulatory approval. Topics not covered here are not evidenced on this page; that does not mean the related protections are absent.
Scope and current status
Historical validation and current availability.
Current product status does not mean inclusion in the historical Core release gate.
Historical release gate
SynqLedger Core 1.0
The validation described on this page covered SynqLedger Core 1.0 only: migration, connected operations, close, reporting and consolidation.
Current status
Payment Orchestration
Available in Sandbox
Live money movement is not enabled.
Current status
SynqLedger Intelligence
Available in preview
Read-only. It provides explanations and written proposed next steps; it does not approve actions, create transactions or change business records.
Want to see the evidence?
We can walk your finance, technology or assurance team through the validation records, scenarios and results behind SynqLedger Core 1.0.