Choose a report
Understand close readiness
Despite the route name,POST /api/v1/reports/close-the-books computes readiness from supplied
lines and inventory. Its response identifies zero-cost and zero-valuation entries. Do not
interpret that response as a command that closes or locks an accounting period.
This illustrative request body follows the checked-in schema:
Build a reproducible reporting job
Record the source system, extraction boundary, timezone, currency, included statuses, and input record count. Interpret date boundaries according to the specific endpoint rather than assuming all reports use inclusive dates or the same timezone. Keep decimal monetary values as decimal strings or exact decimal types. Compare a small fixture with an independently calculated result before processing production records.Verify completion
An HTTP success means the request completed according to that endpoint. Inspect the report body and reconcile it with the input set. Separately verify delivery to a destination system; posting an export to another service is a second operation with its own failure handling. If a scheduled run fails, retain its input identity and inspect any prior output before retrying. See error handling and the integration test plan for recovery checks.Next steps
- Period close — accounting workflow and independent checks.
- API directory — service hosts and credentials.
- Support checklist — report a mismatch with redacted inputs.