Calculation Reports
A Calculation Report records the inputs, rules and engine version used to produce a result.
Why you would use one
Six months after a decision, "the system said 14 August" is hard to defend. A report shows what was asked, which calendar rules applied, what the engine skipped and why, and which version produced the answer. Anyone can re-run the same inputs and get the same result.
What a report records
- The calculation type, every input and every option used.
- The result.
- The calendar rules, if a Business Calendar was used: country, subdivision, timezone, working week, whether public holidays were included, and how many custom exclusions applied.
- A trace: business days counted, non-working weekdays skipped, public holidays skipped, custom exclusions skipped, calendar days elapsed.
- The holiday data provider and its version, the engine version, the report code and the time it was generated.
Formats
PDF for reading and filing, CSV for spreadsheets, JSON for systems. All three describe the same record. Batch jobs can also produce a summary report covering the whole job.
Integrity hash
Each report carries an integrity hash of its payload. The integrity hash helps detect whether the report payload has changed. It is not a digital signature or legal certification.
To verify a report, recompute the hash from the JSON payload and compare it with the value on the report. Matching means the payload is byte-for-byte what Calcadian produced.
Expiry
- Pro: reports are kept for 7 days, then removed.
- Business: reports are kept for 30 days, then removed.
Download and store anything you need to keep beyond that.