Control loop
Image → recognize → decide → execute → confirm. The device transports/holds paper; Mobile-ID recognizes and decides; Trusted Records reconciles. Early images, deadlines, ACKs and buffers are requirements pending vendor validation.
From Paper to Trusted Digital Records
From scattered records.To trusted information.
Digitize · Manage · Discover · Preserve · Trust
Trusted Records connects paper and digital records through custody, quality controls and processing evidence — for government, financial institutions and enterprises.
From intake to governed records. Agree delivery scope and deployment criteria per project.
Records lifecycle
- 01Intake / BoxID
- 02Prepare / SheetID
- 03Image → recognize → decide → reconcile
- 04Declare / RecordID
- 05Govern and preserve
- 01Source / package
- 02Ingest / validation
- 03Register / declare
- 04Authorized search
- 05Preserve / disposition
Identifiers · Access · Quality · Evidence
Six steps of paper–digital operation
- 01Load dossiers
- 02Flow R captures images
- 03Mobile-ID recognizes
- 04Send decision
- 05Flow R executes
- 06Reconcile paper–digital
Governance loop
QC → acceptance → registration → access → discovery → preservation → delivery/disposition. Born-digital records use package validation and bypass Flow R. Uncertain AI results require configured holding/buffering/stopping rather than assuming a reviewer can respond during an unverified transport window.
Sheet ↔ image ↔ dossier ↔ decision ↔ location ↔ reconciliation. Capture order is not authoritative order; reconstruction requires mappings and evidence.
Born-digital records
Controlled admission
Package/manifest → validation/quarantine → reviewed declaration. Preserve source hashes, metadata and versions; bypass Flow R.
Govern before access
Authority → access → retention/holds → profile/preservation → handover. Decisions and evidence remain record-specific.
TURAPING Flow R — selected device
Capture and organize paper dossiers
The manufacturer describes Flow R as a scanning, holding, return, filing and packaging system. Published capabilities do not establish acceptance of Mobile-ID sheet-level control requirements.
Manufacturer source ↗Confirm specifications, firmware, supported paper, timing and maintenance in the technical agreement; vendor pricing or benchmarks are not service prices or SLAs.
Read the device contractFour portals, four authorities
Digitization Operations Portal
Coordinate paper records from intake to handover: preserve order, assess quality and resolve discrepancies at each station.
Explore portal experience
Records Governance & Preservation Portal
Register, access and preserve records under policy: identify authoritative representations, authorized users and permitted lifecycle disposition.
Explore portal experience
Platform Administrator Portal
Govern organizations, permissions, configurations and integrations while preserving project responsibility boundaries and privileged-action controls.
Explore portal experience
Customer Records Owner Portal
Track service delivery, inspect results, request corrections and accept portions; receive records with metadata and handover evidence.
Explore portal experienceADM/GOV use inspected final sources where available; DIG/CUS retain references because finals were not received.
Explore interfaces by taskContent, usability and evidence
Govern
Record/version, authority, retention and holds
Store content
Source bytes, replicas, locations and operator permissions
Preserve usability
Formats, representation information, migration/lineage
Preserve evidence
Contract-specific validation, profiles, receipts, renewal and verification
Backup / DR
Restore operations without replacing preservation layers
LTANS — long-term evidence preservation
Connect records lineage to Mobile-ID’s published LTANS capability; agree the Records configuration in a contract and profile.
Read detailsPreservation Profile Center
Choose preservation configurations by record class, designated community and required evidence. Illustrative profiles are not approved service offerings.
Read detailsPreservation standards and evidence
Standards → controls → workflows → contracts → evidence. Reference design mappings rather than Trusted Records certification.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsOne authentication entry, scoped connections
GoPaperless SSO
Shared identity for four portals; business authority remains organization- and project-scoped.
Read detailsRAR SSO
External identity route for authorized journeys; bind the result to subject, application and session.
Read detailsRAR ShareInfo
Permitted information sharing for a stated purpose; it does not confer unrestricted citizen-data access.
Read detailsRAR RSHUB
RAR connectivity requires an official contract before establishing Trusted Records functions.
Read detailsPayment and invoicing are distinct journeys
Acceptance → billable usage → payment request → confirmation → reconciliation → invoice. NAPAS QR/Trusted Billing are contractual; the offline package contains no payable QR.
Service models and billing principles
Reconcile accepted quantities with contractual rules before billing instead of charging all processing attempts.
Read detailsNAPAS QR and Trusted Billing
Integration design separates payment confirmation, reconciliation and invoice issuance.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsEvidence for assessment, beyond claims
Integrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsSample package export and verification
Check synthetic-package hashes before delivery; distinguish byte integrity from authenticity, signatures and legal status.
Read detailsCertificates and publication sources
Publish certificates only for their documented subjects, scopes and validity.
Read detailsProposed service policies
Policy content for project discussion; it is not confirmed as issued policy.
Read detailsDeploy around your records and criteria
Start with records and responsibilities
Sector solutions bind access, retention, integration and verifiable pilot criteria.
Read detailsAssessment and pilot
Use representative records to verify process, quality and integration before scaling.
Read detailsImplementation, acceptance and handover
Bind implementation milestones to deliverables, approvers and inspected evidence.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment