User manual · LEDGER

LEDGER — Tax & Finance.

The books, and the tax context around them. LEDGER exposes comparatively strong wallet and ledger reads plus tax surfaces whose rate-basis date must remain explicit.

What LEDGER owns

  • Designed VAT OSS / GST workflows for explicitly supported jurisdictions; the reviewed tax rates are static and do not guarantee tax correctness
  • Tax-snapshot fields such as locations, product type, basis, rate and the stated rate-basis date where captured
  • Available exports for configured finance, reconciliation or audit purposes; filing suitability requires review
  • A jurisdiction tax matrix as operational context, not legal or tax advice
  • ledger.books read surfaces for wallets, postings, reconciliation and safeguarding; integrity properties must be verified for the scoped data

The tax snapshot

Where the workflow records a tax snapshot, retain its locations, classification, basis, rate and rate-basis date and link any refund where supported. The reviewed rates are static; verify jurisdiction, effective date and export completeness before using a snapshot for a filing or audit.

Know your rate basis

The reviewed tax context requires an explicit rate-basis date. Check that each relevant snapshot and report carries it; if it is absent, do not infer the applicable table or present the output as a tax conclusion.

Filing exports

Choose scope

Client Portal → Tax → Exports (or Console for operators): select jurisdiction, period and report type — VAT OSS, GST, reconciliation or audit sample.

Generate

Generate the available export from the selected records and inspect row counts, rate basis, manifest and hashes where the implementation provides them.

Hand over

Have finance or tax specialists validate the scope before filing. Regeneration and byte-level equivalence must be tested; they are not assumed.

The books

The reviewed UI provides wallet, posting, reconciliation and safeguarding reads. Append-only or hash-chain properties, PSP settlement coverage and case creation must be verified against the producing services and selected data; a read surface alone does not prove ledger completeness or immutability.

Want the complete manual as a PDF? Leave us your email and we'll send it over.

Request the manual